How to run multiple branches from one place without losing control
By Al-ArjanUpdated: 8 min read
The problem: one file per branch
When each branch runs its own program or file, numbers reach management late and in different formats, nobody knows one branch has surplus of an item another lacks, and manipulation is hard to spot.
Principles of central control
- One database, unified items
- Centrally approved prices and discounts
- Permissions stopping branches editing others’ data
- Transfers with dispatch and receipt documents
- A daily consolidated report: sales, cash, critical stock
- Offline branch operation with auto-sync
Want the cost and timeline for your specific project?
Get a quote in two minutesWhich permissions does each branch role need?
Most branch leaks come from permissions wider than needed, not from the system itself. The rule: each employee sees and edits only what belongs to their branch and job, and every exception (a discount above the limit, a return without an invoice, a price change) needs an approval that records who approved it and when.
A common practical split: cashiers sell and print but can’t change prices; the branch manager receives goods, approves returns and sees their branch’s reports; the storekeeper records movements but doesn’t see profit; head office sets prices and items and sees every branch. An audit log that keeps who changed what and when is what makes these rules reviewable.
How should stock transfers between branches be documented?
A documented transfer has three steps: a dispatch document at the sending branch that deducts the quantity and marks it “in transit”, a receipt at the receiving branch by count or barcode, then settlement of any difference between sent and received with a document that carries a reason and an approval. That way goods don’t vanish between two branches, and a gap shows up with a name and a date instead of in a stock count months later.
- A dispatch document with a serial number
- An “in transit” state counted at neither branch
- Receipt by count or barcode
- Difference settled with a reason and approval
- A weekly report of open transfers
What should the consolidated management reports include?
A daily management report doesn’t need dozens of figures. Five are enough for most multi-branch companies: sales and gross margin per branch, actual versus expected cash in each till, items below reorder level, open transfers between branches, and exceptions (discounts, returns, price edits) with the names of who approved them. With dinar and dollar, every figure should show in both currencies or in a base currency with a stated exchange rate.
That is what ERP accounting software usually builds on top of the single database; what each branch’s checkout needs is covered in accounting and POS systems.
Frequently asked questions
Can each branch have its own prices?
Yes, if you want, while the decision stays with head office.
What happens if a branch loses internet?
In a system built for offline work the branch keeps selling and receiving locally with document numbers that never collide, then syncs everything with head office when the connection returns, and the consolidated reports update after the sync.
Do I need a server in every branch?
Usually not. The common setup today is one central or cloud server, with branch devices keeping a local copy that’s enough to work offline. A local server only helps in a large branch with many devices and a very weak connection.