3PL Operations

Switching 3PL Providers: Inventory Transfers, Open Orders, and Shipping Cutover

Once you have chosen a new 3PL, coordinate three handovers. Move and verify the physical inventory. Assign each open fulfillment task and its remaining quantity to one warehouse. Then validate shipping accounts, tender arrangements, tracking and billing at the new location. An integration can be live while stock is still in receiving. A pallet can be on the dock before its contents are available to pick. A successful label print says little about whether the old warehouse stopped the same task.

Set a release decision for each group of orders or SKUs. Agree who can authorize it, what evidence they need, and which team takes action when an exception appears. Keep existing customer promises in view, including marketplace ship-by deadlines and outstanding returns. Some groups can keep shipping throughout a move. Others need a planned pause or a revised promise. The objective is to know which orders can actually ship, from where, and under whose control.

Two operations leads reviewing a transfer manifest beside palletized stock while a separate bench prepares outbound parcels.
Inventory transfer and daily parcel dispatch need coordinated release decisions.

Choose a transition method that fits the inventory and orders

Start with the part of the assortment you can actually separate. Look at how products sell together, which SKUs have shallow stock, and how long the old facility can continue taking work. Mark subscriptions, kits, lots with expiration dates and channels with tighter dispatch commitments. A clean split by SKU can still be a bad split by order if buyers routinely combine items from both groups. The migration plan has to work for those orders too.

MethodWhen it fitsRouting and stockCost, customer promise and poor fit
A. Deplete old stock. Replenish the new site.New supply is reliable. The old site can finish orders as stock runs down.Route replenishment to the new site. Retain SKU coverage until new stock clears.Some overlap and residue. Watch sellouts and cross-site orders. Poor fit for scarce stock or distant replenishment.
B. Move stock in waves.Separably stocked SKU, order or channel groups.Requires reliable dual-site routing and SKU reserve through each handoff.Two sites add work and can add parcel and storage costs. Poor fit for shared components or weak routing.
C. Pause a defined scope and restart.A small assortment, shared kit stock or unreliable dual routing.Hold affected assignments. Plan for receiving and the accumulated order queue.Less concurrent shipping. Customer promises need a planned window. Poor fit when ship-by dates cannot tolerate a pause.
Relative timelines compare depleting old stock and replenishing the new site, moving in waves with split ownership, and pausing selected orders before resuming at the new site.
Illustrative steps. Confirm release conditions and the actual window with both warehouses.

With depletion, direct new purchase orders to the incoming site while the departing site works down existing stock. Before changing a SKU's default shipper, check residual stock, open reservations and what is arriving at each site. Decide how to handle the slow movers, returns and remaining packaging once the main assortment moves. If stock at the old warehouse runs down before new replenishment can be put away, decide whether to delay routing that SKU, use a documented fallback or change the customer promise. Speeding up the default rule cannot close that physical gap.

A phased transfer works when the team can draw a stable responsibility boundary, such as a named SKU group or channel that rarely shares inventory with other work. Price the temporary overlap, including separate replenishment, minimums, staff coordination and extra parcels when mixed orders split. For a kit assembled from shared components, define where the component reserve lives and who may build the kit. Consider moving the entire kit family as a unit if the same component would otherwise be promised from both sites.

For the overlap to work, prove that both teams see the same inventory ownership and dispatch state. Set a staffing owner for cross-site exceptions and test what happens when the new site is out of one component. If the default substitution is to ship the rest and follow with a second parcel, decide whether the service cost and customer experience are acceptable. If the brand promises a single kit, do not release the kit until all components and assembly instructions are present at one approved site. An overlap that creates weekly order exceptions can cost more than a planned pause for that product family.

A planned stop and restart can be easier to control for a small assortment, a tightly coupled product family or an operation that cannot safely route through two providers. Write down what intake continues, which orders wait, what customers will see, and how much backlog the new warehouse can clear. Use a confirmed appointment and receiving plan rather than the truck's estimated arrival alone. The Cahoot migration guide and ShipMonk’s transition article discuss these different approaches. The actual overlap and stop window depend on your inventory, providers and cutoffs.

Before locking the method, walk a representative cart from checkout through dispatch. Include the unit that consumes the shared component, the order on a tight cutoff and the supplier delivery already booked to the old address. Show how each is handled during overlap and after release. If both sites would need to make an exception to fulfill the same common cart, narrow the phase or schedule a controlled stop for that product group.

Establish the inventory baseline before releasing stock

