Amazon FBA Reimbursement 2026: The 60-Day Rule, Manufacturing Cost Payouts, and What You’re Still Owed

Amazon FBA reimbursement 2026 — 60-day claim window manufacturing cost monthly audit — DAM Law Firm

Amazon FBA reimbursements — the money Amazon owes you for inventory it lost, damaged, or mishandled while in its custody — have always been underclaimed by most sellers, but two policy changes that took effect in 2025 and carried into 2026 have made the problem dramatically worse: reimbursements are now calculated at your manufacturing or sourcing cost rather than the retail selling price, cutting average recovery amounts by 50 to 75 percent, and most claim windows have been compressed to approximately 60 days from the discrepancy surfacing, which means sellers who run quarterly audits are forfeiting every reimbursement opportunity from the first two months of each quarter by design.

The combination of lower per-unit payouts and shorter filing windows means sellers who were leaving money on the table before are now leaving significantly more — while those who have adapted their audit rhythm and cost data practices are recovering amounts the majority of the market is not.

This guide covers exactly what changed, what it is costing sellers who have not adjusted, and the specific monthly audit process that recovers what is owed.

Legal escalation options are also covered for when Amazon disputes claims or declines reimbursements that the policy clearly supports.

Why most sellers are leaving more money on the table now than before

The two changes compound each other. Lower per-unit payouts from cost-based reimbursement mean each unclaimed event costs more than it did. Shorter claim windows mean more events fall outside the filing deadline before sellers notice them. This guide covers both changes, the monthly audit that fixes them, and the legal escalation path when Amazon disputes valid claims.

The two 2026 changes every FBA seller must understand: Since March 2025, Amazon reimburses lost and damaged FBA inventory at manufacturing or sourcing cost — not the retail selling price. Sellers report recovery amounts dropping 50 to 75 percent on average. If your per-unit cost fields in Seller Central are missing or set to zero, Amazon substitutes its own internal estimate, which is almost always lower than your actual cost. Most reimbursement claims must now be filed within approximately 60 days of the discrepancy surfacing — down from 18 months under prior policy. Quarterly audit habits forfeit two months of claims every quarter.

Table of Contents

  1. The Two Policy Changes Cutting FBA Reimbursement Recovery in 2026
  2. The Manufacturing Cost Reimbursement: What It Means and How to Maximize It
  3. The 60-Day Claim Window: Why Quarterly Audits No Longer Work
  4. What Amazon Owes You: The Five Reimbursement Categories
  5. The Automation False Comfort: What Auto-Reimbursement Misses
  6. The Monthly Audit Routine That Recovers What Automation Misses
  7. How to File a Reimbursement Claim That Gets Approved
  8. When Amazon Disputes or Denies a Valid Claim
  9. Why Q4 Is the Highest-Stakes Period for Reimbursement Tracking
  10. Frequently Asked Questions
  11. How DAM Law Firm Can Help

The Two Policy Changes Cutting FBA Reimbursement Recovery in 2026

As Leviathan Sellers’ 2026 reimbursement policy tracker documents, since March 2025, Amazon reimburses lost and damaged FBA inventory at manufacturing or sourcing cost — not the selling price — with sellers’ recoveries dropping 50 to 75 percent on average. If per-unit cost fields in Seller Central are missing or zero, Amazon substitutes its own lower internal estimate. These two changes — the shift to cost-based reimbursement and the compressed claim windows — operate independently but compound each other. A seller who has not entered accurate cost data is being reimbursed at a fraction of what they are owed per unit — and one who runs quarterly audits is forfeiting two months of claims every quarter. Both problems together mean losing in both directions simultaneously.

Why most sellers have not adjusted yet

Amazon now auto-reimburses many lost and damaged inventory cases without a claim — which is genuinely useful, and also the most dangerous development in the policy, because it convinces sellers the problem is solved. Automation handles the clean, single-event cases: a unit scanned lost in a fulfillment center, an obvious warehouse damage event. The result is that sellers see reimbursements arriving automatically and conclude that Amazon is handling the issue. What they do not see are the categories of loss that automation consistently misses — inbound receiving shortfalls, returns that never re-enter sellable inventory, fee overcharges — which require manual identification and manual claims and which are subject to the 60-day window regardless of whether automation has created any appearance of coverage.


