Why Mechanical Receiving Increases This Specific Error
Amazon has shifted a significant portion of how inbound FBA shipments get checked in away from a human physically counting and verifying each unit, toward mechanical and automated processing. Cartons move through scanning systems that read barcodes, sort by SKU, and log received quantities largely without a person opening every box and counting contents by hand the way receiving used to work at smaller scale.
That shift has coincided with a documented spike in sellers reporting a very specific problem: the quantity Amazon's system records as received doesn't match what actually shipped, even when the seller's own carrier tracking, UPS or otherwise, confirms the correct quantity left their facility and was delivered to the fulfillment center. This isn't a case of sellers miscounting their own outbound shipment and blaming Amazon. The carrier's own proof of delivery shows the right count arriving. The mismatch happens somewhere inside the fulfillment center's own receiving process.
Mechanical receiving is efficient at scale, but it's also more prone to certain specific failure modes than a careful human counter would be. A barcode that's smudged, partially obscured by shrink wrap, or printed at an angle that a scanner reads inconsistently can cause units to be missed or double counted. Units that are physically stuck together, common with certain packaging shapes or with static-prone materials, can get scanned and counted as a single unit when two or three are actually stacked together. And in a mixed-SKU carton, a scanning or sorting error can misattribute units from one SKU to another entirely, which produces a different and even more confusing version of this problem.
A Real Case: 500 Units Shipped, 100 Received
One of the more extreme documented examples involved a seller who shipped 500 units into FBA and had the fulfillment center's system record only 100 units as received, a discrepancy of 400 units on a single shipment. That's not a rounding error or a small miscount that could plausibly be explained by a couple of missed barcodes. That's four out of every five units in the shipment simply not showing up in Amazon's receiving record, despite carrier tracking confirming the full shipment arrived.
The gap between what was shipped and what got logged as received, in a single documented case. When a discrepancy is that large, it points strongly toward a systemic scanning, sorting, or logging failure at the receiving dock rather than any plausible version of the seller having shipped the wrong quantity in the first place.
What makes this genuinely painful is what happens next. When a seller opens a case describing a discrepancy like this, Seller Support's default posture leans toward treating the warehouse's recorded count as correct and the seller's claim as the thing that needs to be proven wrong. That's a real burden shift. You're not just reporting a problem, you're building a case to overcome an institutional assumption that the fulfillment center got it right.
The Documentation You Need Before You Ship, Not After
By the time you notice a receiving discrepancy, the shipment has already been received, sorted, and possibly partially sold through. Your ability to win a reimbursement case depends almost entirely on documentation you should have created before the shipment ever left your facility, not evidence you scramble to assemble after the fact.
- Carrier manifest and proof of delivery. Your UPS, FedEx, or freight carrier's own record of what was picked up and confirmation of delivery to the fulfillment center, showing the correct piece count or weight consistent with your claimed unit quantity.
- Your packing list, matched to the shipment plan in Seller Central. The itemized list showing exactly what went into each carton, matched against the shipment ID and box contents you declared when you created the shipment in Seller Central, not a generic packing slip that doesn't tie back to that specific shipment.
- Photos or video of the sealed carton before pickup. Time-stamped images or video showing the carton packed, counted, and sealed, ideally showing the unit count visible during packing and the final sealed state before the carrier took possession. This is the single most persuasive piece of evidence you can have, because it establishes what was inside the box before it ever left your control.
- Unit-level barcode scan logs, if your operation has them. If you scan each unit's barcode during your own packing process (common for sellers using warehouse management software or a 3PL with scanning discipline), that log is strong supporting evidence tying an exact unit count to an exact carton and shipment ID.
Don't wait until you've been burned once to start documenting shipments this thoroughly. Build carton-sealing photos and packing list retention into your standard shipping workflow for every FBA inbound shipment, the same way you'd retain invoices for tax purposes. The cost of taking a few photos per carton is nothing next to the cost of having no evidence when a 400-unit discrepancy shows up on your account.
How to File and Escalate a Receiving Discrepancy Case
A receiving discrepancy is a distinct problem from a standard "lost inventory" claim, and treating it as the same thing in how you file the case weakens your position. A lost inventory claim typically concedes that the units were received and then went missing somewhere inside the fulfillment network afterward. A receiving discrepancy claim asserts something different and more specific: that the units were never correctly logged as received in the first place, despite arriving.
- File the case specifically referencing the shipment ID and the discrepancy between shipped and received quantities, not a general inventory adjustment inquiry. Use the reconciliation report tied to that specific shipment as your reference point, not your overall inventory ledger.
- Attach your pre-shipment documentation immediately in the initial case, rather than waiting to see if Amazon asks for it. Cases that arrive with carrier proof of delivery, packing list, and carton photos already attached move faster and get taken more seriously than a case that opens with just a complaint and documentation added later under pressure.
- Explicitly state the carrier confirmed delivery of the full quantity, and include the carrier tracking number and delivery confirmation details in the case text itself, not just as an attachment that might get skimmed.
- If the first response is a denial or a generic reply asserting the warehouse count is correct, escalate rather than closing the case. Request escalation to the Seller Support team specifically handling FBA reconciliation issues, and reference that you have carrier-confirmed delivery evidence that conflicts with the recorded receiving quantity.
- Keep every case number and correspondence, since a pattern of repeated receiving discrepancies across multiple shipments, documented with case numbers, is itself useful evidence if you need to escalate further or raise the issue through your Amazon account manager if you have one.
The SKU-Level Mismatch: A Distinct Diagnostic Clue
There's a subtler and, in some ways, more revealing version of this problem worth calling out specifically to Seller Support when you see it. Sometimes the total quantity received across an entire shipment matches what you shipped, but the per-SKU breakdown inside that total is wrong. One SKU shows fewer units received than you shipped, while a different SKU in the same multi-SKU shipment shows more units received than you actually sent.
A straightforward shortage (you shipped 500, they logged 100) can, in theory, get argued away as a shipping or counting error on your end, however implausible that argument is with good documentation. A SKU-level mismatch where the total is correct but the per-SKU counts are scrambled is much harder to explain as anything other than a misattribution error during receiving, units from one SKU getting logged against a different SKU's barcode. Call this pattern out explicitly by name when you file a case, because it points Amazon's investigation toward the right kind of error rather than a generic "some units are missing" framing.
This pattern also matters because it corrupts your inventory and performance data in a way that's easy to miss if you're only watching your total unit count. A SKU showing artificially low received quantity can trigger unnecessary restock urgency or even affect your in-stock rate and IPI score, while the SKU showing artificially high quantity sits with phantom inventory that will eventually create its own reconciliation problem when it doesn't sell through as expected. Checking your Manage FBA Inventory Reconciliation report at the SKU level after every shipment, not just glancing at the total received count, is the only reliable way to catch this version of the problem early.
Realistic Expectations for Reimbursement
Even with strong documentation, treat this as a process that takes real time and persistence, not a same-week resolution. Cases involving significant discrepancies, particularly ones that get escalated past the first response, commonly take several weeks to resolve, and multiple rounds of correspondence are the norm rather than the exception, especially if the first response is a denial that you then have to appeal with additional evidence.
Reimbursement success is genuinely higher for sellers who show up with the full documentation package described above than for sellers who file a case with just a description of the problem and no supporting evidence. Amazon's own reconciliation systems do periodically catch and correct some receiving errors without a seller ever having to file a case at all, which is worth checking for before you assume a manual case is your only path, since an automatic adjustment sometimes appears in your reimbursement reports on its own within a few weeks of the original shipment.
The larger point worth internalizing is that this is a known, recurring category of error tied to how modern fulfillment centers process inbound freight, not a rare fluke or a sign you did something wrong. Building strong shipment documentation into your standard process, treating a discrepancy as its own distinct case type rather than a generic inventory complaint, and specifically flagging SKU-level mismatch patterns when you see them are the concrete steps that move you from being at the mercy of Seller Support's default assumptions to building a case they can actually act on.
