Data Model
Types, hierarchy, localisation and enforcement. The four decisions that get baked into every downstream integration within six months.
-
Attributes, variants and the SKU problem
A product with six colours and five sizes is thirty things to sell and one thing to describe. Confusing those two numbers is the single most common cause of a catalogue that cannot be maintained, and it happens in the first month.
-
The product data model that survives growth
Most catalogue rebuilds are not caused by the platform. They are caused by a data model that could not represent a variant, a market or a unit, and had to be flattened into free text to keep going. Here are the decisions that are expensive to reverse.