---
schema_version: "1"
id: b2fd776e129792c284a415607db9332fe6c764b053d54b1248c5ca9d37c101f6
title: Hierarchy of Store Pricing
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/commerce/264-0-0/rt_cms_settings_hierarchy_of_store_pricing.md
canonical_url: https://help.salesforce.com/s/articleView?id=commerce.rt_cms_settings_hierarchy_of_store_pricing.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 38da6052c0c9e09101d732a0fc71f2b0e0eaa22d2f527d295dcf8d49153ab2cb
description: Determine how prices are calculated based on store, store group, sales price, and list price in Point of Sale CMS.
products:
  - Commerce
release: "264"
---
# Hierarchy of Store Pricing

Determine how prices are calculated based on store, store group, sales price, and list price in Point of Sale CMS.

By default, the priority order for pricing will be:

1. Store Price
2. Store Group Price
3. Sales Price\*
4. List Price

However, this priority can be changed by configuring the CMS setting, **Enrich store pricing to product**.

Consider this example of products and their prices:

    
| Product ID | List Price | Sales Price | Store Price | Store Group Price |
| --- | --- | --- | --- | --- |
| 123 | $50 | $50 | $45 | $40 |

## Store Group Level

If **Enrich store pricing to product** is set to "STORE\_GROUP\_LEVEL", the product's store price will be the store group price (for example $40). However, according to the store pricing hierarchy, if the store group price is absent or zero, the sales price will be adopted as the store price (for example, $50). If the sales price is zero or not specified, the store price will default to the list price (for example, $50).

## Store Level

If **Enrich store pricing to product** is set to "STORE\_LEVEL", the product's store price will be the store-level price (for example $45).

## Both

If **Enrich store pricing to product** is set to "BOTH", based on the hierarchy, the product's store price will be the store-level price (for example $45). However, if the store-level price is missing or zero, the store price will default to the store group price (for example $40). If the store group price is absent or zero, the sales price will be used (for example $50). Lastly, if the sales price is zero or not provided, the store price will default to the list price (for example $50).

\* Sales price will be overridden by the store price if the "store.price.overrides.sale.price" flag is enabled (**CMS > Store Management > Store Settings > Search**). Additionally, even if this flag is disabled, the store price will still override the sales price under these conditions:

- Store price is less than the sales price (and greater than 0)
- Sales price is null

## Pricing Based on Fulfillment Type

The POS app displays either the store price or the sales/list price based on the fulfillment type (in-store or online).

Consider this example product and its prices:

    
| Product ID | List Price | Sales Price | Store Price | Store Group Price |
| --- | --- | --- | --- | --- |
| 123 | $50 | $50 | $45 | $40 |

In-Store Fulfillment: If product 123 is purchased in-store, the price will be $45, as it's the store price.

Online Fulfillment: If product 123 is purchased for online fulfillment (for example, ship to home), the price will be $50, as it reflects the sales/list price.