The Manufacturing Cost Reimbursement: What It Means and How to Maximize It

The shift from retail-price reimbursement to cost-based reimbursement is the single most significant policy change in FBA reimbursement history for most sellers, because it restructures the economic relationship between what Amazon owes and what sellers actually recover. Understanding exactly how the calculation works — and where sellers can maximize recovery within the policy’s framework — determines whether the 50 to 75 percent average recovery drop applies to a specific account or whether that seller recovers closer to full entitlement.

How Amazon calculates the reimbursement amount

Amazon calculates every reimbursement using the per-unit cost entered in Seller Central for the ASIN at the time of the event. Accurate cost data means reimbursement at that cost — a zero, blank, or outdated figure means Amazon substitutes its own internal estimate, which is consistently lower than the seller’s actual cost and which sellers have no visibility into or recourse against once applied. The practical implication is that every ASIN in a seller’s FBA catalog needs an accurate, invoice-backed cost figure entered in Seller Central before a reimbursable event occurs, not after. After the event, the cost figure that was in the system at the time of the event governs the reimbursement calculation.

What “manufacturing or sourcing cost” means in practice

Sellers who manufacture their own products calculate the manufacturing cost as the landed cost per unit — materials, labor, packaging, and inbound shipping divided by units produced. For resellers and private label sellers sourcing from manufacturers or distributors, the sourcing cost is the per-unit invoice price including allocated inbound freight. Amazon does not reimburse the retail margin — it reimburses the cost of replacing the unit in the seller’s inventory, not the revenue the unit would have generated. A seller with a $12 cost basis and a $45 retail price who loses 100 units to warehouse damage is entitled to $1,200 in reimbursement under the current policy — not $4,500. The gap between what is owed and what the seller would have earned from those units represents the policy’s structural shift.

How to enter and maintain cost data in Seller Central

Cost data is entered through Seller Central under Inventory, then Manage Inventory, then the Cost column — or through a bulk upload using the inventory file template. The field is labeled “Cost of Good” or “Cost” depending on the interface. Every active FBA ASIN should have an accurate cost figure in this field. New ASINs should have cost data entered before the first shipment arrives at the fulfillment center. Existing ASINs without cost data should be updated as a priority — the update takes effect prospectively, meaning reimbursements calculated after the update use the new figure. The update does not retroactively change reimbursements already issued at the lower estimate.


The 60-Day Claim Window: Why Quarterly Audits No Longer Work

Most reimbursement claims must be filed within roughly 60 days of the discrepancy surfacing — down from the old 18-month lookback. Annual and quarterly audit habits forfeit money by design now; monthly is the minimum viable rhythm. The 60-day window applies differently to different claim types, and understanding the specific window for each type determines the audit frequency required to capture each category of reimbursement.

The specific windows by claim type

Warehouse lost and damaged claims — units lost or damaged inside Amazon’s fulfillment centers — must be filed within 60 days of the event appearing in inventory reports. FBA customer return claims — refunds issued to buyers for items that were never returned to sellable inventory — must be submitted between 45 and 105 days after the refund was issued. Removal claims for inventory lost or damaged during the removal process must be filed within 15 to 75 days for lost-in-transit cases, and within 60 days for other removal-related claims. Fee overcharge claims — billing for incorrect dimensional weight, wrong product tier, or misapplied surcharges — operate under separate dispute timelines that vary by fee type. The practical effect of these windows is that no single quarterly audit can capture all claim types within their respective windows for the full quarter.

The monthly cadence that keeps every window open

A monthly audit run within the first week of each month covers the prior month’s inventory events before the 60-day windows close. The audit pulls four reports from Seller Central: the FBA Inventory Adjustments report, the FBA Returns report, the FBA Removal Order Detail report, and the FBA Fee Preview report. Each report surfaces a different category of reimbursement opportunity. Running all four monthly — and cross-referencing the adjustments report against the returns report to identify returns that closed without a reimbursement — captures what automation misses while keeping claims inside their filing windows.


