What this tool does
This free FBA Reimbursement Calculator helps Amazon India sellers find refunded returns that Amazon never paid them back for. It reads your two Seller Central reports, matches them against each other, and shows you a clear list of strong claims to file first and cases that are only worth reviewing — so you can recover real money without wrestling pivot tables.
Everything runs inside your browser. Your reports are never uploaded to any server, so your order data stays entirely on your own device.
How to use this tool
- Download your FBA Customer Returns Report from Reports → Fulfilment, for the last 45 to 60 days.
- Download your Reimbursements Report for the same date range, from the same menu.
- Drop both files into the upload boxes above — keep them exactly as Amazon gives them, unedited.
- Click Find Unclaimed Returns to see your strong claims and review cases.
- Download the claim list as a CSV and work through each order in Seller Central.
What counts as a claim
Not every painful return is recoverable, and filing for the wrong ones only wastes your time. The tool sorts your returns using the same test Amazon applies: was the loss outside your control?
Usually claimable (strong)
A refund was issued but the unit never came back to your sellable inventory, a wrong or different item was returned, or the unit was damaged by Amazon or the carrier — and there is no matching reimbursement on record.
Usually a seller cost (review only)
The unit was returned as customer-damaged, defective, or expired. Amazon generally treats these as your cost, so the tool flags them for review rather than filing.
The two reports explained
FBA Customer Returns Report — lists every returned unit with its order ID, ASIN, return reason, and detailed disposition (sellable, unsellable, customer-damaged, carrier-damaged, and so on), plus whether the unit was returned to inventory.
Reimbursements Report — lists every loss Amazon has already paid you back for automatically. The tool uses this to make sure you never file for something you've already been reimbursed, which protects your account from duplicate claims.
Reading your results
- Returns scanned — total returns read from your Customer Returns report.
- Strong claims — file these first; they're the cleanest, highest-value cases.
- Worth reviewing — confirm the cause in Seller Central before deciding whether to file.
- Est. units to claim — the combined count you may be able to recover on.
The tool reads only the columns Amazon provides and does not guarantee approval. Always open each order in Seller Central to confirm before filing, and remember the India claim window is roughly 60 days from the refund or delivery date.
Worked example
- Returns scanned: 120 over 60 days
- Sellable, back in inventory: 96 — no loss, skipped
- Already reimbursed: 11 — skipped automatically
- Carrier/warehouse-damaged, unpaid: 7 — flagged as strong claims
- Never returned, refund issued: 3 — flagged as strong claims
- Customer-damaged: 3 — flagged for review (likely a seller cost)
In this case the seller files 10 strong claims straight away and reviews 3 more, instead of writing all 13 losses off as a cost of doing business.
Tips & edge cases for Amazon sellers
- Run it every 15 days. India's 60-day window means a monthly audit leaves your oldest cases half-expired. Fortnightly keeps everything claimable.
- Keep cost records ready. Since 2025 many reimbursements pay on estimated product cost, not selling price. Submit your cost data when Amazon asks to recover closer to fair value.
- One issue per case. File each order separately with the order ID, ASIN, refund date, and the report line that proves the loss.
- Don't over-file. Skipping customer-damaged returns keeps your claim quality high and your queue clean.
- Re-download unedited. If the tool can't read a file, pull a fresh copy from Seller Central without opening it in Excel first.
Glossary
- Disposition: Amazon's verdict on a returned unit's condition — sellable, unsellable, customer-damaged, carrier-damaged, and so on.
- Reimbursement: money Amazon pays back when a loss is its responsibility.
- FNSKU: the unique code Amazon assigns to each of your products in FBA.
- Claim window: the period you have to file — roughly 60 days in India.
- Strong claim: a refunded return with no reimbursement that's most likely recoverable.
Changelog
- v1.0: Initial release — two-report matching, strong vs review grouping, CSV export, fully in-browser.
FAQs
Does this tool upload my data anywhere?
No. The tool reads your files directly in your browser and matches them on your own device. Nothing is sent to any server, so your order-level data never leaves your laptop. You can even disconnect from the internet after the page loads and it will still work.
Can FBA sellers file a SAFE-T claim?
No. SAFE-T claims are only for seller-fulfilled orders. FBA sellers recover money through the FBA reimbursement process instead — audit your Customer Returns and Reimbursements reports, then open a case for any refund where the unit was never returned, came back as a different item, or was damaged by Amazon.
What is the FBA reimbursement claim window in India?
For India FBA customer-return claims you generally have about 60 days from the verified delivery or refund date. That tight window is exactly why a fortnightly audit beats a monthly one, since waiting a full month leaves your oldest eligible cases close to expiry.
Why is my reimbursement smaller than my selling price?
Since early 2025, Amazon calculates many reimbursements on your estimated product cost rather than your retail price. The defence is to keep accurate per-SKU cost records and submit your cost data whenever Amazon requests it, so you're reimbursed closer to fair value instead of Amazon's lower estimate.
Does Amazon reimburse customer-damaged returns?
Usually not. If a buyer opens, uses, or damages an item and returns it unsellable, Amazon typically treats that as a cost you carry. That's why the tool puts these in "worth reviewing" rather than "strong claims" — file only after confirming the cause in Seller Central.
How often should I run this tool?
Every 15 days is the sweet spot for Indian sellers given the 60-day window. A fortnightly thirty-minute audit catches losses while they're still claimable and keeps the workload small. Pull your two reports, run them through, file the strong claims, and log each one.
