How Amazon FBA Shipments Actually Work

What an FBA shipment actually is

People use "FBA shipment" to mean three different things, and mixing them up is where most confusion starts. A shipping plan is the request you create in Seller Central: these SKUs, this quantity, shipping from this address. A shipment is what Amazon turns that plan into — one or more physical moves, each with its own shipment ID, tracking number, and destination fulfillment center. FBA itself is neither of these; it's the fulfillment program that stores, picks, and ships to customers once your inventory has arrived.

That distinction matters because Amazon, not you, decides how many shipments a single plan becomes. You might submit one plan for 500 units of one SKU and get back instructions to send cartons to three different fulfillment centers. That's not an error in your setup — it's how Amazon distributes stock across its network based on where it forecasts demand.

How to prepare your first FBA shipment

The mechanics are the same whether it's your first shipment or your fiftieth: register for FBA, convert or create listings that Amazon will fulfill, then run the Send to Amazon workflow. That workflow asks for unit prep (poly bags, suffocation warnings, bubble wrap depending on category), case-pack information if you're shipping in cartons rather than loose units, and box content labeling so receiving staff can match what arrives against what the plan says should arrive.

• Prep: follow the category-specific prep requirements before anything ships — this is the single most common reason receiving gets delayed.
• Label: FNSKU labels go on the unit, box content labels go on the carton. Confusing the two causes discrepancies at receiving.
• Book the carrier: small parcel through Amazon's partnered carrier program for light shipments, LTL or FTL freight with a dock appointment for pallet volume.
• Track to receiving: a shipment isn't done when the truck leaves your dock. Watch it through to "closed" status, where received quantities are reconciled against what you sent.

For a first shipment specifically, keep the quantity modest. It's tempting to send your entire first production run in one plan. A smaller first shipment gives you a clean read on prep quality and labeling accuracy before you commit a full batch to a process you haven't run yet.

Combining and splitting shipments — how it actually works

You can combine multiple SKUs into a single shipping plan, which is worth doing if they're shipping from the same origin — it reduces the number of separate freight moves you have to book and track. What you generally can't do is force Amazon to keep everything at one destination. Amazon's placement logic spreads inventory across its network for delivery speed, and a shipment split into two or three destinations is the normal outcome for anything beyond a small parcel shipment.

Amazon does sell a way around this: the FBA inbound placement service lets you pay a per-unit fee to send everything to one or two fulfillment centers instead of Amazon's preferred distribution, and Amazon redistributes it from there. Whether that fee is cheaper than running three separate freight legs yourself depends on your carton count, weight, and lane — it's a real trade worth pricing out, not a fee to avoid on principle.

A worked example: what a split shipment looks like

Say you're sending 600 units of one SKU, packed 40 units to a carton. That's 15 cartons total. Submit that as one shipping plan and Amazon might come back with instructions to send 6 cartons to one fulfillment center, 5 to a second, and 4 to a third. You now have three separate shipments from one plan, each needing its own carrier booking or its own line on a single LTL bill of lading if your freight partner can consolidate the pickup.

The cost question is straightforward even without a specific rate card in front of you: three destinations usually means three delivery legs on your freight bill, versus one leg plus Amazon's placement fee if you consolidate. Which is cheaper depends on your carton weight and the lanes involved — run both numbers before you book, because the answer flips depending on volume and season. This is exactly the kind of comparison that gets skipped when a shipment gets built under deadline pressure, and it's a small decision that compounds across every reorder cycle for that SKU.

The mistakes that actually cause problems — including ours

The most common failure isn't exotic. It's shipping the full forecast quantity in one plan instead of working batches, which ties up cash in a single SKU sitting in transit for weeks with no visibility into what's sellable yet. The second most common is treating a shipment plan as final once it's created. Amazon can re-route a plan to a different set of fulfillment centers between creation and pickup, and we've had an LTL truck booked against a plan that Amazon had already re-assigned to different destinations before the pallet left the dock. The fix isn't complicated — check plan status again right before pickup, not just when you built it — but it's the step that gets skipped when three shipments are moving at once.

Full Circle has managed more than $500M in revenue across 100+ brands, and shipment discrepancies — units received don't match units shipped, or a carton goes missing between the dock and the receiving scan — show up in nearly every inventory audit we run, regardless of brand size. It's not a sign of a badly run operation. It's a routine cost of freight volume, and the brands that catch it fastest are the ones checking reconciliation weekly rather than at reorder time.

When the numbers don't match

If received quantity is lower than what you shipped, don't assume it's lost until you've checked the shipment's content history against the carrier's proof of delivery — sometimes it's a labeling mismatch that gets corrected once someone at the fulfillment center re-scans a mislabeled carton. If it genuinely is short or damaged, file a case through the shipment's discrepancy report rather than a general support ticket; it routes faster and keeps the paper trail Amazon needs for reimbursement. Amazon does enforce a filing window for lost and damaged claims, and that window has moved before, so check the current policy rather than relying on what it was last year.

If the leak you're chasing isn't in the warehouse at all — wasted ad spend, a campaign burning budget on the wrong search terms — that's not a shipment problem, and no amount of inbound-placement tuning fixes it. That's a job for Dr. PPC, not inventory tools.

Where this fits with Dr. Stock

Most sellers can run their own shipments fine with the steps above. Where it gets harder is at volume — multiple SKUs, multiple origins, reorders timed against a forecast that keeps moving — where a missed reconciliation or a mis-sized shipment plan quietly becomes a stockout three weeks later. Dr. Stock, a managed product from Fable 5 at Full Circle, works that specific layer: shipment discrepancies, reimbursement recovery, and the reorder timing that sits behind stockouts, with purchasing decisions always routed to a human regardless of how much autonomy the account runs on. It won't ship a box for you — it's not a 3PL — and it won't replace an ERP if that's what you actually need. It's built for the leak that's already happening in a shipment record, not the warehouse floor itself.