inventory quantity
The quantitative on-hand stock of the product, as a count of the selling unit (a numeral on the QuantityUnits dimension — each, pair, set, case, dozen; reused from the tier-price counting dimension, so the count and its unit are one fact and no separate inventory-unit token is needed). A product carries many inventory quantities (cardinality many): each named state is a distinct statement, self-correlating its count with its quantity_state qualifier (available 47, committed 12, incoming 100). THE pool declares the bundle's grammar — that stock can be reported as a count by named state in a counting unit; the realised magnitudes are the data layer's offer/instance rows (L1), exactly as list_price's realised amount is downstream. Distinct from availability_status (the single buyable-state token in-stock/out-of-stock that this count sits behind). The 'only N left' urgency, low-stock bar, and 'selling fast' badge a surface prints are PRESENTATION over these counts (A10), never stored. The state this count holds is not an existing standalone product property (no product carries an inventory-state slot), so this is a by-state host, not the variant-host kill (A9).
Inventory quantity is a measured figure, given as a whole count of selling units.
It belongs to availability — whether it can be obtained.
the bundle what travels with each inventory quantity
A inventory quantity is not a lone value — each statement is a self-correlating bundle, carrying its own:
asked by the kinds that answer it
49 kinds answer it, each for any number of values. The same question can be reused by unrelated kinds — one meaning, many homes.
asked by kinds that answer it
The same question can be reused by unrelated kinds — one meaning, many homes.
| kind | how many |
|---|---|
| Product | many |