Store shared product facts separately from differing variant facts

Find the facts that really stay the same

The fictional lamp product has a supplied note ID NOTE-W shared by both variants. The black cable is 1 metre and the white cable is 2 metres. The note ID is opaque: it contains no warranty recommendation. This model stores the shared note at product level and cable metres at variant level. It reports a common cable value only when every variant has the same known value.

Display each offer without inventing inheritance

A product-level 1-metre cable value would misdescribe white. Keeping 1 and 2 on the variants represents both offers while retaining NOTE-W once in the source. Choosing a variant still needs the separate stock identity contract; a cable field does not select a SKU.

1. List supplied product facts
2. Compare every offered variant
3. Keep differing fields on variants
4. Render each offer’s known fields

A missing variant value does not inherit the other variant’s value.

Prepare a field-scope brief

The complete material compares different lengths, equal lengths and unknown white length. Use it to specify product/variant presentation fields before a catalogue build; keep operational SKU records separately owned.

Cable values are positive whole metres up to 1,000 or null under this narrow example. Null white length gives no common value and an unknown variant, rather than a guessed 1-metre result. No measurement conversion, legal note interpretation or supplier claim is performed.

Use this product-data brief when discussing catalogue fields, then inspect definition review before applying stricter validations.