---
schema_version: "1"
id: d36a06a16076b06c03e97bdea4d3c8a82d0f6a2db59c5a27b387b60db743b4a1
title: Rules of Precedence for the Enhanced Method for App Config Segmentation
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_layouts_configs_segments_enhcd_rules.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_layouts_configs_segments_enhcd_rules.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 49f7827c905cefdb67f0e78af14ae8a80882cb35d11928500fec27fef4759566
description: When defining segmentation rules for app configs in Point of Sale, prioritize specificity and granularity to resolve conflicts. Clear precedence ensures that registers or associates are targeted accurately, enhancing app functionality and user experience.
products:
  - Commerce
release: "264"
---
# Rules of Precedence for the Enhanced Method for App Config Segmentation

When defining segmentation rules for app configs in Point of Sale, prioritize specificity and granularity to resolve conflicts. Clear precedence ensures that registers or associates are targeted accurately, enhancing app functionality and user experience.

## Example

To take an example, if there are four app configs–Manager mPOS, Associate mPOS, Manager Fixed, Associate Fixed–with segmentation rules as follows:

   
| App Config Name | Device Type Segmentation Rule | Personnel Segmentation Rule | Location Segmentation Rule |
| --- | --- | --- | --- |
| Fixed POS Manager | Device=iPad | Role=Manager | All |
| Fixes POS Associate | Device=iPad | Role=Associate | All |
| mPOS Manager | Device=iPhone | Role=Manager | All |
| mPOS Associate | Device=iPhone | Role=Associate | All |

Then, when a store user, Jane Smith, logs in on an iPad, and her role is Manager, her register would be served the Fixed POS Manager app config. Now, imagine that a fifth app config is added where the the Personnel criterion of its segmentation rule directly targets an associate with ID equal to “Jane Smith”. In this case, when Jane logs in, her register would receive the fifth app config, Jane Smith App Config.

   
| App Config Name | Device Type Segmentation Rule | Personnel Segmentation Rule | Location Segmentation Rule |
| --- | --- | --- | --- |
| Fixed POS Manager | Device=iPad | Role=Manager | All |
| Fixes POS Associate | Device=iPad | Role=Associate | All |
| mPOS Manager | Device=iPhone | Role=Manager | All |
| mPOS Associate | Device=iPhone | Role=Associate | All |
| Jane Smith App Config | Device=iPad | Associate=Jane Smith | All |

## App Launch (Before Login)

If a token is entered, the app config with the matching token is loaded. However, If no token is entered, the default app config for the merchant is loaded.

## Associate Login (After Login)

When an associate logs in, the app config that will be served is the one with the highest-ranking (meaning most specific) segmentation rule that targets that associate and/or their register. Refer to the following table for that rank ordering.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/images/icon_note.png)

Note A segmentation rule that targets a Device Type segment, an Associate segment, and a Store segment is the highest-ranking rule possible.

     
| App Config Order of Precedence | Device Type (iPad/iPhone) | Personnel—Role) | Personnel—Associate | Location—Group | Location—Store |
| --- | --- | --- | --- | --- | --- |
| 1 | ✓ |   | ✓ |   | ✓ |
| 2 | ✓ |   | ✓ | ✓ |   |
| 3 | ✓ | ✓ |   |   | ✓ |
| 4 | ✓ | ✓ |   | ✓ |   |
| 5 |   |   | ✓ |   | ✓ |
| 6 |   |   | ✓ | ✓ |   |
| 7 |   | ✓ |   |   | ✓ |
| 8 |   | ✓ |   | ✓ |   |
| 9 | ✓ |   | ✓ |   |   |
| 10 | ✓ | ✓ |   |   |   |
| 11 |   |   | ✓ |   |   |
| 12 |   | ✓ |   |   |   |
| 13 | ✓ |   |   |   | ✓ |
| 14 | ✓ |   |   | ✓ |   |
| 15 |   |   |   |   | ✓ |
| 16 |   |   |   | ✓ |   |
| 17 | ✓ |   |   |   |   |