3PL onboarding: the go-live week, told as a timeline

Short answer: 3PL onboarding fails in the data, not in the trucks. The merchants who struggle sent messy SKU files, skipped the first-receipt verification, and started selling against stock the 3PL hadn't confirmed. The merchants who go live clean spend two weeks on data prep, run one small test shipment, and cut over on a Tuesday — never a Friday. Here's the whole move as a timeline, with the failure points marked where they actually happen.

The store we're following

To make this concrete, follow a bath-bomb brand through its move — 240 SKUs across 12 scent families, fulfilling from a garage-plus-storage-unit setup at roughly $900K GMV. They signed with a mid-size 3PL in September 2026. Nothing about their arc is unusual: the same sequence applies whether you hold 240 SKUs or 2,000, and whether your destination is an independent 3PL or Shopify's own fulfillment network (the tradeoffs between those two are covered in the SFN vs 3PL comparison — this article is about the move itself).

One framing rule before the timeline: onboarding ends when the ongoing rhythm starts. The weekly reconciliation, the SLA reviews, the counting-through-a-3PL discipline — that's the relationship, and it's covered separately in the 3PL inventory management guide. This article gets you to the handoff.

Weeks 1–2: data prep (where most onboarding dies)

The 3PL's WMS is literal. Your Shopify catalog grew organically for three years; it contains everything the WMS will choke on.

What the bath-bomb brand actually did, week by week:

• Purged dead SKUs. 31 discontinued scents were archived in Shopify but still "active" in the export. The 3PL would have priced storage and receiving per SKU on ghosts. Rule: nothing enters onboarding that you don't intend to keep stocking.
• Fixed SKU structure. Their SKUs had evolved — some carried scent and size (BB-LOV-8OZ), some just a product ID. The 3PL needs one unambiguous SKU per physical variant, and it must match Shopify's SKU field exactly, character for character. Case sensitivity matters. So do stray spaces.
• Unit-of-measure truth. The brand sells singles but receives cases of 24 from their supplier. The 3PL needs to know both numbers per SKU, or your first case-pack receipt becomes a 24-unit variance on every line.
• Dims and weights. Per-SKU weight and dimensions for everything the 3PL will pick. Guessing these breaks their rate card and your storage invoices later.
• Supplier and PO data. The 3PL needs to know inbound POs by number so receiving ties to a record. If you don't have a PO convention yet, start one — a format like INV-2027-001 gives every shipment a unique, sortable identifier the 3PL can reference back to you.

The failure mode to avoid: sending "the catalog as it is" and promising to clean up later. Every later correction becomes a ticket, and tickets during onboarding move at the 3PL's pace, not yours. A clean SKU and catalog structure is the cheapest thing on this whole timeline.

Weeks 2–3: the commercial paperwork nobody warned you about

(Fulfillment-model context, if you're still weighing whether a 3PL or Shopify's own network is the right destination, sits in the Shopify Help Center's fulfillment overview — Order management and fulfillment, accessed October 2026. This section assumes you've chosen.)

Between data prep and physical movement sits a stack of documents that define the next three years:

1. The SLA. Receiving turnaround (hours from arrival to sellable), order cutoff times, same-day-ship thresholds, accuracy commitments, and the remedy when they miss. Get numbers, not adjectives. "Same-day receiving" and "receiving within three business days" are different businesses — and the difference silently corrupts your days-of-cover math, because inbound stock you can't sell yet isn't stock.
2. The rate card, line by line. Receiving per pallet/carton/unit, storage per bin/pallet/sq ft, pick-pack per order plus per additional item, returns processing, and the long tail: account management fees, monthly minimums, inbound freight notes. Ask which activities trigger charges that aren't listed.
3. The systems agreement. Which integration connects their WMS to Shopify, what syncs (orders out, inventory back), how often, and what happens during an outage. This single document determines most of your future reconciliation workload.
4. Who owns shrinkage. Units lost in their custody — the standard framing makes the 3PL responsible up to defined evidence thresholds, but the definition is negotiable. Negotiate it before your first loss, not after.

Week 3–4: the first receipt — your real go-live

Here is the step merchants skip and regret. Do not move your full stock first. Send one or two pallets of your bestsellers and treat the receipt as an audit of the entire onboarding.

The bath-bomb brand sent 2 pallets — 8 SKUs, 1,150 units, PO INV-2027-041 — and verified the receipt line by line:

• Counted vs. declared, per SKU. They declared 120 units of BB-LOV-8OZ; the 3PL received and made sellable 120. One SKU came in at 118 — two units short against the supplier, caught at the 3PL's dock, which is exactly what receiving is for (the receiving checklist logic doesn't change because someone else's dock does the counting — it just gets a counterparty).
• Sellable in Shopify, same day. Units were available on the 3PL's Shopify location within the receiving SLA. When they weren't — one pallet sat unprocessed for two days during the test — that was a finding, not a footnote, and it went into the SLA conversation before the full move.
• A live order, end to end. They placed a test order to a founder's address: picked, packed, shipped, tracking synced to Shopify, inventory decremented. The billing cycle for that one order was also checked against the rate card — pick fee, packaging fee, surcharges. Billing surprises are cheapest to discover at one-order scale.

