Configure a store’s offered assortment

Purpose

Administrators establish a recognizable selling context with an assortment and payment policy.

How It Works

Staff create the store after its policy and categories are available. They choose which shelves the offering includes and the shelf used as its starting point. The saved view brings those choices together with the policy reference and sort. Organization purchasing roles and extension references provide additional sale context. Invalid category choices are identified during saving, and a stale record cannot replace the current version. Earlier checkout and order references affect whether staff can remove the store. The product should verify extension references at configuration time.

Relationships

The configure reusable sale-processing policies capability supplies related configuration or assessment used in this work.

The organize product shelves capability supplies related configuration or assessment used in this work.

The present the store’s available products capability supplies related configuration or assessment used in this work.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: The console supports store preparation and subsequent maintenance.Category assortment determines the store offering.
Surfaces: consoleapi
Intent sources: services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D3services-commerce:docs/milestones/plans/COMM-M1-plan.md#2. Scope (item 2)services-commerce:docs/milestones/plans/COMM-M1-plan.md#D3. Build the Stores screen?

Controls

22 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-005 TC-AZ-006 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-CRY-001 TC-CRY-004 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-DAT-004 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`commerce.stores.read`	api	tenant
`commerce.stores.create`	api	tenant
`commerce.stores.update`	api	tenant
`commerce.stores.delete`	api	tenant
`commerce.stores.bulk`	api	tenant

Business Rules

13 rules, 9 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	Every store references a checkout policy in its workspace; an omitted or unknown policy produces a field-specific refusal. origin: COMM-M1 D3 (docs/milestones/COMM-M1-set-up-what-you-sell.md) no proof recorded yet	validation	api, service, database, console	test services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers 400 to an ordering profile the tenant does not have, naming the property
`02`must prove Proposed	Commerce rejects business-unit or currency fields on a store because its checkout policy supplies those values. no proof recorded yet	validation	api	test 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
`03` Proposed	Staff define an assortment as all categories, selected categories, or all categories except selected exclusions. origin: COMM-M1 D3 (docs/milestones/COMM-M1-set-up-what-you-sell.md)	policy	api, database, console	test services-commerce:modules/catalog/tests/integration/db/catalog-tables.table.integration.spec.js#refuses a store category rule outside all, only and all_but
`04`must prove Proposed	Assortment references must resolve to categories in the store’s workspace; categories from another workspace are treated as unknown. no proof recorded yet	validation	service	test services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses a category id the tenant does not have, 400 naming category_ids and the id, creating nothing
`05`must prove Proposed	The chosen home category must satisfy the store’s inclusion or exclusion rule. origin: COMM-M1 D3 (docs/milestones/COMM-M1-set-up-what-you-sell.md) no proof recorded yet	validation	service	test services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses a home category an "all_but" rule leaves out, 400 naming home_category_id
`06` Proposed	Without configured purchasing roles, a store permits any affiliated contact to purchase for an organization.	policy	service, database	test services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#defaults the purchasing roles to none: any affiliated contact may buy for an organization
`07` Proposed	A store retains its supplied or name-derived identity, and creation under an occupied identity is refused.	validation	service	test services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#derives the id from the name when the request names none, and defaults the purchasing roles to none
`08`must prove Proposed	Commerce refuses removal of a store referenced by a checkout or order and identifies that store. no proof recorded yet	lifecycle	service, database	test services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#refuses deleting a store a checkout was opened in, naming the store
`09` Proposed	The shared asset pipeline retains a store’s default picture; replacement detaches the previous image for retirement, and store deletion detaches the current image. origin: COMM-M1 D11 (docs/milestones/COMM-M1-set-up-what-you-sell.md)	lifecycle	service	test services-commerce:modules/catalog/tests/integration/services/assets/catalog-assets.integration.spec.js#detaches the store’s picture when the store is deleted
`10`must prove Proposed	Saving a store preserves its two pricing-extension references without verifying that registered handlers exist for them. no proof recorded yet	policy	service	observed services-commerce:modules/configuration/services/persistence/stores.ts:storeColumns
`11`must prove Proposed	Store replacement requires the complete record at its read version and rejects stale versions. no proof recorded yet	invariant	api, service	test services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#replaces a store at the version read, the purchasing roles with it, and answers 409 to the stale version after
`12`must prove Proposed	Store inspection requires read permission; creating, replacing and deleting require the corresponding administrator permissions. no proof recorded yet	permission	api, console	test services-commerce:modules/configuration/tests/e2e/configuration-security.e2e.spec.js#is refused the creates, 403 permission_missing
`13`must prove Proposed	A full lock prevents replacing a store, and either full or deletion-only locking prevents removing it. no proof recorded yet	policy	service	observed services-commerce:modules/configuration/services/persistence/stores.ts

Scenarios

Id	Given	When	Then	Provenance
`01`	Main and the Books and Apparel categories are configured	Create Bookstore offering those categories with Books as home	Its first saved version retains that policy and assortment	test services-commerce:modules/configuration/tests/integration/services/persistence/stores.integration.spec.js#creates a store whose rule names categories the tenant has, and whose home category the rule admits
`02`	Bookstore admits only Books	Choose Apparel as its home category	The home selection fails validation	test services-commerce:modules/configuration/tests/e2e/stores.e2e.spec.js#answers 400 to a home category outside the assortment, on a create and on a replacement, naming home_category_id

Planning

Configure a store’s offered assortment ​

Purpose ​

How It Works ​

Relationships ​