Fixing inter-branch stock transfer mismatches between two sites

What the mismatch usually means

Most transfer mismatches are not theft. They come from timing and process. Stock leaves Branch A on Monday, the van arrives on Wednesday, and the receiving clerk counts on Friday after two other deliveries have been put away. If nobody has a record of what is in transit, the two branches end the week with different numbers for the same goods.

Four causes account for most gaps. The first is a dispatch note that was never matched to a receipt. The second is a partial receipt, where a line was keyed as received in full. The third is damage that was never recorded, so the item silently drops out of the count. The fourth is a wrong item or wrong size that got put away as the item on the note. Each one looks identical on a stock report unless someone compares the two documents.

Inventory-loss research points the same way. Appriss Retail's 2026 Total Retail Loss Benchmark Report, which covers 2025, attributes about 21 percent of the $90 billion in total shrink to inventory errors, and names distribution-centre mispicks and transfer errors as a source. The report covers retail in general, not your business, so treat the share as a sign of where to look rather than a forecast for your branches.

What the mismatch costs

No public study gives one dollar or pound figure per transfer that fits every business, so the honest way to price the problem is with your own numbers. Three cost lines matter.

The first is the stock itself. A short shipment of goods bought at a known cost is a direct loss if it cannot be found or recovered from a carrier. The second is lost sales. If the receiving branch believes it has stock and does not, a customer order goes unfilled, or the branch sells a substitute at a lower margin. The third is staff time. Someone has to find the dispatch note, call the other branch, recount the shelf and update the record. That work repeats for every open transfer.

A worked example shows the arithmetic. Suppose 40 units leave a branch at a landed cost of 12 each, and 15 of them never reach the shelf. The direct loss is 180 in your currency. Add two hours of a branch clerk's time across three phone calls and a recount, and the true cost is the stock plus the hours. Across a network that moves hundreds of transfers a month, a small error rate in each one adds up. The free audit measures your actual transfer volume and error rate, which is the figure that matters for your business.

The manual way and the automated way

The table below compares how a typical branch network handles this work today with a setup that matches records automatically. The automated column describes what the system is built to do. It does not promise a particular result for your business.

The manual way is cheap to start and works when the network has two or three branches and a handful of transfers a week. It breaks as volume grows, because the matching depends on someone remembering to do it.

How to automate it, step by step

The steps below assume you already have a stock system, even a basic one. If you do not, start with step one on a shared spreadsheet and move to a system later.

1. Give every transfer one reference number. Use the same number on the dispatch note, the transfer record and the receipt. Without a shared reference, nothing can be matched automatically.
2. Create the transfer as an in-transit record at dispatch. In NetSuite, for example, a transfer order moves the quantity out of the source location when it is fulfilled and holds it as in transit until the destination receives it. Oracle's NetSuite help documentation describes this two-stage flow, and a receipt must be entered at the destination before the stock counts there.
3. Require the receiving branch to enter a count against the transfer reference within a set time, for example by the end of the next working day. Set the deadline in the rule, not in someone's memory.
4. Use OCR for paper notes. Where a branch still receives paper delivery notes, a document-reading tool can pull the line items and quantities into the receipt form. The clerk checks the extracted numbers before saving. OCR reads printed text well and handwritten text less reliably, so check handwriting by hand.
5. Automate the comparison. Each receipt line is compared with the dispatch line. Any difference, including a short or over count, creates an exception with the transfer reference, item, both quantities and the two branch names.
6. Send scheduled reminders through the channel the receiving branch actually uses. Email works everywhere. In many markets, WhatsApp is the faster channel for branch staff. Under Meta's WhatsApp Business Platform, messages that start a conversation outside an open customer service window must use a pre-approved template. Meta's documentation describes these as the only message type allowed in that case. The On-Premises API was sunset on October 23, 2025, so new builds should use the Cloud API. Templates need approval before first use, and unverified accounts face lower template limits, so plan the approval time in advance.
7. Use a language model to draft the chase message and summarise the open list for the owner. The model writes the wording from the exception data. It should not decide whether stock is missing. That decision belongs to a person.
8. Send a daily or weekly digest of open transfers older than the agreed deadline to the operations head. Escalate by a rule, for example any gap over a set value goes to the owner the same day.

Connecting these steps depends on the tools you already have. A stock system with transfer orders and a receipt step covers most of the work. Accounting software such as Tally, Zoho Books or QuickBooks can receive the adjustment entries, but the link between the stock system and the ledger needs checking with whoever keeps your books.

What breaks and how to prevent it

The most common failure is a branch that never enters the receipt. The system then shows stock in transit forever, and the report looks like a loss when it is really a missing count. The prevention is the deadline and the daily digest. Make the open list visible to a named manager.

The second failure is a receipt entered in full when only part of the goods arrived. Some systems do not allow partial lines to be received, as NetSuite's documentation notes for transfer order lines, so the branch must either receive the whole line or the team must split the transfer. Decide the rule before go-live, not during the first dispute.

The third failure is bad matching caused by unit mismatches. One branch counts cases, the other counts units. Lock the unit of measure for each item across branches before any matching runs. Otherwise every line shows a false gap.

The fourth is over-reminding. A branch that receives six automatic messages a day stops reading them. Limit reminders to one or two per open item, then escalate to a person.

The fifth is a damage record that nobody closes. A damaged item should have its own status, a photo or note, and an owner. Otherwise damage gets counted as a shortage and the wrong person chases it. Automation can route damage to the right person. It cannot inspect the goods, and a photo does not prove the cause of damage. Someone on site still has to judge it.

Finally, carriers. If a delivery was short or damaged in transit, the claim is made to the carrier under its own terms, and the window for filing may be short. Automation can flag the exception on the day it appears so the claim is filed in time. It does not know the carrier's terms, which you should check with the carrier or your logistics contact.

When not to automate

Automation is not worth it for every network. If you move fewer than a few transfers a month between two sites, and the owner or one manager already checks every receipt by phone, a shared spreadsheet with a receipt column and a weekly review is enough. Adding a system and an approval flow can create more work than it removes.

Be cautious when stock records are poor to begin with. If the opening counts at each branch are wrong, the first months of automated matching will produce long exception lists that only reflect the old errors. Run one physical count at each branch first, then start matching.

Do not automate the decision to write off stock, to blame a named employee or to change a branch manager's targets based on transfer gaps. Those decisions need context that no list contains. If a gap points to possible theft by staff, the handling of that matter, including any investigation or disciplinary step, follows your own HR policy and the labour rules where you operate. Check those with a lawyer or your HR adviser before you act on the data.

What it typically takes

For a network with a working stock system and a few branches, the usual sequence is a short design session to agree on the reference number, the count deadline and the gap categories, followed by setup of the transfer flow and the exception list. The part that takes longest is not the software. It is getting every branch to enter receipts on time for two or three weeks until the habit holds.

Plan for the first month to be noisy. Expect a backlog of old transfers to clear, and expect the reminder schedule to need adjusting once you see which branches are slow. Template approval for WhatsApp, where used, adds days before the first message can go out. Time spent per week on chasing should drop once the exception list replaces the phone calls, but the free audit measures your current time so you can compare it with the same figures after setup.

This explains the general approach to stock transfer matching in plain terms. It is not legal, tax or accounting advice for your case, and the right treatment of transit losses in your books should be confirmed with your accountant.