Product catalog and variants management in e-commerce in 2026

The verdict in three sentences

A catalog that treats "T-shirt" as a single product with un-stocked options always ends up selling red in L when only blue in S remains: that is the phantom stockout. The right 2026 architecture assigns one SKU per variant (size × color), with stock, price and alert specific to each combination. This choice cuts order errors by about 30 % and makes CSV import reliable — the condition for a catalog that grows without breaking.

One SKU per variant vs single product with options

The debate settles fast the moment you handle sizes, colors or bundles. A single product with options is simpler to create but unable to track stock combination by combination. One SKU per variant asks for a bit more rigor up front and repays it daily in reliability.

The data model to apply

Here is a concrete example for a fashion item with variants. Each row is a unique SKU, scannable, importable and trackable.

Key rules: a readable product prefix (TSH), a 3-letter color code, a normalized size, an alert threshold per SKU, and a price that can vary (larger sizes often cost more). CSV import uses exactly these columns, letting you add 200 references in a few minutes without error.

Mini case study

Moussa runs a shoe store in Abidjan with 60 models in 6 sizes and 3 colors, nearly 1,080 combinations. With a product-with-options model, he logged about 30 % of orders needing correction (wrong size in stock, wrong price on large sizes): on 400 orders/month that meant 120 disputes and 6 to 8 hours of support per week. Switching to one SKU per variant with alert thresholds, errors drop to under 8 %, about thirty disputes. He recovers roughly half a workday per week and cuts refunds.

FAQ

Do I really need a SKU for every combination?

Yes, as soon as stock varies by combination. A model in 5 sizes and 4 colors = 20 SKUs. It is the only way to know precisely what remains and to avoid selling a sold-out combination, the number-one cause of cancellations.

How do I import a large catalog without retyping everything?

Via a structured CSV file: one row per SKU, columns SKU, variant, price, stock, threshold. A 500-SKU catalog imports in under 10 minutes and updates the same way, with no manual re-creation.

What stock alert threshold should I choose?

It depends on your restock lead time. If you resupply in 7 days and sell 1 unit/day of a SKU, a threshold of 7 to 10 avoids stockout. The threshold is set per SKU, not globally.

Can the price vary from one variant to another?

Yes, and it is common: large sizes, limited editions, bundles. The one-SKU-per-variant model natively handles a price specific to each row, which a product-with-options handles poorly.

How much does setting up a variant catalog cost?

For a store of 50 to 300 products, allow 150,000 to 400,000 FCFA depending on volume and initial import. It is a structural investment that avoids months of stock errors.

Let's talk about your project. We model your variants as clean SKUs and import your existing catalog without retyping. WhatsApp +221 77 596 93 33.