What Amazon Owes You: The Five Reimbursement Categories

Amazon’s reimbursement obligation covers five distinct categories of inventory events. Each has different reporting sources, different claim processes, and different automation coverage levels.

Category 1: Lost in fulfillment center

Units that are scanned into a fulfillment center but subsequently cannot be located are “lost in FC” events. These appear in the inventory adjustments report under specific adjustment codes — the M code indicates missing or lost inventory. Amazon’s auto-reimbursement system catches a significant portion of clear FC-lost events, but inbound receiving shortfalls — where the unit count checked in by Amazon is less than the unit count on the seller’s shipping plan — are frequently missed by automation and require manual claim submission with the original shipping plan as supporting documentation.

Category 2: Damaged in fulfillment center or during shipment

Units that are damaged while in Amazon’s custody — either in the fulfillment center before shipment or during last-mile delivery — are reimbursable when the damage occurred under Amazon’s handling. Adjustment codes E1 and E3 in the inventory adjustments report indicate damage events. As SentryKit’s reimbursement audit guide confirms, look for negative adjustment codes — specifically E1 (damaged), E3 (damaged at fulfillment center), E7 (removed by customer), and M (missing or lost) — without a corresponding reimbursement entry in the transaction view. Every negative adjustment code without a matching reimbursement is a potential open claim.

Category 3: Customer return not restocked

The FBA Returns Report shows what customers returned. Comparing this against inventory received-back numbers identifies a return processed by Amazon that never arrived back in inventory — a potential reimbursement case. This category is among the most systematically underclaimed in FBA reimbursement audits. Refunds are issued to buyers automatically, and the assumption is that the returned unit will reappear in sellable inventory within a few weeks. When the unit does not appear — because it was lost during the return process, was received damaged and disposed of without reimbursement, or was never sent back by the customer but the refund was issued anyway — the seller has both issued a refund and lost the unit without compensation.

Category 4: Removal order loss and damage

When sellers initiate removal orders — requesting that Amazon return inventory to a specified address — units can be lost in transit during the removal process or arrive at the seller’s location in damaged condition. Amazon now credits both the product value and the removal fee when units are damaged during the removal process. Removal loss claims require the removal order ID, the expected unit count, and documentation of the discrepancy between expected and received units. Sellers who do not inspect and count incoming removal shipments promptly — and who do not file within the 15 to 75 day window — forfeit these claims by default.

Category 5: Fee overcharges

Amazon’s fee calculations use the product’s dimensions and weight as declared in Seller Central and verified by Amazon’s own measurement. When Amazon’s system applies fees based on incorrect dimensions — billing a product at a larger tier than it actually occupies — the overcharged fees are recoverable through the fee dispute process. The FBA Fee Preview and Transaction View let sellers audit fee charges by pulling the fee preview for their ASINs and comparing against standard rates for their declared dimensions and weight. Fee overcharges accumulate silently over time and can represent significant aggregate amounts for sellers with high unit volumes, particularly for products near tier boundaries where a dimension error shifts the unit into a higher fee bracket.


The Automation False Comfort: What Auto-Reimbursement Misses

Amazon’s automated reimbursement system is genuinely useful — it handles a meaningful volume of clear, single-event reimbursement cases without requiring sellers to file manual claims. It is also the source of the most common reimbursement audit mistake in 2026: assuming that automatic reimbursements appearing in the transaction view mean the reimbursement process is complete.

What automation reliably handles

Automation reliably handles clear warehouse damage events where a unit is scanned damaged at a specific fulfillment center and the system logs the damage event, generates the reimbursement, and closes the case within days — along with straightforward lost inventory cases where a unit simply disappears from the inventory count without explanation. These are the cases that appear in the transaction view with a “FBA inventory reimbursement” label — clean, closed, automatic.

