Amazon Says FBA Units Are Missing? Check This First

By Bernardo Campelo, Forbes Business Council E-Commerce Leader, Amazon SPN Certified provider, Amazon SP-API authorized partner, and Founder of PrepVia.

The message arrives the same way every time. A seller opens a shipment in Seller Central, looks at the Received column, and finds it short. Shipped says 1,200. Received says 1,050. The screen flags 150 units as a discrepancy, and every instinct fires the same alarm: Amazon lost my inventory.

Sometimes Amazon did. Far more often, something much less dramatic happened, and it happened before the truck ever left. The most misunderstood mechanic in the entire FBA inbound system is this: the shipped quantity on that screen is not a count of what shipped. It is a count of what you planned to ship, frozen at the moment the shipment was created, and Amazon never adjusts it downward, no matter what happens at the dock afterward.

I run PrepVia, an Amazon SPN Certified prep center in Miami, Florida. Across thousands of shipments we process, the declared-versus-received gap is the question sellers bring to us most often in a panic, and the answer is usually sitting in their own records. Below: the mechanism, a complete worked example, and the audit sequence that separates a bookkeeping gap from a real loss.

The Quantity on the Screen Is the Plan, Not the Truck

Here is the mechanic, stripped to its bones. When you create an FBA shipment, the shipment is born with a declared quantity: the number of units in the plan at the moment of creation. Send to Amazon, an older workflow, a prep partner building it for you: the mechanic is the same. That number is what the Shipped column will display for the rest of the shipment's life.

What that number is not: a scan of what got loaded. There is no scale at your dock reporting to Seller Central. There is no carrier scan that decrements the declaration box by box. The declared quantity is a statement of intent, recorded once, and the entire receiving process at the fulfillment center reconciles against that statement.

In the early workflow statuses you can still edit contents freely. After you confirm, Amazon only permits small quantity adjustments: about 5 percent or six units per SKU as of 2026. A whole pallet cut at the dock is far beyond anything the workflow will let you edit in. And here is the part that catches everyone: boxes pulled at the last minute are not deducted by anyone. Not by Amazon, because Amazon cannot see your dock: a declared box left on the warehouse floor looks identical to a declared box in transit until receiving gives up waiting for it. Not by the carrier, whose pickup scan counts boxes and pallets, never units. And usually not by the seller, because the seller was not standing at the dock when it happened.

So the account shows 1,200 units shipped because 1,200 units were declared. The truck carried 1,050 because 1,050 were loaded. Nothing in the system reconciles those two facts until the fulfillment center counts what came out of the boxes, and at that point the difference surfaces in the most alarming possible framing: units missing.

A Complete Worked Example: 1,200 Planned, 1,050 Shipped

Say you planned 1,200 units of a single SKU, packed 30 units per box across 40 boxes. The shipment is created, box labels print, the declaration reads 1,200. Then the real world happens at the dock.

Two boxes fail final inspection: retail stickers are still exposed on some units, and the team pulls both boxes rather than delay the pickup. Three more boxes are cut when the pallet stack exceeds the height the carrier will accept. Five boxes stay on the warehouse floor. Thirty-five boxes, 1,050 units, get loaded and picked up.

Nobody edits the shipment. The pickup window was closing, and a 150-unit cut is far beyond the small post-confirmation adjustment the workflow permits. Here is what every screen involved now shows:

The 150 units did not vanish inside Amazon's network. They never entered it. But the account will carry that 150-unit gap as shipped-and-not-received indefinitely, because the one number that could close the gap, the declaration, is the one number nothing ever updates.

Multiply this pattern across a year of shipments and the cumulative gap looks enormous. Audit shipment by shipment before concluding anything. Most of it will resolve into declarations that were never adjusted, matched by merchandise that stayed at origin or moved out later under a different shipment ID.

Why Boxes Stay Behind After the Plan Is Locked

Boxes staying behind is not sloppiness. It is how freight works. Every reason makes sense at the dock. None of them is visible to whoever reads Seller Central three weeks later.

