Multi-warehouse transfers never sync? Two-sided confirm beats “each side books once”

The three blank hours at the reconciliation meeting of the two warehouses

The group's raw material warehouse driver ships out at nine o'clock, but the workshop warehouse manager doesn't scan the first pallet until three in the afternoon. In those three hours in between, the goods are either on the truck, at the dock, or stuck in someone's 'unload later' process. The shipping warehouse account has been reduced, but the receiving warehouse account hasn't increased, yet the planner's completeness report shows that the raw materials are sufficient — because someone treats in-transit goods as available, while another treats unreceived goods as shortages. At the end of the month, both sides make entries for inventory gains and losses to 'align' the numbers, and the fact disappears.

After having multiple warehouses, the controversy changed from 'whether there is stock' to 'Which account the goods are in, and who has the authority to make commitmentsThe solution is not to make another entry on both sides, but to acknowledge a third account: in transit.

In transit is not transitional; it is the third ledger.

When there is no in-transit status, two common types of leveling are seen on site:

• After the issuing warehouse deducts the inventory, if the receiving warehouse does not confirm for a long time, the gap is compensated by inventory loss or 'borrowing materials';
• The receiving warehouse first manually adds the account to ensure completeness, after the issuance of the voucher, then reconcile once more.

Both adjustments can make the report look good, but the audit cannot reconstruct 'when it left the shipping warehouse, when it entered the receiving warehouse, and why the discrepancy occurred.' The transfer closed loop must force the system to answer these three questions, rather than pushing the problem to the month-end inventory count.

The definition must be frozen in advance:

The definition is not frozen, and the completeness, sales commitments, and financial inventory will correspond to three sets of 'truths'.

What actions need to be left for a transfer

Turn 'Application—Issued—In Transit—Received—Closed' into a work task that can be spot-checked, rather than a process poster:

1. Application FormBind the issuing warehouse, receiving warehouse, owner, material/batch, or container, and prohibit moving goods without a document.
2. Send ScanLock inventory and generate in-transit; after issuance, it must not still be available for outbound warehouse wave release.
3. In-transit Visibility: Planning and warehouse management can see the documents, quantities, departure time, and estimated arrival, rather than only in the driver's WeChat.
4. Acknowledgment of receiptPost after counting or scanning; high-value materials require mandatory container/SN to reduce errors in whole order receiving.
5. Difference handling: Shortage, surplus, and damage are classified by cause; they trigger replenishment, damage reporting, or re-inspection, rather than recording one instance of warehouse shortage upon receipt and one instance of warehouse surplus upon dispatch.
6. Close and Post: Reconcile with the ERP posting status; if it fails, enter the business to-do list, and it is forbidden to only write the interface log.

The essence of 'recording a note on each side' is that it skips steps 2–5, using the result account to pass off as the process account.

Multiple owners and organizational boundaries: transfers cannot conveniently change the owner

When group warehouses, outsourced warehouses, and channel warehouses operate in parallel, the mapping of organization dimension, goods owner, and ERP account set should be fixed during the account opening period. Task assignment and inventory visibility are trimmed by organization/goods owner—miswriting across goods owners is harder to detect than a one-digit quantity difference.

Common failures:

• Temporarily allocate Owner A's inventory to Production Line B, and the inventory transaction directly changes the owner;
• The rules for outsourced warehouse receipt and loss responsibility are undefined, with all shortages either entirely passed on to the processing party or fully absorbed internally.
• The channel warehouse treats in-transit goods as salable, and when returns are sent back, the batch status and quality status are lost.

The rules should be simple and straightforward:The transfer of mobile positions and custodial responsibilities does not automatically change the owner of the goods; The consignor changes to operate independently. Outsourced warehouses rely more on receipt and loss agreements, which can be linked with outsourced reconciliation topics, but there must still be a bilateral confirmation within the warehouse first; otherwise, the financial reconciliation lacks operational evidence.

Containers and batches must be fixed when scanned for dispatch. During transit, if pallets are changed, boxes are unpacked, or shipments are combined, and the receiver only checks the total quantity, discrepancies will turn into 'unclear whether items were missed or counted incorrectly.' High-turnover auxiliary materials can be received and counted by the box, while high-value items should be received and counted by SN or container code—the rules should be written according to the type of goods, not a warehouse-wide 'mark the whole order as complete' approach.

Don't use inventory checks to cover up allocation gaps

Cycle counting addresses the classification and responsibility of accounts and physical inventory; if transfers are not closed in a loop, it will create 'false discrepancies' — the goods are actually in transit, but the inventory count shows a loss on one side and a gain on the other. The recommended governance sequence is:

