---
schema_version: "1"
id: 6b9ec03336fc95937eb5c68f53f769b74de46a0f7a73ca16c8ef6b77616149d3
title: App Config Segmentation in the POS app
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_intro.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_layouts_configs_segments_intro.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 63cc06e50e8d51f7673ed57f5465a612b5a7c9b7d605caf44cf3b55fa117e53b
description: One fundamental capability of POS is how easily and deeply it can be customized. A core component of that configurability, is the App Configuration or, App Config, for short.
products:
  - Commerce
release: "264"
---
# App Config Segmentation in the POS app

One fundamental capability of POS is how easily and deeply it can be customized. A core component of that configurability, is the App Configuration or, App Config, for short.

An App Config is a comprehensive repository of instructions that determines the POS app's behavior and appearance. App Configs are created and managed in CMS, and then downloaded to the POS device on app launch, on login, and, depending on the use case, on other triggering events. In this article, you’ll learn all about what app configs are and how to best put them to work for your needs.

![The components of the app configuration segmentation in the POS app](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-commerce-retail-264-0-0-production-enus/17d647fb-8988-49fb-9add-c4f4cc79c9e4/retail/images/rt_cms_layouts_configs_segment_components.png)

A few notes, to help you form a conceptual model of the app config:

- Each App Config needs a name. You might have multiple app configs, each optimized for a different use case (e.g. inventory, clienteling, etc.), for the various roles of store associates, or for the device the app will run on.
- App configs have two main parts: First, (shown in yellow) the list of tabs that appear on app launch. Second, (shown in blue) the settings and layout definitions that together determine which features are activated, the user interface, navigation, and app aesthetics.

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

Tip For more information on tabs, refer to this article.

## Types of App Configs

Below are the different types of app configs that are available to create and customize on the POS app.

- Modern POS enables merchants to create an Omni-Channel shopping experience; encompasses mPOS, Cash Register, Clienteling, Endless Aisle, and BOPIS
- Clienteling equips store associates with comprehensive customer insights
- Endless Aisle provides in-store access to the brand's entire digital product catalog
- BOPIS / Store Fulfillment facilitates in-store pickup strategies
- mPOS allows store staff to quickly handle customer payments and contact information
- Inventory Management supports store operations, including receiving, cycle counting, transfers, and inventory adjustments

## Default Layouts

The following default layouts are created when a new app config is created. Layout names are prefixed with the app config name.

- Store Home Template
- Sign Up Template
- Category Bleed Images Two Column Template
- Two Blank Layouts
- PDP for Store Associate
- Menu Layout
- Search Layout
- Touch Menu Layout

## Segmentation

Each register can download and use only one app config at a time. However, a merchant can create multiple app configs and define rules for each to determine the scenarios for which they’ll be used. This enables tailoring an app config to the specific use case, or segment, it will serve.

To take an example, a merchant might want one app config for managers, with access to performance reports or other privileged functionality, and another app config for associates with limited access. Another example might be configuring an app config based on the type of checkout process, mobile POS for on-the-go transactions or fixed registers with peripheral scanner and terminal use.

There are two methods for segmenting app configs. The traditional approach involves linking roles and associates directly to a designated app config. Please note that this method will be deprecated in the future. The enhanced approach is recommended, especially for new and onboarding merchants. It allows you to segment app configs based on three criteria: Device Type (iPad vs. iPhone), Personnel (based on role or individual associate), and Location (based on store group or store).