Inter-Branch Transfers: Why Stock in Transit Disappears From Everyone's Numbers

A part leaves the warehouse at Branch A on Tuesday morning. It is scanned out, loaded into a courier's van, and sent to Branch B, where a technician is waiting to finish a job. On Thursday the technician asks where it is. Branch A says it shipped. Branch B says it never arrived. The ERP shows nothing useful at either site.

This is the quiet problem with inter-branch transfers. Between the moment stock leaves one location and the moment it is received at another, it often belongs to no one. It is not available to sell, it is not in either branch's on-hand figure, and it is not clearly part of anyone's valuation. For a day, or a week, it is invisible.

This article explains why stock in transit disappears, how to measure how much of it you have, and what it costs. It then sets out how to fix the inter-branch stock transfer process so that availability and valuation stay correct, and how The Ninjaz Group approaches the problem in practice.

Why in-transit stock becomes nobody's stock

Most transfer processes are two separate transactions pretending to be one. Branch A records an issue, and its quantity goes down. Branch B records a receipt, and its quantity goes up. Between those two events nothing holds the item. Depending on configuration, it may sit in a generic transit location that nobody reports on, it may be deducted from the source with no matching addition, or it may stay on the source's books until someone remembers to post the movement.

Each of those leaves a different hole:

• If stock is deducted at dispatch and only added at receipt, availability drops everywhere. A sales desk at a third branch sees zero and quotes a long lead time on something that is in a van across town.
• If stock stays on the source's books until receipt, the source branch keeps promising an item that is physically gone.
• If a transit location exists but sits outside standard reports, the value is on the balance sheet but absent from every operational view.

The gap also lasts longer than it should because transfers are low-priority work. A sale has a customer waiting. A transfer has an internal requester who may not chase it. Receipts are posted late, partial deliveries are booked as complete, and discrepancies go unnoticed until the next stock count.

Lost stock in transit is rarely a dramatic theft or a courier disaster. It is usually a pile of small administrative lapses that nobody sees as a group.

How fragmented systems create the gap

Consider a group with twelve locations. All of them use the same ERP, but three high-volume sites run a separate warehouse management system. The automotive branches keep parts stock in a dealer management system (DMS). Dispatches go out through a courier booking portal. Finance closes each month from ERP exports.

Now follow one transfer through that landscape.

Branch B raises a request in the ERP. Branch A's WMS picks and packs it, and the pick confirmation reaches the ERP in a nightly batch. Someone books the courier in the portal and pastes the tracking number into an email, or a free-text note, or nowhere. The parts counter at Branch B quotes from DMS stock, which knows nothing about the transfer until receipt. Finance sees the ERP issue posted, but the value of goods in transit is lumped into a single account with no ageing and no link to individual transfers.

That is four systems giving four different answers to "where is it, and who owns it?" None of them is wrong by its own logic. The failure is that none holds the shared status. Multi-location inventory visibility breaks down not because data is missing, but because the data lives in places that disagree about the lifecycle of a transfer.

Courier tracking makes it worse. The carrier knows exactly where the parcel is, but that knowledge stays in the carrier's system. The people who need it, such as the technician, the parts counter and the stock controller, are in other systems entirely. So they phone, email, or walk to the stockroom and look.

What it really costs

The cost rarely appears as a line item, which is why it persists. It shows up in several places at once:

• Time. Staff spend hours chasing transfers by phone and email. The one person who knows which courier contact to call becomes the unofficial tracking system, and the process stops working when they are away.
• Inventory. A receiving branch that cannot see an incoming item may buy it again from a supplier. Later there are two units, one of them surplus, and the original transfer may still be unreceived.
• Lost deals. A counter or sales desk that cannot promise a date loses the sale to a competitor who can. The stock existed. The group simply could not say so.
• Mistakes. Valuation is wrong at month-end, shortages are written off at count with no trace of which transfer they came from, and branches dispute who bears the loss.
• Burnout and customer frustration. Customers get vague answers and staff absorb the blame. Over time, the people who handle transfers become the people who apologise for them.

The valuation effect deserves particular attention for finance and executive teams. Goods in transit are an asset the business owns. If they sit in an unreported location, or are double-counted in two branches, the figures leadership uses for margin, working capital and branch performance are quietly off.

How to diagnose it in your own network

You do not need new software to find out how serious the problem is. You need a few hours and access to transfer data. Work through this sequence:

