How to control inventory across multiple branches
A practical guide to shared product records, stock in transit, branch permissions, replenishment and comparable multi-site reporting.

Multi-branch inventory becomes controllable when every location uses one product definition, transfers remain visible while in transit, local staff have clear permissions, and head office compares branches using the same rules.
Create one product truth before joining branches
Branch control starts with shared product codes, units, categories and costing rules. If the same item has a different name or pack size at each location, a central dashboard only adds the wrong figures faster.
Choose which fields head office owns and which a branch may change. Prices, supplier terms, reorder levels and local descriptions do not all need the same owner, but every exception should be deliberate.
Keep transfers visible between dispatch and receipt
A transfer should not disappear from the sending branch and appear instantly at the receiving branch. It is stock in transit until the destination confirms what arrived. Record who dispatched it, who received it, the time, quantity and any difference.
That one state prevents the common argument where both branches believe the other branch owns the shortage. It also gives management a live list of transfers that have taken too long.
Stock in transit is a real business state. Treating it as a spreadsheet gap hides loss and delays replenishment.
Separate local speed from central control
A branch must be able to sell, receive and count without waiting for head office on every routine action. Central control belongs around high-risk decisions: changing prices, approving large adjustments, opening credit, writing off stock or overriding a limit.
Use roles and value thresholds, then keep the author, time and reason for every exception. The goal is not to slow the branch; it is to make unusual decisions visible while normal trade keeps moving.
Replenish from demand instead of the loudest phone call
Set a target or minimum by product and location, because branches do not sell at the same rate. Replenishment should consider on-hand, reserved, incoming and in-transit quantities before suggesting a purchase or transfer.
Use slow-moving and ageing views beside shortage alerts. Buying more of what sells prevents stockouts; stopping purchases of what does not sell releases cash trapped on shelves.
Compare branches on definitions everyone shares
Sales alone do not tell you whether a branch is healthy. Compare gross margin, stock turns, shrinkage, returns, overdue credit, cash variances and transfer delays using the same date, currency and costing rules.
A branch score should lead to a question and an action, not a public league table. The useful outcome is knowing where to investigate, what support a manager needs and where cash can be released.
Take this checklist into the demo
- One product and customer master
- Stock-in-transit state with dispatch and receipt evidence
- Local roles with central approval thresholds
- Location-specific replenishment rules
- Last-synced visibility for every site
- Comparable branch margin and stock reports
Straight answers before you commit.
How should stock transfers between branches work?
The sending branch dispatches the quantity, the system marks it in transit, and the receiving branch confirms the actual quantity. Differences stay visible with their author, time and reason.
Can branches keep working when head office is offline?
A multi-site system should define which local workflows continue and show the last successful synchronisation. Test the exact selling, receiving and transfer behaviour during the buying process.
Which Corelith plan supports multiple branches?
Grow includes up to 3 sites for US$99 per month and Scale includes 6 sites for US$199 per month. Current details are always on the pricing page.