Amazon Received More Units Than You Shipped: Overages Explained

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

Everyone writes about the shipment where units go missing. Almost nobody writes about the other one. A seller opens Seller Central, pulls up a closed shipment, and the Received column is higher than what he shipped. He declared 950 units. Amazon says it received 990. He is now staring at 40 units that, as far as his records are concerned, do not exist.

The reactions split into two camps, and both are wrong. Camp one panics: something is broken and this will blow up later. Camp two quietly celebrates: free inventory, say nothing and sell through it.

The real explanation is more boring than either, and much more useful. Those 40 units were yours all along. They were physically inside your boxes when the truck left. Your manifest just never counted them. Once you understand how a manifest undercounts real, physical units, overages stop being mysterious and become what they are: a diagnostic reading on your outbound counting process.

I run PrepVia, an Amazon FBA prep center in Miami, Florida. Across thousands of shipments we process, receiving discrepancies in both directions are among the most common things sellers ask us to explain. Here is where the extra units come from, why they are not free, and how to make the number go to zero.

What a Receiving Overage Is, and Where to See It

A receiving overage is simple to define: the quantity Amazon logs as received for a shipment is greater than the quantity you declared when you created it. It is the mirror image of the shortage everyone worries about, and it comes from the same gap: paperwork versus what was physically in the cartons.

Here is where to confirm you actually have one, because interim numbers mislead people constantly.

If the ledger is unfamiliar, start with how the Amazon Inventory Ledger actually works. It is the source of truth for everything in this article.

Where the Extra 40 Units Actually Come From

Back to the example: you declared 950 units and Amazon closed the shipment at 990 received. Sellers imagine exotic explanations. In practice, nearly every overage traces to one of three mechanical sources.

1. The manifest undercounted what was physically in the boxes

This is the dominant cause, and it has three classic flavors.

Multiple packers, one count. Packer A fills a box with 30 units and logs 30. Packer B walks past, sees room, tops the box off with 6 more from the same pallet, and logs nothing, because in his mind he was helping, not creating inventory records. The box now holds 36 real units and a manifest line that says 30.

Boxes sealed without a final scan. The count was taken from the pick list, or from memory, or from counting stacks by eye. Nobody scanned what actually crossed the box rim. Whatever the pick was off by, the manifest is off by, and pick errors run in both directions.

Case-packs counted as 1. A sealed case of 12 gets entered as one unit because the person at the station scanned the case barcode once and moved on. That single keystroke error produces an 11-unit overage on its own. Do it with a case of 24 and one keystroke accounts for 23 of the 40 extra units in our example.

2. Units from a previous shipment surfacing in this cycle

Amazon receiving is a rolling process, not a single event. A carton that was set aside, misrouted internally, or delayed at a fulfillment center can be processed days or weeks after the rest of the shipment. When the timing crosses a reconciliation window, last cycle's stragglers get counted alongside this cycle's arrivals, and the current shipment looks fat.

The signature: an earlier shipment of the same SKU showed a shortage that later healed, and the overage on the new shipment appears at roughly the same time. The ledger dates give it away.

3. The fulfillment center corrected its own count

The first receive scan happens at speed. During putaway, cycle counts, or downstream handling, Amazon recounts, and when the recount finds more units than the first pass logged, it posts additional receive events. From your side this looks like units materializing out of nowhere; from Amazon's side it is routine self-correction.

An Overage Is Not Free Inventory

Camp two deserves a direct answer. No, you did not gain 40 units. You bought them, prepped them, and paid to ship them. They were always yours. Amazon finding them adds nothing to your position, it just moves units from invisible to visible.

What the overage does add is doubt, and doubt is expensive in three specific ways.

First, your books are wrong. Your records and reorder math were built on 950; reality was 990. One shipment barely matters. A process that drifts a few percent every shipment compounds into reorder decisions made on fiction.

Second, shortages become undecidable. The whole method for pursuing a genuine shortage, laid out in the declared-versus-received breakdown, rests on your declared count being trustworthy. A seller whose shipments regularly close over has no standing to insist that this time, the count was exact and Amazon must be wrong.

Third, your evidence gets weaker exactly when you need it strong. When you eventually need to prove Amazon received a shipment, your case is built on documentation discipline. A trail of overages is documentation of the opposite.

One more reason not to celebrate: receive counts can be revised, and a later recount can adjust downward just as easily. Spending the overage before the history settles is how sellers end up oversold on paper inventory.

