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.