Amazon FBA Reimbursements: The 2026 Fee-Leakage Audit

Amazon now auto-pays some of what it owes you and quietly runs out the clock on the rest. Here is the operator's audit: the five drains where FBA money actually leaks, the exact claim window on each, and the monthly sweep that files everything before it expires.

DG David Gallo·August 25, 2026·16 min read·Last updated August 25, 2026

Amazon FBA profitability audit diagram showing five fee-leakage drains, reimbursement claim windows, and a monthly 60-day sweep cadence

TL;DR

Amazon FBA reimbursements in 2026 run on short clocks: most fulfillment-center claims must be filed within 60 days, customer-return claims between 45 and 105 days after the refund, removal claims between 15 and 75 days — and since March 2025 Amazon pays your manufacturing cost, not your sale price. This playbook maps the five drains where FBA money leaks and the monthly 60-Day Sweep that files every claim in time. SellerForge (our product, disclosed) runs the sweep at $99/month flat.

Amazon owes most FBA sellers money right now. Industry audits consistently find 1–3% of annual revenue sitting in unclaimed reimbursements and fee overcharges: inventory lost in fulfillment centers that automation missed, refunds issued for units that never came back, fulfillment fees computed on the wrong size tier. On a $500,000 account, that is $5,000 to $15,000 a year. This playbook — built around a monthly cadence I call the 60-Day Sweep, and the reason SellerForge (our product, disclosed throughout) ships a Reimbursement Claims module — is how you get it back before the claim windows close.

The clock is the story. In October 2024 Amazon cut most claim windows from 18 months to 60 days. In November 2024 it started proactively reimbursing fulfillment-center losses, which sounds like the problem solved itself. Then in March 2025 it switched payouts from sale price to manufacturing cost, cutting per-claim recoveries 50–75%. The net effect: the easy money shrank, the deadlines tightened, and every month you skip the audit, claims expire permanently.

Across the 57 accounts I managed at Worldfront, profitability audits were monthly, not quarterly — and the difference was never sophistication. It was that a monthly rhythm sees every claimable event while it is still claimable. Here is the full audit: the five drains where FBA money leaks, the official window on each, and the sweep that files everything in time.

How do Amazon FBA reimbursements work in 2026?

Amazon FBA reimbursements in 2026 run on three rules: Amazon proactively reimburses most inventory lost in fulfillment centers (since November 1, 2024), everything else must be filed manually inside windows as short as 60 days (since October 23, 2024), and payouts are based on your manufacturing cost rather than your sale price (since March 10, 2025).

The proactive layer is real but partial. Per Amazon's reimbursement automation announcement, items identified as lost in a fulfillment center trigger a reimbursement on the identification date and process within about five business days, no claim needed, with most warehouse-damage and customer-return cases covered the same way. What stays manual: every removal claim, and every loss the automation fails to flag — which is exactly the residue a monthly audit exists to catch. Auto-payments land in the Reimbursements report, which is also where you reconcile what did NOT arrive.

The manufacturing-cost change is the one that reset expectations. Amazon now pays what the unit cost you to source — excluding shipping, handling, and customs duties — not what you would have sold it for. You can provide your own per-unit cost, backed by supplier invoices, or accept Amazon's estimate, which sellers widely report runs low. Feeding accurate cost data for every SKU is now the single highest-leverage input in the whole reimbursement system: it is the difference between being paid your real cost and being paid Amazon's guess.

Three dates rewired this game: October 23, 2024 (claim windows cut from 18 months to 60 days), November 1, 2024 (proactive reimbursement for fulfillment-center losses), and March 10, 2025 (payouts switch to manufacturing cost). Any audit habit formed before those dates is miscalibrated today.

How far back can you claim Amazon FBA reimbursements?

Sixty days, for most claims. The 18-month lookback died on October 23, 2024, and each claim type now has its own tight window: fulfillment-center lost and damaged claims close 60 days after the loss is reported, customer-return claims open at day 45 and close at day 105 after the refund, and removal claims lost in transit run from day 15 to day 75 after shipment creation.

Claim type	Official window	Filed by
Fulfillment center lost or damaged	Within 60 days of the item being reported lost or damaged	Amazon auto-pays most; you file the misses
FBA customer returns	45–105 days after the refund or replacement date (filing before day 45 is rejected)	Amazon auto-pays most; you file the misses
Removal claims — lost in transit	15–75 days from the removal shipment creation date	Always manual — automation never covers removals
All other removal claims	Within 60 days of the shipment being delivered back to you	Always manual

