Amazon FBA Reimbursement Claim Deadlines in 2026: Lost Inventory, Returns and Removals
Check Amazon FBA reimbursement claim windows in 2026: 60-day lost-stock rule, 45–105-day returns, removal timelines, re-evaluation, evidence and worked examples.
Amazon's October 15, 2025 US claim-window announcement lists 60 days for reported lost or damaged fulfillment-center items, 45–105 days for qualifying customer returns, 15–135 days for certain lost removal orders and 90 days from the initial claim for re-evaluation requests. Other removal categories have different clocks. Confirm the latest policy in your own Seller Central marketplace before submitting; a deadline cannot establish eligibility by itself.
2026 FBA reimbursement deadlines by claim category
Amazon published a US Seller Central update effective October 15, 2025, replacing the idea that every reimbursement follows one universal timeline. The announced windows below refer to that update, not an automatic guarantee that the same timing applies to every marketplace or every subcategory.
A seller can have a warehouse-loss event, a customer-return event and a removal-shipment issue for the same product. These are distinct review paths with different starting dates. Always identify the claim type first; then check the currently applicable help page in the relevant Seller Central account.
| Event or request | Announced window | Clock starts from |
|---|---|---|
| Fulfillment-center inventory reported lost or damaged | Within 60 days | Date Amazon reported the loss or damage |
| Qualifying customer returns | Day 45 through day 105 | Customer refund or replacement date |
| Lost removal orders | Day 15 through day 135 | Removal shipment creation |
| Damaged removal orders | Within 120 days | Removal delivery date |
| Removal grading issues | Within 120 days | Date item left the fulfillment network |
| Re-evaluation requests | Within 90 days | Initial claim (per the announced update) |
Do not confuse an older policy article with the current rule
Search results may still show articles written before the October 2025 update. For example, an older Amazon announcement described a 15–75-day lost-removal window. The later announcement lists a 15–135-day window for lost removal orders. Dates in an older guide are useful historical context, not enough evidence to file a 2026 claim.
There are also specific subcategories. A separate March 15, 2025 Amazon notice shortened the claim window to 15 days for certain removal-related switcheroo, missing-main-unit and missing-component issues. Do not assume the general removal table overrides a special policy: resolve the exact issue type in Seller Central.
Treat this table as a research starting point. Marketplace, event type, policy revision and how Amazon defines the start date all matter. Verify them before putting a final deadline in your operational tracker.
Example: Amazon marked your inventory lost 45 days ago
Assume a fictional seller discovers an Inventory Ledger entry today and establishes that Amazon reported a fulfillment-center loss 45 calendar days earlier. If the current policy for that exact US event provides a 60-day window, roughly 15 calendar days remain in a simple calendar-day estimate. Do not treat the spreadsheet estimate as the official filing deadline; confirm the exact event timestamp, the policy language and Amazon's handling of boundary dates.
First verify whether the units have since returned to inventory or were already reimbursed. Then preserve the original event reference, SKU, FNSKU, ASIN, quantity and relevant history. A well-documented case submitted on time is more useful than an unsupported request based on the negative quantity alone.
If the record is 65 days old, do not assume a different date from the download can restart the clock. Check the policy and recorded event dates honestly. If a particular claim path is closed, keep the evidence for records without claiming that an exception will necessarily be granted.
- Locate the reported event date, not just the day you exported the report.
- Confirm the actual claim category and marketplace.
- Check later inventory resolutions and earlier cash or inventory reimbursements.
- Preserve the case number and evidence before submitting anything.
- Record the policy page and date on which you verified the deadline.
Example: a customer refund does not start the warehouse-loss clock
Suppose a customer was refunded 30 days ago and the seller has not confirmed a return. The customer-return claim window in the October 2025 US announcement opens at day 45. Being inside the 60-day warehouse-loss period is irrelevant to the return case; a claim filed too early could be rejected or require a different process.
At day 70 after the refund, the example falls within the announced 45–105-day range, but that says nothing about responsibility or eligibility. Verify what was returned, whether Amazon has already handled the case and whether the specific returns policy provides an automatic outcome.
Keep customer refunds and fulfillment-center losses in separate workflows. Combining both into a single overdue count can make a dashboard look urgent while hiding the real next steps.
Evidence checklist: decide whether the event is actually unresolved
A claim deadline is only one part of reimbursement review. A loss in the Inventory Ledger may be resolved later by a found movement, an inventory adjustment or a reimbursement. A product match alone is weaker than an event-level match, especially where the same ASIN has multiple losses.
When a seller asks whether Amazon has already paid, the goal is to reconstruct one event and its possible resolutions using the available identifiers. Keep the original exports unchanged and annotate a working copy; do not reclassify uncertain matches as settled claims.
| Field to preserve | Why it matters | Where to check |
|---|---|---|
| Marketplace and seller account | Select the applicable policy | Seller Central account context |
| Reported event date + type | Determines which clock may apply | Inventory Ledger / relevant report |
| Reference ID, SKU, FNSKU, ASIN | Trace the exact event and product | Original export rows |
| Affected and later resolved units | Avoid overstating outstanding quantity | Subsequent inventory movements |
| Reimbursement or case reference | Detect a prior payment or adjustment | Reimbursements report and case history |
| Documented unit cost | Provide a reviewable valuation basis | Invoices or manufacturing records |
| Policy URL and verification date | Show which rule the reviewer checked | Official Seller Central help |
Prioritize by time, confidence and missing proof—not by headline dollars
An event that has a confirmed, near-term eligibility deadline and complete documentation may deserve attention before a larger but speculative amount. Consider a queue with three states: verify policy immediately, gather missing evidence, and closed because paid or resolved.
A weekly review interval may make this easier than a year-end audit, particularly for short claim windows. Use age and deadline as prompts to review; never translate them into a promise that Amazon owes the calculated amount.
The present FluxPilot Recover workflow focuses on supported Inventory Ledger lost/damaged-event review and can use optional sourcing-cost and reimbursement-history files. It does not automatically file Amazon cases, and it should not be presented as a complete returns, removals or re-evaluation eligibility engine.
Frequently asked questions
Is every Amazon FBA reimbursement claim due within 60 days?
No. Amazon publishes different claim windows for fulfillment-center loss, returns, removals and re-evaluation. Check the event type and current Seller Central policy for your marketplace.
Can I submit a customer-return reimbursement claim 30 days after the refund?
The US October 2025 announcement lists a 45–105-day submission window for qualifying customer-return claims. A 30-day-old refund is earlier than the announced opening, although the current policy and automatic process should still be reviewed.
How long do I have to request reimbursement re-evaluation?
Amazon's October 2025 US announcement lists 90 days from the initial claim for re-evaluation requests. Confirm the relevant category and current help page before relying on this for a specific case.
Does finding a missing unit in Inventory Ledger mean Amazon owes reimbursement?
No. Check subsequent movements, prior reimbursements and the applicable policy. A negative inventory movement is a reason to investigate, not automatically a claim.
Does FluxPilot submit reimbursements or guarantee recovery?
No. FluxPilot helps review supported Inventory Ledger events and organize evidence and estimates. It does not automatically submit cases or guarantee Amazon approval.
Sources and further reading
Workflows and examples are from FluxPilot. Amazon policies change; verify the current policy for your marketplace before filing a claim.
Amazon Seller Central: October 15, 2025 claim-window announcement Amazon Seller Central: earlier reimbursement deadline announcement Amazon Seller Central: special 15-day removal cases announcement Amazon FBA inventory reimbursement policy: select your marketplace Amazon official FBA report field documentation