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.