Those windows are Amazon's own, from the official eligibility-window update, and they cut both ways: file too late and the claim is void, file a returns claim before day 45 and it is auto-denied because the buyer still has time to send the unit back. The operational consequence is simple and non-negotiable — any audit cadence longer than monthly now forfeits claims by design. A quarterly audit leaves up to two months of fulfillment-center losses unclaimable every single cycle.

The 60-Day Sweep: a monthly audit built for 60-day windows

The 60-Day Sweep is a monthly, five-drain audit sized to Amazon's shortest claim window: run it every 30 days and every claimable event is at most ~30 days old when you find it, leaving half the window to gather evidence and file. It replaces the quarterly audit, which made sense under 18-month windows and silently loses money under 60-day ones.

The five drains are the five distinct ways FBA accounts leak money. They live in different reports, carry different clocks, and need different fixes — which is why sellers who only check one of them (usually lost inventory) recover a fraction of what is theirs.

Drain	What it looks like	Where it shows	Clock
1. Lost & damaged inventory	Units vanish or break in the FC; automation pays most, misses some	Inventory Ledger vs. Reimbursements report	60 days
2. Refund gaps	Buyer refunded, unit never returned; refund exceeds the original charge	Returns report vs. refund transactions	45–105 days
3. Fee measurement errors	Wrong dims or weight put the SKU one size tier up	Fee Preview vs. your own measurements	Fix stops the bleed; recent overcharges recoverable
4. Category classification errors	SKU pays a higher referral-fee percentage than its category warrants	Fee schedule vs. per-SKU referral charges	Same — catch early, correct forward
5. Schedule drift	New fees and surcharges land silently in unit economics	Fee announcements vs. per-SKU margin	No claim — a repricing decision

Here is the sweep itself, in the order I ran it. Budget an hour a month for a mid-size account the first time; it gets faster.

1Pull the Inventory Ledger and reconcile every lost and damaged event against the Reimbursements report; flag any event with no matching reimbursement ID.
2Cross the Returns report against refund transactions; flag every refund past day 45 with no returned unit, and every refund larger than the original charge.
3Spot-check fulfillment fees on your top 20 revenue ASINs against your own measured dimensions and weight; queue a remeasurement case for every mismatch.
4Check each ASIN's referral-fee category against the current fee schedule; flag SKUs charged a higher percentage than their category calls for.
5Read the month's fee announcements and re-run unit economics on every SKU they touch; a surcharge here and a placement-fee change there compound quietly.
6File every flagged claim with evidence the same week, log the claim IDs, and carry unresolved cases into next month's sweep so nothing falls between cycles.

The sweep is deliberately boring. It is reconciliation, not detective work — the same discipline behind tracking contribution margin per ASIN: the numbers are all in reports Amazon already gives you, and the leak persists only because nobody looks monthly.

How do you know if Amazon overcharged you on FBA fees?

Compare Amazon's stored dimensions and weight for each SKU against your own measurements, because every fulfillment fee is computed from Amazon's numbers, not yours. Industry audits find up to 20% of inventory carries a wrong size, weight, or category — and fee tiers are cliffs, not slopes, so a fraction of an inch is real money.

The canonical example, documented in MyAmazonGuy's fee-overcharge guide: a product measured at 9.1 inches instead of its true 8.9 lands in the next size tier at roughly $0.50 more per unit — about $3,000 a year on a single ASIN moving 500 units a month. The fix is a remeasurement case (a Cubiscan re-scan): open a case with your own evidence — the packaged unit photographed against a ruler, a scale reading — and if the re-scan confirms your numbers, Amazon corrects the measurement and the fee tier going forward, and you can request reimbursement of the recent overcharge on top.

Referral-fee classification is the same error in a different ledger: a SKU mapped to a category carrying a higher commission percentage than the one it belongs in overpays on every order. It happens at listing creation and after catalog edits, it survives because referral fees are percentage-based and invisible per-order, and it is worth checking whenever a fee looks large against the sale price. Fee-focused reviews put 2–5% of total FBA costs as recoverable from these measurement and classification errors combined — on fees you were never supposed to owe.

Fee-error math is per-unit × velocity: a $0.30 error on a 1,000-unit-a-month ASIN outweighs a $3 error on a slow one by 10x. Always sweep your highest-velocity SKUs first — it is where the same error costs the most.

What changed in Amazon's 2026 fee schedule?

