How to Reduce Stock Leakage in a Multi-Store Garment Chain
Stock leakage silently destroys margins in garment retail. These are the five places it happens most — and how to close each gap with the right process and software.
Stock leakage — the gap between what your system says you have and what you actually have — is one of the most damaging problems in multi-store garment retail. Unlike a cash discrepancy which shows up immediately, stock leakage compounds silently. By the time you audit, it's already cost you tens of lakhs.
In Indian garment chains, the industry average for shrinkage runs between 1.5% and 3% of revenue. For a chain doing ₹5 crore annually, that's ₹7.5–15 lakh walking out the door every year. The good news: most of it is preventable with process and the right software.
The 5 Biggest Sources of Stock Leakage in Garment Retail
1. Inbound — Supplier to Warehouse
The first place stock goes missing is at the receiving dock. Supplier sends 500 units on the invoice. Your warehouse receives 480. Without barcode-level GRN confirmation, the 20-unit gap gets absorbed silently. The system books 500 because the invoice says 500.
Fix: mandatory barcode scan at GRN. Every item scanned on receipt. Quantity accepted in the system = quantity actually scanned. Invoice vs. GRN discrepancies flagged automatically and escalated to purchase team.
2. Warehouse to Store — Dispatch Leakage
Stock is packed for dispatch at the warehouse. By the time it arrives at the store, some items are missing — misplaced in the warehouse, loaded into the wrong delivery, or removed in transit. Without scan confirmation at the store end, this disappears into the stock count.
Fix: formal IST workflow with barcode confirmation at dispatch AND at receiving. Discrepancies between dispatched and received quantities are automatically logged as a discrepancy report, not silently adjusted.
3. Store Floor — Shoplifting and Staff Theft
This is the most discussed form of shrinkage but often not the biggest. In garment retail, shoplifting runs 0.3–0.8% of revenue — significant, but usually less than process-based leakage. Staff theft in garments typically involves removing tags and billing at reduced prices, or billing an exchange without actually receiving the returned item.
Fix: POS-level controls — require manager override for price changes, track exchange transactions separately, alert on excessive discounts per staff member. CCTV and anti-theft tags address external theft.
4. Returns and Exchanges — The Invisible Leakage
Customer returns and inter-store exchanges are the most underestimated source of leakage. A customer returns an item. The salesperson issues a refund. The item goes back to the stockroom — sometimes without being scanned back in, sometimes counted as available even when damaged, and sometimes processed as a credit for an item the store never actually received.
Fix: every return must be scanned — the barcode confirms the item is actually being received back. Returns should land in a "pending QC" state, not immediately back to sellable stock. Damaged returns need a separate write-off workflow.
5. Stock Audit — Phantom Stock That Never Existed
Many garment chains conduct stock audits and find that the variance is partially explained by data entry errors that accumulated over months. A GRN entered with 5 extra units here. A transfer that was recorded but not physically sent there. These phantom stock entries mean your reported stock was never real.
Fix: cycle counting — frequent partial audits of specific categories rather than one massive annual audit. Any variance above a threshold should require explanation before being adjusted.
Building a Leakage Control System
| Control Point | Process Required | System Feature Needed |
|---|---|---|
| Supplier receipt | Barcode scan per item at GRN | GRN with scan confirmation + auto invoice reconciliation |
| Warehouse dispatch | Pick-list generation + scan at pack | IST with pick-pack-dispatch workflow |
| Store receipt | Scan confirmation against IST document | Mobile GRN at store end |
| POS billing | No manual price override without manager code | Role-based POS permissions |
| Returns | Scan-in + QC status | Returns with condition tagging |
| Stock audit | Cycle count with variance approval | Physical stock count module |
What Results Look Like After Proper Controls
Garment chains that implement systematic leakage controls with software support typically see shrinkage drop from 2–3% to 0.8–1.2% within 6 months. For a mid-size chain doing ₹3 crore in revenue, that's ₹4–6 lakh saved annually. The investment in software that enables these controls typically pays back in the first 3–4 months.