---
id: CON-COM-CAT-002
name: Store
feature: FEAT-COM-CAT-01
product_area: commerce
module: catalog
revision: 1
status: draft
product_intent: confirmed
implementation_evidence: observed
source_sha:
  services-commerce: c8b66a98e2490617aec38ba5c8165dd9bd0a8f9b
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
definition: >-
  A store is a named selling context that combines an offered assortment with a
  checkout policy and storefront presentation choices.
owned_by: MOD-COM-CAT
synonyms:
  - Point of commerce
  - Shop
not_to_be_confused_with:
  - 'A checkout policy, which says how a purchase is processed'
  - A product grouping admitted by an assortment
  - The application surface that presents the offering
facets:
  - name: Checkout policy
    meaning: >-
      The chosen checkout policy connects the store with billing and payment
      arrangements.
    used_for: Supplying the store’s financial processing context.
  - name: Assortment
    meaning: Category inclusion or exclusion defines the products offered here.
    used_for: Selecting the available assortment.
  - name: Home category and default sort
    meaning: The home category and default sort describe the first browsing context.
    used_for: Choosing the initial browsing presentation.
  - name: Organization purchasing roles
    meaning: Organization-role selections qualify contacts acting for organizations.
    used_for: Assessing represented-organization purchases.
  - name: Pricing extension points
    meaning: Preprocessing and review references allow customer-specific pricing work.
    used_for: >-
      Organization-specific order pricing including loyalty credits or
      surcharges.
  - name: Default image and active state
    meaning: >-
      A shared-pipeline image represents the store and active state determines
      whether its shelf is open.
    used_for: The storefront.
relationships:
  - to: CON-COM-CAT-001
    statement: >-
      The referenced policy supplies the store’s unit and currency rather than
      separate store values.
    provenance: test
    source: >-
      services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers
      400 to a currency or a business unit on the body: the store carries
      neither since D23
  - to: CON-COM-CAT-003
    statement: Admitted category memberships connect listings with the store offering.
    provenance: test
    source: >-
      services-commerce:modules/catalog/tests/integration/services/storefront/storefront-listings.queries.integration.spec.js#admits
      under `only` the listings on a named active shelf, and under `all_but`
      those on some other active shelf
lifecycle:
  - state: Active
    meaning: The store returns its shelf and public quotes.
    how_it_changes: Created active; customer staff switch it off.
  - state: Inactive
    meaning: The shelf is empty and public quotes fail validation as closed.
    how_it_changes: >-
      Customer customer staff switch it back on; a store a checkout has used is
      does not deleted.
acted_on_by:
  - CAP-COM-CAT-003
  - CAP-COM-CAT-008
visible_to:
  - ACT-COM-001
  - ACT-COM-004
  - ACT-COM-005
  - ACT-COM-006
evidence:
  - >-
    Pinned service inputs: modules/configuration (stores), modules/catalog
    (storefront, assets), COMM-M1 D3
  - 'Pinned console inputs: components/commerce/stores/**'
supersedes: []
---

# Store

## What It Is

A store answers where the customer offers a collection of products. Staff might recognize a bookstore, a merchandise shop or a conference shop as different stores even when some products appear in several. Creating a store gives that selling context a durable identity, a readable name, an assortment and a reference to the policy governing its sales.

The store organizes an offering rather than copying the product records into a separate inventory. Categories determine which listings can belong to its assortment. The same catalog product can therefore participate in several stores, with its listing and underlying Accounting identity retained. Staff maintain the store’s context while product editors maintain what each item says about itself.

The store also carries presentation and organization-purchasing choices. Those choices help a shopper find the intended shelf and help Commerce assess a purchase made for an organization. Active state makes the store available for browsing; closing it retains its configuration rather than erasing earlier sales.

## What It Is Not

A store is separate from its checkout policy, its shelves and its stock locations. It gets money-processing context from the policy rather than maintaining an independent currency or business unit. A category is one way to group products within the offering. Inventory and fulfilment determine physical stock and delivery in their own module.

## How It Is Used

Administrators establish a policy and categories, then configure the store around them. They inspect the saved view to check its offering and policy together. Later changes can fail when a selected category is unknown, a home shelf falls outside the offering or another editor has advanced the record. Removing a previously used store is a different question from closing its storefront, because checkout and order references retain its identity.

## Its Facets

**Policy reference.** The chosen checkout policy connects the store with billing and payment arrangements.

**Assortment.** Category inclusion or exclusion defines the products offered here.

**Landing and order.** The home category and default sort describe the first browsing context.

**Purchasing roles.** Organization-role selections qualify contacts acting for organizations.

**Pricing extensions.** Preprocessing and review references allow customer-specific pricing work.

**Image and availability.** A shared-pipeline image represents the store and active state determines whether its shelf is open.

## How It Relates

A store draws on catalog categories and listings, points to a checkout policy and gives pricing a selling context. CRM supplies contact-role references used in organization purchasing. Orders retain the store associated with their sale, while fulfilment owns the physical work that follows purchase.

## What It Could Become

The product should validate store extension references when staff save them rather than waiting for a quote to discover a missing handler. Portal presentation remains a delivery question, and the product should settle how store closure and ongoing staff sales are explained to customers.
