In this guide 6 sections
Move to multi branch retail software when branches send stock to each other, prices must change in every shop at once, or margin by branch needs phone calls. Settle item codes, price lists and transfer rules before the first branch goes live.
The signs you have outgrown shop level billing
Shop level billing works while each shop is its own business. It breaks the day one branch needs what another holds. The first sign is a phone call asking whether the other shop still has size 42 in black leather loafers.
Other signs follow. On Monday the owner exports four daily Z-reports and pastes them into one workbook. A price change takes three days to reach every barcode printer and till. No one can tell which branch earns the best margin after rent and wages.
Stock takes make it worse. Each shop finds a different count, and each branch quietly keeps its own SKU naming for the same pair of sneakers. Reports disagree. Trust drains away. A shared item master ends that argument.
- Stock moves between branches on paper notes
- Price changes keyed separately in each shop
- Monday morning spent merging branch sales files
- Different item codes for the same product
- No way to see branch stock without a phone call
Transfers and stock visibility
Transfers come first. A transfer note leaves one branch and sits in a stock-in-transit ledger. A named person then counts cartons against the dispatch manifest and posts a goods received note. Any difference is flagged that day.
Receiving matters as much as sending. The branch records shortages and damage, then closes the note. An open transfer older than three days deserves a call.
Visibility follows. A floor salesperson at the point of sale should see whether a nearby branch holds the item. That one screen saves sales that would otherwise walk out of the door.
Central pricing and branch exceptions
Head office should own the price list. It publishes the base price, a discount ceiling per cashier role and a clearance calendar. Every branch downloads the same file overnight, and each till loads it before the shutters go up.
Real shops need exceptions. Plan for them. A railway-station branch may stock a smaller range, while an outlet store carries deeper markdowns on last season’s coats and denim. Allow branch price lists, but make each one an approved override with a name and dates. Never allow a silent edit at the till.
Promotions need the same care. A festival offer carries a start time, an end time and a branch list. Every till switches together.
Margin by branch and who sees it
With one item master and one ledger, margin by branch becomes a standard report. Rent, wages, shrinkage, markdown loss and gross margin sit side by side. Branch managers see their own numbers. The owner sees them all.
Decide roles early. A branch manager approves discounts up to a set limit. A cashier never edits a cost price or voids a closed bill. An area manager might see three branches but not the rest. Only head office edits the item master.
Add a weekly branch scorecard. It shows sales per square foot, stock cover in weeks, planogram compliance, markdown share and shrinkage on one page. Managers act on a page. They ignore a thirty-page export.
What to settle before the first branch goes live
Software cannot fix inconsistent data. Clean the item master first, so each product has one SKU, one EAN barcode and one description. Agree on size and colour naming, tax rules per location, shelf-edge label format, hanger and tag stock, and a single supplier list.
Pilot with one branch for a full month, including its month-end close. Compare the closing stock and the cash-up with the old method. Go slowly. Resist the urge to rush. Then add branches one at a time, keeping the old register alive at each until its first full stock count agrees.
- One item code and barcode per product
- Head office price list and branch override rules
- Transfer note flow and receiving responsibility
- Role and permission list for every branch
- A pilot branch and a date for its month-end check
Branch rollout readiness checklist
One sheet with three blocks. The data block covers item master clean-up, SKU and EAN barcode check, size and colour names, supplier list, shelf-edge label format and opening stock count. The rules block covers price list owner, discount limits per role, transfer note flow and permissions. The pilot block lists the branch, start date, month-end close check and sign-off.
Open a blank worksheet to printQuestions owners ask
How many branches before multi branch software makes sense?
No set count applies. Two branches that trade stock already benefit from one ledger. Five branches that never share a carton may manage with separate tills for longer, provided head office can still read each branch’s Z-report.
Can each branch keep its own price list?
Yes. Keep a head office list as the base and let branches hold approved overrides. Each override needs the approver’s name and the dates it runs.
What happens if the internet drops at a branch?
Tills should keep billing offline from a local copy of the price file and push sales to the central ledger when the link returns. Ask the vendor to unplug the router during the trial and bill ten sales.
Should we pilot one branch or go live everywhere?
Pilot one branch first. A single branch exposes data and process gaps cheaply, and you fix them before the others depend on the system.