I build retail operations systems for multi-store businesses in India and the UAE: billing, live stock across branches, purchase and supplier management, GST or VAT compliance, and a phone-first owner dashboard.
Why does “aaj kitna hua?” take three phone calls?
Because multi-store retail fragments its own truth. Each store’s billing is an island. Stock exists as totals nobody trusts — the sheet says forty, the shelf says thirty-two, and which store the difference walked out of is a genuine mystery with a genuine cost. Purchases follow instinct rather than sell-through, so the slow item keeps arriving and the fast one keeps running out. And the customer credit book lives in the manager’s memory, which resigns when he does.
None of that is unusual. It is what happens when a business grows past the point where one person can hold it, without the systems growing at the same time. The tell is simple: if the day’s number requires phone calls, the chain is running on people rather than records.
What does the system cover?
- Fast billing. Barcode or quick-key, offline-capable, GST e-invoicing for India (mandatory above the ₹5-crore threshold — cbic.gov.in) and FTA VAT for UAE stores.
- One stock truth. Store-wise levels, inter-branch transfers tracked as movements, and variance reports after every count — the sheet-versus-shelf gap named per store and per item.
- Purchase discipline. Reorder points computed from actual movement, supplier ledgers with payment ageing, and rate history that survives the buyer’s day off.
- Customer credit. Balances and ageing in the system, with statements — credit on trust, records on Postgres.
- Owner dashboard. Sales, margin, dead stock and dues, per branch and consolidated, on a phone.
The number most chains have never seen
Dead stock, by store, by age. Almost every retailer can tell you their best sellers; very few can tell you what has not moved in ninety days and what it is worth. That capital is sitting on shelves, and it is usually the largest single sum available to release without selling anything new.
The second number is transfer-worthy stock: the item that is dead in Borivali and selling in Thane. Without one stock truth, that opportunity is invisible, and both stores keep ordering. With it, the evening transfer approvals become a routine that converts stranded capital into sales — no marketing, no discount, just moving what you already own to where it is wanted.
Both numbers come from the same foundation: stock recorded as movements rather than maintained as totals. Once every unit’s journey is a fact — received here, transferred there, sold at this counter — dead stock and transfer opportunities are queries you can run on a Tuesday evening, not projects you commission.
The deployable version of this — pilot store, then waves — is the Retail ERP; the systems-buyer’s architecture view is /industries/retail-systems.
Related reading
/products/retail-erp — the productised build · /industries/retail-systems — the architecture view · /products/distribution-erp — the wholesale sibling · /industries/jewellery — a specialised retail vertical
Tonight’s glance
Today’s sales, by store, with margin — without calling anyone. If that is not possible right now, that is the entire pitch, and the pilot store proves it in two weeks. /contact.
Questions I actually get
We sell unlabelled items — is barcode mandatory?
No. Quick keys and unit shortcuts bill loose and unlabelled items in seconds, with barcode used where it exists. A billing screen that only works with barcodes is useless in half of Indian retail, so it is built the other way around.
Franchise stores under one brand?
Per-franchisee ledgers, royalty computation and one brand-level view. Franchise relationships fail on settlement disagreements more often than on merchandising, and settlement disagreements are a records problem.
Dubai and India stores in one business?
One system, two tax brains — GST for the Indian entity, FTA-compliant VAT for the UAE one, with per-entity books and a consolidated owner view. That combination is common among corridor businesses and badly served by software built for one market.
What happens during a power cut?
Billing continues offline and syncs when the connection returns; stock conflicts from that window resolve by rule with a variance trail. Power cuts are a feature of the market, so they are a feature of the product.
How do we manage customer credit?
In the system rather than the manager's memory — balances, ageing and statements you can actually send. Credit extended on judgment is fine; credit recorded only in someone's head is a resignation risk.
How long does a rollout take?
Pilot store in about two weeks, then waves. Never big-bang, because retail cannot pause for software and a bad first week poisons adoption across the chain.