FBA Reimbursement Claim Windows: When You Can Still Recover Revenue

Most Amazon sellers know they can file FBA reimbursement claims for lost or damaged inventory. What they don't know is that different claim types have radically different eligibility windows—and missing a deadline means leaving money permanently on the table. The difference between a 60-day window and an 18-month window can mean thousands of dollars in recovered revenue.

Amazon doesn't make these windows obvious. Seller Central documentation scatters deadline information across multiple help pages, and the FBA Dashboard shows "reconcilable" discrepancies without explaining which ones are still claimable. Sellers with hundreds of SKUs routinely discover they had valid claims that expired months ago.

This guide maps every FBA reimbursement eligibility window by claim type, shows you how to identify which deadline applies to each discrepancy, and provides a prioritization framework for claims approaching expiration.

How Amazon's claim windows work

Amazon's reimbursement eligibility windows start from the date the discrepancy occurs—not the date you discover it. This distinction matters because you might not notice a lost unit until weeks after Amazon's system registers the loss.

Each claim type has a specific window based on the nature of the discrepancy. The windows range from 60 days to 18 months, and they are non-negotiable. Once a window closes, Amazon's system automatically rejects the claim regardless of documentation quality.

The window types break down into four categories:

• Short windows (60-90 days) — Customer return and removal discrepancies
• Medium windows (9 months) — Warehouse damage and processing errors
• Long windows (18 months) — Lost and misplaced inventory
• No window — Fee overcharges and dimensional weight disputes

Lost and misplaced inventory: 18-month window

Lost inventory claims have the longest eligibility window at 18 months from the date Amazon's system last scanned the unit. This includes inventory that disappears during receiving, storage, or fulfillment.

The 18-month window applies to these scenarios:

• Units marked "received" in your shipment but never added to available inventory
• Inventory that vanishes from your inventory ledger with no corresponding fulfillment or removal
• Units Amazon relocates between warehouses and loses in transit
• Items removed from your inventory for FC transfer that never arrive at the destination warehouse

The practical challenge with lost inventory is detection lag. Amazon's reconciliation process can take 60-90 days to identify a discrepancy, meaning you might not see the issue until months after the loss occurred. The 18-month window provides breathing room, but sellers with high SKU counts still need systematic auditing.

Example: A seller ships 500 units on March 1st. Amazon receives and checks in 500 units, but only 485 appear in available inventory by March 15th. The 18-month claim window runs from March 15th (when the discrepancy became visible in the system), giving the seller until September 15th of the following year to file.

When the 18-month window starts

The clock starts when Amazon's inventory management system records the discrepancy—not when you notice it in your reports. For receiving discrepancies, this is typically the date the shipment closes. For storage losses, it's when the inventory ledger reflects the missing unit.

Check your Inventory Ledger report filtered by transaction type "Lost" or "Damaged" to see the exact date Amazon recorded each discrepancy. That date determines your filing deadline.

Warehouse damaged inventory: 9-month window

Inventory damaged while in Amazon's custody falls under a 9-month eligibility window. This covers units damaged during storage, handling, or the picking and packing process—but not customer returns.

The 9-month window applies when:

• Amazon marks units as "warehouse damaged" in your inventory adjustments
• Units are damaged during FC transfer between warehouses
• Amazon damages inventory while processing a removal order
• Inventory is destroyed due to FC operational issues (water damage, forklift incidents)

Amazon's system automatically flags many warehouse damage events and may issue reimbursements proactively. However, reconciliation errors happen frequently enough that manual verification is necessary. Cross-reference your Inventory Adjustments report against actual reimbursements received.

The 9-month window is strict. Unlike lost inventory claims where Amazon sometimes shows flexibility on borderline cases, warehouse damage claims filed after 9 months receive automatic rejections.

Customer return discrepancies: 60-day window

Customer return issues have the shortest eligibility windows. When a customer returns a product and Amazon either fails to return it to your inventory or returns it in worse condition than sent, you have 60 days from the return completion date to file.

Specific scenarios with 60-day windows:

