Product Data & Architecture

Where product facts belong, which system should own them and what happens when they change.

Every resource on where product facts belong and which system should own them.

Start here

Which System Should Own Each Product Fact?Learn how to choose the authoritative source for each product fact, separate system of record from evidence and resolve conflicts…
Which Product Facts Belong at Model, Variant and SKU Level?Learn which product facts should live at model, variant, SKU, batch or item level, how inheritance works and how to avoid…
When a Product Changes, Do You Overwrite the Fact, Version the Record or Create a New Product?A decision guide for product-data changes: when to correct, version, create a batch, new variant or SKU, assign new identity or…

How to Organise Product Data Without a PIM: A Small-Business Operating Model
How a small ecommerce business can govern product data across Shopify, spreadsheets, shared files and supplier evidence without…
Last verified 2 September 2026
When a Product Changes, Do You Overwrite the Fact, Version the Record or Create a New Product?
A decision guide for product-data changes: when to correct, version, create a batch, new variant or SKU, assign new identity or…
Where Product Data Stops Meaning the Same Thing
You mapped a catalogue into a compliance format and about half of it arrived intact.
Sources as at 28 August 2026
Which Product Facts Belong at Model, Variant and SKU Level?
Learn which product facts should live at model, variant, SKU, batch or item level, how inheritance works and how to avoid…
Which System Should Own Each Product Fact?
Learn how to choose the authoritative source for each product fact, separate system of record from evidence and resolve conflicts…
Your Technical File Holds Compliance Evidence. Which Parts Should Become Governed Product Data?
Decide which technical-file facts should stay as evidence and which should become governed product data, with scope, provenance and…
Last verified 1 September 2026