What automation consistently misses

What automation does not reliably catch includes inbound receiving shortfalls — where you shipped 500 units and Amazon checked in 480 with no flag on the 20 — and returns that never return, where a refund was issued but the unit never re-entered sellable inventory and was never marked lost. Fee overcharges are entirely outside the automated reimbursement system — no fee dispute is ever initiated automatically. Removal order discrepancies require the seller to identify the gap between expected and received units before any claim can be filed. The categories that require human identification are also the categories with the most compressed filing windows — which is why the combination of automation reliance and quarterly audit habits produces the systematic under-recovery that characterizes most FBA sellers’ reimbursement track records.


The Monthly Audit Routine That Recovers What Automation Misses

The monthly audit is a four-report pull that takes approximately two hours per month for most catalog sizes — recovering amounts that scale directly with FBA volume, with each report informing the next.

Report 1: FBA Inventory Adjustments

Download the FBA Inventory Adjustments report from Seller Central under Reports, then Fulfillment, then Inventory Adjustments. Filter for negative adjustments in the prior 30 to 60 days. Identify every row with adjustment codes E1, E3, E7, or M. For each negative adjustment, cross-reference against the transaction view to confirm whether a corresponding reimbursement was issued. Every negative adjustment without a matching reimbursement is a potential open claim. Document each gap with the ASIN, the adjustment date, the quantity, and the adjustment code — this documentation is the core of the claim submission.

Report 2: FBA Returns

Download the FBA Returns report for the prior 60 days. Cross-reference each return against the inventory received-back column. Any return where the customer received a refund but the unit quantity is not reflected in current sellable inventory — and where no reimbursement appears in the transaction view for that unit — is a candidate for a returns-not-restocked claim. Pay particular attention to high-value ASINs where the per-unit cost is significant and where the number of open return-not-restocked gaps compounds rapidly.

Report 3: Removal Order Detail

For any removal orders completed in the prior 60 days, download the FBA Removal Order Detail report and compare the expected quantity against the received quantity at the destination address. Any shortfall — units that appear on the removal order but did not arrive — and any damage noted at the receiving location are claimable within the applicable window. File removal claims promptly: the 15-day window for lost-in-transit cases is the tightest deadline in the entire reimbursement system.

Report 4: FBA Fee Preview

Download the FBA Fee Preview report and compare the fee applied to each ASIN against the fee schedule for the declared product tier. Any ASIN where the applied fee is higher than the published rate for its declared dimensions and weight is a fee overcharge candidate. Cross-reference against the actual product dimensions if available — a product that has been reclassified into a larger dimensional tier without a physical measurement update is a common source of systematic fee overcharges across all units of that ASIN.


How to File a Reimbursement Claim That Gets Approved

Amazon’s reimbursement claim review process has tightened alongside the policy changes. Claims that were approved with minimal documentation under prior policy now require specific evidence to pass review, and claims submitted without that evidence are denied without opportunity to resubmit within the same window.

What a strong claim submission includes

Every claim submission should include: the specific ASIN and unit count claimed; the specific date of the discrepancy event; the specific adjustment code or return transaction identifier; the per-unit cost figure from the supplier invoice for that ASIN; a screenshot or export of the relevant report row showing the negative adjustment or return gap; and a brief explanation of the discrepancy in plain language. Vague submissions — “some inventory is missing” — are denied. Claims that identify a specific unit count, a specific date, a specific event code, and a specific cost basis are approved at materially higher rates.

The supplier invoice as cost documentation

When Amazon’s system has the correct cost figure in Seller Central and a reimbursable event occurs, the reimbursement is calculated automatically at that cost — but when the cost figure is missing or incorrect, the claim submission should include the supplier invoice for the relevant ASIN showing the per-unit cost paid. The invoice establishes the cost basis independently of what Seller Central shows — which is the documentation path for sellers whose Seller Central cost data was not updated before the reimbursable event occurred. Including the invoice with the claim submission and requesting that Amazon apply the invoice cost rather than the Seller Central estimate is the specific documentation argument that recovers the difference between the two figures.


