A seller's path through FBA fee overcharge refund

TL;DRAn FBA fee overcharge refund is the recovery of fulfillment fees that Amazon charged incorrectly – most often because the product's dimensions or weight were recorded wrong in the catalog, causing every shipment to be rated at a higher fee tier than the item actually warranted. On Amazon US, the path to recovery runs through a formal measurement dispute, a re-measurement request, and a structured reimbursement claim. The money does not flow back automatically. A seller must identify the overcharge, document it, and press the claim through the right channel before the lookback window closes.

The following case study walks through how one seller found the problem, what was really happening in the account, the strategy we used to recover the overcharged fees, and what other Amazon US sellers can take from the experience. Identifying details have been changed to protect confidentiality.

What actually happens when Amazon overcharges FBA fees

FBA fees on Amazon US are calculated from the dimensions and weight Amazon holds on file for each ASIN – not from what the seller ships. When those recorded measurements are wrong, every unit fulfilled draws a fee based on a phantom product that does not exist.

In the matters we handle, the overcharge usually traces to one of three causes. First, the original product setup used an imprecise package size. Second, a catalog merge or variation-listing update overwrote the measurements silently. Third, Amazon's own measurement scan, done when inventory first arrives at a fulfillment center, returned a bad reading – and no one caught it.

Each of those root causes leads to the same downstream problem: the seller's fee reports show one charge per unit, the seller's own box tape and scale show a different weight or size, and the gap compounds across thousands of shipments. Over a full selling season the total overcharge can reach a figure that matters seriously to cash flow.

What makes this genuinely difficult is that the overcharge is invisible in ordinary Seller Central reporting. The fee appears on the disbursement as a standard fulfillment fee. A seller has to pull the FBA fee preview report, cross-reference it against physically verified dimensions, and then run the calculation manually before the discrepancy becomes visible. Most sellers never do that reconciliation. The overcharge simply drains the account, quietly, month after month.

The situation: what the seller came to us with

A sporting goods seller on Amazon US – mid-range FBA volume, a catalog of roughly two dozen active ASINs – came to us in the summer of 2025 after noticing that net margins had drifted significantly below what the pricing model predicted. The account was active and in good standing. There was no deactivation and no disbursement hold at the outset. The immediate problem was that cash generation from the account had become inconsistent, and neither the seller nor their bookkeeper could reconcile the difference.

The seller had already tried two things before contacting Tutamen. They had filed a reimbursement case through Seller Central for one ASIN they suspected was overcharged. Amazon closed it without reimbursement, citing insufficient documentation. They had also called Seller Central support, which produced a ticket, a wait, and then a form denial that referenced the standard fee schedule without engaging with the specific measurement discrepancy the seller had described.

That sequence – informal case, closure, phone call, form denial – is the most common pattern we see before a matter reaches us. The seller is not wrong about the overcharge. But the path through Seller Central's standard support tiers is designed for simple queries, not for a multi-ASIN measurement dispute that requires cross-referencing fee reports against physical verification data.

What was really going on in the account

When we reviewed the account, the fee overcharge problem was real and larger than the seller realized. Three ASINs – not one – showed measurement records in the Amazon catalog that differed materially from the seller's manufacturer specifications and from independent remeasurement data the seller had obtained from a third-party logistics provider.

The core issue was that two of the three ASINs had been affected by a catalog update the previous year. A listing edit – intended only to update a product image – had triggered a backend recalculation that pulled measurements from a related parent ASIN with different dimensions. From that point forward, fulfillment fees for those two ASINs were charged at a higher tier. The third ASIN had a different problem: Amazon's own measurement scan at the fulfillment center had recorded the product in its unpackaged state rather than the retail-ready packaged configuration, understating weight and overstating a single dimension in a combination that pushed the item into a larger fee bracket.

This matters for strategy because the two catalog-corruption ASINs and the fulfillment-center scan ASIN each require a different evidentiary approach. A single generic reimbursement case filed for all three simultaneously – which is what most sellers do – will draw a generic denial because Amazon's case-management system cannot distinguish between root causes when they are bundled.

We also identified a timing issue. Amazon's lookback window for FBA reimbursement claims is not unlimited. For overcharges tied to fee events that had occurred earliest, the window was approaching. Acting promptly was not a preference; it was a structural constraint.

The strategy: separating the claims and building the evidence

