FBA reimbursement deadlines depend on the claim type and the event that starts its clock. A shipment delivery date, customer refund date and inventory-loss report date are different dates. Do not apply one 60-day countdown to all three.
Scope and source check: September 12, 2026. This guide summarizes public Amazon announcements on the US Seller Central site. Confirm the current policy and eligibility shown in your own marketplace before filing. The linked help policy requires an interactive Seller Central session and was not independently verified in a signed-in seller account.
FBA claim windows by type
Inbound timing comes from Amazon's September 2024 announcement. The other rows reflect its later October 15, 2025 update, which supersedes several widely repeated 2024 windows.
| Claim | Filing window | Clock starts at |
|---|---|---|
| Missing inbound units | Days 15–60 | Shipment delivery |
| FC loss or damage | Within 60 days | Reported loss or damage |
| Customer returns | Days 45–105 | Customer refund or replacement |
| Lost removal order | Days 15–135 | Shipment creation |
| Damaged removal order | Within 120 days | Shipment delivery |
| Removal grading | Within 120 days | Item removed from the fulfillment network |
| Re-evaluation request | Within 90 days | Initial claim |
This is a reference for the listed categories, not a determination that a particular unit qualifies. Review the FBA inventory reimbursement policy and the claim workflow for exceptions, required records and any subsequent changes.
Worked example: delivery and closure are not interchangeable
Synthetic example: a shipment arrives September 1 and closes September 20. Adding 60 calendar days to delivery gives October 31; adding them to closure gives November 19. The second reminder is 19 days later. Save the actual delivery evidence and check the eligibility date in Seller Central rather than waiting for a closure-based reminder.
A practical log needs: shipment or order ID, marketplace, claim type, clock-start event, event date, first eligible date, final filing date, case ID and next follow-up. Save a dated copy of the policy you used and schedule your own preparation reminder before the final day.
What to do before the window closes
- Compare expected and received units, then investigate unresolved differences.
- Check reimbursements and inventory adjustments so you do not count the same loss twice.
- Collect identifiers and the evidence requested by the applicable claim workflow.
- Record submission and follow-up dates separately from the original event date.
For an inbound shortage, use the step-by-step claim guide and template. A discrepancy is a reason to investigate; it is not proof that Amazon owes a payment.
Does shipments.fyi calculate Amazon's official deadline?
The free scanner identifies short-received rows in supported shipment CSVs. The claim tracker calculates an inbound reminder using the seller-entered delivery date and a 60-day interval. Verify that date and the official eligibility state in Seller Central. Connecting Amazon does not currently supply the delivery date automatically, and a reminder does not establish claim eligibility or model every other policy clock above.
Deadline questions sellers ask
Is every claim limited to 60 days?
No. Match the category and start event in the table, then confirm it in your account.
Should I wait until the last day to file?
Prepare records while receiving is in progress. Follow the investigation eligibility shown for that shipment; do not assume a status change restarts the policy clock. If the workflow remains unavailable near the deadline, contact Seller Support and retain the dated response.
Does an automatic reimbursement mean my records are reconciled?
Check which event and units the payment covers. Keep unrelated shortages open in your own records until you can attribute the payment or adjustment reliably.
Find shipment quantity differences before preparing a claim.
The scan runs in your browser without signup. Saving claims is a separate account action.
Related: Amazon reimbursement policy changes and sourcing costs.