Only after the test receipt reconciled did they schedule the main transfer.

The go-live week, day by day

Never Friday. Go live early in the week so the 3PL's full staff is present when the almost-inevitable snags appear. Here's the shape of the week:

• Day 0 (Friday before): Freeze outbound from the garage. Final local count of remaining stock. Set the storefront's in-house location to sell-through its last units or close it.
• Monday: Transfer of remaining inventory to the 3PL. Ship with a packing list that matches PO INV-2027-042, SKU-by-SKU.
• Tuesday–Wednesday: 3PL receives. You verify every line against your packing list before applying anything in Shopify — same discipline as the test receipt, now at full scale.
• Thursday: Flip order routing to the 3PL location in Shopify. Run a second live test order. Watch the first real customer orders flow through end to end.
• Friday: First week-one review: receive times, first order bills, sync behavior, and your top-20 SKUs' counts on both sides. Everything found this week gets logged — it's the seed of the ongoing discrepancy log.

The stock that's in transit during Monday–Wednesday is the honest hard part: it's cash you own and coverage you can't sell. (Shopify's own fulfillment docs make the same distinction between fulfillment services and self-fulfillment — Shopify Help Center, fulfilling orders, accessed October 2026.) Time the move against your supplier lead times so the transition week doesn't sit on top of a replenishment gap — if inbound POs were already due, delay the cutover, not the coverage.

The five onboarding failures, ranked by how often they happen

Not a mystery — a pattern that repeats across moves:

1. Dirty SKU data (by far the most common): mismatched SKU strings, dead SKUs, missing dims. Costs weeks of ticket ping-pong.
2. Skipping the test receipt. The full stock arrives before anyone knows how the 3PL receives, syncs, or bills.
3. The SLA signed but never specified. "Best efforts" language on receiving and accuracy, discovered meaningless during the first peak week.
4. Cutover on a Friday with skeleton staff on both sides.
5. Replenishment timed during the move. A PO lands mid-transition; nobody's watching both docks; the receipt becomes a variance nobody can trace.

Notice what's absent: the physical move itself, trucks and pallets, is the easy part. Onboarding is a data project wearing a logistics costume. (For the market-side view of how 3PL capacity and rates move — the context that shapes your SLA negotiating position — industry trackers like Armstrong & Associates' North American 3PL market coverage are the standard reference, accessed October 2026.)

What onboarding does NOT fix

Two honest notes before you sign anything.

First, onboarding doesn't fix a fulfillment model that's wrong for you. If your volume is small and your orders simple, a 3PL's fees may exceed what you save in time — the decision framework lives in the SFN-vs-3PL-vs-self-fulfillment comparison, not here.

Second, onboarding doesn't fix your demand math. Moving stock doesn't change what's selling or how fast; your reorder discipline needs to survive the transfer intact. The buying rhythm you ran in-house — cover, lead times, order-by dates — carries over unchanged; it just reads from a new location now.

Common questions

How long does 3PL onboarding take? For a store under 5,000 SKUs, plan on 3–5 weeks: one to two weeks of data prep and paperwork, one week for the test receipt, one week for the cutover. Stores that try to compress it to days usually pay for it in receiving errors and billing disputes during the first month.

What data does a 3PL need from me? Per SKU: exact SKU string matching Shopify, description, unit of measure, case pack, weight and dimensions. Plus your PO list with expected quantities, your supplier's ship-from details, and your order-profile expectations (units per order, peak days) so they can staff receiving and picking.

Should I send all my inventory to the 3PL at once? No. Send a test shipment of one or two pallets first and verify the receipt, the sync to Shopify, and a live order end to end — including the billing against your rate card. Cut over the full stock only after the test receipt reconciles line by line.

When should I go live with a 3PL — which day of the week? Early in the week, Monday or Tuesday, so both teams are at full staff when snags appear. Never Friday. Also avoid cutting over during a promotion or in the same window as a large inbound PO, so the transition doesn't compete with your coverage.

What SLA terms matter most in 3PL onboarding? Receiving turnaround (hours from arrival to sellable), order cutoff and same-day-ship commitments, pick-and-pack accuracy, inventory sync frequency with outage behavior, and who owns shrinkage. Get each as a number with a remedy, in writing, before the first pallet moves.

Where to go next

This week, before you sign anything: export your catalog and audit it against the WMS's requirements — SKU uniqueness, case packs, dims, dead SKUs. That audit tells you how long your own onboarding will really take. Then, once you're live, the rhythm changes from project mode to maintenance mode; the weekly reconciliation and SLA review that sustains the relationship is laid out in the 3PL inventory management guide.