Why does the product-family → variant structure need to be modeled carefully in the PIM?

So variants group under one product page (shared reviews, working size/color pickers) while each SKU keeps its own GTIN, price, and stock

So each color and size gets a totally separate page with its own reviews

So variants group under one product page (shared reviews, working size/color pickers) while each SKU keeps its own GTIN, price, and stock

Because GTINs are optional and interchangeable

So the brand can avoid using barcodes

🔖 GTINs and variants: giving every product a name machines agree on

Machines need unambiguous IDs. A GTIN (Global Trade Item Number — the number encoded in a UPC or EAN barcode) is the globally unique identifier for a sellable product. Retailers use it to match your item to the same item in their catalog, to prevent duplicate listings, and to link multiple sellers to one page. Wrong, missing, or reused GTINs are a top cause of listings getting blocked or merged incorrectly.

Then there's the variant problem. A single "product" often comes in many buyable versions:

text

Product family:  "Classic Merino Sweater"
├── SKU 1: Charcoal / S   (its own GTIN)
├── SKU 2: Charcoal / M   (its own GTIN)
├── SKU 3: Navy / S       (its own GTIN)
└── SKU 4: Navy / M       (its own GTIN)

Each SKU (the specific sellable variant) needs its own GTIN, price, and stock, while shoppers expect them grouped under one product page with color/size selectors. Modeling this product family → variant structure correctly in the PIM is what makes reviews accumulate on one page (not scatter across four), keeps the size/color picker working, and prevents the dreaded "out of stock" that's really just one variant out of stock. Get the identity layer right and everything downstream lines up; get it wrong and the shelf fractures.