A retailer I know opened their fourth branch and picked an ERP because the demo looked slick and the sales rep was friendly. Six months later they were exporting stock reports from one branch, emailing them to head office, and rekeying the numbers into a spreadsheet because the system couldn't show live inventory across locations. They'd bought software that treated four branches like four separate companies. That's the exact problem an ERP is supposed to kill.
Choosing an ERP for a business with more than one location is a different job than choosing one for a single shop. The stakes are higher, the mistakes are more expensive, and the demo won't warn you about any of it. Here's how to think about it.
Start with the problems, not the features
Before you look at a single product, write down the three things that hurt right now. Not "we want to grow," but specific pain. Something like: "We can't see what's in stock at Branch 2 without calling someone," or "Month-end takes nine days because every branch closes its own books differently," or "We can't tell which location is actually profitable."
Those problems become your test. Every vendor will demo their strongest features. Your job is to drag the conversation back to your list and make them show you, live, how their system handles your actual mess. If they dodge, that's your answer.
The multi-branch questions that matter
Single-location ERP buyers can skip most of this. You can't. These are the questions that separate software that scales from software that just adds branches as an afterthought.
Can you see one branch or all branches, instantly?
You should be able to check stock at every location from one screen, and also drill into a single branch when you need to. If a customer wants an item you're out of at Branch 1, staff should see it's sitting at Branch 3 in two clicks. If that requires a report, an export, or a phone call, the system isn't built for how you work.
Does it handle transfers between branches properly?
Stock moving from one location to another is constant in a multi-branch business, and it's where a lot of systems fall apart. You want a real transfer process: goods leave one branch, sit in transit, and get received at the other, with the counts updating on both sides. If a transfer is just a manual adjustment at each end, you'll lose track of inventory within weeks.
Can head office set the rules, and branches follow them?
You want central control over pricing, product data, and permissions, with room for local variation where it makes sense. A branch manager should be able to run their day without being able to change a product's cost or delete a sales record. Ask exactly what a branch user can and can't do, and who approves what.
What does month-end actually look like?
Get the vendor to walk you through closing the books with several branches. You want consolidated financials that roll up automatically, plus a profit and loss per branch so you can see who's carrying whom. If consolidation means manually combining files, you've just bought yourself the same spreadsheet job with extra steps.
Watch out for these traps
- Per-branch pricing that punishes growth. Some vendors charge steeply for each new location or user. Model the cost at the size you expect to be in two years, not today. A price that's fine at four branches can be brutal at ten.
- "Yes, it can do that" with no timeline. Anything described as "on the roadmap" doesn't exist. Buy what works now.
- A POS that isn't part of the same system. If your sales floor runs on separate software that syncs overnight, your inventory and your accounts will drift. For retail and distribution, the POS and the back office should share one set of numbers.
- Migration nobody scoped. Ask how your existing data gets in and who does the work. Bad migration ruins good software.
Run a real pilot before you commit
Don't roll out everywhere at once. Pick one or two branches, load real products and real customers, and run them for a few weeks alongside your old process. You'll find the gaps fast, and it's far cheaper to find them in a pilot than after you've trained 60 people. Pay attention to how the vendor responds when something breaks during the pilot, because that's the support you'll live with.
The bottom line
The right ERP for a multi-branch business is the one that makes head office and every location work from the same live numbers, without extra rekeying. Judge it on your three real problems, test the branch-specific stuff hard, and pilot before you sign. Get that right and the software fades into the background, which is exactly what good software should do.