Select the policy governing a sale

Purpose

Staff and applications obtain a predictable governing policy from explicit choices and configured defaults.

How It Works

Administrators maintain defaults for the workspace and individual selling applications. Commerce uses the available context to resolve a policy when a sale begins. Checkout applies the broader selection order recorded by Product, while the shared resolution read supports a narrower context. Staff can inspect where a resolution came from instead of treating every selection as explicit. Defaults replacement validates the referenced policies and retains the previous document when a selection is unsuitable. Conflicting item contexts are a dependency on checkout’s enforcement of a single order policy. The product should align the resolution interface with the context checkout evaluates.

Relationships

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

The configure a store’s offered assortment 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: Customer customer staff and applications can rely on a predictable answer to which policy governs a sale.A placed sale does not mixes business units or currencies.
Surfaces: consoleapi
Intent sources: services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D9services-commerce:docs/milestones/plans/COMM-M1-plan.md#D9. Adopt the expanded ordering-profile selection order?services-commerce:docs/milestones/plans/COMM-M1-plan.md#4. Assumptions (A1, A2)

Controls

19 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-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`commerce.ordering-profiles.read`	api	tenant
`commerce.ordering-profiles.update`	api	tenant

Business Rules

8 rules, 6 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	Policy selection takes the first available choice in this order: an explicit policy, the store’s policy, the first item’s selling-context policy, the application default and the workspace default. origin: COMM-M1 D9 (docs/milestones/COMM-M1-set-up-what-you-sell.md) proved by `ATS-COM-CAT-002-05`, `ATS-COM-CAT-002-07`	policy	service	documented services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D9
`02`must prove Proposed	Adding an item that resolves to a different policy is refused with both policies identified, preserving one policy per order. origin: COMM-M1 D9 (docs/milestones/COMM-M1-set-up-what-you-sell.md) proved by `ATS-COM-CAT-002-05`, `ATS-COM-CAT-002-07`	invariant	service	documented services-commerce:docs/milestones/plans/COMM-M1-plan.md#D9. Adopt the expanded ordering-profile selection order?
`03`must prove Proposed	The resolution read selects an explicit policy before an application default before the workspace default and identifies the winning source. origin: COMM-M1 plan A1 (docs/milestones/plans/COMM-M1-plan.md) proved by `ATS-COM-CAT-001-13`, `ATS-COM-CAT-002-01`, `ATS-COM-CAT-002-06`, `TST-COM-CAT-030`, `TST-COM-CAT-036`	policy	service	test services-commerce:modules/configuration/tests/e2e/ordering-profiles.e2e.spec.js#resolves a context: the profile it names (explicit), else its application’s default, else the tenant default
`04`must prove Proposed	Resolution rejects an unknown policy reference and returns no policy when the workspace has none configured. proved by `ATS-COM-CAT-002-02`, `TST-COM-CAT-030`	validation	service	test services-commerce:modules/configuration/tests/e2e/ordering-profiles.e2e.spec.js#answers 400 to a context naming a profile the tenant does not have, and nothing for a tenant with no profile at all
`05` Proposed	Saving the combined workspace and application defaults document replaces the application map, removing omitted entries.	policy	service, console	test services-commerce:modules/configuration/tests/e2e/ordering-profiles.e2e.spec.js#removes an application default left out of the document, the tenant default kept when null
`06`must prove Proposed	Defaults replacement succeeds only when every referenced policy belongs to the workspace and is active; otherwise the saved document remains intact. proved by `ATS-COM-CAT-002-03`, `TST-COM-CAT-030`, `TST-COM-CAT-035`	validation	service, console	test services-commerce:modules/configuration/tests/e2e/ordering-profiles.e2e.spec.js#refuses a document naming an inactive or an unknown profile, 400, the document unchanged
`07` Proposed	The workspace default supplies the policy for an application with no application-specific default. origin: COMM-M1 plan A1 (docs/milestones/plans/COMM-M1-plan.md)	policy	service	documented services-commerce:docs/decisions/ordering-profiles.md
`08`must prove Proposed	Read permission allows defaults inspection and resolution, while defaults replacement requires policy update permission. proved by `ATS-COM-CAT-002-04`, `TST-COM-CAT-028`	permission	api	test services-commerce:modules/configuration/tests/e2e/configuration-security.e2e.spec.js#lists and reads the ordering profiles, the defaults document and the resolution

Scenarios

Id	Given	When	Then	Provenance
`01`	Events has an application policy distinct from the workspace fallback	Resolve the events application context	Resolution returns its application default with that source identified	test services-commerce:modules/configuration/tests/integration/services/persistence/ordering-profiles.queries.integration.spec.js#resolveOrderingProfile walks the hierarchy of 22 §3 and names the source
`02`	The cart already uses Main USD	Add an item assigned to Conference EUR by its selling context	The conflicting item is refused with both policies identified	documented services-commerce:docs/milestones/plans/COMM-M1-plan.md#D9. Adopt the expanded ordering-profile selection order?

Planning

Implementation

Select the policy governing a sale ​

Purpose ​

How It Works ​

Relationships ​