Multi-branch stock control: one live stock position across shops, stores and vans
How Kenyan retail chains and distributors keep a single trustworthy stock position across every branch, warehouse and van — transfers, counts and shrinkage included.
The moment a business opens its second branch, a quiet problem is born: there are now two versions of the truth. Each shop knows its own stock, roughly. Head office knows neither, precisely. And everything that moves between them — the lorry sent to restock, the fast-seller borrowed from the other branch, the van loaded for a route — lives in phone calls and goodwill.
By branch five, the symptoms are familiar: a customer sent to a branch that turned out to be out of stock, transfers that left one shop but never quite arrived in the system at the other, stock-takes that trigger arguments instead of adjustments, and a stock valuation nobody would sign their name under.
The principle: locations, not silos
The fix is architectural, not motivational. Every place stock can sit — shop floor, back store, central warehouse, each van — must be a location on the same ledger, so that any movement is a transfer between locations rather than an export from one system and a re-entry into another.
Once that is true, four disciplines become possible:
1. Transfers that exist in the system before the lorry moves
A transfer should be requested, approved and documented before goods leave — then tracked in transit until the receiving branch confirms it. In-transit is the state most systems skip, and it is exactly where stock disappears: goods that left branch A and were never received at branch B are invisible unless the system holds them somewhere in between.
2. Stock that moves when goods move
If inventory is deducted when the invoice is raised but the customer collects on Thursday, the system and the shelf disagree for three days — and both counts and reorder decisions are wrong for those three days. Dispatch-controlled stock, with a gate document per collection, keeps the books and the yard in lockstep.
3. Counts that don’t close the shop
Blind counts — where the counter writes what they see without seeing what the system expects — remove the temptation to “count to the number.” Reconciling against pending movements (uncollected sales, in-transit transfers, unreceived deliveries) means trading can continue during the count instead of shutting the branch for a day.
4. Shrinkage with a name on it
The gap between counted and expected is not one number; it is a classification: expiry, damage, theft, counting error, paperwork lag. Posting shrinkage to the ledger with a reason is what turns stock loss from an annual shock into a weekly, managed metric — per branch, per category, per person on shift.
What head office should see
The test of multi-branch stock control is a single screen answering: what do we hold, where is it, what is in transit, what is committed to customers but not yet collected, and which lines are below reorder at which branches. If assembling that answer takes phone calls, the system is not doing its job.
This is precisely how Asili treats stock — branches, warehouses and vans as locations on one ledger, approval-gated transfers with in-transit tracking, blind counts that reconcile against pending movements, and shrinkage posted with reasons. See it on your own product list: try the live demo or write to begin@ipos.co.ke.