Variants Sharing a Color Cannot Be Selected Separately

A seller running a motorcycle gear store reported that when a product holds several variants of the same color, only one of them is reachable on the storefront. The others exist in the product editor, hold their own price and stock, and are published, but a buyer has no way to open or add them to the cart. The seller worked around it by publishing each variant as a separate product, which is the right instinct and the wrong amount of work.

Color is being used as the variant's identity. Across the whole storefront a variant is addressed by its color value and nothing else. The swatch row deduplicates the variant list by color before rendering, so the second black variant is dropped before it ever reaches the page. The product page resolves the selected variant by matching that same color against a value carried in the address bar, so two variants sharing a color also share a URL, and the first one always wins. A variant saved with no color at all is skipped entirely by the same code path.

The dashboard and the storefront disagree. In the product editor each variant is listed under its own SKU, so the seller sees every variant it created, correctly distinct. Nothing in that view suggests that some of them will be unreachable once published. That gap is what made the problem read as a display bug rather than as a limit of the model, and it is why it went unnoticed until a catalog with repeated colors ran into it.

Planned change. The variant's own identifier becomes the key used to select, link and render it, so two variants may share a color and still be independently addressable, each with its own URL. Color returns to being presentation: it paints the swatch, it no longer decides which variant a buyer gets, and a variant without a color stops disappearing. Variants will also carry a name of their own, shown wherever the color alone cannot tell two options apart, so a buyer choosing between two black helmets can see which is which. Catalogs that were split into duplicate products to work around this can be merged back afterwards.