How to Reconcile Inventory Transfers Between Warehouses
Treat in-transit stock as a controlled inventory location. This guide shows how to preserve custody, separate variance types and close transfers cleanly.
Inventory should not disappear into a vague “in transit” status when it moves between warehouses. A controlled transfer uses a unique transfer ID, freezes the shipped quantity at origin, records container-level custody, receives against the same record at destination and closes only after every variance has an owner and disposition.
Treat a transfer as two linked transactions
The origin transaction reduces available inventory and creates in-transit inventory. The destination transaction receives and puts away that same inventory. The transfer is not complete when the truck leaves, and it is not complete merely because the truck arrives.
Keep three quantities visible for each SKU: planned, shipped and received. If one field overwrites another, you lose the evidence needed to identify whether the variance began in planning, loading, transit or receiving.
The minimum transfer record
| Field | Purpose |
|---|---|
| Transfer ID and status | One reference from planning through closure |
| Origin and destination | Exact facilities and staging locations |
| SKU, lot/serial and expiry | Preserve item identity and traceability |
| Planned, shipped, received quantity | Expose variance without overwriting history |
| Container or pallet ID | Support sealed handling and targeted recounts |
| Seal, carrier and tracking reference | Create chain-of-custody evidence |
| Timestamps and users | Show who performed each scan |
| Variance reason and disposition | Close exceptions deliberately |
Control the origin
Allocate the transfer before picking so the same stock cannot be promised to customer orders. Pick by scan, then verify each tote, carton or pallet before sealing. Record the final shipped quantity rather than assuming the planned quantity left the building.
Stage completed transfers in a controlled location. A pallet on the dock should have a status such as “verified, awaiting pickup,” not simply “picked.” Capture seal numbers and photographs when the value or risk justifies it. Physical evidence does not replace scanning, but it can resolve carrier-damage or tampering questions.
Receive without contaminating available stock
The destination should receive against the transfer ID, not a new spreadsheet. Scan container IDs first, inspect visible condition and count by SKU or handling unit according to the risk plan. Damaged or uncertain units should enter quarantine, not sellable inventory.
Putaway comes after receipt confirmation. If associates move goods directly from the trailer to ordinary pick faces before the count is complete, a recount can mix transferred units with existing stock and turn a small discrepancy into a larger one.
A hypothetical reconciliation example
Assume a transfer planned 1,000 units across three SKUs. Origin scanning confirms 990 units shipped: 500 of SKU A, 300 of SKU B and 190 of SKU C. Destination receives 987: all of A and B, but only 187 of C.
| SKU | Planned | Shipped | Received | Variance to investigate |
|---|---|---|---|---|
| A | 500 | 500 | 500 | 0 |
| B | 300 | 300 | 300 | 0 |
| C | 200 | 190 | 187 | 10 not shipped; 3 shipped not received |
The ten-unit planning shortfall belongs to the origin pick process. The three-unit ship-to-receive variance requires a container recount, staging search, damage review and custody check. Combining both into “13 short” would hide two different causes.
If the hypothetical unit cost of SKU C is CAD $40, the unresolved in-transit exposure is 3 × CAD $40 = CAD $120. That amount helps set escalation priority, but units with serial, safety or customer-allocation importance may require escalation even at lower value.
Set closure rules before the first transfer
Define tolerance by unit, value and risk. A zero-tolerance rule may be appropriate for serialized electronics, regulated goods or scarce launch inventory. Low-value consumables may use a small tolerance only if accounting, client agreements and control policy permit it.
- Destination posts the received count.
- The system calculates planned-to-shipped and shipped-to-received variances separately.
- Teams recount the exact affected containers and staging locations.
- A named owner assigns a reason code: origin short, destination over/short, damage, wrong SKU, carrier loss or documentation error.
- Approved adjustments post to the correct facility and financial period.
- The transfer closes only when in-transit quantity returns to zero.
Measure the process monthly
Track transfer fill rate, received-in-full rate, average days in transit, days to close variances and value written off. Review recurring variance by origin, destination, carrier, SKU and handler. A transfer that is “mostly right” but takes ten days to reconcile can still distort reorder and customer-allocation decisions.
Use the same discipline alongside multi-warehouse inventory placement, cycle counting, lot and expiry tracking and inventory aging.
The essential rule is that “in transit” must be a controlled inventory location with an owner, aging clock and reconciliation path. 247 Fulfillment can help brands build inventory management controls that preserve accuracy as the network grows.