Pick a snapshot time and time zone. Export a physical count by warehouse, SKU and, where relevant, lot, expiration or serial number. Separate allocated units, unallocated usable units, and stock on hold, under inspection or damaged. Track planned transfers as a reservation against eligible stock. Track dispatched but unresolved units by transfer and shipment. Record inbound replenishment by expected date and site. A planned move, a dispatched unit and an expected purchase order are records of different events. Each physical unit belongs in one physical state at a time.

For example, if a usable unit is reserved for a transfer, flag it within usable stock and subtract the reservation when calculating what can still be promised to customers. When it leaves the dock, remove it from the old site's physical quantity and list it under the transfer as dispatched. At the new site record receipt and condition before releasing it to order allocation. Confirm whether both systems measure eaches, cartons or packs. A count can balance on paper while the pack-size conversion silently makes stock wrong in the store.

Keep a delta log after the snapshot. Include customer shipments, returns, cancellations that release reservations, transfer picks and shipments, receipts, corrections and change of stock status. Compare the expected closing balance for the same time window with the observed closing balance. If both warehouses exported at different times, walk the intervening movements and align the record by event time. Assign an owner to investigate late postings and preserve the original values so the discrepancy has an audit trail.

Reconcile availability as well as physical counts. A received return can be counted in physical stock while its status stays on hold until inspection. An order cancellation can free a reservation without moving anything. A bookkeeping correction needs a reason and supporting count so it cannot cover a missing pallet. For the migration period, ask both warehouses to identify the person who can approve adjustments and keep the adjustment reference on the transfer. Review unmatched records before rolling the next wave into the same disputed quantity.

Use a transfer reference, packing list and an agreed receiving count, with lot and serial information where required. Capture who loaded which cartons, who accepted the freight for transport and who verified inner quantity at destination. Shopify supports inventory transfers and can record partial receiving outcomes. Its receiving flow distinguishes receipt actions, and items may need activation or stocking at the destination before they can be sold or fulfilled there. In a 3PL app setup, confirm which system writes the authoritative balances and whether both locations can participate in the same workflow. Use the receiving SOP for detailed dock and putaway checks. Shopify inventory transfers · Shopify receiving

For a staged move, give each wave a separate transfer reference and list the physical handling units. Record partial releases against that reference. A short shipment from the old warehouse is the gap between planned and actually dispatched. A receiving discrepancy is the gap between dispatched and counted. Those gaps need different evidence and can both occur in the same wave.

Calculate what the old warehouse must keep

The old site needs the units already committed to orders plus enough unallocated usable units to cover the demand it will serve until the new site is ready. For each SKU, count transport time, appointment delays, receiving and inspection, putaway and system activation. Build the buffer from an observable risk such as a late inbound slot or a wider range of demand. Track held inventory physically at the old site if it will stay there, and leave it out of the usable reserve. If stock under inspection is moving separately, give it its own transfer instructions and inventory status.

Hypothetical case 1. A phased transfer with a partial receipt

At the same snapshot, a hypothetical seller has 10,000 physical units of one SKU at the old warehouse, including 600 already allocated to existing orders and 200 frozen. The new site should be ready for this SKU in 8 days. New demand still assigned to the old site is forecast at 150 units per day for those 8 days, in addition to the 600 already allocated. The plan holds a 300-unit buffer. Assume no other receipts, shipments or adjustments affect the planning baseline, frozen units are unavailable, and the move and receiving capacity can accommodate the first shipment.

The 8 days of demand account for 8 × 150 = 1,200 units. Keep 1,500 unallocated usable units, made up of the 1,200 forecast units and 300 buffer units. Adding 600 allocated and 200 frozen leaves 2,300 physical units at the old site. The planned first transfer is 10,000 − 2,300 = 7,700 units. Starting from unallocated usable stock gives the same result. Of the 9,200 usable unallocated units before the move, 7,700 can be planned for the transfer and 1,500 remain as the reserve.

The ship-out record confirms 7,700 left. The new warehouse counts 7,675 received, of which 75 are pending inspection, leaving 7,600 available in this example after putaway and activation. The outstanding difference is 25 units between confirmed ship-out and receipt. Open an investigation against the original count, pallet IDs, carrier records and receiving log. Keep the 75 on hold and 25 unresolved out of the inventory offered to new orders. Before the truck arrives, the 7,700 belong in the dispatched transfer record. After reconciliation begins, 7,675 have a confirmed location and 25 still need an explanation.