Our approach was to treat each ASIN as a separate evidentiary case rather than one consolidated claim. For the catalog-update ASINs, the strategy was to document the timeline of the listing edit, pull the fee preview reports for the period before and after the update, obtain the manufacturer's specification sheet and box measurements, and request a formal re-measurement through the FBA reimbursement process. The manufacturer specs served as the baseline; the fee reports showed the fee-bracket migration; the timeline of the listing edit established causation.

For the fulfillment-center scan ASIN, the approach was different. We used the seller's own physical measurement and weight documentation – taken from sealed retail units from the same production run – and submitted those alongside a request for Amazon to re-scan the ASIN. Because Amazon operates its own measurement process at inbound, the argument here was not "your catalog is wrong" but "your scan produced an anomalous result that diverges from every other measurement source."

Separately, we mapped every held balance and reserve in the account and confirmed that no disbursement hold was pending – an important check because a reserve policy can interact with a reimbursement credit in ways that effectively defer the cash benefit. On this account, the disbursement status was clean, which simplified the recovery calculation.

The seller also needed to understand the realistic range of outcomes. Not every overcharge period is recoverable. If Amazon's own measurement records for a period match Amazon's fee schedule, the overcharge argument depends on proving the measurement itself is wrong, which requires physical evidence. For periods where the seller had limited documentation, we advised against pressing the claim – a weak filing on an undocumented period risks contaminating a well-documented claim on the recoverable period.

For a broader view of how measurement-driven overcharges originate and what sellers can do to identify them earlier, the dedicated briefing on why weight and dimension fee overcharge happens and how sellers respond covers the mechanics in detail.

The outcome and what changed in the account

Over the following weeks, Amazon accepted the re-measurement requests for all three ASINs. The corrected dimensions and weights produced revised fee calculations. Amazon issued reimbursement credits for overcharges on the two catalog-update ASINs across the recoverable lookback period. The fulfillment-center scan ASIN also drew a credit after the re-scan confirmed the seller's physical measurements. Going forward, the corrected measurements reduced the per-unit fee on those ASINs to the appropriate tier.

We do not describe outcomes in terms of specific dollar amounts. What we can say is that the total credit – for the recoverable lookback period across three ASINs – was commercially significant relative to the seller's monthly operating costs. The forward-looking fee correction, compounded over a full year's fulfillment volume, was in many respects more valuable than the backward-looking recovery.

The seller's bookkeeper was able to reconcile the account properly for the first time in over a year. The disbursement cycle normalized. Inventory purchasing decisions could be made on accurate margin data rather than the inflated fee assumptions that had been distorting the model.

One point worth noting: the first reimbursement case the seller filed independently, and which Amazon closed with a form denial, was filed for one of the three affected ASINs. That denial did not foreclose the claim. A prior denial based on insufficient documentation can be reopened with properly structured evidence. Sellers who have already received one rejection should not treat that as the end of the road. If anything, it often clarifies exactly what documentation Amazon's system requires.

For context on how removal orders and inventory discrepancies interact with fee recovery claims – a related issue that arises in many FBA accounts – see the analysis of why removal order discrepancies happen and how sellers respond.

The lesson: what other Amazon US sellers can take from this

The myth that matters most here is the one we hear most often: that once funds have been incorrectly charged or held, they are simply gone. That is not accurate. Overcharged fees are recoverable within the applicable lookback period, provided the claim is structured correctly and supported by the right documentation. The money is not gone – it is sitting in an unresolved claim state, waiting for someone to file the right case.

The harder truth is that FBA fee overcharges are almost never caught by Amazon's own systems in real time. Amazon's fee architecture is designed to apply the fee that its catalog records support. If those records are wrong, the fee will be wrong indefinitely, and Amazon will not correct it without a formal claim. The seller has to find it, document it, and file it.

The decision points that this matter illustrates are worth making explicit.

First: is the problem in the catalog records, the fulfillment-center scan, or both? The answer determines the evidence you need and the channel you file through. A single approach for all affected ASINs usually fails.

Second: what is the recoverable period? Amazon's lookback window is a hard constraint, not a guideline. Filing within it is not optional. If you are uncertain whether a discrepancy exists in your account, that uncertainty is itself a reason to check now rather than later.