Notice the common thread: every row leaves the declaration untouched and the merchandise at origin. Notice also that the gap is almost always a multiple of whole boxes. That detail matters below, because genuine receiving losses look different: partial boxes, odd counts, scattered noise across many SKUs.

The Audit: How to Reconcile a Shipment That Shows Missing Units

This is the sequence we run at our FBA prep center whenever a client brings us a shipment with a scary discrepancy line. It works from the outside too, with the documents any seller can gather.

Declaration Gap or Real Loss: Reading the Signals

After the audit, the evidence sorts itself into one of two columns. Read them side by side before deciding what to do next.

If your evidence lands in the right-hand column, you have a genuine loss and a genuine claim. If it lands in the left-hand column, you have a paperwork artifact, and filing a claim against it will end badly, for a reason worth spelling out.

When the Gap Is Real: The Claim Path

Real inbound losses happen. Boxes disappear between the carrier scan and the fulfillment center shelf, and Amazon has a reimbursement process for exactly that. When the audit above leaves a residual gap on units you can prove were loaded and delivered, file the claim, and structure the evidence the way Amazon's investigators evaluate it.

The full process, the eligibility windows, and the evidence list are in our guide to FBA reimbursement for lost inbound shipments. Two companion reads matter just as much: how to prove Amazon received your FBA shipment, which covers the delivery-to-receipt evidence chain, and the patterns behind denied FBA reimbursement claims, because the most common denial we see is a claim filed against the declared quantity instead of the proven-shipped quantity. And if the shipment never arrived at all and the status still says In Transit, start instead with the stuck-in-transit playbook, because that is a different problem with a different clock.

Prevention: Reconcile Before the Truck Leaves

The entire problem exists because reconciliation happens at the wrong end of the trip. The fulfillment center counts on arrival; nobody counts at departure. Move the count to the dock and the discrepancy line loses its power to frighten anyone.

Final Take

The most frightening number in Seller Central is usually the most boring one. Shipped minus received looks like loss and triggers loss-shaped responses: panicked support cases, premature claims, distrust of every party in the chain. But the shipped number was never a measurement. It was a plan, written before the dock had its say, and the system will never go back and correct it.

So audit before you escalate. Reconcile by shipment, count what was loaded, read the ledger, wait out the receiving window, and let closed shipments finish trickling. What survives that process is a real claim worth filing properly. What does not survive it, and across thousands of shipments that is most of it, was never missing at all.

Frequently Asked Questions

Why does Amazon show more units shipped than I actually sent?

Because the shipped quantity on the shipment screen is the quantity you declared when the shipment was created, not a count of what left your dock. Amazon never reduces that number when boxes are pulled or held back after the plan is made. If 150 units stayed behind at the warehouse, the screen still shows the original figure, and the difference surfaces as missing units at receiving.

Does Amazon reduce the shipment quantity if boxes are removed?

No, not automatically. After you confirm a shipment, Amazon only allows small manual quantity adjustments per SKU, roughly 5 percent or six units, so a whole box or pallet pulled at the dock cannot be edited out of the declaration. Boxes removed at the dock or during loading are not deducted automatically by Amazon, the carrier, or anyone else. The only accurate record of what shipped is the physical count of boxes that were actually loaded.

How do I audit an FBA shipment that shows missing units?

Reconcile at the shipment level, not the SKU level, because renamed SKUs and merged listings distort SKU totals. Count only the units packed in boxes that were physically loaded, using box content data and the carrier pickup documents. Then compare that number against the received count and the receipt events in the Inventory Ledger. The gap between declared and physically shipped explains most of what looks missing.

Can a closed FBA shipment still receive units?

Yes. Closed means Amazon marked receiving complete, not that the record is frozen forever. Small late receipts of a few units still post to closed shipments when stray boxes are processed weeks later. Always recheck closed shipments before treating a small gap as a permanent loss.