Jen Shanahan Senior Solution Consultant

For companies with large numbers of stores with screen layout variations, it's incredibly difficult to maintain and manage screen layouts.

STORE A has a requirement that differs form STORE B this requires different button grids and sometimes entirely different screen layouts. In the particular case we are working with there are over 150 stores, this leads to an incredible amount of effort to change screen layouts, test and push updates.

It would be incredibly beneficial if screen layouts could be mapped with a database table:

EXAMPLES

STORE 1 needs Top right button (button1) as Product 2

STORE 2 needs Top right button (button 1) as Product 7

If we could create a mapping like this example in a table configuration by store channel:

Store1: Button1 is mapped to Product 2

Store2: Button1 is mapped to Product 7

This would greatly improve flexibility and functionality of the configuration of screen layouts in large scale store scenarios, where different stores have different requirements for layout functions.

It would be very helpful to have a store specific custom field in the footer of the receipt that would be easily updated. Throughout the year messaging changes at the bottom of many store receipts. Store Operating Hours, Scheduled Events etc. that are placed in the footer of the Receipt.

It would be incredibly helpful to have a custom Field called Footer Text or something like that, this field could be filled into HQ and stored on the Retail Channel individual Store configuration. This text would be pulled into that custom field on the receipt designer. It's incredibly difficult to have to go into the receipt designer for each and every store. When a receipt change is needed across all stores, now that same change has to be implemented store by store, because a different receipt profile has to be assigned to allow this functionality.

We would like to have a feature that runs store commerce (SCA) download sessions as a service.

Problem 1: In scenarios where a named windows account is used for each user, when they leave SCA running and another user comes along they cannot launch SCA without a reboot since it's locked to run once per machine.

Problem 2: if SCA is not left on the login screen download sessions do not continue so when the first user logs in the AM, all channel distribution jobs that were run incrementally overnight have to catch up leading to hundreds of pending downloads. The larger the product database / discount / coupons etc. the more impactful this issue becomes.

Possible solution would be to have a named service account that runs on the client side that is always running that can login and pull down the pending download sessions to the local database so the offline database always remains synchronized.