FBA Inbound Discrepancies: Reconciling Short-Received Units After Your Shipment Checks In
Where short-received FBA units actually go, how to reconcile a shipment after check-in, and the prep-side carton records that make a discrepancy claim supportable.
You sent 1,200 units to Amazon. The shipment closed at 1,164. Somewhere between your supplier, your prep partner, the carrier and the fulfillment center, 36 units stopped being counted — and unless someone reconciles that gap on purpose, it simply becomes a write-off.
Inbound discrepancies are one of the most common and least managed costs in FBA. This article walks through where short-received units actually come from, how to reconcile a shipment after it checks in, and which prep-side records make a discrepancy claim possible to support.
What an inbound discrepancy actually is
A discrepancy is any difference between the quantity you declared on the shipment and the quantity the fulfillment center recorded as received. It shows up in a few forms:
- Short-received units — fewer units than declared, the most common case
- Over-received units — more than declared, often a sign that two SKUs were mixed in one carton
- Unexpected SKUs — items arrived that were never on the shipment plan
- Unfulfillable on arrival — units received but classified as damaged or non-compliant
Each of these has a different root cause, and each needs different evidence if you want to dispute it.
Where the missing units usually go
In practice, most gaps trace back to a handful of places. Knowing which one you are dealing with changes what you do next.
| Source of the gap | What it looks like | Where to look first |
|---|---|---|
| Carton count error at origin | Whole-carton multiples missing | Supplier packing list vs. received carton count |
| Label or FNSKU mismatch | Units received under a different SKU | Over-received counts on a sibling SKU |
| Mixed cartons | One SKU short, another over | Carton contents records from prep |
| Receiving still in progress | Shipment shows "receiving" for weeks | Shipment status and last-updated dates |
| Transit damage | Units flagged unfulfillable | Carrier proof of delivery and carton condition notes |
The pattern matters. A shortage that is an exact multiple of your case pack almost always points to a missing carton, not a counting error inside a carton.
Reconcile after check-in, not months later
A shipment is not finished when it is delivered. It is finished when the received quantity has been checked against what you sent. A simple routine works for most sellers:
- Wait for receiving to close. Large shipments are often received in stages. Reconciling too early produces false alarms.
- Compare three numbers per SKU: units shipped from your supplier, units shipped out of prep, and units received by the fulfillment center.
- Check sibling SKUs. If one variant is short and another is over by a similar count, you likely have a labeling or mixed-carton issue rather than a loss.
- Pull the prep records for any SKU with a remaining gap.
- Open a case inside the marketplace's time window with those records attached. Eligibility windows are limited, so a shipment reconciled late may no longer be claimable.
Doing this on every shipment turns discrepancies from a vague cost into a tracked number you can actually reduce.
The prep records that make a claim supportable
When you dispute a short receipt, the question is always the same: can you show the units left in the quantity you declared? The prep step is where that proof is created — or lost. Useful records include:
- Per-carton contents — which SKU and how many units went into each box
- Carton weights recorded at packing, which help show a box left full
- Photos of packed cartons before sealing, especially for high-value SKUs
- Label verification confirming the FNSKU on units matches the shipment plan
- Carrier handoff documents with carton count and pickup date
If your prep flow does not produce these, it is worth tightening it before your next inbound. Our earlier piece on building a repeatable marketplace prep process covers the labeling and packaging side in more detail.
Fixing the upstream cause
Claims recover some value, but the better outcome is fewer discrepancies to begin with. The most effective upstream changes are usually simple:
- Count at receiving, not just at shipping. If your supplier shorted a carton, you want to know before it is relabeled and forwarded under your name.
- Keep one SKU per carton wherever the case pack allows. Mixed cartons are the single biggest source of sibling-SKU mix-ups.
- Scan-verify labels against the plan instead of relying on visual checks.
- Record exceptions immediately — a crushed carton noted on arrival is evidence; the same observation remembered later is not.
For sellers importing directly, many of these problems start before the goods ever reach a prep bench. The path from container to marketplace is covered in how imported container freight becomes an Amazon shipment.
Treat discrepancies as a metric
Track the discrepancy rate per shipment — units short as a share of units shipped — and look at it monthly. A rising number usually points to one supplier, one SKU family or one packing step. A falling number tells you the process changes are working.
If you want a prep partner that builds carton-level records into the workflow rather than reconstructing them after a problem, see how our FBA prep services handle receiving counts, labeling checks and outbound documentation.
