Product variants need stable identifiers for the combinations customers can actually buy. Separate a product's presentation from the SKU that carries price, stock and fulfilment meaning. A colour or size label changing should not silently create a different item or rewrite an existing order.
Let’s plan your product catalogue model.
Bring your workflow, constraints and open questions. We’ll help you define the requirements and work through a practical next step.
Define valid combinations
List option types, values and the combinations offered. Some combinations may not exist, while others exist but are temporarily unavailable. Show that distinction instead of presenting every missing choice as out of stock.
For a hypothetical apparel catalogue, blue in medium and blue in large may have different stock. A single product-level quantity cannot explain which selection is available.
Create a catalogue identity matrix
| Concept | Meaning | Rule to define |
|---|---|---|
| Product | Shared presentation and grouping | Which attributes apply to all variants? |
| Option | Choice such as size or colour | Stable internal value and display label |
| SKU | Purchasable combination | Unique reference and stock relationship |
| Availability | Current selling state | Unlisted, unavailable and sold out distinguished |
| Price | Applicable amount under the commercial model | Variant-specific differences visible |
| Order line | Purchased snapshot | Later catalogue edits do not rewrite history |
Do not use display names as the only identifiers. Labels can be translated, corrected or reused without changing the underlying business identity.
Design selection and invalid combinations
Make the chosen combination clear before Add to cart. If changing one option invalidates another, explain the adjustment rather than silently substituting a different item.
Show variant-specific images and descriptions where they matter, but keep accessible labels for choices. Colour alone may not communicate the selected option to every customer.
Test catalogue updates
Rename an option, deactivate a SKU and change a price while synthetic carts and orders exist. Verify new purchases use the current rules while prior transactions preserve their accepted details.
Check imports and integrations for stable mappings. A supplier changing a label should not create duplicate SKUs through a name-based match.
Variant questions
Should every possible option combination get a SKU?
Only model the combinations the business actually supports, with explicit treatment of unavailable choices.
Can two variants share one stock pool?
Sometimes, depending on fulfilment and transformation rules. Define the relationship and allocation behaviour rather than assuming one SKU always means one independent pool.
Connect catalogue changes to CSV import validation, and discuss identity rules with Drema's ecommerce team.
