Here's an uncomfortable truth: when a 3PL switch goes wrong, it's almost never the freight. It's the inventory math.
In 2023 I helped a home-goods seller move from their old 3PL in New Jersey to a new one in Allentown, Pennsylvania. Over 90,000 square feet of product, 4,000+ SKUs, more than 40 truckloads — the freight all arrived fine. Then the first week after cutover turned into chaos: the storefront showed in stock, the new warehouse's system said zero on hand, and the old warehouse was still sitting on 200+ unshipped orders. Customer service got hammered. Ad spend kept burning while listings went out of stock, and it took three full months to win the rankings back.
Moving freight is manual labor. Money solves it. The real fight happens before and after the trucks roll: data, systems, counts, and contracts. Get those wrong and no amount of trucking saves you.
Count First, Move Later
Week one of a warehouse switch: don't call the trucking company yet. Reconcile first.
Do a three-way reconciliation: your own ERP inventory, the old 3PL's WMS inventory, and a physical spot count. If any of the three disagree, cutover week will explode. The worst case I ever saw had an 11% gap between the seller's spreadsheet and the 3PL's system. It took three days to find the cause: the old 3PL had been shipping promotional freebies under the same SKU as the paid product, and the system couldn't tell them apart.
SKU master data cleanup is unglamorous, but skip it at your peril. Duplicate SKUs, long-dead discontinued SKUs, one product with two barcodes (UPC and internal codes mixed together) — every one of these becomes an integration error later. My approach: produce a SKU mapping table — old code, new code, barcode, specs — reviewed line by line and signed by both sides. That table will save your life.
The handover count is the main event. Before cutover, run one joint full physical count: your people, the old 3PL's people, and the new 3PL's people if they'll send someone. Three parties present, signatures on the count sheet. Who eats the variance? Put it in the contract. My standard language: the 3PL reimburses at cost for any variance beyond 1%, written into a contract appendix. Without that clause, every shortage comes out of the seller's pocket — don't ask me how I learned that.
Then there's the old contract's termination terms, which most people never read until moving day: 90 days' written notice, clearance handling billed at double the normal rate, minimum monthly storage charges. Pull those terms out before you start moving. Negotiate what you can, accept what you must — but don't discover you're locked in during the final week.
Integrate Before You Migrate
Week two has exactly one job: get both systems talking to each other.
EDI or API integration — order feed, inventory sync, ASNs, return authorizations — test all four, one by one. Never trust "our API is standard." Standard interfaces produce non-standard errors; that's just how it goes. Run at least 50 test orders end to end: order in, pick, pack, ship, tracking number pushed back, delivery confirmation received. Deliberately throw in multi-line orders, split shipments, and out-of-stock lines to see whether the exception flows actually work.
Settle the carrier account question this week too: your own discounted carrier account, or the 3PL's? Their "all-in shipping rate" sounds simple, but ask how fuel surcharges, residential delivery fees, and oversize surcharges are handled. Do the math per order, not just on the headline rate.
Week three: pilot shipping. Move 10–20% of your fast movers over first and ship from the new warehouse for 3–5 days. Watch three numbers: pick accuracy, dock-to-ship time, and damage rate. Split new orders between both warehouses, and keep the old one able to take orders — that week of "paying double" is the cheapest stockout insurance you'll ever buy.
In-flight order ownership needs to be in writing now, not later: everything ordered before midnight on cutover day gets finished by the old warehouse; everything after goes to the new one. Update the customer service scripts at the same time, or CS and the warehouse will be blaming each other all week. Returns work the same way: after cutover day, all return parcels route to the new warehouse. RMA numbering rules, QC standards, who authorizes refurbish versus scrap — decide now, not when the first return shows up.
Cutover Week: Three Things to Watch
Week four, cutover day. Change the ship-from address in your storefront and ERP to the new warehouse in one move. Like a DNS cutover: clean and decisive. Two warehouses taking orders at the same time is how stockouts start.
Whatever is left at the old warehouse, move it by full truckload — it's the cheapest option by far, and LTL piece by piece is slow and expensive. After the sweep, run one closing count and reconcile it against the week-one joint count. Any gap shows up immediately.
Last item: settle the final invoice, line by line. Storage billed through which date? Any inflated handling charges? Was the variance credit deducted? My habit is holding back 10% of the final payment until the closing count is signed off by both sides. Without a holdback clause in the contract, money paid is money gone. Back in 2022, one client got billed for two extra months of storage they didn't owe — over $30,000. If the holdback hadn't been in place, that money was as good as lost.
Here's the 30-day checklist, ready to use:
Week 1 (D-30 to D-23): Data and contracts
- Export the full SKU master file from the old 3PL; scrub duplicates and dead SKUs
- Three-way reconciliation: your ERP vs. old 3PL system vs. physical spot count
- Standardize barcodes (UPC vs. internal); produce draft SKU mapping table
- Sign the new contract: SLA, variance reimbursement, and return-processing turnaround in an appendix
- Old contract: confirm notice period, clearance handling fees, minimum storage terms
- Submit the inbound forecast template to the new 3PL; confirm pallet specs and labeling requirements
Week 2 (D-22 to D-15): Systems integration
- EDI/API integration: orders, inventory sync, ASNs, and return authorizations
- SKU mapping table reviewed and signed by both sides
- Run 50+ test orders end to end, including exception cases
- Confirm carrier account ownership and who prints labels; nail down surcharges
- Returns SOP: RMA rules, QC standards, refurbish/scrap authorization
Week 3 (D-14 to D-8): Pilot and parallel running
- Move 10–20% of fast-moving SKUs to the new warehouse
- Pilot-ship 3–5 days; verify accuracy, ship time, and damage rate
- Split new orders between both warehouses; keep the old one order-capable
- Joint full count at the old warehouse; three-party signatures; variances settled per contract
- In-flight order rules written into both SOPs; CS scripts updated
Week 4 (D-7 to D+7): Cutover and closeout
- Cutover day: flip storefront/ERP ship-from address to the new warehouse in one move
- Midnight cutover boundary: old warehouse finishes prior orders; new warehouse takes everything after
- After cutover day, all returns route to the new warehouse
- Sweep remaining inventory from the old warehouse by full truckload; run a closing count
- Settle the final invoice: verify every line, deduct variance credits, hold back 10% pending sign-off
- D+7 review: stockout rate, mis-ship rate, and transit time vs. the old warehouse baseline
So here's the question worth asking before your next renewal: does your current 3PL contract have an inventory variance clause? If not — pull it out tonight, and decide whether you'll have the nerve to negotiate it in next time.
