Merit · PIM · Concept explainer
This is the idea behind MSP-392, the variant creation flow, and DEC-0172, the decision that made Region a variant axis on Smartphones. Six diagrams, each with a short caption underneath.
A category has many attributes. Only some of them are promoted to axes.
Smartphones category
An axis is an attribute that Merit has marked as the thing that makes two items different buyable versions of the same product. Colour is an axis on T-shirts. Storage is an axis on phones. Weight is not an axis, because nobody buys a different weight of the same phone. It stays on the product page as information only.
Every attribute describes the product. Only an axis splits the product into separate Variants a buyer can choose between. Getting this wrong is what created the iPad problem in section 5.
Two axes on Smartphones: Storage and Colour. Every combination becomes its own child SKU.
Storage [128GB, 256GB] × Colour [Black, Blue, Titanium]
Six boxes, six child SKUs. FR-17 says every combination of axis values generates a child SKU with its own barcode field, its own stock and its own price. Nobody enters these six by hand. The system builds the grid from the axis values.
Add a third axis: Region [UAE, International, US]
Adding one axis with three values did not add three SKUs. It multiplied the whole grid by three. That multiplication is the cost of adding an axis, and it is why an axis is never a free addition to a category.
FR-10 allows at most five variant axes per category. Smartphones spends three of them today.
Smartphones variant axes, five slots
DEC-0172, decided 19 August, made Region the third axis on Smartphones, with allowed values fixed to exactly UAE, International and US. Two slots remain, and nothing else is queued for this category.
A catalogue admin can. A seller can never.
Two lanes
A seller-invented axis fragments the category permanently, and FR-17 means every existing product in that category gains a cross product of empty SKUs. The rule stays in the schema, not only in a document, so nobody rebuilds a hole for it later.
One Variant with two different physical items hidden behind it. This is the case that made DEC-0172 necessary.
Before: Connectivity is not an axis
After: Connectivity is a variant axis
This is the fix DEC-0172 applied to Region, and the same fix MSP-392 applies to Connectivity. One Offer never carries two different physical items. When two real items collide on the same axis values, the fix is a new axis, not a second Offer.
The seller cannot force a new axis into existence. The flow fails loudly and routes the decision to an admin.
No duplicate Variant and no Offer go live during the wait. A silent merge or a duplicate only surfaces after a customer has already received the wrong item, which is the exact failure section 5 shows.
Merit Incentives · PIM · What a variant axis is
Sources: PRD PIM Category and Attribute Structure, MSP-392 Variant Creation Requirement, Master PIM Documentation.