1. First, clear the outstanding SLA orders in transit, supplement receipt or close discrepancies;
2. Conduct an inventory check on the storage locations that still do not match.
3. Separate 'transfer not closed' in the inventory reason codes to avoid mixing it with actual theft or misplacement reports.

Wave picking and production material issuance rely on the correct available quantity. When in-transit metrics are chaotic, material shortages and warehouse locking will occur on two tracks: the system locks one set, while the site borrows another. Cross-warehouse material requests should go through a transfer or distribution closed loop, rather than verbally borrowing materials and then creating a supplementary order.

Differences and shortages especially prohibit 'adjusting each time separately.' In-transit losses, missing items, measurement differences, and wrong SKU shipments have different causes and different responsibilities, and the follow-up actions are also different—reshipping, reporting losses, carrier claims, or reinspection should all be linked to the original transfer order. If the receiving warehouse records a loss and the sending warehouse records a surplus, the audit cannot reconstruct the facts, and the same shortage will occur again next time.

The quality status should follow the goods.

When frozen batches or batches pending inspection are transferred between warehouses, allocations cannot 'cleanse' the quality status. The batch quality status should be carried when dispatched, and the receiving warehouse must not automatically change it to available due to the warehouse transfer; if business allows the transfer of quarantine responsibility, it must also be explicitly recorded on the document instead of relying on verbal agreements by warehouse staff. Expiration dates and FIFO rules still apply when reassigning in the receiving warehouse, to avoid placing near-expiry frozen materials into available stock just to clear in-transit inventory.

Reconcile with finance: keep the job granularity in the warehouse, the resulting accounts in ERP

Manufacturing and warehousing plans usually stipulate: financial inventory and posting results are based on ERP, while batches, locations, containers, and operational events remain in the WMS. When performing spot checks on cross-warehouse transfers, it should be possible to simultaneously see the sending/receiving scans, transit duration, discrepancy approvals, and whether the ERP posting was successful. If either side fails, it must be visible to the business and closed, prohibiting 'interface green, but the accounts unchanged.'

Liabilities in transit, automatic posting, and whether unplanned cross-warehouse transfers are allowed should all be fixed in the account opening configuration table to avoid inconsistencies in interpretation between the two sets of accounts caused by verbal changes in the later stages of the project. If the group warehouse and the subsidiary warehouse are mapped to different ERP accounts, the conditions for closing a transfer should include 'both sides successfully posted or a clear unilateral rule'; otherwise, one side may have closed the order while the other side is still pending.

JEDP-WMS covers multiple warehouses, multiple owner isolation, transfers, and task assignment. Within the warehouse, it supports planned/unplanned and cross-warehouse transfers; the 'cross-warehouse transfer double confirmation' in the receipt list is exactly the key feature to prevent 'each warehouse having separate accounts, reconciled only at the end of the month.' Long-term in-transit items can alert the responsible person, butDo not automatically sign for——Automatic receipt will hide discrepancies in 'Completed'.

Narrow the scope first when advancing

When a single warehouse has no cross-organization movement, finance does not require warehouse-level accounts, and the owner model has not yet been defined, there is no need to implement complex isolation first—first stabilize the unique inventory ledger to align with operational tasks. For outsourced warehouses that do not yet have a receipt routine, first practice 'shipment—in transit—receipt' before discussing loss allocation; for channel warehouses, prioritize freezing whether 'in-transit inventory is available for sale' to prevent sales commitments from being based on non-existent stock.

Observation indicators should be few and solid: timeliness rate of closed-loop allocation, number of in-transit items exceeding SLA, completeness rate of discrepancy reasons, number of uncleared items on the day according to ERP reconciliation. If the closed-loop timeliness rate rises but many discrepancy reasons are labeled as 'Other,' it indicates that orders are just being rushed to close, not that the facts are being managed. Driver delays, platform queues, and insufficient receiving staff should all be visible from the distribution of in-transit durations—before blaming 'system inaccuracies,' first check whether the timestamps for sending and receiving actually exist.

What to do next

Export this week's 'transfer orders exceeding the agreed SLA', sorted by the issuing warehouse; randomly check five orders to verify whether the dispatch scanning, receipt confirmation, and discrepancy reasons are complete. Follow the rule of filling in whichever part is missing first, and do not expand to a third warehouse yet.

• WMS Warehousing Solution: Multiple Warehouses, Multiple Owners, and Transfers
• Cycle counting: Don't use counting to cover up transfer shortages
• FIFO and Batch Control
• Wave picking accuracy and availability