• Customer returns an item marked "received" by Amazon but never added back to sellable inventory
• Amazon receives a return and marks it unfulfillable when the customer actually returned the item in sellable condition
• Customer return goes missing after Amazon receives it at the returns processing center
• Amazon loses a customer return during the inspection process

The 60-day window makes return discrepancies the highest-priority category for regular auditing. Sellers who check their Returns reports monthly risk missing claims entirely. Weekly monitoring is minimum best practice for stores processing more than 50 returns per month.

Exception: If Amazon damages a returned item during their inspection or restocking process, the claim may fall under the warehouse damage window (9 months) instead of the customer return window (60 days). The Inventory Ledger transaction type determines which applies.

Why the return window is so short

Amazon's policy assumes sellers actively monitor their returns and can quickly identify discrepancies. The 60-day window reflects the typical timeframe for a return to fully process through Amazon's system and reconcile against your inventory.

In practice, return processing often takes 30-45 days from the customer shipment to final inventory disposition. This leaves sellers with a narrow 15-30 day detection window before claims become ineligible.

Removal order discrepancies: 90-day window

When you create a removal order to retrieve inventory from FBA, discrepancies fall under a 90-day eligibility window from the order completion date. This includes both items removed to your address and items Amazon disposes of on your behalf.

Common removal order claim scenarios:

• Amazon ships fewer units than listed on the removal order
• Units go missing during the removal process
• Amazon damages inventory while processing the removal
• Disposal orders show completed but inventory remains in your FBA account

Removal order claims require comparing your removal order confirmation against what actually ships or gets disposed. Amazon provides tracking for shipments to your address, but disposal confirmations often lack unit-level detail, making discrepancy identification difficult.

Track removal orders in a spreadsheet with three columns: units requested, units Amazon confirms removed, units actually received (for shipments) or confirmed disposed. Any gap between columns two and three is a potential claim.

Fee and weight disputes: ongoing eligibility

Fee overcharges and dimensional weight disputes don't have fixed claim windows. You can dispute incorrect fees for any transaction visible in your Payments reports, typically going back 18 months based on report retention.

Common fee disputes include:

• Incorrect product size tier assignments leading to higher fulfillment fees
• Dimensional weight measurements that don't match your product specifications
• Duplicate referral fee charges on the same transaction
• Incorrect storage fee calculations during high-storage-fee periods

Fee disputes require different documentation than inventory claims. You need to provide evidence of the correct product dimensions, weight, or fee structure rather than proof of inventory loss.

File fee disputes through the Seller Central "Fee Preview" report by selecting the specific transaction and requesting a fee review. These cases often take 5-10 business days for Amazon to investigate and respond.

Identifying which window applies to your claim

The Inventory Ledger report shows transaction types that determine which claim window applies. Download the report and filter by these transaction type codes:

The "Reason" column provides additional context. Common reason codes include "WAREHOUSE_LOST", "CARRIER_LOST", "WAREHOUSE_DAMAGE", and "FC_TRANSFER_LOST". Each maps to a specific claim window.

When the transaction type shows "Adjustment" with no clear reason code, the default assumption is the 9-month warehouse damage window unless you can document the discrepancy as a loss (which extends it to 18 months).

Prioritizing claims approaching expiration

Sellers with large catalogs face a backlog problem: dozens or hundreds of potential claims across different window timelines. The key is prioritizing by both urgency and value.

This framework ranks claims by filing priority:

1. Customer return discrepancies within 45 days of the return date — highest urgency due to 60-day window
2. Removal order issues within 75 days of completion — second priority with 90-day window
3. High-value warehouse damage within 8 months — focus on units worth more than $50 approaching the 9-month deadline
4. Lost inventory within 15 months — longer window but still requires eventual attention
5. Low-value lost inventory within 18 months — file if time permits, but don't let these distract from higher-priority claims

For sellers processing hundreds of returns monthly, the 60-day customer return window demands weekly auditing. Set a recurring calendar task to review return discrepancies every Monday morning and file claims for any issues identified in the previous week.

