Product variants color/size: inventory per SKU done right (Johannesburg, 2026)

The verdict in three sentences

Managing a dress in 3 colors and 5 sizes isn't managing one product, it's managing fifteen: each combination is a SKU with its own stock count. Without that granularity, you oversell the popular variant and tie up the dead one. A color × size matrix, a per-SKU low-stock threshold and multichannel sync bring oversell from 6 % of orders to under 1 %.

Color × size matrix: think in SKUs, not products

The right mental model: the "parent" product (the dress) is one page; each combination is a child SKU with its own stock counter. Here's a typical matrix.

Each cell has its own stock. "Blue M" can be out while "Red L" overflows. Showing availability per variant avoids selling an absent combination and kills disappointing cancellations.

Low-stock threshold and oversell prevention

Per-SKU stock is useless if it isn't watched variant by variant. Each SKU needs a threshold tuned to its rotation speed, not one global figure.

The golden rule against oversell: decrement SKU stock at confirmed payment, never at add-to-cart alone. And across multiple channels (site, marketplace, store), sync in real time so you don't sell the last unit twice.

Back-in-stock alerts and bundles

An out-of-stock SKU isn't a lost sale if you capture intent. A "Notify me" button on an absent variant collects emails/numbers and fires a notification on restock: it's among the best-converting emails a store sends.

For bundles (a 3-size set, a color pack), create a bundle SKU whose stock is computed from its components: the bundle is available as long as every variant in it is. Otherwise you sell a set you can't fulfil.

Mini case study

Thabo runs an online clothing store in Johannesburg: 40 styles, roughly 12 variants each, about 480 SKUs. He tracked stock at the parent-product level only. Result: 6 % of orders oversold, with cancellations and refunds.

On 500 orders/month at an average basket of ZAR 650, that meant 30 orders/month cancelled — ZAR 19,500 of lost revenue plus dented trust. He moves to per-SKU stock, a per-variant threshold, site-marketplace sync, and decrement at payment. Three months later: oversell at 0.8 %, about 4 orders/month — 26 sales/month recovered. Back-in-stock alerts add roughly thirty monthly re-sales on restocked variants as a bonus.

FAQ

Do I need a SKU per color × size combination? Yes. A dress in 3 colors and 5 sizes = 15 SKUs, each with its own stock. Tracking at the parent level only is the number-one cause of oversell.

When should I decrement stock? At confirmed payment, not at add-to-cart. Decrementing too early locks stock for abandoned carts; too late causes oversell.

How do I avoid selling the last item twice across channels? Real-time stock sync between site, marketplace and point of sale. Without sync, each channel thinks it holds the last unit.

Are "back-in-stock" alerts worth it? Yes: they're among the best-converting notifications a store sends, because purchase intent is already there. They turn a stockout into a deferred sale.

How do I manage bundle stock? Create a bundle SKU whose availability depends on its components: available as long as each variant in it is. Otherwise you sell an unfulfillable set.

Let's talk about your project. We model your variants as SKUs and sync your multichannel stock. WhatsApp +221 77 596 93 33.