1. List open transfers by age. Pull every transfer dispatched but not received, and sort by days since dispatch. Anything older than your slowest legitimate courier route deserves a look.
2. Reconcile the transit balance. Compare the value held in your in-transit location or account with the total value of transfers you can prove are genuinely open. The difference is your unexplained stock.
3. Trace a sample end to end. Take twenty recent transfers and record the time at every handoff: request, approval, pick, dispatch, delivery, receipt posting. Note where the longest waits sit.
4. Ask the branches. Ask three branch managers how they would find out where a transfer is right now. If the answer is "call someone," you have your finding.
5. Test availability. Check what a sales desk sees for an item that is currently in transit. Is it shown as unavailable, available at the source, or visible as incoming?
6. Review count adjustments. Look at recent stock count write-offs and check how many involve items that were recently transferred.

Most groups find that the problem is concentrated in a few routes, a few product types, or a few branches that post receipts late. That is good news, because it means the fix can start narrow.

Steps to tighten the transfer process

Whatever systems you run, five decisions improve the inter-branch stock transfer process.

Pick one ownership rule and apply it everywhere. Stock either belongs to the sending branch until received, or it belongs to the group in a defined in-transit state from dispatch. Either can work. Mixed practice across branches cannot, because valuation and availability then follow different rules depending on who handled the transfer.

Define a single status model. A workable set is requested, approved, picked, dispatched, in transit, received, discrepancy and closed. Every system and every branch should use the same words with the same meaning.

Make the courier reference structured data. A tracking number typed into a note is invisible to everything else. Held as a field on the transfer record, it can be used to check progress and raise alerts.

Set expected-arrival times and escalation rules. Each route has a normal transit time. When a transfer passes it, someone should be notified automatically, not discover the delay at month-end.

Handle partial and damaged receipts as first-class events. If five of six items arrive, the process should record five received and one in discrepancy, with an owner and a deadline. Booking all six and sorting it out later is how stock quietly vanishes.

These steps work on paper. They work much better when the systems involved can share the status instead of each keeping their own copy.

How The Ninjaz Group approaches it

Ninjaz does not ask a group to replace its ERP, WMS or DMS to solve this. The work follows the Blueprint, then Build & Link, then Operate model.

In the Blueprint stage, we map how a transfer actually moves through the operation. That means finding where the handoffs are, where data goes stale, where the same status is re-keyed by hand, and where value goes unreported. The client keeps that map whether or not they continue with us.

In Build & Link, Managed Link comes in: the integration layer Ninjaz builds, owns and maintains between the systems you already have. The Ninjaz Operating Platform connects to the ERP, the warehouse and inventory systems, the DMS and the finance system. Where courier tracking data is available, it can be brought in as well. The platform's unified data layer then holds one record per asset and order, so a transfer is a single record with one shared status rather than a set of unconnected entries.

In practice, that makes several things possible:

• Inventory and asset views across sites can show in-transit stock as its own quantity, with origin, destination, dispatch time and expected arrival. A parts counter can see that an item is on its way instead of reading zero.
• Valuation stays attached to the transfer. Finance can see what is in transit, from where, and for how long, rather than one undifferentiated balance.
• The Command Center can raise alerts when a transfer passes its expected arrival time or sits unreceived, and show live KPIs across locations.
• Workflow automations can start a follow-up when a delivery is confirmed but the receipt has not been posted, or when a partial receipt creates a discrepancy.
• Team chat boards tied to records keep the conversation about a missing item attached to the transfer itself, not scattered across personal inboxes.
• Roles and an audit trail show who changed a status and when, which settles the question of where responsibility sat when a loss turns up.

After go-live, Managed Business Operations can keep the connections healthy, so the shared status does not drift as systems are updated.

What this will and will not do

It helps to be clear about the limits. A shared transfer status does not stop a parcel from being damaged or a receiving clerk from skipping a scan. People still have to dispatch and receive correctly. Courier data quality also varies, and some carriers provide far richer tracking than others, so the Blueprint stage has to check what is actually available for each route.

What the approach does is remove the ambiguity. When every system and every branch can see the same status, a late or missing transfer becomes visible within hours, and someone owns it. The ERP and finance system remain where they are. What changes is that they, along with the warehouse, the DMS and the people behind them, finally agree on where the stock is.

The most dependable gains come from the groups that agree on the ownership rule and the status model first, then connect the systems to reflect them.

Where to start

If you suspect stock is disappearing between your sites, run the diagnostic above on your oldest open transfers. The result will tell you whether you have a handful of late receipts or a structural gap in how your systems share information.

If it is the second, we can help you map it and close it. You can book a consultation to talk through your transfer flows with our team, or see the platform demo to look at how inventory and asset views across sites work in practice.