Compare the operating models
In this fictional example, operational SKUs L-B and L-W are black/white lamps with their own units and balances. The store page Desk lighting groups both with photos and independent English/zh-HK copy. A page is not necessarily one stock record.
| Business requirement | One combined master/page record | Stock master plus presentation |
|---|---|---|
| Stock identity | Page name may hide exact SKU | L-B/L-W remain exact choices |
| Editorial content | Warehouse labels may reach shoppers | Audience copy/photos on page |
| Variant choice | Ambiguous if selection lacks ID | Black → L-B; white → L-W |
Work through the chosen model
The page stores title, imagery, locale copy and selected offer links. SKU master stores item identity, units and operational type. Each add-to-basket choice names the exact SKU; descriptive copy cannot substitute for the link. Publication can group items without merging stock.
- Publish the customer-facing offer
- Customer selects exact stock choice
- Send that SKU to fulfilment
Separation protects both operational clarity and editorial flexibility but needs maintained SKU links. This concerns object choice, not translation-field transformation.
One page offers two variants. Selecting white creates an L-W order line, leaving L-B stock untouched. Rewriting the page title does not rename the two operational identities.
When the other model fits
There is one simple item with no variant or grouped presentation. Must two systems be introduced?
Show the worked answer
No. Conceptual field separation can exist in one platform; do not add infrastructure without a business need.