FBA reimbursements you are probably missing
Dastan
Founder & Owner

A missing FBA unit is a reason to check your records, not proof that Amazon owes you money. First match the loss, return or removal against any payment already made. Then check whether the issue qualifies for a claim in your marketplace.
This guide gives you a short weekly routine, a claim-window reference and an evidence checklist. It does not promise a payout. Amazon decides each claim under the policy that applies to that event.
Key takeaways
- Check for an automatic reimbursement before opening a manual claim for the same units.
- Match the claim type, marketplace and event date before calculating its deadline.
- Use the dated claim-window table as a reference, then confirm your live Seller Central policy.
- Keep item IDs, quantities, report rows and supporting documents together in one case record.
- Review open issues weekly; a quarterly-only check can miss short filing windows.
Check for a payment before you claim
FBA claims are not all opt-in. Amazon's UK automation announcement explains that many warehouse-loss, damage and return cases receive automatic payments. It also says unpaid eligible cases may need a manual claim, while removal claims still require one.
Start with the Reimbursements report. Match the item, event and quantity, then check for later corrections. A stock adjustment on its own is not the same as an unpaid loss. Keep any linked payment ID with your notes so you do not claim twice.
Claim windows: match the type and the start date
Policy reference checked: 3 September 2026. The table summarises Amazon's public claim-window notice effective 15 October 2025 on UK Seller Central. It is a dated reference, not a worldwide filing rule.
Before filing, select your marketplace and read its live FBA inventory reimbursement policy (sign-in may be required). The account-specific policy was not available for this public-source review. Do not transfer these dates to a US or other marketplace claim without checking.
On a small screen, scroll the table sideways to read all three columns.
| Claim type | Filing window | Count from |
|---|---|---|
| Warehouse loss or damage | Within 60 days | The reported loss or damage |
| Customer return | Days 45–105 | The refund or replacement |
| Lost removal shipment | Days 15–135 | Shipment creation |
| Damaged removal shipment | Within 120 days | Shipment delivery |
| Removal grading dispute | Within 120 days | Removal from the fulfilment network |
| Request to review a claim | Within 90 days | The initial claim |
Record the event date as soon as you spot an issue. Your discovery date may not start the clock. Where a window has an opening day, prepare the evidence early but do not submit before the claim is eligible.
Keep inbound stock and fee disputes separate
A removal shipment travels back out of Amazon's network. It is not the same as stock you send to Amazon. For an inbound shortage, use the shipment's reconciliation screen and the shipment-to-Amazon reimbursement policy for your selected marketplace. Do not apply a removal deadline to it.
Wrong weight or dimensions can also lead you to question an FBA fee. Treat that as a separate fee dispute, not a warehouse-loss claim. Check the relevant fee policy and request deadline in Seller Central. Save the charged fee and the measurements that support your request.
A weekly check you can repeat
We suggest a weekly review, plus reminders for claims nearing their deadlines. This is a working routine, not an Amazon requirement. A quarterly-only check can leave too little time to act on a short filing window.
- Collect: export recent stock movements, returns, removals and reimbursements for one marketplace.
- Match: compare item IDs and quantities. Check whether missing units were found, returned or already paid for.
- Classify: choose the claim type. Save the event date, policy link, opening day and deadline.
- Document: gather the report rows and proof needed for that issue. List any gaps before filing.
- Track: record the case ID, response and final outcome. Check payments and later adjustments before closing your record.
Pair this stock review with the weekly Account Health routine. Keep the records separate: an inventory claim does not resolve a policy warning or appeal. Check urgent account notices on their own schedule.
Build a clear evidence pack
Use the IDs that belong to the issue. Not every claim has a shipment ID. A return may need an order ID; a stock adjustment may need a transaction reference. Follow the documents requested in the relevant claim workflow.
- Marketplace, ASIN or FNSKU, and the units in dispute.
- Order, shipment, removal or transaction IDs that connect the records.
- Event dates and report rows showing the gap.
- Invoices, delivery proof or item photos where the workflow requests them.
- Any linked claim, reimbursement or later adjustment.
Write a short summary: what happened, which records disagree, and what you want reviewed. Keep source files unchanged. Do not inflate quantities, alter invoices or describe a suspected loss as a confirmed one.
If Amazon denies the claim
Read the stated reason before replying. Check whether the issue is timing, eligibility, missing proof or a payment you missed. If review is allowed, address that point with the relevant record and keep the original case ID. A repeated claim with no new evidence does not fix the gap.
Keep separate totals for amounts requested, approved and paid. Do not treat a submitted claim as recovered money. There is no reliable payout estimate without checking the account's records.
If you need help with that review, see our FBA reimbursement service. Share the marketplace, issue type and available records first. The scope and quote should follow the evidence, not an assumed recovery amount.
Related Service
Resolve Reimbursement & Disbursement IssuesNeed Help With Your Amazon Account?
Our experts are available 24/7. Free consultation, results-based pricing.
Chat on WhatsApp