The 2026 schedule's headline is the 3.5% fuel and logistics surcharge on FBA fulfillment fees in the US and Canada, effective April 17, 2026, extended to Multi-Channel Fulfillment and Buy with Prime on May 2 — about $0.17 per unit on average. January 15, 2026 also reset inbound placement rates. None of it asks permission; it just lands in your unit economics.

That is drain five: schedule drift. There is no claim to file against an announced fee — the audit action is noticing, re-running per-SKU economics, and deciding to reprice, repack, or cut. The surcharge announcement is on Amazon's seller forums; the full 2026 fee landscape is mapped in our 2026 fee overhaul survival guide, and the returns-side fees have their own defense playbook in the returns-fee margin defense guide. The pattern that matters for the sweep: fee changes in 2025–2026 arrive as percentages and surcharges rather than headline rate hikes, which is precisely the shape that slips through annual planning and shows up only in a monthly per-SKU look.

Schedule drift also compounds with the calendar: a surcharge that costs $0.17 a unit in May costs multiples of that across Q4 volume, which is why the sweep feeds directly into Q4 inventory and cash-flow planning — you cannot plan holiday cash on unit economics that are two fee changes stale.

Are Amazon reimbursement services worth it?

Reimbursement services are worth it when their 20–25% contingency fee beats the value of your own time — truest for large catalogs with long unaudited histories, and for operators who know they will never run the audit. GETIDA charges from 25% of recovered funds with a $50 minimum invoice since July 2025; Carbon6's Seller Investigators, now SPS Revenue Recovery after SPS Commerce's $210M acquisition of Carbon6 closed in February 2025, charges 25%.

The honest 2026 picture is that the contingency model is being squeezed from both ends. Amazon's automation absorbed the easiest claim class (fulfillment-center losses), and the manufacturing-cost basis cut the value of every remaining claim 50–75% — same percentage fee, smaller pie. What contingency firms still genuinely win: deep back-catalog cleanups at scale, denial-pattern knowledge from filing thousands of cases, and stubborn-case escalation. What they cannot fix: the 25% comes off the top forever, and the monitoring half of the job is a software task being billed at service rates.

Approach	Cost	Best for	Honest ceiling
DIY with this checklist	Free (about an hour a month)	Small catalogs, disciplined operators	Depends entirely on you actually doing it monthly
Contingency service (GETIDA, SPS Revenue Recovery)	20–25% of recoveries; $50 minimums	Big unaudited back catalogs; zero-effort preference	Fee scales with your losses; monitoring still billed at service rates
SellerForge (ours)	$99/month flat, all 14 modules	Ongoing monthly discipline without doing it by hand	Not a white-glove back-catalog cleanup crew; you approve and file claims

Where SellerForge fits (and where it does not)

Disclosure again: SellerForge is our product. Its Reimbursement Claims module runs drains one and two of the sweep continuously — reconciling Inventory Ledger events against reimbursement IDs and refunds against returned units, then drafting the claim with the evidence attached. Custom Breakdowns is where fee creep shows per-SKU (drains three through five), the Document Vault keeps supplier invoices filed by ASIN — which matters more now that manufacturing-cost documentation decides what a claim pays — and the Weekly Business Report surfaces the drift between sweeps. Flat $99/month for all of it; the $499/month Agency tier runs the same sweep across client accounts.

Where we are not the answer, plainly: a five-year unaudited back catalog is a contingency-service job — GETIDA or SPS Revenue Recovery will extract more from deep history than any monthly tool, and 25% of found money you had written off is a fine trade. A five-SKU account does not need software at all; run the checklist above by hand in under an hour. And if your gap is product research rather than protecting live margin, that is Jungle Scout and Helium 10 territory, compared honestly in our Amazon seller tools roundup.

Who should run what in 2026

Under $10K/month: DIY. Run the six-step sweep monthly by hand, keep supplier invoices organized per SKU, and file your own claims — at this scale the leak is real but small, and the habit is the asset.
Growing private label ($10K–$100K/month): software-assisted. The sweep needs to survive busy months, fee errors on hero ASINs get expensive, and per-SKU cost data must stay current for manufacturing-cost claims. This is the SellerForge lane, and where the margin picture should connect to the benchmarks in our FBA profit-margin guide.
Large or long-unaudited catalogs: hybrid. Bring in a contingency service for the historical cleanup, then run monthly software-based sweeps so you never need the cleanup again.
Agencies: make the sweep a deliverable. A monthly recovered-funds line item is the most self-justifying report an agency can send, and the Agency tier runs it across every client account.

