The 12-showroom problem
A jewellery retailer scaling from one showroom to four to twelve goes through three distinct operational eras:
- 1The single-showroom era. The owner knows every piece in the safe, sets the daily rate by feel, knows every karigar personally, and approves every customer exchange. Reconciliation happens informally over evening chai.
- 1The 2-4 showroom era. Each showroom develops its own rhythm. The Banjara Hills branch likes certain designs; the Charminar branch sees different customer demographics; the Kompally branch is more wedding-driven. Inventory starts to fragment. Owners hire a "central operations manager" who lives on phone calls and WhatsApp groups.
- 1The 5+ showroom era. WhatsApp coordination breaks. Two showrooms launch the same design promotion on the same day with different prices. A customer at Showroom A asks for a piece visible in the Showroom C window through the brand's social media; the salesperson cannot confirm if it is still available. The central operations manager spends 70% of the day reconciling rather than managing.
The third era is where most chains either stagnate or get acquired. The ones that scale through it invariably do so by centralising the operating system — putting every showroom on the same ERP, with the same master data, and the same real-time view of stock, customers, and prices.
What needs to centralise (and what should not)
Centralisation done badly is more painful than no centralisation. The trick is knowing what to lift to the centre and what to leave with the branch.
Lift to the centre
- Product master and design catalogue. Every SKU, design code, weight band, and stone schedule lives once at the head office and propagates to all branches. New designs get a single code across the chain.
- Daily rate card. One MCX-linked rate card pushed at 9:30am to all 12 branches. No branch overrides allowed without a head-office approval workflow.
- Karigar master. A central registry of approved karigars with their fine-weight performance history, wastage profile, and outstanding balances. Any branch can issue gold to any karigar in the master.
- Customer 360 record. A customer who walks into the Hyderabad showroom should have her entire purchase history (from any branch) visible to the salesperson in 5 seconds.
- Compliance documentation. BIS HUID register, GST returns, TCS declarations, income-tax stock register — one source of truth.
Leave at the branch
- Showcase layout and merchandising. Branch managers know their customers. A Diwali display in Coimbatore looks different from one in Lucknow; let them choose.
- Operating hours and staffing. Local labour markets, festivals, and demographics drive these decisions.
- Branch-level promotions. Within head-office guidelines, allow branch managers to run "wedding season opening price" promotions tuned to local competition.
- Customer relationship intensity. A branch manager who hand-delivers a finished piece to a VIP customer should not need head-office approval; the system records the activity but the branch owns the relationship.
The four hard problems centralisation has to solve
1. Real-time inventory visibility
A customer at Branch A wants the silver-and-diamond cocktail ring she saw on the brand's Instagram. The brand inventory needs to instantly tell her: which branch has it, is it allocated to anyone else, can it be transferred today, and how long does the transfer take?
This is where most spreadsheet-based chains fail. A jewellery ERP solves it with per-piece location tracking: every SKU has a current location (Branch A safe, Branch C showcase, in transit, with karigar X for repair). When a sale or transfer happens, the location updates in seconds.
2. Inter-branch transfer logistics
Moving high-value jewellery between branches involves armed transit, insurance, GST documentation (interstate transfers above ₹50,000 need an e-way bill), and physical receipt confirmation. A jewellery ERP automates:
- E-way bill generation against the transfer
- Insurance schedule update
- Real-time "in transit" state with expected arrival time
- Tamper-evident sealed bag IDs scanned at dispatch and receipt
- Automatic re-balance of fine-gold balances between branches once received
Without this, a chain of 12 branches loses 2-3 working days per inter-branch transfer in coordination.
3. Pricing consistency
The biggest brand-damage risk for a multi-branch chain is price inconsistency. Two customers from the same family buying the same design on the same day at different branches must see the same price for the same metal, the same making charge, and the same stone valuation. Any variance must be explainable and approved.
A centralised ERP enforces this by making the rate card and making-charge schedule a head-office master with versioned changes. Branch overrides require approval workflow. The audit trail is permanent.
4. Karigar deployment across branches
A 12-branch chain typically works with 40-80 karigars. A specific karigar may be the brand's best heritage-jewellery designer; he can serve any branch. The central karigar master allows any branch to issue gold to him against a job ticket, while head office reconciles his consolidated outstanding fine-gold balance weekly.
Without centralisation, each branch develops its own karigar list, the brand pays for redundant relationships, and karigar pricing inconsistency creeps in.
The implementation sequence that works
A jewellery chain centralising on a single ERP should sequence the work like this:
Months 1-2 — Master data cleanup. Before any technology rollout, the head office consolidates the design catalogue, deduplicates the karigar list, and standardises the chart of accounts. Bad data centralised is worse than fragmented data.
Months 3-4 — Pilot branch. Pick one branch — usually the head-office branch — and run the full ERP. Stress-test every workflow: receiving from karigar, daily rate update, customer sale, exchange, transfer to another branch, BIS submission, GST e-invoice, monthly close.
Months 5-6 — Wave 1 rollout. Three more branches go live in parallel. The pilot branch acts as the buddy for each. By end of month 6, four branches are on the system and inter-branch transfers between them are happening live.
Months 7-10 — Wave 2 rollout. The remaining eight branches go live in batches of two per month. Hardware procurement (POS terminals, weighing scales, barcode printers, signature pads) for the rollout branches happens in parallel with training.
Months 11-12 — Optimisation. With all 12 branches live, the head office now sees real-time data for the first time. AI demand forecasting, design-mix analytics, and karigar performance analysis become possible. Working capital tied up in slow-moving SKUs across branches becomes visible and addressable.
A reasonable budget for a 12-branch chain implementing a jewellery ERP is ₹40-80 lakh including software licences, hardware, implementation services, and training. The payback is typically realised in 12-18 months from inventory optimisation, working-capital release, reduction in gold leakage, and customer-experience improvements that drive repeat business.
The strategic outcome
Centralisation is not about technology — it is about converting a federation of branches into a single operating system that scales linearly with showroom additions. Every new branch becomes a configuration exercise rather than a rebuild.
The best Indian jewellery brands of the next decade will be the ones that solved this problem early. The ones that did not will be the ones being acquired by the ones that did.
FlowSense Jewellery ERP is built for multi-branch jewellery chains in India, with centralised masters, real-time stock visibility across branches, head-office pricing governance, and chain-wide compliance reporting. If you are running 3+ showrooms on spreadsheets and WhatsApp groups, the gap between where you are and what is possible is large — and it grows every quarter.
