Price
What It Models
A price cell describes an audience's offer in one currency and pricing period, optionally limited to an effective interval. Its mode supplies an amount, a percentage of standard, conversion or purchase prohibition. Accounting validates the grid; Commerce owns choosing and calculating the price used for a purchase.
Identity and Attributes
Cells are parts of a complete product grid and have no independent version. Storage preserves submitted order and separately prevents duplicate cell keys. Migration handovers retain the criteria and pricing context of former special prices until Commerce can establish their audiences.
Relationships
The owning product supplies the business unit and its permitted currencies. Audience and period identifiers refer to Commerce vocabulary. Bundle allocation and accounting-share validation consult the product's selected standard base-currency amount.
Invariants
Saving checks window overlap and the existence of backing cells in the matching or always period. Backing validation does not require those cells to cover every instant of the dependent cell's window. The database prevents duplicate keys, but window-overlap prevention belongs to write validation.
How It Is Stored and Shared
Product saving replaces price rows within its local transaction. Shared readers use these rows and their lookup indexes. Accounting also retains and exports migration handovers; it provides no HTTP command to complete them. Commerce's realization worker is outside the verified source scope.
Open Design Questions
Held migrated audiences need one admission policy across product write paths. Period existence validation and removal of the compatibility audience alias still need decisions or implementation work.