Third: is there a disbursement hold or reserve issue running concurrently? Fee overcharge recovery and disbursement holds are separate mechanisms, but they interact. A reimbursement credit that posts to a frozen disbursement balance does not reach the seller's bank account. Both issues need to be resolved in sequence, and understanding which comes first matters.

Fourth: has Amazon already denied a prior claim? If so, that denial is not necessarily final. The question is whether the denial was substantive (Amazon reviewed the measurement evidence and disagreed) or procedural (the case was closed for documentation reasons). Procedural denials are routinely reopened with better-structured filings. Substantive denials require a different strategy – sometimes a re-measurement request, sometimes an escalation path.

If you are working through a frozen-funds or disbursement problem that involves a broader account hold, the complete guide on frozen-funds recovery for Amazon sellers maps the full range of mechanisms and claim types.

What this seller's experience demonstrates, above all, is that FBA fee overcharge recovery is a structured, documentable process. It is not a negotiation or a goodwill gesture from Amazon. It is a formal reimbursement mechanism that responds to properly filed, properly evidenced claims – and it is routinely available to sellers who take the time to build the right case.

If the fee reports in your account do not reconcile with your own measurement data, that gap is worth investigating. The cost of not investigating is the overcharge continuing to compound.

Related areas

• Frozen Funds & Recovery – recovering held balances, reserves, and FBA reimbursements on Amazon
• IP & Brand Registry – responding to rights-owner complaints and protecting your listings

If a first claim or case has already come back rejected, a second look can identify exactly why it failed and whether a properly structured refiling is still viable. Email info@tutamenlaw.com to describe your situation.

Frequently asked questions

How long does resolving FBA fee overcharge refund usually take on Amazon US?

Resolution timelines vary considerably depending on the number of ASINs affected, the root cause of the overcharge, and whether Amazon requires a physical re-measurement. In matters we handle, straightforward single-ASIN claims with clean documentation can close in a matter of weeks. Multi-ASIN matters, or cases where Amazon's measurement scan needs to be redone, typically run longer – often across several review cycles before credits post. The most important timing constraint is not the resolution timeline but the lookback window for recoverable overcharges, which closes regardless of how long the claim takes to resolve. Acting before that window narrows is the priority.

What are the main risks if I handle FBA fee overcharge refund alone?

The most common risk is filing a bundled claim that mixes ASINs with different root causes, which produces a generic denial that closes the case without engaging the actual measurement evidence. A second risk is filing within the lookback window but with insufficient documentation – Amazon's system closes undocumented cases, and those closures can be harder to reopen than a case that was never filed. A third risk is missing the lookback window entirely while waiting for Amazon support to respond to informal inquiries. In the matters we handle, sellers who come to us after a prior denial have often lost the recoverable period for at least some of the overcharged shipments.

Do I need a lawyer for FBA fee overcharge refund?

Not every FBA fee overcharge requires legal representation. A single-ASIN discrepancy with clear physical measurement documentation and a short overcharge period is something a seller can sometimes resolve through Seller Central's reimbursement case system directly. Legal representation becomes more important when multiple ASINs are involved, when a prior claim has been denied and the documentation strategy needs to be rebuilt, when the overcharge period is long and the total amount is material, or when the overcharge is running alongside a disbursement hold or account-health issue that complicates the recovery path. An attorney-led review at the outset also preserves the strongest version of the claim from the first filing rather than correcting course after a denial.

About Tutamen

Tutamen is an independent law firm for online marketplace sellers. We represent Amazon, Walmart, Etsy and eBay sellers in account deactivations, frozen-funds recovery, intellectual-property disputes, arbitration and Notices of Dispute, and US federal Schedule A defense, plus EU marketplace regulation. Our work is attorney-led and confidential, with fees quoted up front. We act for founders, brand owners and in-house teams who need a specialist for a marketplace dispute. Work on FBA reimbursement and fee overcharge matters is conducted under legal privilege, and every engagement begins with a short review before any fee is agreed. To discuss your situation, email info@tutamenlaw.com.

Byline: Claire Donnelly – arbitration & disputes analyst, Tutamen

Disclaimer: This article is general information, not legal advice, and does not create an attorney-client relationship. Marketplace policies and the law change, and every account and case is different. For advice on your situation, contact Tutamen at info@tutamenlaw.com.

Page authored by Claire Donnelly, Arbitration & Disputes Analyst, Tutamen.