FBA Inventory Reimbursement Audit: Finding Units Amazon Lost or Damaged

Amazon moves an enormous number of units, and some go missing: a carton counted short at receiving, a unit damaged on a shelf, a return refunded but never restocked. Amazon reimburses some of these on its own, but it cannot reimburse what nobody checks, and it has no way to know about the shortfalls you never raise. A reimbursement audit is plain bookkeeping. You compare what should exist with what Amazon says exists, subtract what has already been paid or found, gather proof for the rest, file, and repeat on a schedule. This article lays out that method without special software.

Where units go missing

Losses cluster in four places. Inbound shipments can be received short, with fewer units checked in than you sent. Inventory can be lost or damaged after check-in, in storage or while being picked and packed. Customer returns can be refunded without the unit ever coming back in a sellable or unsellable state. And removal orders can leave Amazon but fail to arrive at your address. A fifth category, fee overcharges from wrong size or weight measurements, is money rather than units, but it belongs in the same audit habit.

Not every gap is Amazon's fault, and a good audit says so. Units can be received against a different SKU than the one on your plan, especially when similar products share cartons or labels are wrong. Before you claim a shortfall on one SKU, look at its siblings for an overage. A shortage that is mirrored by a surplus is a labeling problem on your side, and the fix belongs in your packing process, not in a case.

The first two losses account for most of the work, and they use different evidence. The comparison below shows how they differ.

Reconcile inbound shipments first

For each shipment, the shipment page lists what you said you would send and what Amazon has recorded as received, by SKU. The arithmetic is as simple as it looks. If you shipped 500 units and 488 were received, 12 are missing from the count. At a hypothetical unit cost of $9, that is $108. Small on one shipment, but it accumulates across SKUs and months.

Do not file the moment you spot a gap. Receiving is often spread over days or weeks and large shipments arrive in parts, so a shortfall on day three may close by day twenty. Wait until the shipment is closed, then compare final figures. Also check your own side: confirm the number of cartons the carrier delivered against the number you sent. If the loss happened in transit, the right claim, and the right party, can depend on whether you used Amazon's partnered carrier program or your own carrier, so read the current help page for the route you used.

Then the ledger: lost, damaged and found

The inventory ledger records every movement of your units: receipts, customer shipments, returns, removals and adjustments, each with a reason. Pull it for a period and, per SKU, check that the starting balance plus what came in, minus what went out, matches the ending balance. Adjustments for lost or damaged units are the candidates for claims.

Then net them. Check the reimbursement report for what Amazon has already paid. And look for adjustments that show units found, because a unit reported lost in March may turn up in May. Claiming units that are already paid or already found will get a case denied and wastes your time.

In that example, 20 units were adjusted out as lost or damaged. Amazon paid for 8 and later found 3, which leaves 9 that remain unexplained. Those 9 are the claim, and the proof you attach should tie to them.

Keep the unit value in view. A claim is reimbursed under Amazon's valuation rules, not necessarily at your cost or your retail price, so run the numbers on what a case is likely to recover before you spend an hour on it. The goal of the audit is steady, repeatable recovery of real losses, not a hunt for every cent.

Returns and removals

Customer returns need a different comparison. Take the orders you refunded and check each against the customer returns report to see whether the unit came back and in what condition. A refund with no matching return is a candidate. Amazon has policies for returns it never receives, so check what applies before you file by hand.

For removal orders, compare the quantity Amazon says it shipped to you with the quantity you received, and keep the carrier tracking. Both comparisons are easiest when you record counts the moment boxes arrive.

Build the proof pack, then file the case

Evidence decides whether a case succeeds, and the cheapest evidence is gathered before the problem exists. Put a folder together for every shipment at the time you pack it:

• The supplier invoice, showing quantity, unit price and a clear match to the product.
• The shipment ID, packing list and carton count.
• The carrier's proof of delivery and tracking.
• Photos of sealed cartons, labels and weights taken at packing time.
• For returns, the order ID, refund date and return status; for damage, photos and the ledger line.

When you file, open a case with Seller Support in the category for FBA inventory or inbound problems. Use one case per issue or shipment, list the SKU, quantities and dates, show the arithmetic in a few lines and attach the documents. Keep the tone short and factual. Write down the case ID in a log with the date, units, status and amount.

Expect to follow up. Some cases are approved, some are denied, and some come back asking for more documents. Amazon sets how reimbursed units are valued, so read its current rules, and never promise yourself a recovery. Set a floor too: if a claim is worth less than the time it takes, batch it with others or skip it.

A cadence so nothing ages out

Every claim type has a time limit measured from the event, and the limits have changed over the years. Read the current rules for each type, then set your review rhythm to be shorter than the shortest one. A loss that you find after its window closes is a loss you keep.

Treat reimbursements as accounting events too. Mark them in your records so a payment does not look like a sale, and ask your accountant how they should be handled.

The short version

• Reconcile each shipment once it is closed: units shipped against units received.
• Reconcile the ledger monthly: lost and damaged, less reimbursed, less found.
• Compare refunded orders and removal orders with what actually came back.
• Build a proof pack at packing time, not after a problem appears.
• File one case per issue, log every case ID, and follow up.
• Check the current claim windows and keep your rhythm shorter than all of them.