When Amazon Disputes or Denies a Valid Claim

Amazon’s claim review process produces denials for two reasons: missing documentation, and genuine disputes about whether the reimbursement obligation exists. The correct response differs for each.

Denied for missing documentation: resubmit with evidence

When a claim is denied because the submission lacked specific evidence — the adjustment code was not cited, the invoice was not attached, the return gap was not documented with a specific transaction ID — the denial is fixable by resubmitting with the complete documentation package. Resubmission must still occur within the original claim window, not a new window opened by the denial. A denial does not restart the clock. Sellers who receive a denial and take two weeks to gather documentation may find that the filing window has closed before they resubmit, converting a fixable denial into a permanent loss.

Disputed on the merits: escalation options

When Amazon disputes a claim on the merits — asserting that the inventory event does not qualify as a reimbursable loss, that the unit was not lost under Amazon’s custody, or that the reimbursement was already issued — the escalation path runs through Seller Central case escalation first.

Opening a case with the full documentation package and explicitly referencing the specific FBA reimbursement policy provision that supports the claim is the first escalation step. When Seller Central case escalation does not produce resolution, and when the disputed amount is material, legal escalation through a pre-arbitration demand letter to Amazon’s legal counsel asserting the specific contractual basis for the reimbursement obligation — the FBA Service Terms, which create Amazon’s custodial responsibility for inventory — is the mechanism that produces outcomes the Seller Central process cannot. Our pre-arbitration demand letter guide covers the complete escalation framework, and our Amazon withheld funds team handles FBA reimbursement disputes where the amounts justify legal escalation.


Why Q4 Is the Highest-Stakes Period for Reimbursement Tracking

Q4 produces more FBA inventory events — more units received, more units shipped, more returns processed — than any other quarter. More volume means more opportunities for the loss, damage, and discrepancy events that generate reimbursement claims, and it also means more opportunities for those claims to fall outside the 60-day window if the audit rhythm is not maintained through the peak season.

The return surge and the returns-not-restocked gap

Q4 generates a return surge in January that is the highest return volume of the year for most consumer product categories. Every returned unit that is processed by Amazon in January creates a 45 to 105 day returns-not-restocked claim window that opens in January and closes between February and April. Sellers who do not audit January returns promptly — amid the operational pressures of the post-holiday period — forfeit the most valuable reimbursement category from the most profitable selling quarter. Running the returns audit as a specific January priority, separate from the standard monthly audit, is the operational habit that captures this category before the window closes.

FBA cost data before peak inbound shipments

Q4 inbound shipments represent the highest per-unit replacement cost of the year for most sellers — units purchased specifically for peak season at costs reflecting peak demand from suppliers. Sellers whose Seller Central cost data was not updated before Q4 inbound shipments arrived will be reimbursed at their older, lower cost figures for any units lost or damaged during the peak period. Updating cost data for every ASIN in the Q4 inbound shipment plan before the first shipment arrives at the fulfillment center is the specific step that ensures peak-cost units are reimbursed at their actual replacement cost.


Frequently Asked Questions

How do I know how much Amazon currently owes me in unclaimed reimbursements?

There is no single report in Seller Central that shows total unclaimed reimbursements — the figure requires running the four-report audit described above and identifying the gaps. Third-party reimbursement tools can automate the cross-referencing process and surface an estimated unclaimed amount, though their estimates vary in accuracy depending on how they handle the 60-day window logic. The most reliable method is the manual monthly audit combined with a one-time historical audit covering the prior 60 days across all four report types to identify any open claims from the current window that have not yet been filed.

Can I use a third-party reimbursement service to file claims on my behalf?

Yes, though Amazon’s terms of service restrict third-party reimbursement services to filing claims through Seller Central — not through automated API calls or bulk submission methods that Amazon has restricted. Services that use compliant submission methods are permissible. Sellers evaluating third-party services should confirm that the service’s submission method is compliant with Amazon’s current seller tools policy, that the service’s fee structure makes economic sense given the reduced per-unit recovery amounts under the new cost-based reimbursement policy, and that the service maintains claim documentation in a format that supports legal escalation if Amazon disputes a claim the service filed.

