The Complete Amazon FBA Reimbursement Guide (2026)
Every category of FBA reimbursement, exact filing deadlines, evidence requirements, the auto-reimbursement gotchas, and a step-by-step procedure for filing claims through Seller Central in 2026.
If you sell on Amazon FBA, there are reimbursement-eligible discrepancies in your account right now that you have not collected. Between inbound shortages, lost units, damaged inventory, return fraud, and fee overcharges, the typical seller has between 1% and 3% of annual revenue tied up in errors that Amazon will not auto-correct.
For an eight-figure seller, that translates to tens of thousands of dollars sitting on the table every year. The burden of detecting these discrepancies, gathering evidence, and filing claims falls on you — and the deadlines are unforgiving. Miss the window and the money is gone.
This is the definitive 2026 guide to FBA reimbursements: every claim category, the current filing deadlines, the auto-reimbursement coverage gaps that catch sellers off guard, the evidence packets Amazon expects, and a working procedure for filing claims through Seller Central. By the end you will know exactly what to look for, how to document it, and how to file.
Why FBA reimbursements matter
Amazon's fulfillment network handles billions of units per year. At that scale, errors are statistical certainties: units get lost, miscounted, damaged, charged the wrong fees, refunded incorrectly, and returned to the wrong sellers. Amazon's automated systems catch some of these and credit you automatically, but the auto-reimbursement coverage is incomplete. The categories where it works well are warehouse-lost and warehouse-damaged inventory. The categories where it leaves money on the table are inbound shortages, customer return discrepancies, fee overcharges, and removal-order shortages.
The reason most sellers under-claim is not laziness — it is that the discrepancies are hidden across multiple Amazon reports, the matching logic between reports is non-obvious, and the eligibility windows are short. A seller manually checking inventory adjustments once a month will miss most claims. A seller running automated audits across the full claim window will catch them.
The financial scale matters. For a seller doing $1M revenue at typical FBA churn rates, recoverable reimbursements run between $10,000 and $30,000 per year. For an eight-figure seller, the same percentages compound to six-figure annual recoveries. This is not "found money" in the casual sense — it is money Amazon already owes you, that they will not give you unless you explicitly file the claim.
1. Inbound shipment shortages
When you ship inventory to an Amazon fulfillment center, the received quantity does not always match what you sent. Units can disappear during the unloading process, get miscounted at receiving, fall behind conveyor belts, or end up in the wrong fulfillment center entirely. Amazon used to reconcile most of these automatically; their auto-reimbursement coverage has tightened in recent years and many shortages now require manual claims.
How to detect it: Compare the shipped quantity from your FBA shipment plan against the quantity Amazon reports as received in the Inbound Shipments report. Any difference greater than zero is a potential claim. Be careful to check ALL shipment IDs in a multi-destination split — partial receipts on individual shipment IDs are easy to miss when you focus only on the parent plan.
Filing window: 60 days from the shipment delivery date. Amazon shortened this dramatically — older guides still cite the previous 9-month (270-day) window, but under Amazon's current US policy you must file within 60 days. Reconcile every shipment quickly while the evidence chain is fresh and Amazon's receiving records are still available.
Required evidence: The original shipment plan with declared quantities, the carrier's proof of delivery showing the box count and weight, and ideally pack-list photos for each box. SellerVault's reimbursement engine cross-references inbound shipment lines against received quantities continuously and surfaces shortages with the evidence packet pre-attached.
2. Inbound shipment damage
Sometimes Amazon receives units but damages them during the intake process. These items get marked as unsellable, may be disposed of, and you may never know they were destroyed. If the damage occurred while inventory was in Amazon's care, you are entitled to reimbursement at the unit's sale price.
How to detect it: Monitor the Inventory Adjustments report for reason codes related to warehouse damage on units that were recently received. Cross-reference against any auto-reimbursements applied to confirm Amazon did not already credit you.
Filing window: 60 days from the shipment delivery date — the same short window as inbound shortages, so file both as soon as you spot them on a shipment.
3. Warehouse lost inventory
This is the largest single reimbursement category for most sellers. Amazon's fulfillment centers handle massive unit volumes, and units get misplaced, fall behind shelves, get sent to wrong bins, or vanish during inter-FC transfers. Amazon now auto-reimburses most warehouse losses through the Inventory Discrepancy Report (IDR) within 30 days — but "most" is the key qualifier.
How to detect it: Cross-reference the Inventory Ledger against the Inventory Adjustments report. Look for units removed from sellable inventory with reason codes like "misplaced", "lost", or "warehouse damage". Then check the IDR to see whether Amazon auto-credited you. The gap between adjustment-out and auto-credit is your manual claim opportunity.
Filing window: 60 days from the date the inventory was reported lost — a short window, so check weekly.
Auto-reimbursement gotchas: (a) Auto-reimbursement only applies after a 30-day search window, so claims that should be auto-credited may sit pending for a month before resolving. (b) Some reason codes are excluded from auto-reimbursement entirely. (c) If you have a high IPI score and clean account history, auto-reimbursement coverage is broader. Distressed accounts get less.
4. Warehouse damaged inventory
When inventory is damaged while stored or handled inside Amazon's warehouses — picking, packing, customer ship-out, internal transfers, the works — you are entitled to reimbursement. Like warehouse lost, most warehouse damage is auto-reimbursed through the IDR. The gaps are the same: filter the IDR, find the misses, and file manually within 60 days.
Why this category is bigger than people think: Warehouse damage often happens at scale on hazmat or fragile categories. A single bad pick session can damage dozens of units of one SKU. Sellers who only spot-check one or two SKUs miss the cluster events.
5. Customer return discrepancies
Customer returns are the most complex reimbursement category because there are multiple distinct ways things can go wrong. The four main failure modes:
(a) Missing return. A customer received a refund but never sent the item back. Amazon's US policy (effective 2024-10-23) gives sellers a 60-day wait before they can file a reimbursement case — that window exists so the customer has time to ship the return. If no return is received and Amazon does not auto-reimburse, you can file from day 60 through day 120.
(b) Wrong item returned. A customer sends back a different product than what they purchased. You receive damaged or completely unrelated inventory while the customer keeps your product. Detecting this requires comparing return SKUs against original order SKUs.
(c) Damaged on return. The customer sends the item back in unsellable condition. Amazon should mark it unsellable AND reimburse you. Sometimes they only mark it unsellable.
(d) Refund overcharge. Amazon refunds the customer more than the original sale amount. This is rare but it happens during promotional code edge cases.
Filing windows (Amazon US, effective 2024-10-23): Wait at least 60 days after the refund (so the customer's return window has closed and Amazon's auto-reimbursement has had a chance to fire), then file by day 120. For wrong-item returns, file as soon as you can document the discrepancy and within the same 60-120 window.
Evidence: The refund amount and date, whether the item was returned, the condition of the returned item, and (if you can get it) photos of the wrong item received.
6. Fee overcharges (weight and dimension errors)
Amazon charges FBA fulfillment fees based on the unit's weight and dimensions on file. If those measurements are wrong — even by a fraction of a pound or inch — you may be paying a higher fee tier on every single sale. For a high-velocity SKU, a small dimensional error can cost thousands of dollars over a year.
How to detect it: Pull Amazon's recorded weight and dimensions for each ASIN and compare against your actual measurements. Flag any case where Amazon's value is materially higher. Re-measuring physical units against the FBA Fee Preview report is the gold standard.
Filing window: 90 days from the date the fee was charged. Because the overcharge applies to every sale, the cumulative recoverable amount can be substantial.
Filing process: Amazon's "request a re-measure" process automatically corrects the dimensions going forward, then back-credits fee differences for the recent past.
7. Removal order discrepancies
When you create a removal order to have inventory sent back to you (or disposed), Amazon sometimes loses or damages units in transit. If the quantity you receive does not match the quantity on the removal order, you have a valid claim.
Detection: Compare the removal order quantity against what physically arrived at your return address (or what Amazon confirms as disposed). The reconciliation is straightforward but tedious without automation.
Filing window: Between 15 and 75 days after the removal shipment was created. The 15-day floor exists because Amazon needs time to actually process the removal.
Critical deadlines at a glance
| Category | Deadline |
|---|---|
| Inbound shortages | 60 days from delivery |
| Inbound damage | 60 days from delivery |
| Warehouse lost | 60 days from report (auto-credited first) |
| Warehouse damaged | 60 days from report (auto-credited first) |
| Customer return missing | 60-120 days from refund (US) |
| Customer return wrong item | 60-120 days from refund (US) |
| Refund overcharges | 120 days from refund |
| Fee overcharges | 90 days from charge |
| Removal lost | 15-75 days from removal creation |
| Removal damaged | 60 days from delivery to seller |
Build a recurring weekly audit cadence that touches every category. Most windows now close within 60-90 days (inbound shortages and damage, warehouse lost/damaged, removals, fee overcharges), so they need frequent attention; only the customer-return and refund categories stretch to 120 days.
How to file a reimbursement claim
Filing is done through Seller Central. The exact path varies by claim type but the procedure is consistent: open a case, select the correct category, attach evidence, write a clear claim narrative, and follow up if Amazon's first response is generic.
Amazon explicitly forbids API automation for reimbursement filing — claims must be opened manually through Seller Central, even if the detection workflow is fully automated. SellerVault's reimbursement engine respects this by surfacing claims in a queue with copy-ready evidence packets, but the human still clicks "submit" inside Seller Central. Tools that promise "automated filing" through APIs are a TOS risk and may get your account flagged.
The narrative matters. Generic ("I am missing inventory, please reimburse") gets a generic deny. Specific ("Shipment FBA12345 declared 240 units; received report shows 230. Carrier proof of delivery attached, weight reconciles. Please reimburse 10 units of B07XYZ123") gets approved. Always cite specific shipment IDs, dates, and quantities.
Building a sustainable reimbursement cadence
The mistake most sellers make is treating reimbursements as a quarterly project. They batch the audit, file 30 claims, get exhausted, and put it off for another quarter. By then half the claims have hit their deadline.
The right cadence is weekly, not quarterly. Most categories now close within 60-90 days — inbound shortages and damage, warehouse lost/damaged, removals, and fee overcharges — so they cannot safely wait. Spend 30-60 minutes once a week reviewing new discrepancies, and file the claims that are clearly eligible. Only the customer-return and refund categories (up to 120 days) have enough slack to batch monthly.
For sellers above ~$1M revenue, the time investment to do this well exceeds what makes sense in-house. The two options are: hire a flat-commission service like GETIDA (typically 25%), or use a bundled reimbursement engine like SellerVault that runs continuously and presents pre-built claims for human review (10-25% commission depending on plan tier). For a seller recovering $30K/year, the difference between 25% and 10% commission is $4,500 — meaningful but not life-changing. The bigger benefit of continuous auditing is that you do not let claims expire.
Frequently asked questions
Do I need to use a third-party tool to file FBA reimbursements?
Not strictly. You can file every claim manually through Seller Central if you have the time and discipline to audit the relevant reports weekly. Tools like SellerVault and GETIDA exist because most sellers do not have that discipline, and the deadlines are unforgiving — a tool that runs continuous audits catches eligible claims before they expire.
Is automated reimbursement filing allowed by Amazon TOS?
No. Amazon explicitly forbids API-based automated reimbursement filing. Claims must be opened manually through Seller Central. SellerVault detects claims automatically and prepares the evidence packet, but the human still submits the case through Seller Central. Tools that promise "fully automated" filing via API are a serious TOS risk.
How much can I expect to recover per year?
The general rule of thumb is 1-3% of annual revenue, but it varies based on category mix, supply chain complexity, and whether you have been auditing in the past. Sellers who have never run a reimbursement audit before typically recover larger amounts on the first audit because it sweeps their entire backlog of still-claimable discrepancies at once.
What if Amazon denies my claim?
Re-open the case with additional evidence and a more specific narrative. Generic claims get generic denies; specific claims with shipment IDs, dates, and quantities get approved. If a second submission fails, escalate to a supervisor through the case message thread. Persistence matters — the same claim with the same evidence often gets approved on the second or third submission.
How does SellerVault's reimbursement engine differ from GETIDA?
Three things: (1) commission tiers — SellerVault commission scales from 25% on Starter down to 10% on higher plans, vs GETIDA's flat ~25%; (2) bundled with the rest of your operations — the reimbursement engine sits alongside inventory, repricing, and analytics in the same dashboard rather than being a separate portal; (3) continuous auditing — claims surface weekly instead of in quarterly batches, so the deadline math works in your favor.