Leak 25 · Inventory & Working Capital - Poor inventory transfer decisions
Stock shipped between branches to cover a shortage, then shipped back when the shortage is over. Freight both ways, and no one is counting.
Diagnostic note. Symptoms, required records, an initial check, and possible fixes. This shorter note does not include a full worked example.
What is it?
Transfers are the fix for branch-level stock imbalances, and they are useful. They become a leak when they are reactive, frequent, and small: a single item shipped between branches to fill one order, repeated many times a week, sometimes reversing an earlier transfer. Each move costs freight and handling that a better stocking decision would have avoided.
- Family
- Inventory & Working Capital
- Primary owner
- Inventory Manager
- Secondary owners
- Branch Managers, Operations Manager
- Primary impact
- Freight / inventory
- Typical data source
- ERP transfer orders, freight on transfers, branch stock levels
- Detection difficulty
- 30-day measurability
Ask yourself
Do you know your annual inter-branch transfer count, the freight it costs, and how much of it moves stock that later transfers back?
Yes, partially, no, or don’t know. “Don’t know” is the most useful answer, because it points at the test below.
What does it look like?
Warning signs. None of these proves the leak exists. They tell you where to look.
- High transfer counts with low average transfer value.
- The same item transferring in both directions within a quarter.
- Transfer freight not tracked separately from customer freight.
What data do I need?
The minimum viable set. Most of it is already in your ERP.
| Field |
|---|
| Transfer orders: item, from, to, quantity, date, freight |
| Branch stock and demand for the transferred items |
The initial check
Start with a small sample. Gathering the exports, agreements, or observations is separate from running the check; agree that work with the person who owns the records.
- 1Export last quarter’s transfer orders with freight cost where available.
- 2Count transfers and sum freight. Then find items that moved in both directions.
- 3Estimate handling time per transfer and add it.
Transfer cost = Σ (freight + handling time × loaded rate); reversal share = round-trip transfers ÷ all transfers
Then ask one question: Would a stocking change at either branch have removed the need for the round-trip transfers?
How much could it be costing us?
A conservative range, not a headline. The goal is a number management can trust enough to investigate.
Annual transfer cost × share of transfers that a stocking rule or consolidation window would have avoided
Common root causes
Fixes fall into three layers. Not every problem needs software, and almost none needs AI first.
- Process
- Transfers are requested ad hoc with no consolidation or review.
- Data
- Transfer freight is buried in general freight expense.
- Technology
- No scheduled transfer runs or suggested transfers based on network stock.
What should we do?
Start with the simplest intervention that could solve it. Move down the list only if the one above is not enough.
Level 1
Visibility
A monthly transfer report with count, value, freight, and reversals.
Level 2
Policy
Scheduled transfer runs and a minimum transfer value, with exceptions for customer-committed orders.
Level 3
Workflow
Suggested rebalancing transfers generated from network stock and demand, consolidated into the scheduled run.
Where AI helps
- Predicting branch demand well enough to rebalance ahead of shortages rather than after.
Where AI probably doesn’t
A scheduled transfer run and a stocking policy fix most reactive transfers.
Before you call it a leak
- A transfer that saves a sale is worth the freight. Measure against lost sales, not just transfer cost.
Think this might be happening in your business?
Turn the finding into a next step.
If the numbers say there is something there, send us what you found and we will help you decide whether it is worth a full investigation. No transaction files needed for that conversation.
Related leaks
- Leak 24 · InventoryInventory duplicated across branchesFive branches each hold three months of a slow item. The company holds fifteen months. Each branch manager is being sensible.
- Leak 23 · InventoryStockouts on high-value SKUsThe fast, high-margin item is out again. The customer buys elsewhere, and the sale is never recorded because it never happened.
- Leak 10 · FreightExcessive split shipmentsOne order, three boxes, three carrier charges, one freight charge to the customer. Backorders and branch stocking decide it, not anyone in particular.
Let’s start with one thing.
What would better performance look like?
Bring a result you want to improve, a symptom, or a workflow you already understand. You do not need to know the bottleneck yet. We’ll help choose what to investigate first.
No transaction files needed for the first conversation.