Amazon reimbursed me less than my actual cost. What are my options?

When a reimbursement has been issued at an amount lower than the seller’s documented cost — because Seller Central showed an incorrect cost figure at the time of the event — the first step is to submit a Seller Central case requesting a reimbursement adjustment, attaching the supplier invoice as evidence of the correct cost. A denied case then calls for legal escalation through a formal dispute citing the FBA Service Terms and the documented cost discrepancy is the next step. The FBA Service Terms create Amazon’s obligation to reimburse at the seller’s cost — not at Amazon’s internal estimate — and a claim that documents the discrepancy between Amazon’s estimate and the seller’s invoice-backed cost has a specific contractual basis for the adjustment request.

My account is suspended. Can I still file reimbursement claims?

Reimbursement claims can be filed through Seller Central even when an account is under review or suspended, though Amazon’s processing of those claims may be delayed until the account review is resolved. The 60-day filing window runs regardless of account status — a suspension does not pause the clock. Sellers whose accounts are suspended during Q4 and who have significant FBA inventory should prioritize filing any open reimbursement claims immediately, both to preserve the claims within the window and to document the full scope of what Amazon holds on the seller’s behalf as context for fund recovery discussions. See our Amazon withheld funds guide for the complete fund recovery framework when account suspension intersects with FBA reimbursement claims.


How DAM Law Firm Can Help

DAM Law Firm handles FBA reimbursement disputes where Seller Central case escalation has not produced resolution — specifically disputed claims where the contractual basis for reimbursement is clear and the amount justifies legal escalation, and fund recovery situations where suspended accounts have significant unreimbursed inventory events alongside withheld disbursements.

FBA reimbursement dispute escalation

When Amazon disputes or denies a valid reimbursement claim after Seller Central escalation, our Amazon withheld funds team pursues recovery through pre-arbitration demand letters asserting the specific FBA Service Terms provision that creates Amazon’s reimbursement obligation, documenting the discrepancy between the reimbursement issued and the amount owed, and demanding specific relief within a defined timeline. FBA reimbursement disputes that involve material amounts — typically $5,000 or above — have a clear legal basis in Amazon’s own service terms and are exactly the dispute category that pre-arbitration demand letters are designed to resolve without formal arbitration.

Fund recovery for suspended accounts with FBA inventory

When an account suspension freezes disbursements while FBA inventory continues to generate sales — and while open reimbursement claims exist on units lost or damaged before the suspension — our team pursues both the reinstatement appeal and the fund recovery simultaneously. The reimbursement claims are preserved and filed within their windows regardless of the suspension status, and the fund recovery demand includes the reimbursement amounts as part of the total Amazon obligation calculation. Our arbitration against Amazon team handles cases where the combined withheld funds and disputed reimbursements justify formal AAA arbitration. Contact our team for a same-day assessment of your FBA reimbursement dispute.

Related DAM Law Firm services:


This article is for general informational purposes only and does not constitute legal advice. Amazon’s FBA reimbursement policies are subject to change. Contact DAM Law Firm for legal advice tailored to your situation.


Related articles from DAM Law Firm

    Leave a Reply

    More Blog Posts

    Amazon FBA Reimbursement 2026: The 60-Day Rule, Manufacturing Cost Payouts, and What You’re Still Owed

    Amazon FBA reimbursements — the money Amazon owes you for inventory it lost, damaged, or

    Amazon FBM Automated Transit Times April 2027: What the Change Means and How to Use It in Enforcement Appeals

    Amazon has announced that by April 2027, all parcel shipping templates for Fulfilled by Merchant

    Vorys Letter on Amazon: The Warranty Trap, Your Defenses, and the 72-Hour Response Framework

    A Vorys letter is not a lawsuit, it is not a court order, and it

    Discover more from DAM Law Firm

    Subscribe now to keep reading and get access to the full archive.

    Continue reading