Amazon FBA reimbursements analyzer
Amazon reimburses you when it loses or damages your FBA inventory, or gets a fee or a customer return wrong — but the report that lists it is a wall of rows. Open it here and it is grouped into what you were reimbursed, by reason and by SKU, with reversals shown on their own line. The file is read on this device and never leaves it.
By Vedant Agarwal, who builds WidenMargin's toolsUpdated
Not tax or financial advice — every result is an estimate from the numbers you enter. Confirm your bookkeeping and taxes with a CPA or tax professional.
How it reads your file
- It works out the delimiter itself. Tab-separated, comma-separated and semicolon-separated files all work, and it copes with a byte-order mark, quoted fields, blank lines and accounting brackets for negatives.
- Every line is counted once. Each reimbursement is added to exactly one reason and one SKU, so the groups add back up to the net total.
- Reversals are kept separate. A negative reimbursement, or one carrying an original-reimbursement-id, is counted as a reversal and netted into the total rather than hidden.
- It never assumes a rate. No fee table and no reimbursement rate is written into it — every figure on screen was summed out of your own file.
What the reason labels mean
These are the common families of reason you will see. The analyzer groups by whatever labels are actually in your file, so if Amazon uses a slightly different spelling, your own label is what it shows.
- Lost_Warehouse
- A unit lost while it was stored in an Amazon warehouse.
- Damaged_Warehouse
- A unit damaged while it was stored in an Amazon warehouse.
- Lost_Outbound
- A unit lost after it left the Amazon warehouse (on its way to a customer).
- CustomerReturn
- A customer was refunded but the item did not come back in the time allowed, so Amazon reimbursed you. Amazon may take it back if the item arrives later.
- CustomerServiceIssue
- Amazon covering a service problem on its side, such as damage in transit or a late delivery.
- Reimbursement_Reversal
- Amazon taking back an earlier reimbursement — a negative line whose original-reimbursement-id points at the one reversed.
- Lost_Inbound, Damaged_Inbound, FeeCorrection and others
- Amazon doesn't publish definitions for these; your file shows them under their own label. See the full list in the reasons guide.
What this can, and can't, tell you
It tells you, precisely, what Amazon has already reimbursed — the total, the split by reason, the worst-hit SKUs, and any reversals. That alone is worth checking: a spike in one reason or one SKU is a signal worth a look.
It does nottell you what you are still owed. That is a genuinely harder question, because it means matching lost and damaged units in your inventory ledger against what was reimbursed here, unit by unit — a second report this one does not include. We would rather say that plainly than show you a made-up "you are owed $X" number, which is what a reimbursements report on its own cannot honestly produce.
Questions Amazon US sellers ask about reimbursements
Which report do I download from Seller Central?
In Seller Central go to Reports, then Fulfillment, then Reimbursements, and download the report for the date range you want. It is a tab-separated file with one row per reimbursement Amazon has made — the reason, the amount, the units and the SKU. A CSV saved from the same report also works.
Does this tell me what Amazon still owes me?
No, and it is important to be clear about that. This report only lists reimbursements Amazon has already made. Working out what you may still be owed means comparing lost and damaged units in your inventory ledger against what was reimbursed here — that reconciliation needs a second report this one does not contain. Anyone promising a figure from the reimbursements report alone is guessing.
Is my report uploaded anywhere?
No. The file is read by your own browser and added up on your own device. There is no upload and no server call carrying your figures — close the tab and it is gone.
What do the reason labels mean?
They are Amazon's own labels for why a reimbursement happened: a unit lost or damaged inside a fulfillment center, units lost on the way in (inbound), a customer return or service issue Amazon covered, or a fee it corrected. The analyzer groups your reimbursements by whichever reason labels are in your file, so you can see where the money came from.
Why is one of my reimbursements negative?
That is a reversal — Amazon taking back a reimbursement it made earlier, usually because a unit it had reimbursed you for was later found or returned. A reversal carries an original-reimbursement-id pointing at the earlier line and a negative amount. The analyzer counts reversals separately and nets them into the total, so the figure is honest.
Does the tool know Amazon's fee or reimbursement rates?
No. There is no rate table anywhere in it. Every figure it shows is a sum, a count or a share of numbers already in your file, so it cannot be out of date about a rate it never claims to know.
Related free tools
- Reimbursement report reasons explained — what Lost_Warehouse, CustomerReturn, Reimbursement_Reversal and the other reasons mean.
- Lost & damaged inventory finder — check Amazon paid for units it lost or damaged in its warehouses.
- Settlement report analyzer — the payout side: read a full settlement line by line, including reimbursements as they land.
- Settlement profit calculator — what a settlement really leaves you after fees, refunds and ads.
- FBA inventory sales-tax by state — which states your stored inventory may make you register in.
Free for the first 50 sellers
Want lost & damaged units watched for you? Free during early access
I'm building WidenMargin to reconcile reimbursements against your inventory ledger on its own — to flag lost and damaged units that have not been reimbursed yet. Join the early-access list and we'll email you when it's ready for Amazon US sellers. Your reports are never sent to us.