Sell through the application that owns the purchase

Purpose

Owning applications contribute their product knowledge to a common sale process. Commerce can coordinate the sale without implementing every application’s domain work.

How It Works

An owning application registers its product types and contract information during deployment. Commerce uses that declaration to locate the application for an item. During preview and placement, the application evaluates details and prepares what it can sell. Limited resources use the declared claim arrangement. Delivery later passes through the fulfilment register to the appropriate owning application. Registration or invocation problems are reported instead of allowing Commerce to guess the application’s answer.

Relationships

Cart review asks for application advice, placement asks for preparation and claims, and the neighbouring fulfilment module requests delivery or reversal.

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: Applications can register products for the common Commerce sale process.A plain Accounting product can be sold without external delivery work.
Surfaces: apijob
Intent sources: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D14services-commerce:docs/milestones/plans/COMM-M2-plan.md#Words used in this plan.

Permissions

Key	Checked at	Scope
`commerce.checkouts.read`	api	tenant

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Deployment registration validates an application manifest and reconciles its registry, advancing the version on a repeat and retiring or reactivating types as declarations change. proved by `ATS-COM-ORD-005-19`, `ATS-COM-ORD-012-01`, `ATS-COM-ORD-013-15`, `TST-COM-ORD-146`	lifecycle	service, database	test services-commerce:modules/participants/tests/integration/services/persistence/participants.integration.spec.js#registers the same manifest again as one reconcile: the version moves, nothing else does
`02`must prove Confirmed	Registration rejects malformed manifests, unsupported contract versions and missing or non-executable claim functions with the detected problems. proved by `ATS-COM-ORD-012-02`, `TST-COM-ORD-146`	validation	service	test services-commerce:modules/participants/tests/integration/services/persistence/participants.integration.spec.js#a manifest that does not parse, every problem named (400 manifest_invalid)
`03`must prove Confirmed	A declared product type cannot belong to two active selling applications. proved by `ATS-COM-ORD-012-03`, `TST-COM-ORD-146`	invariant	service, database	test services-commerce:modules/participants/tests/integration/services/persistence/participants.integration.spec.js#a product type another active participant sells (the floor is the partial unique index)
`04`must prove Confirmed	The application database role reads the participant registry, with writes admitted only through registration. proved by `ATS-COM-ORD-012-09`, `TST-COM-ORD-146`	invariant	database	test services-commerce:modules/participants/tests/integration/services/persistence/participants.integration.spec.js#the application role writing the registry itself: SELECT alone, the function the one way in
`05`must prove Confirmed	Application calls include the acting subject and use operation timeouts of five seconds for advice, ten for preparation and sixty otherwise, distinguishing unavailable calls from invalid responses. proved by `ATS-COM-ORD-003-14`, `ATS-COM-ORD-012-04`, `ATS-COM-ORD-012-13`, `TST-COM-ORD-149`	policy	service	test services-commerce:modules/participants/tests/unit/client/lambda-participant-client.spec.js#times out by the contract’s timeout for the operation, aborting the call: advise 5 s, prepare 10 s
`06`must prove Confirmed	Contract schemas reject undeclared structural fields in requests and responses, with support for the current major version and its predecessor when a second major exists. proved by `ATS-COM-ORD-012-05`, `TST-COM-ORD-002`	validation	service	test macroservice-libraries:packages/commerce-contracts/src/envelope.spec.ts#refuses an extra key
`07`must prove Confirmed	Item details must use a declared schema version and satisfy a published parser, while a remote type without a published parser relies on its version declaration. proved by `ATS-COM-ORD-012-06`, `TST-COM-ORD-148`	validation	service	test services-commerce:modules/participants/tests/integration/services/registry/table-registry.integration.spec.js#parses a payload through the in-process participant’s schema, refusing an undeclared version and a payload outside it
`08`must prove Confirmed	Commerce’s built-in plain-product application accepts empty details for Accounting products, takes no claim, plans one delivery unit and completes that unit without external work. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D14 proved by `ATS-COM-ORD-008-13`, `ATS-COM-ORD-012-07`, `TST-COM-ORD-082`, `TST-COM-ORD-150`	policy	service	test services-commerce:modules/participants/tests/unit/plain/plain-product-participant.spec.js#claims nothing for an item: ok, no claim, an attested empty payload and one unit to deliver
`09`must prove Confirmed	Readers can discover product types owned by active selling applications and their supported schemas; unsellable and unowned types are excluded. proved by `ATS-COM-ORD-012-10`, `TST-COM-ORD-029`	policy	api, service	test services-commerce:modules/checkout/tests/e2e/holds-and-claims.e2e.spec.js#lists the sellable product types with the participant that sells each, to a reader; not the unsellable one
`10`must prove Confirmed	A product type’s declared order kind classifies its sale, with the application identity used when no kind is declared. proved by `ATS-COM-ORD-012-11`, `TST-COM-ORD-152`	calculation	service	test services-commerce:modules/participants/tests/unit/registration/manifest-contract-versions.spec.js#classifies a sale by the declared order_kind, else by the participant’s id
`11`must prove Confirmed	A type can declare up to twenty provisional pricing audiences for purchases that qualify other items in the same order. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#D7 proved by `ATS-COM-ORD-012-12`, `TST-COM-ORD-154`	policy	service	test services-commerce:modules/participants/tests/unit/registry/manifest-pricing-policy.spec.js#answers what a line grants: the audiences once each when the switch is on, nothing when off, undeclared, on with no audience, or not a policy
`12`must prove Confirmed	Claim calls use a consistent ordering of application, resource and line to reduce competing lock-order conflicts. proved by `ATS-COM-ORD-012-08`, `ATS-COM-ORD-012-14`, `TST-COM-ORD-001`	invariant	service, database	test macroservice-libraries:packages/commerce-contracts/src/claims.spec.ts#orders by participant, then resource key, then line
`13`must prove Confirmed	Placed-line delivery belongs to the fulfilment register, which calls the selling application when the frozen delivery condition opens. origin: services-commerce:docs/milestones/plans/COMM-M2-plan.md#A3 proved by `ATS-COM-ORD-012-15`	policy	service	documented services-commerce:docs/milestones/plans/COMM-M2-plan.md#A3

Scenarios

Id	Given	When	Then	Provenance
`01`	A certificate fee needs billing but no shipping or application record creation.	Staff buy the plain product and meet the order’s payment requirement.	The fee follows normal pricing and billing and its built-in delivery completes without external work.	documented services-commerce:docs/milestones/plans/COMM-M2-plan.md#D14

Edge Cases

Id	Given	When	Then	Provenance
`02`	An application manifest declares a claim function unavailable to the claimer.	Register the manifest at deployment.	Registration identifies the unusable function and does not activate the declaration.	test services-commerce:modules/participants/tests/integration/services/persistence/participants.integration.spec.js#a claim function that does not exist, and one the claimer role cannot execute, each named (400 sql_function_not_executable)

Planning

Implementation

Sell through the application that owns the purchase ​

Purpose ​

How It Works ​

Relationships ​

Controls