The Netting Trap: Why You Must Reconcile Shipment by Shipment

Here is a quarter that looks healthy and is actually broken.

Look at the bottom line and you see plus 7 units across the quarter, a rounding error, nothing to fix. Look at the rows and you see that not one shipment closed clean. The overages and shortages cancel in the aggregate, which is what makes the net view dangerous: it launders four process failures into one reassuring number.

This matters because the two directions have completely different meanings. A shortage might be recoverable money. An overage is a process defect. Netting them destroys both signals, and the Inventory Ledger, built around net movements per SKU, will happily let you do it if you never look at the shipment level.

What a Recurring Overage Says About Your Packing Process

One overage is an anecdote. Overages on most shipments are an X-ray of your pack-out floor, and the picture is specific: units are entering boxes without entering records.

If you pack in-house, the checklist writes itself. Who is allowed to put a unit in a box? Is there a scan at the box rim, or a count from a list? How are case-packs recorded? Is the manifest generated from the scan record, or typed by a person at the end of the day?

If a prep center packs for you, the same questions apply. Ask how a unit gets from the receiving shelf into a numbered box, and what record exists afterward that says which units went into which box. A provider who cannot answer in one sentence is counting by eye. The prep center agreement checklist covers turning that answer into a contract term rather than a verbal assurance.

When a Large Overage Deserves Investigation

Small overages, a few units on an occasional shipment, are counting noise. Log them, watch the trend, move on. Three patterns deserve a real look the day you see them.

Overage that tracks your case size. Plus 11 or plus 23 is the case-pack-entered-as-1 error, a case size minus one, and it means your station workflow lets a case barcode masquerade as a unit barcode. Plus 12 or plus 24 in exact multiples points to a whole case that was packed but never logged.

An overage on one SKU paired with a shortage on another in the same shipment. Plus 24 on SKU A and minus 24 on SKU B is not two mysteries, it is one mislabeled or misboxed case. Amazon scanned what the labels said. If the labels said the wrong thing, the wrong SKU got credited, and the units now sitting under the wrong FNSKU will eventually ship to a customer who ordered something else.

Received units of a SKU you did not include in the shipment at all. This is the strongest version of the same signal and it always means a labeling or box-content error somewhere upstream.

Closing the Loop: Scan-Out by Box

Everything above is diagnosis. The cure is one discipline applied at one moment: every unit is scanned into a specific, named box at the instant it goes in, and every downstream document is generated from those scans.

Final Take

An overage feels like a gift and reads like a glitch, and it is neither. It is your own inventory arriving off the books, and the only message in it is that your pack-out process counts worse than Amazon receives.

Treat every closed shipment as a graded exam. The grade is the absolute deviation between declared and received, overages counted the same as shortages, tracked per shipment and per SKU. Get that number to zero and both problems disappear together, because they were always the same problem: units moving without records. The sellers who reconcile shipment by shipment catch it in week one. The sellers who watch the net number find out during Q4.

Frequently Asked Questions

Why did Amazon receive more units than I shipped?

Almost always because your shipment manifest undercounted what was physically in the boxes. The common causes are multiple packers feeding one count, boxes sealed without a final scan, and case-packs entered as one unit instead of the full case quantity. Two other sources are straggler units from a previous shipment being processed in the current cycle and the fulfillment center correcting its own first count. The units were yours the whole time, the paperwork just missed them.

Is an FBA receiving overage free inventory?

No. The extra units were physically packed in your boxes, so you already bought, prepped, and shipped them, and nothing was gained when Amazon found them. What the overage actually tells you is that your outbound count is unreliable, which makes every future shortage harder to judge and can be revised downward later by a recount. Treat it as a process warning, not a windfall.

What causes FBA manifests to undercount units?

The three big ones are multiple people packing against a single count, boxes sealed without a verification scan at the box rim, and case-packs recorded as one unit instead of twelve or twenty four. Manifests typed from a pick list instead of generated from scans also inherit every picking error. Each cause leaves real sellable units inside the boxes that the paperwork never claimed.

Should I worry about small overages on FBA shipments?

A few units on an occasional shipment is counting noise, worth logging but not investigating. What deserves attention is a pattern: overages on most shipments, overages that track your case-pack size, or an overage on one SKU paired with a shortage on another in the same shipment. A pattern means your pack-out process has a structural gap, and the same gap that creates overages also creates shortages.