The verdict in three sentences
A store that tracks stock at the product level rather than the variant level always ends up selling a "red size M" that no longer exists. The fix is simple: one unique SKU per variation, stock tracked per variant, and alert thresholds before the stockout. Done right, this system removes nearly all overselling and invisible stockouts that drive customers away.
The trap of product-level management
When stock is counted globally ("20 in stock") without distinguishing sizes or colors, the inventory lies. A customer orders a sold-out size, you cancel, and you lose their trust. The solution is to drop down to the variation level.
| Approach | Stock tracked at | Oversell risk | Stockout visibility |
|---|---|---|---|
| Simple product | Global product | High | Low |
| Manual variant (spreadsheet) | Variation, by hand | Medium | Delayed |
| Automated variant | Variation, real time | Low | Immediate |
Recommended data structure
A "parent" product carries the shared info (name, description, category); each "child" variant carries its own SKU, optional price and stock. Here is the recommended structure.
| Field | Level | Example | Role |
|---|---|---|---|
| Product name | Parent | "Cotton T-shirt" | Shared identity |
| Variant SKU | Variant | TSH-RED-M | Unique identifier |
| Color attribute | Variant | Red | Filtering / choice |
| Size attribute | Variant | M | Filtering / choice |
| Available stock | Variant | 8 | Real-time count |
| Alert threshold | Variant | 3 | Triggers restock |
| Price (if different) | Variant | 12,000 FCFA | Per-variation pricing |
Manual vs automated
Manual spreadsheet management holds up while the catalog is small; it collapses as you grow. Automation pays off from a few dozen variants.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
| Criterion | Manual (spreadsheet) | Automated (store) |
|---|---|---|
| Stock update | By hand, delayed | Real time on each sale |
| Error risk | High | Low |
| Restock alert | Often forgotten | Automatic at threshold |
| Time per week | 3-5h | < 1h |
| Scaling | Difficult | Smooth |
Mini case study
Cheikh sells shoes in Dakar: 40 models, 5 sizes each, so 200 variants. Under manual management, he suffered about 15 cancellations a month for overselling, each a lost average basket of 28,000 FCFA and a disappointed customer. He switches to stock per SKU with an alert threshold at 2 pairs. Overselling drops to 2 per month. He recovers 13 orders, roughly 364,000 FCFA per month, not counting the trust regained and the bad reviews avoided.
FAQ
Should you have a SKU per variant or per product? Per variant. Each color/size combination needs its own unique SKU to track real stock and avoid overselling.
When should you automate inventory management? From a few dozen variants, or from the first oversell you suffer. Manual spreadsheets cost 3 to 5 hours a week and multiply errors as you grow.
What threshold should trigger an alert? Often 2 to 3 units per variant, depending on your restock lead time. The goal is to reorder before the stockout, not after.
How do you handle a different price per variant? Put the price at the variant level when it varies (for example a larger size costing more). Otherwise, keep the price at the parent to simplify.
Do variants slow down the product page? No, if well structured: visual color and size buttons, stock shown on selection. Good variant UX can even lift add-to-cart by 5 to 10%.
Let's talk about your project. We structure your catalog into SKU-per-variant with automatic stock alerts. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.