One caveat on the middle bullet: the margin benchmarks live in our FBA profit-margin benchmarks by category — knowing what healthy looks like is what makes a 1–3% leak visible at all. If you want the sweep running without doing it by hand, start a free SellerForge trial and point it at your account.

About the author

David Gallo is the founder of SellerForge.AI. Before building it, he managed 57 Amazon seller accounts representing more than $350M in sales at Worldfront, where the monthly profitability audit was a standing calendar block and unclaimed reimbursements were treated as an accounts-receivable line, not found money. He writes the SellerForge blog for operators, not affiliates.

Frequently Asked Questions

Amazon reimburses you two ways. Automatically: since November 1, 2024, inventory lost in fulfillment centers, most warehouse damage, and most customer-return discrepancies are proactively reimbursed within about five business days, visible in the Reimbursements report. Manually: everything the automation misses requires a case in Seller Central with evidence, filed inside strict windows — 60 days for fulfillment-center claims, 45–105 days after the refund for customer returns, and 15–75 days from shipment creation for removals lost in transit.

Sixty days for most claims. On October 23, 2024 Amazon cut the eligibility window from 18 months to 60 days for fulfillment-center lost and damaged claims. Customer-return claims must be filed 45–105 days after the refund or replacement date, removal claims for items lost in transit 15–75 days from shipment creation, and all other removal claims within 60 days of the shipment being delivered back to you. Anything older is permanently forfeited, which is why quarterly audits now silently lose money.

Yes — since November 1, 2024, Amazon proactively reimburses FBA items reported lost in fulfillment centers, triggered on the date the loss is identified and processed within about five business days, no claim required. Most warehouse-damage and customer-return cases are also auto-covered. But the automation is not complete: removal claims are always manual, and any loss the system fails to flag still requires you to find it in the Inventory Ledger and file within 60 days. Auto-reimbursement shrank the job; it did not end it.

Since March 10, 2025, Amazon reimburses based on your product's manufacturing cost — what you paid to source it — not its selling price, and the calculation excludes shipping, handling, and customs duties. You can supply your own cost figure (with supplier invoices to back it) or accept Amazon's estimate, which is frequently low. Sellers report per-claim recoveries dropping 50–75% versus the old sale-price basis, which makes accurate cost data on every SKU the highest-leverage reimbursement input you control.

Sometimes. Contingency services like GETIDA (from 25% of recovered funds, with a $50 minimum invoice since July 2025) and SPS Revenue Recovery, formerly Carbon6's Seller Investigators, are worth it for large catalogs with years of unaudited history and for operators who will honestly never run the audit themselves. They are a weak buy for disciplined sellers: the March 2025 manufacturing-cost basis cut per-claim value 50–75%, auto-reimbursement absorbed the easiest claim class, and a monthly one-hour sweep or flat-rate software keeps 100% of what it recovers.

Compare Amazon's stored dimensions and weight for each SKU against your own measurements — fulfillment fees are computed from Amazon's numbers, not yours, and industry audits find up to 20% of inventory carries a wrong size, weight, or category. A discrepancy of a fraction of an inch can bump a SKU into the next size tier. If you find one, open a case requesting remeasurement (a Cubiscan re-scan); when Amazon confirms the error it corrects the fee going forward, and you can request reimbursement of recent overcharges.

A Cubiscan request is a Seller Central case asking Amazon to re-measure a product's dimensions and weight on the warehouse scanning equipment that set them. Sellers file it when Amazon's stored measurements — and therefore the fulfillment fee tier — do not match the product's real size. If the re-scan confirms your numbers, Amazon updates the measurements and corrects the fee. Bundle your own evidence into the case: photos of the packaged unit against a ruler and a scale reading speed the decision.

Industry audits consistently place unclaimed FBA reimbursements at 1–3% of annual revenue, and fee-focused reviews find 2–5% of FBA costs recoverable from measurement and classification errors. The mechanics compound quietly: one documented example shows a 0.2-inch measurement error adding $0.50 per unit, roughly $3,000 a year on one ASIN at 500 units a month. On a $500,000 account, the combined leak is $5,000–$15,000 a year — invisible on any single order, material on the P&L.

David Gallo·Founder, SellerForge

Amazon seller with 12+ years managing private label brands across 57 accounts and $350M+ in sales managed.

Share this article