A warehouse move has two milestones that are easy to confuse: stock reaches the new building, and the new operation is ready to fulfill orders. Treating those as the same event can turn a carefully scheduled transition into a stock-availability problem.
The strategic choice is where to put the release gate. Make it an agreed inventory-and-order check rather than a date that every team feels pressured to meet regardless of the evidence.
Define the quantity you can actually route against
Inventory systems distinguish movement from acceptance. Shopify's transfer documentation, for example, separates accepted, rejected and canceled quantities, and keeps partially received transfers in progress. That is a documented platform behavior, not a guarantee about a prospective 3PL's integration. Shopify receiving transfers
Ask both providers how their records will reconcile to your selling system. Identify who approves the starting balance and who investigates the exceptions. Do this before the first truck departs, while the parties can still agree on the evidence they need.
A worked cutover gate
Our constructed example starts with 1,000 units dispatched. The destination accepts 940, rejects 30 after inspection and has 30 still unresolved. Of the accepted stock, 120 units are reserved for open orders and 50 are an agreed operating buffer.
The quantity available for additional routing is therefore 940 − 120 − 50 = 770 units. It is not 1,000 and it is not 940. The 60 rejected or unresolved units remain visible in the reconciliation; they are not silently removed from the brand's records.
| Check | Evidence to request | Who signs off? |
|---|---|---|
| Departure quantity | Item-level dispatch record | Origin warehouse owner |
| Accepted quantity | Destination receipt and inspection result | Destination warehouse owner |
| Existing commitments | One reconciled list of open orders | Brand routing owner |
| Exceptions and buffer | Separate quantities with release conditions | Authorized brand decision-maker |
These are hypothetical quantities, not findings from an actual migration. The exercise demonstrates how arrival can be complete while routable inventory remains constrained.
Assign each open order once
Inventory reconciliation is only half the gate. Decide which provider owns each unfulfilled order, including orders already picked, labels already created and changes arriving during the cutover. Record the decision in a shared control list with a timestamp and owner.
A customer should not receive two shipments because each warehouse assumed the other would stop. Equally, an order should not disappear because both assume it belongs elsewhere. Test the ownership handoff with approved sample records before changing live routing.
Agree a fallback with a stopping point
If the acceptance check fails, specify whether new orders stay with the old provider, pause or route only for verified SKUs. Confirm the old provider's actual remaining stock and capacity before treating it as a fallback. Do not assume goods already dispatched can be made available there again with a software change.
Use a staged release if your operation supports it, but make each stage explicit. A partial launch needs an eligible SKU list, quantities and exception owner. It is not permission for every order to flow.
The best launch date is one the evidence can support. Your team can still work toward a calendar target; the inventory gate prevents that target from becoming a substitute for operational readiness.
Related reading
Sources
- Transfer acceptance and exception states — accessed 2026-10-05.