Check the details / Variant Families

Keep shared content separate from sellable differences.

A product family groups related variations. A useful model makes shared information reusable while keeping each variant’s identity and distinguishing attributes intact.

Define what makes a variation distinct

A color, size, finish, or pack quantity may distinguish one sellable item from another. The combination should be clear enough that a colleague can identify a variation without relying on a descriptive title alone. Not every descriptive difference necessarily requires a separate variant.

Begin with the way items are ordered and represented in the source systems. The model should reflect the intended business meaning rather than create combinations simply because several option lists exist.

Decide what can be inherited

A family description or care instruction may apply across several variants. A dimension, identifier, or image may belong to one specific item. Establish an inheritance rule and a visible way to represent exceptions when they are allowed.

Copying a shared value into every variation can make later edits inconsistent. Inheriting everything can be equally misleading when a variant differs. The correct choice depends on the attribute and the agreed source of information.

Avoid creating impossible combinations

A list of two colors and three sizes does not prove that all six combinations exist. Model actual permitted variations and keep unsupported combinations out of the export. The absence of an option may need confirmation rather than automatic creation.

Review identifiers and references when variations are renamed or discontinued. A descriptive title can change without creating a new item, while a changed physical specification may require a separate business decision.

Test both the family and its outputs

Use examples with shared descriptions, one exceptional measurement, a variation-specific image, and a discontinued option. Ask the reviewer to explain which values each export should contain. A family view and an individual item view should remain consistent.

Document the decisions in a compact model note. Destination systems may represent families differently, so a channel map is still needed. A correct internal family structure does not by itself guarantee a valid external listing.