Accounting Product Ownership and Commerce Extensions

Context

Several applications sell the same Accounting product. Copying its financial identity into another owner would create competing sources.

Decision

Accounting retains base products and financial price rows, while Commerce retains selling facets and calculates their use through direct scoped reads.

Alternatives Considered

Replicate base products into Commerce. Replicated product state would require synchronization with the financial source.

Require HTTP reads for every price input. The implementation uses scoped table reads to load the larger product and grid input set.

Consequences

Accounting functions perform product writes, including combined Commerce requests. Cross-service references rely on existence checks rather than foreign keys into Accounting. The hosted price-grid save remains an Accounting product write.