For many Indian retailers, the weakest link in inventory management is not the refreshment algorithm but the quality of master data. When product masters are incomplete — missing attributes like size, purity, weight, colour, or seasonality — the system cannot distinguish between fast movers and slow movers. Similarly, when SKU granularity is inconsistent (e.g., treating “gold bangles” as one line item instead of separating by weight ranges, karatage, and design), replenishment signals become distorted.
The impact is severe:
-
Refreshment errors — demand is aggregated incorrectly, leading to overstocking in some stores and stockouts in others.
-
Per-store mismatch — a lightweight daily-wear chain sells fast in metro stores, but bulk bridal sets dominate tier-2 markets; without granular SKUs, the system cannot capture this nuance.
-
Deadstock build-up — designs languish in certain stores because replenishment rules assume they are “generic” items.
In Indian retail, where regional preferences are strong and assortments change rapidly, clean, granular master data is the foundation of accurate refreshment and efficient replenishment. Technology can automate decisions, but without disciplined master data management, it simply automates mistakes — at scale.
Master Data Hygiene Framework for Indian Retailers
1. Foundational Attributes (must-have for every SKU)
-
Unique SKU code (no duplicates, no reuse).
-
Standardised product description (avoid abbreviations, ensure consistent language).
-
Category hierarchy defined (e.g., Jewellery → Bangle → Gold → 22K → Bridal).
-
Barcode/RFID tag linked and verified.
2. Granularity of SKU Definition
-
Size/Weight — captured in exact grams, carats, or sizes (not just “small/medium/large”).
-
Purity/Material — karatage for gold (18K, 22K), diamond clarity, fabric type for apparel.
-
Design/Style Code — captures seasonality, fashion line, or regional variation.
-
Colour/Finish — e.g., yellow gold vs rose gold; colour shades in apparel/eyewear.
⚠️ Red flag: If multiple variations are bundled under a single SKU, refreshment by store will always fail.
3. Commercial Attributes
-
Cost price, current valuation (esp. for gold/diamonds where rates fluctuate).
-
Retail price (linked to price lists, discounts, promotions).
-
Margin profile tagged (helps tools prioritise high-value SKUs).
-
Vendor/supplier code with lead time.
4. Movement & Lifecycle Attributes
-
Launch date (season / collection).
-
Expected lifecycle (fast fashion: weeks, bridal jewellery: years).
-
Sales velocity tags (fast mover, seasonal, slow mover).
-
Return / exchange rules defined.
5. Store-Specific Mapping
-
Regional preference flag (North India bridal sets vs South India temple jewellery).
-
Minimum display quantity (planogram / showcase rules).
-
Store-specific reorder point / buffer stock.
6. Compliance & Traceability
-
BIS hallmark / certification details.
-
Batch/lot number for stones & metals.
-
Regulatory attributes (e.g., HSN code, GST rate).
7. Governance & Audit Discipline
-
Periodic master data review (monthly/quarterly).
-
Data steward role defined — who owns master data accuracy.
-
No creation of SKUs without mandatory fields.
-
Integration checks with POS/ERP (to prevent mismatch).
🚩 Common Mistakes Retailers Make
-
Using generic SKUs like “Gold Chain 22K” without size/weight — destroys per-store replenishment.
-
Allowing store staff to create SKUs ad hoc — leads to duplicates and confusion.
-
Not updating lifecycle attributes — old/obsolete SKUs continue to be refreshed.
-
Ignoring regional demand patterns in master data.
Quick Self-Test for Retailers
Ask: “If I move one SKU from Chennai to Delhi, will my system tell me whether it is likely to sell, and why?”
-
If yes → SKU granularity is good.
-
If no → master data hygiene is poor, refreshment will fail.
