Configure a purchase confirmation message

Purpose

An integrator chooses shared confirmation content or composes content owned by the product.

How It Works

An integrator chooses shared confirmation content or composes content owned by the product. Accounting checks newly selected shared templates before accepting them. Owned content is sent to Platform after product writes succeed but before their transaction commits. A Platform refusal rolls back the product writes and identifies the problem. Switching away from owned content requests its removal. Omitting the setting leaves existing content untouched. The console hides confirmation controls while preserving loaded values. A failed Accounting commit after a successful Platform call still leaves a consistency gap. Sending a message when a purchase occurs remains an Orders responsibility.

Relationships

This outcome uses create a product with a permanent identity.

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: Confirmation choices remain consistent with product configuration.
Surfaces: api
Intent sources: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#R22

Controls

28 controls apply, from the corpus control catalogue.

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

Permissions

Key	Checked at	Scope
`accounting.products.update`	api	tenant

Business Rules

8 rules, 5 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	Confirmation configuration selects either a product-owned template or a shared workspace template for product confirmations, with an empty setting disabling it. proved by `ATS-ACC-PRD-014-05`	policy	api, database	test services-accounting:modules/products/tests/e2e/product-features.e2e.spec.js#switches to a shared template
`02`must prove Proposed	A newly selected shared template must be active, belong to the workspace and confirmation purpose, and have no record owner. proved by `ATS-ACC-PRD-014-01`, `TST-ACC-PRD-039`	validation	service	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses a product’s OWN template named as a shared one
`03`must prove Proposed	Platform stores product-owned content and validates its Liquid, allowed variables and required reply-to information. proved by `ATS-ACC-PRD-014-02`, `ATS-ACC-PRD-014-05`, `TST-ACC-PRD-039`	validation	service	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses content Platform refuses, naming the property, and writes nothing
`04`must prove Proposed	Accounting requests template changes after its product writes but before committing, and a Platform failure rolls back those product writes. proved by `ATS-ACC-PRD-014-02`, `ATS-ACC-PRD-014-06`, `TST-ACC-PRD-039`	invariant	service	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#rolls the product back when Platform cannot save the template
`05`must prove Proposed	Disabling a product-owned confirmation or choosing a shared template clears the previously owned template. proved by `ATS-ACC-PRD-006-11`, `ATS-ACC-PRD-014-03`, `ATS-ACC-PRD-014-05`, `TST-ACC-PRD-039`	lifecycle	service	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#clears the product’s own template when it switches to a shared one
`06`must prove Proposed	Omitting confirmation configuration preserves both setting and template; supplied owned content merges retained fields and clears optional fields explicitly set empty. proved by `ATS-ACC-PRD-014-04`, `ATS-ACC-PRD-014-07`, `TST-ACC-PRD-039`	policy	api, service	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#asks Platform for nothing
`07` Proposed	The documented confirmation purpose provides product and unit details, line quantity and price, and customer name.	policy		documented services-accounting:docs/accounting/products.md#Features (2026-10-16)
`08` Proposed	The current console hides confirmation controls. origin: services-accounting:docs/milestones/ACCT-M1-books-and-invoices.md#R22	policy	console	observed react-console:components/accounting-config/products/product-section-types.ts:REMOVED_SECTION_KEYS

Scenarios

Id	Given	When	Then	Provenance
`01`	A product uses an owned confirmation template.	A client supplies content Platform rejects.	The product remains unchanged and the refusal identifies the content problem.	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#refuses content Platform refuses, naming the property, and writes nothing

Edge Cases

Id	Given	When	Then	Provenance
`02`	A product has owned confirmation content.	Replacement omits confirmation configuration.	Both content and setting remain and no Platform call is made.	test services-accounting:modules/products/tests/integration/services/persistence/products.features.integration.spec.js#asks Platform for nothing

Planning

Implementation

Configure a purchase confirmation message ​

Purpose ​

How It Works ​

Relationships ​