Of 10,000 old-site units, 2,300 stay and 7,700 are dispatched. Of 7,675 received, 7,600 are available and 75 await inspection. A 25-unit difference remains.
Hypothetical example. The new site releases only cleared and enabled stock.

Suppose the readiness estimate moves from 8 to 10 days before dispatch. Another 2 × 150 = 300 units of projected new demand would reduce the first transfer from 7,700 to 7,400 if the buffer stays at 300 and other inputs are unchanged. Reforecast daily demand the same way. If the load already departed, start from the old site's remaining usable stock after actual sales. Consider a smaller launch group or delayed orders using the revised promise. In the case, release only the scope supported by the 7,600 cleared units and the new site's shipping checks. The exception closes when the assigned owner documents a verified count, approved correction or other agreed disposition for each difference and hold.

Revisit the buffer whenever you change the routing boundary. If a SKU normally ships in a kit, forecast the consumption of its components along with sales of the standalone SKU. Tie the reserved quantity to the orders and days covered, then take it out of both the next transfer pick and the new site's sellable feed. Only count replenishment once its expected arrival and release status fit the plan.

Inventory transfer reconciliation template

FieldFictional example
SKUSKU-MOVE
Lot or serialLOT-A
Snapshot time and zoneS0, 09:00 CT
Transfer IDTX-DEMO
Planned units7700
Old warehouse shipped7700
New warehouse received7675
Available7600
Pending inspection75
Unresolved receipt difference25
EvidenceDock count, load record and receipt
OwnerNew warehouse receiving lead

Download the editable CSV

Transfer open fulfillment tasks at line and quantity level

A customer order can contain several fulfillment tasks and shipments. Give each order line and quantity a single executing warehouse at a time. One warehouse can ship a line while another handles a different line or a separately assigned remaining quantity. Keep the original task reference and the newer one linked so someone can tell exactly what was stopped, what shipped and what remains. The order, shipment, package and label model explains the identifiers each event should reference.

Stage at old warehouseEvidence and confirmerRelease rule and what to hold
No request sentSales channel and order system queue, routing owner.Assign eligible quantity to new warehouse. Hold any duplicate queue entry.
Requested, not acceptedRequest record and actual warehouse queue, old integration contact.Cancel the pending request using the actual workflow and verify it cleared. Hold new release until then.
Accepted by old warehouseAcceptance and task ID, old fulfillment lead.Wait for confirmed cancellation or keep the quantity with the old warehouse. Hold duplicate imports.
Picking startedPick and bench records, shift supervisor.Confirm work stopped and remaining stock disposition. Hold reassignment until the quantity is clear.
Label printed, tender unconfirmedPhysical package, print record and tender evidence, old dock lead.Hold reprinting. Verify possession, stop task, resolve unused label under purchase channel, then release eligible remainder.
Tendered to carrierPiece or load evidence and its parcel linkage, dock or carrier contact.Keep the real shipment and tracking with the old warehouse. Hold duplicate or unapproved replacement.
Part shipped, part openLine quantity by task and package, both fulfillment leads.Retain shipped records. Transfer confirmed stopped remainder only. Hold quantities still disputed.
For each fulfillment task or order line quantity, tendered work stays with the old shipment. Unmoved work is eligible only after checks or required cancellation and physical stop.
Verify the specific remainder before releasing it to the new warehouse.

For an app-connected fulfillment service in Shopify, the merchant can cancel a request that has been sent but not accepted. Once the service accepts, send a cancellation request and wait for the service's response before moving that work. A rejection leaves the existing fulfillment in progress. If the provider confirms it canceled the work but cannot update Shopify, Shopify allows the merchant to revert the order to unfulfilled. Reverting the screen on its own does not stop the provider. Shopify also documents changing locations and moving a subset where the workflow permits. Check which lines and quantities are eligible at the current state. With other OMS, WMS or apps, confirm the actual stop signal, acknowledgement and ability to move partial quantities. Shopify app fulfillment

Record a cutoff with its time zone and the specified channel, location or SKU group. Then handle the backlog explicitly. Export what the old warehouse accepted, what is queued for it, what was imported by hand and what may retry after the cutoff. Use a held list so a canceled or quarantined task cannot return through a replayed file. Ask which partner ingests direct marketplace feeds that bypass your normal routing rule. Review late imports against the handoff register before releasing them. See the multi-warehouse routing framework for ongoing assignment rules. Shopify order routing

