Size & Colour Variant Tracking in Indian Garment Retail — Why It's Different from Any Other Industry
Garment retail has a unique inventory problem that most POS software isn't built to handle. Here's what proper size-colour variant management looks like in practice.
If you run a garment store, you already know the core inventory challenge: one style can exist in six sizes and ten colours. That's sixty combinations — each with its own stock count, its own barcode, and its own sales velocity. Multiply that by 300 active styles and you're managing 18,000 individual inventory positions.
Compare this to a grocery store managing 5,000 SKUs — each a single item, no variants. The complexity gap is enormous. And yet, most POS software treats garment variants the same way it treats grocery SKUs: as individual, unrelated products.
The Variant Problem in Practice
When garment brands use generic POS software, they typically do one of three things — all of them wrong:
- 1Create separate products for each variant — "Kurta Blue M", "Kurta Blue L", "Kurta Blue XL". The catalogue becomes unmanageable within a season.
- 2Use a single SKU for the style and track variants in a spreadsheet alongside. The POS and actual stock are always out of sync.
- 3Group all variants under one stock count and estimate — leading to phantom stock that shows available but is actually the wrong size.
How Proper Variant Management Should Work
The Style-Size-Colour Matrix
The correct model: a "style" (e.g., "SS25-Kurta-001") is the parent. Sizes and colours are attributes. The combination of style + size + colour creates a unique variant, each with its own barcode, stock count, and purchase history. When you search "SS25-Kurta-001", you see a matrix grid — sizes on one axis, colours on the other, stock counts in each cell.
Barcode at the Variant Level
Each size-colour combination gets a unique barcode. This barcode encodes the style code, size, and colour — so a single scan at the POS terminal or warehouse tells the system exactly what was sold or received. No manual selection, no errors.
GRN at the Variant Level
When stock arrives from a supplier, the GRN (Goods Receipt Note) should capture quantities at the variant level — not just "500 units of Kurta-001" but "50 units Blue-S, 80 units Blue-M, 60 units Blue-L..." and so on. This means the purchase order needs to be raised at the variant level too.
Size-Run Analysis
Once you have variant-level data, you can answer the most important merchandising question: which sizes sell fastest? If XL is always the first to sell out while XS sits, your next purchase order should reflect that ratio. This "size run" insight is impossible without proper variant-level tracking.
Season-Wise Inventory Management
Garment retail operates in seasons (Summer, Monsoon, Winter, Festive). Variants that don't sell in-season need to be marked down, transferred between stores, or written off. Your software needs to support season tagging so you can identify aged inventory by style, not just by date.
- Season-wise purchase orders track what was ordered vs. received per season
- End-of-season reports identify slow-moving size-colour combinations
- Stock ageing reports flag variants that have been unsold for 30/60/90 days
- Markdown management lets you apply percentage discounts to specific size-colour combinations
Barcode Printing for Indian Garment Retail
Most Indian garments arrive from manufacturers without proper barcodes. This means the retailer needs to print and attach barcodes at the time of GRN. A garment-specific POS should allow barcode printing in bulk — scan the incoming shipment, auto-generate barcodes for each variant, print labels for attachment before stock hits the shelves.
SigmaPOS handles the full variant lifecycle: style creation with size/colour matrix, variant-level barcode generation and printing, GRN at variant level, sales tracking per variant, and size-run reports per season. For garment chains moving from a generic POS or spreadsheets, this single capability typically justifies the switch.