Amazon FBA reimbursements: what Amazon owes you and how to claim it

Amazon handles millions of units a day, and some of yours will go missing, get damaged or be counted wrong. Amazon pays for a lot of that automatically. The rest sits in your reports until someone opens a claim.

The five cases worth checking

Nearly every reimbursement falls into one of five buckets. Knowing them turns a vague hunt through reports into a checklist you can work through in an hour.

Lost inventory. Units Amazon received but can no longer find. These show up in the Inventory Adjustments report with reason codes, and Amazon often credits them on its own within a few weeks.

Damaged inventory. Units damaged in the warehouse or by a carrier Amazon controls. Damage caused by the customer is a different case and is usually not reimbursable.

Inbound shipment discrepancies. You sent 200 units and Amazon received 188. This is the most common gap and the one sellers miss most, because the shipment closes and nobody reopens it.

Customer returns. A buyer is refunded but the unit never comes back to the warehouse, or it comes back and is never added to your sellable stock. Amazon gives a return window, and after it passes the unit should be reimbursed.

Fee overcharges. Amazon charges FBA fees on the size and weight it measured. If those measurements are wrong, every unit you sell is overcharged until the catalog is corrected.

Why Amazon does not catch everything

Amazon's automated reconciliation is real and it does pay out. What it handles poorly is anything that needs two reports compared against each other, which is exactly where inbound discrepancies and unreturned returns live.

There is also a time limit. Claim windows differ by case type and Amazon has shortened several of them in recent years. A case that would have been paid in month two is often refused in month eight, not because the facts changed, but because the window closed. That is the real cost of not checking: not the effort, the expiry.

How to run a reimbursement audit yourself

Pull four reports from Seller Central: Inventory Adjustments, Inbound Shipment Reconciliation, Customer Returns, and Reimbursements. The last one matters most, because it tells you what Amazon has already paid. Claiming something twice wastes your time and irritates the support team you need on your side.

Match the shipment reconciliation against what you actually sent, line by line, and note every shipment where received is lower than shipped and the difference was never reimbursed.

In the returns report, look for refunds where no unit came back inside the return window, and check whether a matching reimbursement exists.

For fee checks, compare the size tier and weight Amazon lists for your ASIN against the real product. If it is wrong, open a case for a remeasure, and mention every unit sold under the wrong tier.

Then open one case per issue with the shipment ID, the ASIN, the dates and the numbers. One case per issue is slower to file and much faster to resolve than a single case listing fifteen problems.

What a good claim looks like

Amazon support answers hundreds of cases a day, so a claim that reads as a clean, specific request gets handled faster than one that reads as a complaint. Name the shipment or order, give the dates, state the number of units, say what you expected and what happened, and attach the report rows that prove it.

If the first reply misses the point, and sometimes it will, reply on the same case with the same facts rather than opening a new one. A case with history attached is easier for the next agent to approve.

Doing this every month

Reimbursements are not a one time cleanup. Every month adds new shipments, new returns and new adjustments, and every month old cases move closer to their window closing. Sellers who check quarterly recover less than sellers who check monthly, for the simple reason that fewer of their cases are still eligible.

This is the part most sellers never get to, which is why it is worth either blocking an hour a month for it or handing it to someone who does it as a routine.

What you need before you open a case

Amazon decides most claims on evidence, not argument. Before filing, collect the shipment ID and carrier tracking for inbound cases, the order ID and return ID for return cases, the FNSKU and ASIN, the dates, and the exact unit counts you expect.

Keep the packing list from the shipment. When Amazon says it received 188 of 200, the document showing what left your supplier is what turns a refused claim into a paid one.

Write the request as one short paragraph with the numbers in it. Long messages get skimmed, and an agent who has to hunt for the shipment ID is an agent who closes the case with a template reply.

Reimbursements are not free money

A reimbursement is Amazon paying for a unit you can no longer sell, at a value Amazon decides. That value is based on its estimate of your sale price, and it is often lower than what you would have earned on a product that sells well.

That matters for how you treat the result. Recovering the money is good, but a shipment process that keeps arriving short is costing you margin every month underneath the claims. When the same problem repeats, fix the packing and labelling first, then claim.

It matters for your books too. Reimbursements arrive in the payments report separately from sales, so if you never separate them you will misread both your product margins and your real sales trend.

Common questions

Does Amazon reimburse automatically?

For many lost and damaged cases, yes. Inbound shortages, unreturned customer returns and fee overcharges usually need a claim.

How far back can I claim?

Windows differ by case type and Amazon has shortened several of them. Check the current policy page in Seller Central before you file, and work the oldest eligible cases first.

Can a service do this for me?

Yes. Seller Momentum runs the audit inside your Seller Central with the minimum permissions and files each claim under your account, so you can see every case.