Keep a live list of in-flight work while the routing change goes in. Assign one person to compare the final old queue export and the first new intake file at the fulfillment-task level. Ask both sites to confirm the same handoff version. If an operator spots an old print batch after a cancellation, the batch needs to be removed or held at the originating system as well as at the packing station. If messages arrive out of order, preserve the cancellation and the one approved task. Resolve the conflict with the provider rather than overwriting it with the most recent timestamp.

Hypothetical case 2. The old warehouse accepted work and the new warehouse got the same data

A brand sees its old warehouse accepted two units of one item on an open order. The new warehouse just imported the same two units, and the old pick list shows activity. Nobody has confirmed the cartons' physical location. The lead puts the new task on hold and asks the old shift supervisor for the scan history, staging location, parcel IDs and any driver or carrier handoff evidence. The old provider finds one unit in a sealed parcel already tendered and the other still at its bench. The tendered unit stays attached to the old shipment and tracking record.

The brand asks the old provider to stop the remaining unit and waits for a cancellation or equivalent confirmed task reduction. The provider verifies that the second unit is stopped and any picked stock is put back or otherwise accounted for. Only then does the brand release the new warehouse for that one unit, with the canceled old work linked to the new task. The cutover passes for this order when the two units are accounted for separately, no second live task exists for either quantity, and the customer sees the valid tracking associated with each real shipment. If the old warehouse cannot stop the second parcel, the brand keeps both quantities there and closes the duplicate import.

Make the handoff record granular enough for the packer. If the old platform cannot cancel part of a task, do not improvise a partial edit in the new warehouse. Have the old provider finish the eligible work if it can, or use the platform's supported cancellation and recreation process with evidence about the units already shipped. The approval is for a specific remainder.

Open fulfillment task handoff template

FieldTendered unitRemaining unit
OrderMOVE-214MOVE-214
Order lineL1L1
Quantity11
Old fulfillment taskOLD-214OLD-214
Physical stateTenderedStopped at old bench
Cancellation confirmationNot applicable. Keep actual shipment.Old lead confirmed stop for remaining unit.
New accountable warehouse or taskNo change. Old warehouse.New warehouse, NEW-214
Active trackingTRACK-OLD-DEMOPending actual dispatch
Last updated and zoneC0, 11:00 CTC0, 11:00 CT

Download the editable CSV

Validate shipping from the new starting address

Get the new physical ship-from street address and ZIP Code, the billing account and its authorization at that site, product and package eligibility, destination coverage and return address. Then check pickup or deposit, weekday schedules, cutoff, fallback and who owns the handoff evidence. Ship-from, billing and return addresses can differ. For example, USPS Ground Advantage Commercial deposit conditions depend on how postage is evidenced, and approved collection has additional conditions. Ask the actual carrier or label channel about the new arrangement and retrieve written confirmation. USPS DMM 286 · carrier handoff checklist

Quote a representative mix of packed shipments from the new site. Use actual dimensions and weight bands, destination ZIPs, product type and service restrictions. Compare realistic pickup or deposit fees, label rates, adjustments, surcharges and returns, using the same charge basis and package basket. A new location may shorten some lanes while lengthening others. Keep changes observable. If you can keep the carrier and account terms stable for a pilot, you can test the location and handoff first. If the provider, account and carrier must all change together, use a small matched group and log failure by routing, label, physical pickup and event return.

Define the scope of a pilot by what could change eligibility. A small parcel sent to a nearby address can show a printer and one handoff work, while a heavier box, a different destination group or a restricted item needs its own review. Carry representative box types through rating and label validation. Keep the carrier accounts, test package IDs and approved pickup details beside the results. If only one class of parcels passes, release that class and record the scope that still needs testing. This lets the routing team see which service is genuinely available at the new facility.

Hypothetical case 3. A label prints while pickup remains unconfirmed

The new warehouse generates a sample label for the intended service and returns a tracking number to the order system. The old agreement references a different dock, and nobody can show it covers collection from the new address. The team keeps production parcels out of the new route. It asks the channel owner to verify the account and planned pickup or deposit for that specific ZIP, the local cutoff, parcel eligibility and who signs for the load. It checks the printed address and how the tracking number will be paired to the real piece after handoff.

A limited live test moves only after the authorized path is confirmed. The operator records the package on the staging list, obtains the agreed tender evidence and verifies that the applicable carrier event comes back to the correct fulfillment. Billing checks that the label and any charges land on the expected account. If pickup cannot be confirmed, use another eligible service or an approved deposit arrangement only after testing it, or keep the affected scope at the old warehouse if it can still serve it. A saved label file is a useful test result. The operating release needs evidence that the parcel can leave the dock and be tracked from that origin.

