The short answer: manage variants by treating each combination — a specific size and colour, say — as its own tracked stock unit under one parent product. This keeps counts, reorders and reports accurate while still letting you see the product as a whole. Getting variants right is essential for fashion, footwear, cosmetics and food.
Why variants are tricky
A “t-shirt” isn’t one item — it’s every size × colour combination, each with its own stock. Treat the whole shirt as one product and you can’t see that you’re out of medium black while drowning in small yellow. Track each size separately as unrelated products and reporting becomes a mess.
The right structure: parent + variants
- One parent product — “Classic T-Shirt” — for browsing and reporting.
- Variants beneath it — each size/colour with its own barcode and stock.
- Roll-up view — total stock and sales for the style, plus the detail per variant.
This is exactly what a boutique or shoe store needs.
What good variant handling lets you do
- Accurate counts per variant, so you know real availability.
- Reorder the right variants — buy more medium black, less small yellow.
- See best-sellers by variant, not just by style.
- Sell fast — scan the exact variant at checkout.
Avoid the common mistake
The classic error is creating each variant as a separate, unrelated product. It “works” at the till but destroys your reporting and reorder logic. Always keep variants grouped under one parent.
Variants, done properly
RushFlow uses a parent-product-with-variants model — each size/colour tracked and barcoded, with roll-up reporting per style — so variant-heavy shops stay accurate. See the live demo, or read inventory basics.