This approach involves directly linking roles and associates to a designated Retail Cloud app config. This method will be deprecated in the future.
- Enable the Traditional Method for App Config Segmentation
Use these setting to enable the Traditional Method for Point of Sale App Config Segmentation. - Create an App Config using the Traditional Method for App Config Segment
Set up your app's visual identity in Point of Sale by configuring the logo, fonts, and other settings in the CMS. iOS supports a wide range of license-free fonts, allowing you to customize the app's appearance to match your brand. - Set an App Config Token using the Traditional Method for App Config Segment
Configure your POS application by setting a unique token to access specific configurations. - Set a Default App Config using the Traditional Method for App Config Segment
Designate one Retails Cloud app config as the default for live store use by enabling specific iOS modules. - Segment App Configs using the Traditional Method for App Config Segmentation
Assign app configurations to associates and roles through the Point of Sale CMS interface, enabling customized app experiences. - POS App Flow for the Traditional Method for App Config Segmentation
When launching the POS app, the merchant-level default app config is initially loaded. Users can override this with tokens before login, but associate or role-level configs in CMS take precedence post-login, ensuring personalized settings. This allows for flexible and tailored app configurations, enhancing user experience and operational efficiency. - Rules of Precedence for the Traditional Method for App Config Segmentation
When loading app configs on the POS app, the system prioritizes configurations assigned directly to associates, followed by role-specific configurations, and finally the app's default settings. This ensures that associates always use the most appropriate configuration, enhancing efficiency and accuracy in store operations.