Save the tender arrangement with its scope. This includes the local dock, carrier contact or deposit location, pickup calendar, package limits and fallback. Have the person opening the dock know which account the labels are on and where to report a missed collection. A new team needs that information even when the post-cutover rate is identical.

Match old labels and tracking to the real shipment

Use separate fields for the physical parcel, the fulfillment task, the purchase or void status, and the settlement record. If a label was printed but unused, find the carton and confirm the old task stopped or remains on hold. Remove the unused label from active queues and apply the actual purchase channel's void process. If a void or refund is pending, record it in the billing ledger and prevent reuse. A parcel already tendered stays with its shipment and tracking record. Any replacement requires its own decision and label, and should never be authorized by a missing scan alone.

Where changes require a new label, record old and new numbers against the applicable package and quantities. Check which fulfillment is customer-facing, and whether the channel will send a new notification when tracking changes. Only send a notice consistent with what's happening at the warehouse. If a parcel has yet to leave, reconcile its real state before telling the buyer it shipped. Confirm which system holds the final tracking and package record so retries cannot reinstate an inactive number. Shopify's label void and refund instructions apply to labels bought through Shopify and depend on the label's status and channel rules. Shopify label voids · Shopify order tracking · unused and voided labels

Keep a cross-reference for printed labels the old warehouse may still find. Write the last approved use of each number and where the carton is. Give the pick and pack team an instruction for stray copies, including who can put a parcel back into the release queue. Review the refund statement later as a separate financial close, even when the physical task closed the same day.

Keep the old warehouse open for the work that remains

When shipments start at the new site, run a closeout register for the old one. Check accepted or unresolved outbound work, residual physical stock, frozen goods, planned supplier receipts, packaging and branded inserts. Set distinct dates for stopping new intake, finishing remaining work and settling the account. Check the actual agreement for notice, access, stock release, export and any exit charges. Export shipment, order, item, return and transaction records while access remains, and agree how the old provider will handle future inquiries. Rapid Fulfillment’s migration checklist

New shipments continue while old-site returns, remaining stock and packing materials, and historical invoices and claims are reconciled separately.
Assign owners and evidence for residual work before routine old-site operations end.

Hypothetical case 4. New shipments are flowing while old returns and invoices arrive

The incoming 3PL has passed shipping tests. A buyer uses a previously issued label pointing to the old warehouse and the old provider sends a postage adjustment for a shipment from before the cutover. The team has tracking and the original order number, but the pending inspection has no inventory disposition, and finance cannot yet link the adjustment to a base charge. Give the old provider a dated list of legacy returns it is authorized to receive, an owner for unknown packages and a rule for inspection, forwarding and fees. An address update for future returns cannot rewrite an already issued label. The brand uses the return warehouse decision guide for what to route to which site. Shopify return labels

For each legacy return, log the return ID, tracking, receipt and inspection at the old site. Keep it out of sellable stock until a responsible team decides whether to restock there, transfer or dispose of it. Customer service updates the buyer from the same record. Finance matches the adjustment to the original account, tracking, charge reason and appropriate statement. Close the return when the physical disposition and the customer or inventory update agree. Close the charge when payment, credit or dispute is documented. An agreed follow-up owner can still handle outstanding cases after routine operations end, with archived records and access assigned.

Give the returns desk a plan for the handoff's end. It should know who contacts customers with open authorizations, when to offer an eligible new label, how to treat a parcel already in transit and how to document forwarding. Preserve charge and claim records for prior parcels with the accountable party and the access it needs after the old warehouse stops routine work.

Old warehouse closeout template

Closeout itemState or scopeOwnerHandling arrangementCompletion evidence
Residual stockRemaining and held SKUsInventory leadCount by lot and agree transfer or dispositionRelease or disposition receipt
Packaging and insertsCustom-carton balanceBrand operationsConfirm ownership and collect, transfer or disposePacking list and signed handoff
Unshipped tasksExport old open queueOrder leadClose, ship or confirm stop for each remainderFinal task register and tracking
Old-address returnsLegacy label RET-DEMOReturns supervisorReceive under agreed window, inspect and document dispositionIntake, inspection and inventory update
Unsettled chargesLegacy postage adjustmentFinanceMatch base charge and resolve payment, credit or disputeMatched statement or dispute receipt
Lookup and exportsOrders, shipments and returnsAccount ownerExport before access closes. Assign owner for later queries.Readable export and named contact

