Configure product purchasing and price adjustments

Purpose

Administrators choose how product prices are selected and which customer functions adjust them.

How It Works

Staff open the product Pricing page and inspect its grid and Purchasing settings. The console exposes the supported setting subset and displays an existing schedule without offering a replacement picker. API clients manage the remaining settings and product pricing handlers. Grid validation distinguishes missing required coverage from advisory warnings. Registering an active function changes later calculations; deactivation retains its record while skipping the adjustment. Invalid references, mismatched function requests and insufficient permission prevent changes. The product should preserve clear ownership of handler configuration and schedule selection.

Relationships

The configure qualifying price audiences capability supplies related configuration or assessment used in this work.

The maintain dated pricing periods capability supplies related configuration or assessment used in this work.

The calculate and explain a buyer’s item price 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: Staff can select rank-based pricing when imported configuration requires it.Activating or deactivating the registered product function controls adjustment use through configuration.
Surfaces: consoleapi
Intent sources: services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D4services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D14services-commerce:docs/milestones/COMM-M1-set-up-what-you-sell.md#D-REC-9 (to confirm)services-commerce:docs/milestones/plans/COMM-M1-plan.md#2. Scope (item 5)

Controls

28 controls apply, from the corpus control catalogue.

TC-IAM-006 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-TEN-004 TC-CRY-001 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-AVL-004 TC-MON-001 TC-MON-002 TC-MON-004 TC-PI-001 TC-PI-002 TC-PI-003 TC-PI-004 TC-PI-005 TC-PRV-001 TC-PRV-002

Permissions

Key	Checked at	Scope
`commerce.product-purchasing-settings.read`	api	tenant
`commerce.product-purchasing-settings.update`	api	tenant
`commerce.product-purchasing-settings.create`	api	tenant
`commerce.product-purchasing-settings.delete`	api	tenant
`commerce.product-purchasing-settings.bulk`	api	tenant
`commerce.product-extensions.read`	api	tenant
`commerce.product-extensions.update`	api	tenant
`commerce.product-extensions.delete`	api	tenant
`commerce.product-extensions.create`	api	tenant
`commerce.product-extensions.bulk`	api	tenant

Business Rules

10 rules, 7 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` Proposed	Purchasing settings select the schedule, audience-price selection method, promotion exclusion, priced buyer or recipient, purchase or service qualification date, and allowed organization purchasing roles. origin: COMM-M1 D4 (docs/milestones/COMM-M1-set-up-what-you-sell.md)	policy	api, service	documented services-commerce:docs/milestones/plans/COMM-M1-plan.md#D4. Let staff see and set a product's purchasing settings
`02`must prove Proposed	Absent settings use buyer pricing, lowest-price selection, promotion inclusion, purchase-date qualification, no roles and no schedule; replacement resets omitted settings to those defaults. origin: COMM-M1 D4 (docs/milestones/COMM-M1-set-up-what-you-sell.md) no proof recorded yet	policy	service, database	test services-commerce:modules/pricing/tests/e2e/product-purchasing-settings.e2e.spec.js#gives a setting the PUT leaves out its default, the whole record being stated
`03`must prove Proposed	Lowest-price selection chooses the cheapest qualifying audience with lower rank breaking ties, while rank selection takes the first qualifying audience in rank order. origin: COMM-M1 plan A4 (member pricing Q-09) (docs/milestones/plans/COMM-M1-plan.md) no proof recorded yet	calculation	service	test services-commerce:modules/pricing/tests/e2e/product-purchasing-settings.e2e.spec.js#prices the same buyer at the member price under rank, Member coming before Student members
`04`must prove Proposed	Unknown schedules or organization roles and unsupported setting values produce a refusal without changing purchasing settings. no proof recorded yet	validation	api, service	test services-commerce:modules/pricing/tests/e2e/product-purchasing-settings.e2e.spec.js#refuses an unknown organization role id with 400 naming it, and stores nothing (COM-ACC-0799)
`05` Proposed	The product Pricing panel exposes its schedule read-only and edits audience selection, promotion exclusion and organization roles; other purchasing settings remain API-managed. origin: COMM-M1 walkthrough ruling R5 (docs/debt/pricing-schedules-owned-by-event.md)	policy	console	test react-console:components/commerce/pricing/__tests__/purchasing-settings-schedule.test.tsx#never offers a schedule choice, even when schedules exist
`06`must prove Proposed	Each product may reference one registered pricing handler rather than a web address, active by default and ignored when inactive. no proof recorded yet	policy	api, service	test services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#keeps the row and ignores it when it is put inactive: back to $20.00
`07`must prove Proposed	Pricing-function requests reject mismatched products, workspaces or extension points, missing handler references and handler-owned properties without writing a record. no proof recorded yet	validation	api	test services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#refuses an unknown property such as a timeout, which belongs to the handler
`08`must prove Proposed	Any period-and-currency price grid containing prices requires Standard coverage, supplied directly, inherited from Always or explicitly prohibited. origin: COMM-M1 D6 (docs/milestones/COMM-M1-set-up-what-you-sell.md) no proof recorded yet	validation	console, service	test react-console:lib/commerce/pricing/__tests__/rules.test.ts#refuses a period with a Member price and no Standard price, naming the cell
`09` Proposed	Grid warnings flag missing Member coverage, prices above Standard, prohibited Standard cells and entirely computed foreign-currency tabs without blocking a save.	policy	console	test react-console:lib/commerce/pricing/__tests__/rules.test.ts#warns when a cell is dearer than Standard
`10`must prove Proposed	Reading purchasing settings and pricing functions requires their read permissions, while changes require their administrator permissions. origin: COMM-M1 D4 (docs/milestones/COMM-M1-set-up-what-you-sell.md) no proof recorded yet	permission	api, console	test services-commerce:modules/pricing/tests/e2e/product-purchasing-settings.e2e.spec.js#lets a read-only principal read, and refuses it the PUT, 403 permission_missing, the settings as they were

Scenarios

Id	Given	When	Then	Provenance
`01`	The buyer qualifies for lower-ranked Member and cheaper Student pricing	Compare lowest-price and rank selection	Lowest uses Student and rank uses Member	test services-commerce:modules/pricing/tests/e2e/product-purchasing-settings.e2e.spec.js#prices the same buyer at the member price under rank, Member coming before Student members
`02`	The t-shirt’s price row is twenty dollars	Register an active 2.50-dollar product adjustment	The following quote returns 22.50 dollars	test services-commerce:modules/pricing/tests/e2e/product-extensions.e2e.spec.js#adds the function’s $2.50 to the next quote: $20.00 price row and $2.50 extension, $22.50

Planning

Configure product purchasing and price adjustments ​

Purpose ​

How It Works ​

Relationships ​