Amazon FBA Reimbursement Scanner
Pricing
Pay per usage
Amazon FBA Reimbursement Scanner
Audita dados de relatorios Amazon FBA e devolve as reclamacoes de reembolso reclamaveis, com janela de prazo e valor estimado. Deduplica o que a Amazon ja pagou.
Pricing
Pay per usage
Rating
0.0
(0)
Developer
Gabriel Barreto
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
Amazon loses and damages inventory inside its own warehouses, and it does reimburse you for it — but only if you file a claim, and only inside a filing window. Most sellers never file, because the evidence is spread across four separate reports that nobody reads line by line.
Paste those reports in. Get back the claims you can still file, each with the units, the estimated value, the days left before the window closes, and the evidence to paste into the case.
The reconciliation approach behind this was raised publicly on Amazon's own SDK tracker — amzn/selling-partner-api-models issue #5353 — and acknowledged there.
What it detects
| Rule | Category | How it is proven |
|---|---|---|
| A | Inventory lost or damaged in the warehouse, never reimbursed | Adjustment rows with a Lost/Damaged reason and no matching reimbursement |
| B | Customer return never returned to sellable stock | Return recorded, no corresponding inventory movement back in |
| C | Removal order that never arrived | Removal shipped, not received, past the expected window |
Every claim carries the rows it came from. You are never asked to trust the tool — you are shown what to paste into the Amazon case.
What it will not do
- It never claims twice. Anything already covered in
GET_FBA_REIMBURSEMENTS_DATAis matched and excluded. Filing a duplicate claim is the fastest way to lose credibility with Seller Support. - It does not invent values. Amazon reimburses your unit cost, not your selling price. Without a
costMapor adefaultUnitCostthe claims are still correct, but the estimated value comes out as0— and the Actor says so loudly in the log rather than showing you a column of zeros and letting you conclude it is broken. Zero is not the same as unknown. - It does not need your Amazon credentials. You paste report rows. Nothing connects to your seller account from here.
Input
Export these from Seller Central (Reports → Fulfilment) and paste the rows as JSON objects:
| Field | Report |
|---|---|
adjustments | GET_FBA_FULFILLMENT_INVENTORY_ADJUSTMENTS_DATA |
reimbursements | GET_FBA_REIMBURSEMENTS_DATA |
returns | GET_FBA_FULFILLMENT_CUSTOMER_RETURNS_DATA |
removals | GET_FBA_FULFILLMENT_REMOVAL_ORDER_DETAIL_DATA |
costMap | Your unit cost per SKU, e.g. {"MY-SKU": 9.12} |
The default input is a small worked example so you can see the shape of the output before pasting your own data.
Output
One row per claimable reimbursement:
| Field | Meaning |
|---|---|
rule / category | Which rule fired and what kind of loss it is |
sku / fnsku / quantity | What was lost and how many units |
estValue / currency | Units times your unit cost |
daysLeft | Days remaining before the filing window closes. This is the field that decides your order of work. |
evidence | The source rows, ready to paste into the case |
The deadlines are short now
Amazon shortened the filing windows on 23 October 2024, and the change is easy to miss because most guides still quote the old numbers:
| Claim type | Window |
|---|---|
| Lost or damaged in a fulfilment centre | 60 days (it used to be 18 months) |
| Customer return not restocked | 60 to 120 days |
| Removal lost in transit | 15 to 75 days |
This is the single most important thing the scanner gets right. A tool still using the old 18-month window will tell you a claim is fine when the window closed a year ago. Since 1 November 2024 Amazon also auto-reimburses many lost-in-FC cases, so very recent events are marked wait rather than claim now — but only briefly, because waiting 45 days inside a 60-day window leaves almost no time to act.
A deadline worth knowing
Amazon is retiring the settlement report format on 11 November 2026. Reconciliation that depends on it will stop working on that date. This Actor works from the fulfilment reports, which are not affected.
Pricing
Pay per claim found. If the scan finds nothing claimable, you are not charged for findings that do not exist.
