Last month my 3PL sent an email with a very calm subject line: "We will soon be switching to a brand-new WMS. Expect a fully upgraded service experience." Attached: a 12-page slide deck full of "empowerment," "synergy," and "digital transformation."
My first thought: what does this have to do with me?
Everything, as it turns out. The inventory is mine. The orders are mine. The store is mine. IT switches the system, but when orders can't ship, ship wrong, or inventory numbers don't add up, it's my money on the line.
Back in November 2024, my goods sat in a 3PL warehouse in Ontario, California, doing about 300 orders a day. I was online for the entire WMS cutover. At 9 AM, 300-plus orders got stuck at "allocated, not picked" — invisible in the new system, while the old system had already gone read-only. My customer service line blew up. I spent the morning calming buyers down and cursing under my breath. Root cause: a batch of in-flight orders never got migrated. The goods were sitting right there on picking carts. Nobody knew.
I learned my lesson. When your 3PL switches WMS, sellers can't just sit back. Here's the package I now demand from every warehouse before a cutover.
During Parallel Run, I Watch Four Reconciliation Reports Every Day
A parallel run means the old and new systems run side by side for a while, checking each other. Plenty of sellers treat this as the warehouse's internal business. Wrong. If you don't watch during the parallel run, discrepancies grow right under your nose.
I make warehouse ops send me four reconciliation reports daily. If one is missing, I don't sleep well:
Report 1: Inventory reconciliation. The night before cutover, the old system exports a full inventory snapshot: SKU × location × quantity, nothing skipped. After the new system goes live, compare SKU by SKU. My red line: top sellers must match down to the unit; for long-tail SKUs, any single-SKU variance over 2 units freezes shipping until it's explained. Inventory numbers are my money. Off by 100 or off by 1 — same thing.
Report 2: Order status reconciliation. Every unfinished order in the old system gets listed: picked-not-shipped, in-transit, exception-hold. Each one must be confirmed with a matching status in the new system. A "missing" order is the scariest failure — the order vanishes, but the customer doesn't.
Report 3: Tracking number reconciliation. After the new system prints shipping labels, do tracking numbers flow back to my store backend? One day of broken linkage and the marketplace counts it as late shipment. Account health metrics fall fast and climb back slow.
Report 4: Billing reconciliation. The new system's billing rules are configured from scratch, and the odds of a misconfiguration are higher than you'd think. I audit the cutover month's invoice line by line. Don't call me paranoid — I've seen handling fees double overnight.
| Report | What to check daily | My red line | Who sends it |
|---|---|---|---|
| Inventory | SKU-level old-vs-new variance | Zero variance on top sellers | Warehouse ops |
| Orders | Every open order confirmed | Zero missing orders | Warehouse ops |
| Tracking numbers | Numbers flowing back to store | Halt if broken 4+ hours | Warehouse IT/ops |
| Billing | New billing vs old billing | Line-by-line audit in cutover month | Finance/support |
Cutover Day Schedule: Freeze Orders at 3 AM, Ship Half a Day Only
How cutover day is scheduled decides whether you get a "smooth transition" or a full-blown disaster. Here's my timetable — take it straight to your 3PL:
3 days before: Cut ad spend in half. Turn on vacation mode or extend handling times in your store. Never run a promotion during cutover week. The more traffic, the uglier cutover day gets.
Night before, 11 PM: Old system stops accepting orders. Set your store backend so no new orders sneak in overnight.
Cutover day, midnight–6 AM: Data migration, inventory freeze and snapshot. For these 6 hours, the only things in the warehouse should be IT staff and lights.
6 AM–noon: Trial shipments in the new system, 10–20 orders only. Don't get greedy — trial runs exist to surface problems.
Noon: All four reconciliation reports green? Release full volume. One red report? Roll back (see rollback plan below).
All-day rule: ship half a day's volume. Ship what you can in the afternoon; the rest waits for tomorrow. No overtime rush on cutover day — rushed shipments are wrong shipments.
Quick math on my own little store: one dead shipping day at 300 orders a day and a $25 average order value is $7,500 in sales standing still, while ad spend keeps burning. Cutting budgets during cutover week isn't cowardice. It's arithmetic.
Here's the counterintuitive part: "zero-downtime cutover" is a myth. If a 3PL promises you zero downtime, ask more questions. The trustworthy ones admit there will be downtime, compress it into the dead-of-night window, and hand you a written rollback plan. One more thing: a longer parallel run isn't safer. Past three weeks, people go numb and reconciliation becomes theater. My red line is 2–3 weeks, then you cut over.
Five Disasters, Each More Painful Than the Last — Plus Where I Draw the Rollback Line
These are the five cutover disasters I fear most as a seller. I've seen every one happen to a real person:
1. Inventory "evaporates." Opening inventory gets imported with wrong rows. Some SKU shows 500 units short — the system says in stock, the shelf says otherwise. Result: overselling, then the triple hit of refunds, bad reviews, and account risk. Prevention is report 1. The pre-cutover snapshot is the only truth.
2. Orders "go missing." In-flight orders from the old system never migrate. Goods sit on picking carts with no record in the system. The customer asks "where's my stuff" and you can't even quote an order number. Prevention: report 2, close out open orders one by one.
3. Tracking linkage breaks. The new system never pushes tracking back to the store. The marketplace flags you for late shipment. A friend of mine got a warning this way and wrote a three-page appeal letter. Prevention: report 3 — broken linkage for more than 4 hours means halt.
4. Wrong picks. Barcode rules change; the new system misreads old SKU barcodes and ships the wrong items. Return shipping plus reshipping costs — a double kill. Prevention: physically open and inspect trial shipments. Don't trust the system's "pick verified."
5. The "price hike" invoice. The new billing engine is misconfigured, handling fees double, and you stare at the month-end invoice in disbelief. Prevention: report 4 — audit the cutover month line by line and question every extra cent.
A rollback plan isn't a "we'll figure it out if things go south" — it's written down before cutover. My rollback line has three triggers. Hit any one, roll back immediately:
- Total inventory variance exceeds 0.5%, or any top-seller SKU doesn't reconcile;
- More than 2 errors out of 20 trial shipments;
- Data migration overruns its window by more than 2 hours.
The rollback mechanics need prep too: keep the old system on hot standby for at least a week — don't power it off the day after cutover. Keep the read-only pre-cutover snapshot; it's your only baseline after a rollback.
Most important rule: the rollback decision belongs to one person. Name them in writing (usually the warehouse manager). When they say roll back, you roll back — no committee vote. In a real incident, the time spent in a meeting costs you 500 orders.
Sellers need their own Plan B as well: lower ad budgets during cutover week, vacation mode on, and customer service scripts written in advance ("Our warehouse is upgrading its system; your order may ship 1–2 days late"). Don't improvise after things break.
A system cutover is not the time to be a hands-off seller. The system belongs to warehouse IT; unshipped orders and mismatched inventory cost me money. This checklist is battle-tested — last month another warehouse cut over, I showed up with these four reports, and their ops lead paused and said: "You're the most switched-on seller I've ever met."
By Ah K, E-commerce Seller (5 yrs)
