FBA Reimbursement Claims Amazon Won't File For You
A brand we talked to this autumn had stopped filing reimbursement claims entirely. Not out of neglect. Their ops lead had noticed that lost-unit credits were showing up in the statement without anybody asking for them, concluded that Amazon had finally automated the whole thing, and moved the monthly reconciliation off the calendar. That read was half right, which is the expensive kind of right.
Amazon does now repay a lot of fulfillment center losses on its own. It does not repay all of them, the categories it skips are the ones that need a human to notice, and the window you have to file the rest shrank to roughly two months. If your team dropped the reconciliation when the automatic credits started, you have been quietly forfeiting the claims that were always worth the most. This is what FBA reimbursement recovery actually consists of now, which categories you still have to chase yourself, and how to catch them before the clock runs out. If you would rather hand the reconciliation to someone who does it every month, book a call and we will look at your account.
What Amazon reimburses without being asked
Since late 2024, Amazon has proactively reimbursed inventory lost inside a fulfillment center. You do not open a case. The loss gets identified, the credit appears, and for most brands it lands within about a week of the discrepancy being recorded. That is a real improvement and it removed a genuine chunk of manual work.
The automation is narrower than it looks, though, and the gaps are structural rather than accidental. Automatic coverage works where Amazon's own systems can see both sides of the discrepancy: it knows a unit entered the building, it knows the unit is gone, it can reconcile that by itself. Where the two sides of the ledger sit in different systems, or where the error is a miscalculation rather than a disappearance, nothing fires.
Which claim types still need you
These are the categories we still reconcile by hand every month, and why each one escapes the automation.
| Claim type | Who initiates it | Why automation misses it |
|---|---|---|
| Inventory lost in a fulfillment center | Amazon, usually | Mostly covered. Audit the amount rather than the existence of the credit. |
| Customer return refunded but never restocked | You | Amazon refunded the buyer and the unit never came back to sellable stock. Two separate records, no automatic reconciliation between them. |
| Fee overcharges from wrong dimensions or weight | You | Nothing was lost. You were billed on a measurement that is wrong, so there is no discrepancy for a loss-detection system to find. |
| Removal order units lost or damaged in transit | You | The units left Amazon's network. Reported as always requiring a manual claim. |
| Inbound shipment received short | You | Your shipment plan says one quantity and the receiving record says another. Different window from the others, and often discovered late. |
| Damaged in warehouse | Mixed | Often automated, inconsistently. Worth a monthly check against your damaged-inventory report rather than an assumption. |
Look at the second column for a second. Every row that says "you" is a row where the money is sitting in a report that nobody on your team reads unless reading it is somebody's job. That is the whole reason this work survives automation.
How long do you have to file an FBA reimbursement claim?
Plan on about 60 days for most warehouse claims, and treat anything longer as a bonus you should not build a process around.
The short window is the change that matters most to how you operate, and it is the one least discussed. The older policy wording that still circulates gave sellers many months, in some cases up to 18, to find a discrepancy and file against it. On that timeline an annual or semi-annual audit was a perfectly reasonable cadence. A roughly 60-day window makes an annual audit worthless: by the time you run it, most of what you find is already time barred.
Two details change the math further. The clock generally runs from the date Amazon reported the loss, not from the date you noticed it, so a discrepancy that sat unread in a report for six weeks has two weeks of life left. And customer return claims have a floor as well as a ceiling: Amazon will not accept the claim until a set number of days after the refund, because the customer still has time to send the item back. File too early and it gets rejected, file too late and it is closed. There is a middle window, and hitting it is a scheduling problem, not a documentation problem.
If you take one operational change from this page, make it this: the reconciliation has to run monthly. Not quarterly. We moved our own cadence to monthly across every account we run when the windows tightened, and the single biggest category of recovery we now find is claims that a brand's own prior annual audit would have located a year too late.
Why approved claims come back smaller than you expected
This is the part that disappoints brands the first time, and it has nothing to do with claim quality.
Since 31 March 2025, Amazon values inventory lost or damaged before a customer order at your product's manufacturing cost rather than its selling price. A unit that retails at $60 and costs you $11 to make is now a roughly $11 event rather than a roughly $60 one, on the perfectly defensible logic that reimbursing retail price pays you a margin you never earned. Units lost after a customer order is placed are reported to still settle at sale price less fees, so the two cases pay out very differently.
The failure mode is not the policy. It is the input. Amazon reads your sourcing cost from Seller Central, and if that field is blank it substitutes an estimate of its own. We have found that is where the money quietly goes: the claims get approved, the amounts come back low, and the brand concludes that reimbursements are not worth chasing. The real cause is an empty field in a catalog nobody audits. Filling in accurate manufacturing costs across your ASINs is unglamorous, takes an afternoon, and changes the value of every future claim you file. Do that before you judge whether recovery is worth the effort. We wrote up the valuation change in more detail in our note on manufacturing-cost reimbursement.
What a monthly reconciliation actually involves
Four passes, in this order, because each one narrows the next.
- Reconcile the automatic credits. Not whether they arrived. Whether the amount is right, given your sourcing costs and whether the loss happened before or after a customer order.
- Age the open discrepancies. Sort by the date Amazon reported the issue, not by the date you found it. Anything past about 45 days goes to the top of the list.
- Run the fee audit separately. Dimension and weight mischarges never appear in a loss report, so they need their own pass against your fee preview and measurement data.
- Track the denials. First-submission rejection is routine, not a verdict. The recoverable money is disproportionately in resubmissions with better documentation.
None of this is difficult. All of it is tedious, and tedium is exactly what gets dropped when an ops team is busy, which is why the balance sits uncollected rather than disputed.
When to do this in-house, and when not to
If your catalog is under roughly 50 ASINs and somebody on your team has two spare days a month, do this yourself. We would rather say that here than invoice you for it. The arithmetic is simple: reconciliation effort scales with ASIN count because every ASIN is a separate reconciliation, and under about 50 the work fits inside a job somebody already has.
Above that it stops fitting, and the cost of it not fitting is invisible, which is the dangerous part. A missed claim does not generate an alert. It generates a slightly smaller number in a line item nobody compares year over year. Our own fee on this work is a percentage of what actually comes back and nothing if nothing does, which is the shape it has to be, because the alternative bills a brand for the search rather than the result. The figure is on the FBA reimbursement service page.
On proof, we will be straight with you about what we can show. We have not published a reimbursement recovery case study, so we are not going to imply one. The closest published work is an inventory discipline engagement where the constraint was restock limits rather than lost units: daily inventory monitoring replaced a weekly cadence, and that brand's restock limit went from 15,000 units to over 176,000 with a 97% in-stock rate. Different problem, same underlying point, which is that the money in Amazon operations is usually in a report somebody stopped reading. The detail is in that inventory optimization case study.
A note on sources, because this territory is full of confident wrong numbers
The manufacturing-cost valuation and its 31 March 2025 start date are well established and consistent across sources. The automatic reimbursement of fulfillment center losses is widely reported from a change around 1 November 2024 and matches what we see in accounts, though we have not found Amazon's own announcement published anywhere citable.
The claim windows are where the published numbers fall apart. The roughly 60-day figure traces to an Amazon seller forum announcement dated 23 October 2024. Beyond that, third-party write-ups disagree with each other and sometimes with themselves: customer return windows appear as 45 to 105 days in one place and 60 to 120 in another, removal order claims are given up to about 135 days citing an October 2025 update, and inbound shipment claims are described in a Seller Central forum post as nine months from verified delivery. We have not been able to verify any of these against Amazon's own policy page.
So treat 60 days as your planning deadline, and confirm the exact window for each claim type against the live FBA inventory reimbursement policy in Seller Central before you build a process on it. Those terms are the binding ones. Ours are not, and neither is anybody else's blog post, including the ones that state these numbers without a caveat.
The part worth remembering
Automatic reimbursement did not end this work. It moved it, from filing claims to auditing amounts and catching the categories that no system is watching. The brands losing money on this today are mostly the ones who read the automatic credits as a signal that the job was finished. If nobody at your company can say what your reimbursement recovery was last month, that is the answer: have somebody own the reconciliation, monthly, starting with the sourcing cost field.
More on Amazon Strategy
What Changed About Launching a New Product on Amazon in 2026
Three 2026 rule changes reset Amazon launch arithmetic: variation reviews stopped pooling, the FBA New Selection Program now credits fees at the point of sale, and titles are capped at 75 characters. What each one changes in practice.
Amazon's AI-Generated People Rule: What Your Creative Team Has to Tag
Amazon told sellers in July 2026 to label listing images, video and A+ content showing AI-generated people. What triggers the rule, what doesn't, and where it breaks a real creative pipeline.
Seller Central User Permissions: What to Grant an Outside Amazon Operator, and What Expires
Seller Central user permissions are three separate systems wearing one name. Which access an outside Amazon operator actually needs, which to withhold, and why provider authorizations quietly lapse after a year.