Batch filing vs individual claims

Amazon allows batch claim submission through case templates when you have multiple units of the same ASIN affected by similar discrepancies. Batching saves time but requires identical claim types.

You cannot batch a customer return claim with a lost inventory claim even if they affect the same ASIN. The transaction types must match, and the discrepancy dates should fall within a similar timeframe.

For claims approaching different deadlines, file shorter-window claims first even if it means submitting multiple cases for the same product. Better to file three separate 60-day return claims this week than batch them with an 18-month lost inventory claim you can file next month.

What happens when you miss a window

Amazon's system automatically rejects claims filed outside the eligibility window. The rejection message typically states "This claim was filed outside the allowable timeframe for this issue type" with no appeal option.

Escalating to Seller Support rarely helps. Amazon's reimbursement policy team treats eligibility windows as hard deadlines, and supervisor escalations receive the same rejection.

The only exception occurs when you can document that Amazon's system error prevented you from filing on time. If Amazon's Inventory Ledger didn't show the discrepancy until after the window closed due to a reconciliation delay, you may have grounds for appeal. This requires screenshots proving when the discrepancy first appeared in your reports.

Missed windows most commonly happen with customer returns. Sellers who review their Returns report monthly often discover discrepancies from 65-75 days ago—past the 60-day cutoff. The solution is more frequent monitoring, not hoping for policy exceptions.

Tracking claim windows systematically

Manual tracking becomes impractical above 50 SKUs or 100 monthly transactions. Sellers at scale need a systematic approach to window monitoring.

The basic tracking workflow:

1. Download your Inventory Ledger report weekly
2. Filter for transaction types: Lost, Damaged, Customer Return, Removal
3. Add a "Claim Deadline" column calculating the appropriate window from the transaction date
4. Sort by deadline ascending to see which claims expire soonest
5. Flag any transactions within 30 days of expiration for immediate filing

Build the spreadsheet once, then update it weekly by importing new Inventory Ledger data. The deadline calculation is simple: transaction date + window length (60 days, 90 days, 9 months, or 18 months).

SageSeller's reimbursement tracking feature automates this workflow by monitoring your Inventory Ledger daily and flagging claims approaching their eligibility deadlines. The system calculates which window applies based on transaction type and alerts you when a claim has 30 days or fewer remaining.

Common window calculation mistakes

Sellers frequently miscalculate claim deadlines by counting from the wrong date. The window starts when Amazon's system records the transaction—not when you notice it, not when you download the report, and not when Amazon notifies you.

Example of incorrect calculation: A customer returns an item on June 1st. Amazon receives and inspects the return on June 10th. The unit goes missing during inspection, and Amazon marks the transaction "Customer Return - Missing" on June 15th. The seller downloads their June Inventory Ledger on July 1st and sees the discrepancy.

The 60-day window starts June 15th (when Amazon recorded the transaction), giving a deadline of August 14th. It does NOT start June 1st (customer return shipment), June 10th (Amazon receipt), or July 1st (seller discovery).

Always use the transaction date shown in the Inventory Ledger, not the date you discovered the issue or the date you pulled the report.

Planning your claim filing schedule

A sustainable claim filing schedule matches your inventory volume and transaction complexity. Sellers processing fewer than 50 orders per day can typically manage with weekly reviews. Higher-volume sellers need daily monitoring for customer returns and weekly reviews for other claim types.

Recommended review frequencies by claim type:

• Customer returns — weekly minimum, daily for 100+ returns/week
• Removal orders — within 48 hours of order completion
• Warehouse damage — bi-weekly reviews
• Lost inventory — monthly reviews

Block specific times in your calendar rather than handling claims reactively. Tuesday and Wednesday mornings work well because Amazon's reconciliation processes typically complete Monday night, making Tuesday the earliest you'll see the previous week's discrepancies fully reflected in reports.

For teams managing reimbursements, assign clear ownership of each claim type to specific team members. One person monitors returns, another handles removals and damage, and a third focuses on lost inventory. This prevents duplicate effort and ensures no category gets neglected.