Moving Stock Between Branches Without Losing Accountability

A second branch changes the meaning of stock control. In one shop, a missing carton can usually be traced by walking to the shelf, asking the cashier, or checking the store room. In a multi-branch business, the same missing carton can sit between three explanations: dispatched but not received, received but not counted, or quietly lost on the way.

The answer is not to stop transferring stock. Transfers are how growing retailers balance demand, rescue a branch that is about to stock out, and move slow items to a location that can sell them. The answer is to stop treating a transfer as a phone call and start treating it as a controlled stock movement.

Why branch transfers fail when they live in calls and notebooks

The common informal workflow sounds harmless. Branch A asks Branch B for ten cartons. Someone packs the stock, sends a driver, and posts a message saying the goods have moved. Later, Branch B says only nine cartons arrived. At that point the business has no clean source of truth. Was the request wrong? Was the dispatch short? Did the driver deliver less than was loaded? Did the receiver count badly?

That is why a stock transfer needs statuses and evidence. GS1's traceability work is built around the idea that products, locations, parties, and events should be identified so that movement can be followed through the supply chain. A retailer does not need a global traceability programme to learn from that principle. It simply needs every internal transfer to say what moved, from where, to where, who handled it, and when each step happened.

A transfer is not complete when stock leaves the first branch

One of the most expensive mistakes in branch operations is treating dispatch as completion. Dispatch proves the sending branch says the stock left. It does not prove the receiving branch accepted it. Between those two moments, the stock should sit in an in-transit status. That protects both teams: the sender is not blamed for stock still physically on the road, and the receiver is not shown stock it cannot yet sell.

This also keeps reporting honest. If the business runs perpetual inventory, the inventory subledger should preserve the movement evidence by SKU, quantity, source branch, destination branch, actor, timestamp and transfer reference. Finance teams care about this because inventory reports must tie back to source movements, not to memory.

Variance review is where accountability becomes real

A variance is not automatically theft, and it should not automatically become a silent adjustment. Sometimes the sender picked the wrong unit of measure. Sometimes the receiver counted a mixed carton as one item. Sometimes there is breakage, expiry segregation, or a genuine short delivery. The point of the system is to force a reason before the transfer is closed.

A controlled variance review should capture the expected quantity, received quantity, difference, reason code, supporting note or photo where useful, and approver. Only after that review should the stock record be corrected. This is the difference between a stock system and a spreadsheet that happens to contain stock numbers.

What growing retailers should measure

Once transfers are structured, management gets useful questions. Which branch requests emergency stock most often? Which route produces repeated variances? Which item categories move because demand is high, and which move because buying was poorly planned? Which branch receives slowly and leaves stock trapped in transit?

These questions are not only for East African retailers. Any multi-location business can lose margin when the transfer process is informal. The same control pattern applies to boutiques, pharmacies, supermarkets, spare-parts shops, salons with product stock, and franchise networks that rely on head office or a central store.

Process: The clean branch transfer workflow

Controls: Minimum controls before a transfer is closed

• Every transfer has a reference number and source/destination branch.
• Each line records SKU, quantity, unit, batch or expiry data where relevant.
• Dispatch and receiving are separate actions by named users.
• In-transit stock is visible but not treated as sellable stock.
• Short, excess, damaged or expired items require variance review.
• Closed transfers remain traceable in the audit log and stock movement history.

Common questions

Sources and research notes

• GS1 Global Traceability Standard: Used for the traceability principle: identified products, locations, parties and events make movement reviewable.
• IAS 2 Inventories - IFRS Foundation: Used as accounting context for treating inventory as a controlled asset with cost and write-down considerations.
• Chwezi accounting doctrine - inventory and retail controls: Used for source evidence, variance approval, subledger tie-out and audit-log discipline.