How long do I have to file an Amazon FBA reimbursement claim?

Amazon's manual claim window is 60 days from the date of the loss event. Claims filed after 60 days are permanently rejected regardless of the amount owed.

How much do Amazon FBA reimbursements typically add up to?

Most FBA sellers have 1–3% of annual revenue in unclaimed reimbursements. On a $300,000/year account, that's $3,000–$9,000 in unrecovered money — often across dozens of small, individually easy-to-miss line items.

Does Amazon automatically reimburse for lost FBA inventory?

Sometimes. Amazon does auto-reimburse for some clear-cut losses, but many cases require manual claims — especially shipment discrepancies, customer returns not checked in, and fee overcharges. You cannot rely on automation alone.

What reports do I need to find Amazon reimbursement claims?

The key reports are: Inventory Ledger report (for lost/damaged units), Received Inventory report vs. Shipping Queue (for inbound discrepancies), Customer Returns report (for refund-not-returned cases), and the Reimbursements report (to see what Amazon has already paid and what's still open).

Amazon FBA Reimbursements: How to Find Money Amazon Owes You

Q: How does Amazon calculate FBA reimbursement amounts after March 2025?

For pre-order loss events (warehouse, inbound, removals), Amazon reimburses based on your sourcing cost — what you paid to acquire the item from a manufacturer, wholesaler, or reseller, excluding shipping and duties. You can submit your sourcing cost via the Manage Your Sourcing Cost page in the Inventory Defect & Reimbursement portal. If you don't submit one, Amazon uses its own estimate. For customer return claims, the reimbursement is based on the refund or replacement Amazon gave the customer, minus applicable fees.

1. Why Amazon May Owes FBA Sellers Money

When you send inventory to Amazon FBA, you hand over physical control of your products. Amazon receives them, stores them across fulfillment centers, picks and packs them when orders come in, and handles returns. That's a lot of hands on your inventory — and at scale, things go wrong constantly.

Units get lost during inbound receiving, damaged in the warehouse, miscounted during transfers between fulfillment centers, or not returned to sellable stock after a customer return. Amazon's systems flag some of these automatically and issue reimbursements. But many don't get caught — and Amazon won't go back and look without a prompt from you.

1–3%

of annual FBA revenue left unclaimed by the average seller

60 days

manual claim window — miss it and the money is gone permanently

recovered if you miss the window — claims expire permanently

On a $300,000/year FBA account, 1–3% is $3,000–$9,000 sitting uncollected. The individual claims are usually small — $15 here, $40 there — which is exactly why they're easy to miss manually but add up to real money over time.

⚠ The 60-day window is strict: Amazon's manual claim window is 60 days from the loss event. Claims that expire are gone permanently — Amazon will not reopen them. Monthly auditing is mandatory, not optional.

2. The Policy Rules That Determine How Much You Can Recover

Two rules govern Amazon's reimbursement program and directly affect how much you can recover. Understanding both determines whether you get full value from your claims or leave money on the table.

Rule	Current Policy	Impact
Claim window	60 days from loss event	Must audit monthly — not annually
Reimbursement basis	Your sourcing cost (purchase price from supplier, excl. shipping & duties)	Lower payouts; submit actual COGS to counter

What the 60-day window means in practice

If a unit is lost on March 1, your deadline to file a manual claim is April 30. If you run a quarterly audit, you will miss it every time. The only workflow that works now is reviewing your Inventory Ledger report every 2–4 weeks and flagging unclaimed losses immediately.

What the sourcing cost basis means for claim amounts

For Pre-order lost or damaged events (shipment to Amazon, removal, and fulfillment center operations), Amazon reimburses your sourcing cost — what you paid to acquire the item, excluding shipping, handling, and customs duties. If you haven't submitted your sourcing cost via Amazon's Inventory Defect & Reimbursement portal, Amazon uses its own estimate, which is frequently lower than what you actually paid. Submitting your actual purchase price with supporting documentation often results in a higher payout than the default estimate.

Action item: Start tracking your cost basis per unit now (see our COGS & FIFO guide) so you have documentation ready when Amazon underestimates a reimbursement.

3. The 6 Categories of FBA Reimbursements

Amazon's reimbursement obligations fall into six distinct categories. Each requires a different report, a different evidence trail, and a different case type when you open a support ticket.

📦

Category 1: Lost FBA Inventory

Units that Amazon's system records as missing — typically during warehouse transfers or cycle counts. In the Inventory Ledger Summary, these appear as a negative value in the Lost column on rows where Disposition = SELLABLE.

Amazon transfers inventory between fulfillment centers constantly. During these moves, units can be misplaced and recorded as lost in the system. Amazon's automation catches some of these and auto-reimburses, but a significant portion requires a manual claim.

Where to find it: Inventory Ledger report — use the Detail view to see individual loss events by FNSKU and date; or the Summary view, filter for Disposition = SELLABLE and look for a negative value in the Lost column. Cross-reference those FNSKU + date pairs against the Reimbursements report to filter out losses already paid.

Auto-reimbursed: sometimes Manual claim needed: often Window: 60 days from loss date

🔧

Category 2: Damaged Inventory

Units damaged while in Amazon's possession — during storage, picking, packing, or internal transfers. These are distinct from customer-returned damaged items.

When Amazon damages a unit in their warehouse, the Inventory Ledger records it under the WAREHOUSE_DAMAGED disposition — distinct from CUSTOMER_DAMAGED and DEFECTIVE, which reflect items returned damaged by customers. Amazon is responsible for WAREHOUSE_DAMAGED units and reimburses you at sourcing cost. Unlike lost units, damaged inventory sometimes shows up as unfulfillable stock rather than a complete removal — check both.

Where to find it: Inventory Ledger report (Summary view): filter for Disposition = WAREHOUSE_DAMAGED. Any units in this bucket without a matching reimbursement are your claim candidates. Also check your Unfulfillable Inventory report for units marked damaged-warehouse (as opposed to damaged-customer, which follows the refund-minus-fees reimbursement logic).

Evidence tip: Note the FNSKU, date, and quantity in the adjustment report. Amazon will request this when you open a case.

Auto-reimbursed: rarely Manual claim needed: usually Window: 60 days from loss date

↩️

Category 3: Customer Returns Not Checked In

Amazon issued a refund to a customer, but the returned unit was never received back into your inventory — either lost in transit or not processed at the returns center.

This is one of the most common and most overlooked reimbursement categories. When a customer initiates a return, Amazon often issues the refund immediately — before the item comes back. If the item never arrives at the fulfillment center (or arrives but is never checked in), you've lost both the sale revenue and the inventory unit.

Amazon may auto-reimburse some of these cases, but the automation misses a notable share. You need to manually verify that each refund-without-return has been addressed. Note: for customer return reimbursements, Amazon calculates the amount based on the refund or replacement given to the customer, minus applicable fees — not based on your sourcing cost.

Where to find it: Run the Customer Returns report. For each refund, check whether the corresponding unit appears in your inventory (as sellable or unsellable) or as a reimbursement in the Reimbursements report. If neither, it's an open claim.

Auto-reimbursed: sometimes Manual claim needed: for missed cases Dispute window: 60 days from reimbursement date

💸

Category 4: FBA Fee Overcharges

Amazon charged a higher fulfillment fee than your product's actual dimensions and weight warrant — usually due to incorrect measurement on file for the ASIN.

Amazon measures products when they arrive at the fulfillment center and uses those measurements to assign a size tier and calculate FBA fulfillment fees. Measurement errors are common — a product classified as Large Standard when it should be Small Standard will be overcharged on every single order.

For a product with 500 monthly sales, a $0.50 fee overcharge compounds to $250/month — $3,000/year — on a single ASIN.

Where to find it: In Seller Central, navigate to Manage Inventory → select a product → check the product dimensions on file against your actual product measurements. You can also pull the FBA Fee Preview report to see what tier each ASIN is assigned to. If dimensions are wrong, submit a remeasurement request and then file a reimbursement claim for the overcharged period.

Evidence tip: Measure your product including packaging with a tape measure and photograph it. Submit the photos + dimensions when opening the case. Amazon may schedule a physical remeasure.

Auto-reimbursed: never Manual claim required Window: 60 days per overcharged transaction

🚚

Category 5: Inbound Shipment Discrepancies

You shipped X units to Amazon in a shipment, but Amazon only checked in fewer than X — with no explanation for the difference.

Shipment discrepancies happen when Amazon's receiving count doesn't match your send quantity. You ship 200 units, Amazon receives 187, and the shipment closes with 13 units unaccounted for. Amazon is responsible for these if the shortage occurred after the carrier handed off the package.

This is particularly common with multi-box shipments. Amazon occasionally miscounts units across boxes or misattributes them to the wrong shipment.

Where to find it: In the Shipping Queue, find the relevant shipment and compare your "Units shipped" to "Units received." Discrepancies show as a shortage in the reconciliation tab. Amazon typically gives you a window to investigate before automatically closing the case.

Evidence needed: Your packing list or box content scan, carrier tracking showing delivery confirmation and package weight, and a clear record of what was in each box. The stronger the paper trail, the faster the reimbursement.

Auto-reimbursed: rarely Manual claim required Investigate within 60 days of shipment closure

⚡

Category 6: Chargebacks and Vendor Shortages

Amazon issued a chargeback or shortage deduction against your account incorrectly — common for sellers in hybrid retail arrangements or those using Amazon's vendor program.

Chargebacks on the third-party seller side are less common but do occur, particularly around co-op fees, aged inventory adjustments applied in error, or contested shortage claims where Amazon claims to have not received units you can prove were delivered.

Where to find it: Payments → Transaction View → filter for "Other" transaction types. Look for unexplained deductions that don't correspond to known fees. Each line item should have a reference ID — use this when opening a dispute.

Auto-reimbursed: never Dispute required Window: 60 days from charge date

4. Where to Find Open Claims in Seller Central

Every reimbursement investigation starts with a set of reports in Seller Central. Here's exactly where to go for each category.

Inventory Ledger Report (Lost & Damaged)

Seller Central → Reports → Fulfillment → Inventory → Inventory Ledger

The Inventory Ledger has two views. The Detail view shows individual transactions — best for building precise claim evidence (FNSKU, date, quantity, event type). The Summary view aggregates movement by date, FNSKU, and Disposition bucket. The Disposition column tells you whose fault the loss is:

SELLABLE — normal inventory. A negative Lost column value here = lost inventory claim (reimbursed at sourcing cost).
WAREHOUSE_DAMAGED — Amazon damaged the unit. Reimbursed at sourcing cost.
CUSTOMER_DAMAGED / DEFECTIVE — customer returned it in bad condition. Reimbursed at refund amount minus fees (not sourcing cost).

Download for the past 60 days. Cross FNSKU + date pairs against the Reimbursements report to filter out losses already paid.

Reimbursements Report (What's Already Been Paid)

Seller Central → Reports → Fulfillment → Payments → Reimbursements

This shows every automatic and manual reimbursement Amazon has paid. Use it as a subtraction filter: if a loss event appears here, don't file again. If a loss event from your Adjustments report is NOT here, it's an open claim.

Customer Returns Report (Refund-Not-Returned)

Seller Central → Reports → Fulfillment → Customer Concessions → Returns

Filter for orders where the return status is empty or the unit never shows up back in inventory. Give Amazon time to process the return before filing — then anything not resolved is an open claim. If Amazon has already issued a reimbursement but the amount is wrong, you have 60 days from the reimbursement date to dispute it.

Shipping Queue (Inbound Discrepancies)

Seller Central → Inventory → Manage FBA Shipments → Shipping Queue

Open each closed shipment and go to the Reconcile tab. Compare Units Shipped vs. Units Received. Any gap is a potential claim. Download the box content report for the shipment as your evidence.

FBA Fee Preview Report (Fee Overcharges)

Seller Central → Reports → Fulfillment → Inventory → FBA Fee Preview

Shows each ASIN's current size tier and fee. Compare against the actual dimensions of your products. If a product is in the wrong tier, calculate how many orders were overcharged × the overcharge amount, then open a case.

Build a simple tracking spreadsheet: Columns — Date, FNSKU, ASIN, Loss Type, Units, Estimated Value, Claim Filed (Y/N), Case ID, Reimbursement Received. Update it every 2–3 weeks. This takes 30–60 minutes monthly and is the minimum viable reimbursement process for any FBA seller.

5. How to File a Reimbursement Claim

Once you've identified an unresolved loss, filing the claim is a straightforward support case — but the quality of your evidence determines how quickly it resolves and whether Amazon approves the full amount.

Gather the evidence before opening the case. You need: the FNSKU or ASIN, the date of the adjustment or loss, the quantity affected, and the source report where you found it (Inventory Ledger, Returns, Shipping Queue). For shipment discrepancies, also pull your packing list and carrier confirmation.
Go to Seller Central Help and open a new case.
Seller Central → Help → Get Support → Selling on Amazon → FBA Issue → Inventory/Reimbursement
Select the case type that matches your issue. Be specific — "Lost inventory reimbursement" vs. "Shipment receiving discrepancy" route to different teams.
Write a clear, concise case description. Include: the specific loss event date, FNSKU, quantity, and a statement like "The Inventory Ledger report shows [X] units (FNSKU: [FNSKU]) recorded as Lost under SELLABLE disposition on [date]. The Reimbursements report shows no corresponding reimbursement for this event. Please investigate and reimburse." Avoid lengthy backstory — support agents scan quickly.
Attach supporting documentation. Upload the relevant report excerpt (screenshot or CSV rows showing the loss). For fee overcharges, attach product dimension photos. For shipment discrepancies, attach your packing list. The more specific the evidence, the faster the resolution.
Follow up after 5–7 business days if no response. Cases can get stuck in review queues. Reply to the open case with "Following up — please provide an update on the status of this reimbursement claim." Don't open a duplicate case as this can reset the queue position.
Escalate if the reimbursement amount is incorrect. If Amazon approves the claim but pays less than expected, submit your sourcing cost via the Manage Your Sourcing Cost page in the Inventory Defect & Reimbursement portal, or reply to the case with purchase documentation and request a review. Amazon's default sourcing cost estimates are frequently below what sellers actually paid.

⚠ Don't batch multiple loss events into one case. File separate cases for each distinct loss event. Batched cases are harder for support agents to process and more likely to be partially resolved or rejected. One case per FNSKU per loss event is the correct approach.

6. How Amazon Calculates Reimbursement Amounts

Understanding how Amazon values your lost or damaged inventory helps you know when to accept a reimbursement and when to push back. The calculation method depends on when the loss occurred relative to the customer order.

$5,000 per unit cap: The maximum reimbursement for any single FBA item is $5,000. For high-value products above this threshold, Amazon recommends purchasing third-party insurance.

Pre-order losses (warehouse, inbound shipments, removals) — sourcing cost basis

For inventory lost or damaged before an order is placed — during storage, inbound receiving, fulfillment center transfers, or removals — Amazon reimburses your sourcing cost: what you paid to acquire the item from a manufacturer, wholesaler, or reseller. Sourcing cost explicitly excludes shipping, handling, and customs duties.

If you haven't submitted your sourcing cost via the Manage Your Sourcing Cost page in the Inventory Defect & Reimbursement portal, Amazon uses its own estimate based on comparable products sold by Amazon, other sellers, and wholesale channels. This estimate is frequently lower than what you actually paid.

Scenario	Old Method (Selling Price)	Current Method (Sourcing Cost)	Difference
Unit sells for $25, costs $8	~$16–18 (sell price less fees)	~$8–10 (sourcing cost estimate)	−$6–10 per unit
Unit sells for $50, costs $15	~$32–38	~$15–20	−$15–20 per unit
Unit sells for $12, costs $6	~$7–9	~$5–7	−$2–3 per unit

Post-order losses (customer returns) — refund basis

For customer return reimbursements, the calculation is different: Amazon reimburses the refund or replacement amount given to the customer on your FBA order, minus applicable fees. This is not tied to your sourcing cost — it's based on what the customer actually received back.

How to maximize your reimbursement amount

For pre-order losses, if Amazon's sourcing cost estimate is below what you actually paid, you can submit your actual purchase price via the Manage Your Sourcing Cost portal, or attach documentation to your support case:

Purchase invoices showing what you paid per unit to your supplier
Supplier quotes or contracts that establish your per-unit cost basis

Important: Amazon's definition of sourcing cost excludes shipping, handling, and customs duties — submit your per-unit purchase price only, not your full landed cost. Amazon may decline submissions that appear to be outliers compared to similar products, or if documentation cannot be verified.

Key takeaway: Sellers who proactively submit their sourcing cost in the Inventory Defect & Reimbursement portal recover more than those who accept Amazon's default estimates. Keep purchase invoices organized by ASIN — they're your primary evidence for reimbursement disputes.

FAQ

Does Amazon automatically reimburse for everything it owes me?

No. Amazon's automation catches some clear-cut cases — particularly certain types of lost inventory and some customer returns — but it misses a significant share. Fee overcharges, inbound discrepancies, and customer returns where the unit was never logged as received back all require manual claims. You cannot rely on automation to recover everything.

How often should I audit my reimbursements?

At minimum, every 30 days — and ideally every 2 weeks. With the 60-day claim window, any loss event older than 60 days is permanently expired. A monthly audit gives you a buffer; a bi-weekly audit ensures you never miss anything. The process takes 30–60 minutes once you have the workflow down.

Can I hire a third-party service to handle reimbursements for me?

Yes. Many reimbursement agencies work on a commission basis (typically 15–25% of recovered amounts) or flat monthly fees. For sellers who don't want to manage the process themselves, this is a viable option. Just verify that the service files claims correctly and doesn't submit invalid claims that could flag your account. Amazon restricts certain automated filing approaches, so ensure any service you use operates within current guidelines.

What if Amazon rejects my reimbursement claim?

If a claim is rejected, review the rejection reason and re-submit with additional supporting documentation. Common rejection reasons include: the loss was already reimbursed (check the Reimbursements report), the 60-day window has passed, or the evidence provided was insufficient. For the latter, add more specific documentation — report screenshots, exact dates, FNSKUs — and resubmit. If the case is closed, you can open a new case referencing the original case ID.

Are reimbursements taxable income?

Generally yes — reimbursements appear as income in your Amazon settlement and should be treated as such for tax purposes. However, since the underlying inventory was written off as a loss (which reduced your taxable income), the reimbursement effectively offsets that prior deduction. The net effect is usually tax-neutral, but confirm the treatment with your accountant as it depends on how you handled the original loss in your books.

Stop leaving reimbursements on the table.

SellerGuards surfaces lost inventory, return discrepancies, and fee overcharges — automatically, before the 60-day window closes.

Get started free