Case Study · Ethnic Wear Retail
How a 12-Outlet Ethnic Wear Chain Eliminated Dead Stock with Unified Inventory
Industry
Multi-Store Ethnic Wear Retail
Store Network
12 retail outlets across 4 cities
SKU Count
8,500+ active SKUs
Tools Deployed
Zoho Inventory, CRM, Desk, Analytics
This regional ethnic wear retailer operates 12 outlets across four cities in western India, selling sarees, lehengas, kurta sets, and bridal collections. With over 8,500 active SKUs spanning silk, cotton, and blended fabrics, the business faces seasonal demand swings tied to wedding seasons, Navratri, Diwali, and Eid. Store managers tracked stock in outlet-level spreadsheets, reorders were phone-based, and the head office had no consolidated view of what was sitting unsold across the network.
The Problem
Multi-store retail operations in ethnic wear depend on moving the right inventory to the right location at the right time. When each outlet operates as an inventory island, three compounding failures erode margins.
Dead Stock Accumulation
Without cross-store visibility, slow-moving sarees and lehengas piled up at outlets where local demand had shifted. At any given time, 22% of total inventory was classified as dead stock—items unsold for over 120 days. Annual carrying cost for this dead inventory was estimated at ₹56 lakhs across the chain.
Slow Inter-Store Transfers
When a store ran out of a popular design, the manager would call other outlets to check availability, negotiate quantities, and arrange courier pickup. This phone-based coordination took 5–7 days on average, by which time the customer had often moved on. An estimated 14% of walk-in customers left without purchase due to stockouts of items available elsewhere in the chain.
Blind Replenishment Decisions
Purchase orders were placed based on store manager intuition rather than data. Seasonal spikes around weddings and festivals caught procurement off guard, while over-ordering of off-season categories tied up working capital. The buying team had no SKU-level velocity data across the chain, resulting in ₹24L wasted annually on excess procurement of slow categories.
The Solution Stack
Four Zoho modules were configured to create unified inventory visibility across all 12 outlets with demand-driven replenishment and structured inter-store transfer workflows.
Multi-Location Stock Ledger
- Each of the 12 outlets mapped as a separate warehouse with barcode-based stock receipts, sales deductions, and transfer logging
- Real-time central dashboard showing current quantity, ageing, and reorder status per SKU per location
- Automated reorder points set per SKU per outlet using 90-day rolling sales velocity with seasonal adjustment factors
- Draft purchase orders auto-generated when stock dips below threshold, sent to procurement queue for review
Zoho Inventory multi-location tracking served as the central stock ledger, giving the head office a single view of 8,500+ SKUs across all 12 outlets in real time.
Walk-In Capture and Loyalty Pipeline
- Walk-in customers captured at billing counter with phone number, occasion type, and fabric preferences
- Automated WhatsApp alerts for new arrivals matching recorded preferences and past purchase categories
- Loyalty tier tracking based on annual spend with tier-specific discount rules pushed to POS
- Wedding-season campaign pipelines triggered 6 weeks before peak periods using regional calendar data
Zoho CRM contact capture turned anonymous walk-ins into profiled repeat buyers, enabling targeted campaigns ahead of wedding and festival seasons.
Inter-Store Transfer Ticketing
- Store manager raises a transfer request ticket specifying SKU, quantity, and urgency level
- System auto-identifies nearest outlet with available stock and routes the ticket for dispatch confirmation
- SLA timers enforce 24-hour dispatch and 48-hour delivery with escalation to regional manager on breach
- Goods receipt logged via barcode scan at receiving store, closing the ticket and updating both warehouse ledgers
Zoho Desk ticketed workflows replaced phone-based coordination with structured transfer requests, cutting average transfer time from 5–7 days to 1.5 days.
Demand Intelligence and Dead Stock Alerts
- SKU velocity heatmaps showing sell-through rate by outlet, category, fabric type, and price band
- Dead stock alerts triggered at 90 days with recommended markdown or transfer-out actions
- Seasonal demand forecasting using prior-year sales data overlaid with regional festival calendars
- Procurement recommendations generated weekly with suggested quantities per category per outlet
Before vs. After
| Process Area |
Before |
After |
| Inventory visibility |
Outlet-level spreadsheets, no central view |
Real-time dashboard across 12 locations |
| Dead stock (% of inventory) |
22% of total inventory aged 120+ days |
Under 15%—32% reduction |
| Inter-store transfer time |
5–7 days via phone coordination |
1.5 days average via ticketed workflow |
| Reorder decisions |
Store manager intuition, no velocity data |
Auto-generated POs based on 90-day rolling sales |
| Carrying cost (dead stock) |
₹56L/year estimated |
₹38L/year—₹18L annual saving |
| Stockout-driven walkouts |
~14% of walk-ins left due to stockouts |
Under 5% with cross-store fulfilment |
| Customer re-engagement |
No systematic follow-up or profiling |
WhatsApp alerts based on preferences and occasion |
Implementation Phases
The project followed a phased rollout managed by our Zoho implementation team, completing full deployment across all 12 outlets in ten weeks.
1
Inventory Master and Warehouse Setup Weeks 1–3
- Imported 8,500+ SKU records with category, fabric, colour, size, cost, and MRP attributes
- Mapped 12 outlets as separate warehouses with opening stock captured via physical audit and barcode tagging
- Configured reorder points per SKU per outlet using historical sales data from POS exports
- Built real-time inventory dashboard for head office showing stock levels, ageing, and reorder queue
2
CRM and Customer Profiling Weeks 3–5
- Configured walk-in capture workflow at billing counters to record phone, occasion, and fabric preferences
- Imported 18,000+ existing customer records from loyalty cards and POS history
- Built loyalty tier rules with automated discount push to POS based on annual spend thresholds
- Created WhatsApp campaign templates for new arrivals, seasonal collections, and occasion-based recommendations
3
Transfer Ticketing and Desk Workflows Weeks 5–7
- Built transfer request form in Desk with SKU lookup, quantity, and urgency fields
- Configured auto-routing logic to identify nearest outlet with available stock
- Set SLA timers: 24-hour dispatch, 48-hour delivery, with regional manager escalation on breach
- Deployed barcode-based goods receipt at receiving outlets to close tickets and update ledgers
4
Analytics, Training, and Go-Live Weeks 8–10
- Built Analytics dashboards: SKU velocity heatmaps, dead stock alerts, seasonal forecasting, procurement recommendations
- Conducted outlet-level training for store managers and billing staff across all 12 locations
- Ran three-week parallel period comparing spreadsheet records against system output
- Full go-live with legacy spreadsheets archived and quarterly review cadence established
Results
Within the first full year on the unified system, the retailer measured significant improvements across dead stock reduction, transfer speed, and carrying cost savings. The numbers below compare the first full year on Zoho against the prior year.
0
Reduction in Dead Stock
0
Faster Inter-Store Transfers
0
Annual Carrying Cost Saved
Inventory Health: Before vs. After
Stock Age Distribution — Before
Stock Age Distribution — After
What This Means for Multi-Store Retailers
Ethnic wear retail runs on seasonal timing and regional taste. A saree that sits unsold for four months at one outlet may be the top seller at another location 200 kilometres away. When inventory lives in disconnected spreadsheets, every store becomes a silo—overstocked in some categories, starving in others. Unified visibility does not just reduce carrying costs; it turns the entire chain into a single, responsive inventory pool where stock flows to wherever demand exists. The result is fewer markdowns, fewer walkouts, and procurement decisions driven by data instead of guesswork.
Frequently Asked Questions
How does unified inventory work across multiple retail outlets?
Each outlet is mapped as a separate warehouse in the inventory system. Every sale, return, and stock receipt updates the central ledger in real time via barcode scanning. The head office sees a single dashboard showing current quantities across all 12 locations.
What made inter-store transfers faster after implementation?
Transfers shifted from phone-based coordination to a ticketed workflow with SLA timers. The requesting store raises a ticket, the sending store confirms and dispatches, and goods receipt is logged via barcode scan, replacing a 5–7 day cycle with 1.5 day average.
How were reorder points calculated for ethnic wear SKUs?
Reorder points were set per SKU per outlet using 90-day rolling sales velocity, accounting for seasonal spikes like wedding and festive periods. When stock dips below threshold, a draft purchase order auto-generates for procurement review.
Can this approach work for retailers with fewer than 12 outlets?
Yes. The same architecture applies to chains with as few as 3–4 outlets. Smaller chains often see faster ROI because per-store setup effort is lower and inventory imbalances are easier to correct once visibility exists.