Download the editable CSV

Budget the move separately from ongoing operations

Price one-time work against a clear scope. Check the old site's stock sorting and outbound labor, interwarehouse transport, the new site's receiving and counting, temporary dual storage, system setup and manual checks, labels and rework, legacy returns, and agreement-specific exit fees. Some bids package these charges and some list them separately. Ask how to substantiate each fee and whether a minimum or handling unit applies. Compare ongoing costs on the same order mix, with any durable change in storage, packaging, labor, parcel expense and return handling. ShipBob's switch materials are one provider's planning perspective. Use your agreement and observed volumes for budget inputs. ShipBob transition guide · ShipBob switching booklet

Keep incremental expenses, refundable deposits, prepaid balances and unused label credits in separate lines. A promised refund is a receivable until it arrives. A prepaid balance may affect available cash or become an expense under its actual terms. Put each balance with an owner, supporting statement and follow-up date. If you estimate when the move pays for itself, divide incremental migration costs by the net ongoing improvement after all changed expenses, using a clearly stated period and parcel mix. With zero or negative net improvement, that calculation gives no positive payback. A label price alone cannot establish it.

Make the budget period match the overlap. A charge that runs until the last pallet leaves may end before the return handling agreement does. Put expected end events on dual storage and services that continue into closeout. When the schedule slips, update the forecast from those events instead of copying another month of every charge. Flag any amount that requires the old provider's confirmation.

Release only the scope that can ship and be reconciled

Define a launch list by SKU, channel or order group, with one approver and a fallback for each scope. Require verified available inventory, distinct task owners, an approved carrier arrangement for the new origin, working labels and tracking, and someone able to see and respond to exceptions. Exercise a typical order, a split or partial order if relevant, a cancellation and a retry. Have the warehouse show the package, the system show its task and tracking, and finance show where the charge should settle. Use the corresponding records to sign off rather than relying on the test order count alone.

If eligibility fails for one product or pickup fails at one dock, isolate that affected scope. Before sending work back, check where the stock actually sits, whether the old site can still pick and tender, and which new tasks can still be canceled. Leave tendered packages with their original fulfillment. If neither side can safely take the work, hold it, assign an owner and update any threatened customer promise. A rollback may mean changing a shipment plan or waiting for an acknowledgement. Keep disputed work on the hold list until the active system and floor staff agree who owns it.

During the first release, reconcile what the sales channels sent, what the warehouses accepted, what came back as shipped and what went onto the settlement ledger. Report the remaining holds by owner rather than treating the pilot as one pass or fail. If feedback is delayed, look at the physical evidence and put further matching work on hold until the cause is known. Before moving the next group, archive the approved routing version and the people authorized to override it. That creates a record support can use when a duplicate tracking message appears after the active rule has changed.

For the shipping portion of a U.S. warehouse move, bring the new origin ZIP, destination ZIP distribution, packed dimensions and weights, and proposed pickup or deposit to EasyShippingX support. Its documented shipping workflows include Portal, Excel import and API options, with quotes, label generation and tracking for supported accounts and services. Check eligible channels and operating arrangements against that shipment data before committing the new route.

Switching 3PL providers FAQ

A pause is optional. Keep shipping groups with available stock, a single task owner and an approved handoff. Plan a pause where any of those conditions fail.

Use a concentrated move if shared stock or fragile routing makes overlap hard to control and customers can tolerate a planned pause. Otherwise test depletion or staged transfer against supply and demand.

Release after usable units are verified and enabled, task ownership is clear, and shipping works from the new origin. A dock receipt covers only what was received.

Keep the work there or wait for confirmed cancellation or an equivalent stop for the eligible quantity. Keep already tendered pieces attached to their original shipment.

Check the printed origin, account, service, package details and eligibility with the actual channel. If the label cannot be used for this shipment, resolve the old task and label before reprinting.

You can keep the carrier if the account, coverage, parcel eligibility, pricing and handoff work from the new site. Validate the exact location and service.

Name a receiver for legacy parcels and set a handling window. Check which labels are unused and whether they can be replaced under the purchase channel. Track pieces already on the way.

Close routine work after stock, material and order responsibilities are reconciled. Give any later returns, billing and claims named owners, records and access under the agreement.

Sources and methodology

Sources reviewed November 15, 2026. Shopify guidance applies to the named workflows. The migration cases and quantities are hypothetical.