Responding to FBA fee overcharge refund the right way

When Amazon's automated fee system miscalculates a fulfillment charge, the overcharge does not announce itself. It sits quietly inside a Seller Central payment report while inventory bills, advertising invoices, and disbursement expectations move forward on the assumption that the account's numbers are correct. For a mid-market FBA seller running tight margins, the accumulated gap between what was charged and what should have been charged can reach a meaningful sum before anyone flags it. That is the real cost of a fee overcharge: not just the misbilling, but the delayed recovery and the cash-flow pressure that builds while you wait.

TL;DRAn FBA fee overcharge refund is the reimbursement Amazon issues when its systems have billed a seller more than the applicable rate for fulfillment, storage, or related FBA charges – typically due to incorrect weight or dimension measurements on file. The path to recovery requires identifying every affected ASIN, supporting the discrepancy with verified measurement data, and working through Seller Central's reimbursement and case-management tools in the right sequence. Skipping steps or filing without documentation is the most common reason legitimate claims are closed without payment.

This guide covers what an FBA fee overcharge actually is on Amazon US, the procedural sequence that gives a claim the best chance of success, and the decision points where sellers most often choose the wrong path. It draws on the same process we use when we map held balances and press disbursement and reimbursement claims for sellers in the Frozen Funds & Recovery work we handle at Tutamen.

What does "FBA fee overcharge" actually mean on Amazon US?

An FBA fee overcharge is a charge that exceeds the rate Amazon's own fee schedule permits for the product as it is actually packaged and shipped. The charge is almost always traceable to one of two sources: a measurement discrepancy, where the recorded weight or dimensions in Amazon's system are higher than the product's true packaged dimensions; or a product-type classification error, where the ASIN has been assigned to the wrong size tier or handling category.

Both sources share the same mechanism. Amazon's Seller Central calculates FBA fees by pulling from a stored product record. If that record is wrong – because a measurement was taken incorrectly at the fulfillment center, or because a product type was auto-assigned rather than verified – every outbound unit incurs a fee the seller did not earn. The error compounds with volume. A $0.30 overcharge per unit across several thousand shipments is not a rounding error; it is a real recovery claim.

A third, less common source is rate-schedule mismatch: a fee change applied retroactively or a promotional rate that should have been applied but was not. These situations are procedurally different and typically require a more targeted Seller Support escalation, distinct from a standard measurement-based claim.

In matters we handle, the most frequent scenario is the measurement-based overcharge, and it is worth understanding why Amazon's records diverge from reality. Fulfillment-center scans are automated and fast. Units move through measurement stations at volume, and occasional scanner errors or packaging anomalies create records that persist indefinitely unless a seller actively challenges them. Amazon does not proactively audit and correct every stored dimension; the burden of identifying and disputing the error falls on the seller.

How do you identify which ASINs are overcharged?

The starting point is the FBA Fee Reimbursement report and the Fee Preview report in Seller Central, read against your own measurement records and the applicable fee schedule. This sounds straightforward, but the comparison requires precision: you are matching per-unit charges across a payment period against the rate that should apply to the product as packaged.

Step one: pull the Payments – Transaction View report for the period you want to review. Filter for fulfillment-fee line items. Export this data; working inside Seller Central's browser interface alone is not practical for any meaningful volume.

Step two: pull the FBA Fulfillment – Fee Preview report. This report shows Amazon's current stored measurements and the fee tier those measurements produce. For each ASIN where you believe the stored dimensions are wrong, record what Amazon's system shows.

Step three: measure the actual packaged unit. This must be done with a calibrated scale and a tape measure or dimensional scanner, following Amazon's own measurement methodology for packaged products. The measurement you submit will be challenged if it is not documented. Photograph the product on the scale and against a ruler. Note the date. If you are a high-volume seller, a third-party measurement service can provide a documented report that carries more weight in a dispute than an internal spreadsheet.

Step four: calculate the fee delta. For each affected ASIN, compute the difference between what was charged and what should have been charged under the correct size tier, then multiply by the unit count for the relevant period. This gives you the overcharge figure per ASIN. Aggregate across all affected ASINs to build the total claim.

A common mistake at this stage is reviewing only the current period. Overcharges often run for months or longer before a seller notices. The reimbursement window Amazon applies to these claims is not unlimited – going back through a meaningful historical window is important, and doing so thoroughly at the outset avoids having to re-file a supplemental claim later. For a fuller picture of how fee claims interact with broader balance recovery, see our frozen funds recovery guide for sellers.

What is the actual procedural path for filing the claim?

The procedural path for an FBA fee overcharge claim runs through two parallel tracks: a measurement update request and a reimbursement case, both opened through Seller Central. The order matters.

Track 1 – Correct the stored measurement. Before a reimbursement case will succeed on a measurement-based overcharge, the underlying product record usually needs to be corrected. Open a case with Seller Support, clearly identifying the ASIN, the discrepancy between the stored dimensions and your verified measurements, and attaching the measurement documentation. Request that the product's stored dimensions be updated. This step is important: a reimbursement claim filed before the measurement is corrected can be closed on the grounds that the fee was consistent with the system's record.

Track 2 – File the reimbursement claim. Once the measurement has been corrected – or contemporaneously in cases where you can document the historical error clearly – open a separate reimbursement case. State the specific ASINs, the periods affected, the overcharge amount per unit, the unit count, and the total figure you are claiming. Attach the fee transaction data, the corrected measurement record, and your verification documentation. Keep the case focused: a long, general complaint is harder for a specialist agent to act on than a clear, specific, numerically precise request.

Amazon's Seller Support system routes these cases internally. The first response is frequently a template reply that does not engage with the specifics. Do not accept that as a final answer. Escalate the case, attach the same documentation again, and explicitly state that you are seeking a substantive review. Persistence in the case thread – without becoming hostile – significantly increases the chance of a real review.

What happens if Seller Support closes the case without resolution? The escalation path includes the Executive Seller Relations (ESR) team, accessible via a separate escalation route in Seller Central, and – for larger or more complex claims – the Account Health team and, where the BSA's dispute-resolution provisions apply, a pre-arbitration Notice of Dispute. The path depends on the account's circumstances, the size of the claim, and whether the underlying measurement dispute has been resolved. For a detailed look at the fee dimension component of this dispute, our analysis of weight and dimension fee overcharges and the seller's real options covers the specific escalation points in depth.

One micro-case is illustrative. A kitchenware FBA seller on Amazon US (winter 2025) came to us after Seller Support had closed three case attempts on the same ASIN cluster. The problem was procedural: the measurement update had been submitted but the correction had not been applied before the reimbursement cases were filed, so each case was closed as consistent-with-record. We mapped the error sequence, re-opened the measurement cases first, obtained confirmation of the updated records, and then refiled the reimbursement claim with a clean documentation package. The claim moved to payment review within a matter of weeks.

Where does this process typically go wrong?

Sellers working through fee overcharge claims alone encounter the same failure points repeatedly. Understanding these points is not a warning to scare you off the process – it is practical knowledge that changes whether you succeed.

Measurement documentation is too thin. A note in a spreadsheet saying "I measured it at 8 x 6 x 4 inches" is not sufficient for a contested claim. Amazon will close the case. The documentation needs to be datestamped, photographically supported, and ideally conducted against Amazon's stated measurement methodology. If you have a third-party logistics partner, ask whether they can provide a formal dimensional record – that document is considerably more persuasive than a seller-prepared spreadsheet.

Filing the reimbursement case before the measurement is corrected is the second, and probably the most common, procedural error. The case agent reviewing a reimbursement claim looks at whether the fee was consistent with the stored product record. If the record still shows the wrong dimensions, the answer is yes, and the case closes. The fix is simple in theory but consistently missed in practice: correct the record first.

Scope errors go in both directions. Some sellers file for one ASIN when several are affected, leaving money on the table. Others file for an inflated period, overstating the claim, which can trigger a manual review or raise credibility questions. Build the claim from the transaction data, not from an estimate.

Finally, and this applies specifically to sellers who have experienced a disbursement hold or account deactivation: a fee overcharge claim is not the right tool to recover a held balance. Those are different mechanisms with different procedural requirements. If your account is currently subject to a hold, the FBA reimbursement claim runs in parallel with, but does not substitute for, the reinstatement and disbursement work. We regularly see sellers conflate the two, which delays both processes.

What are the decision points and trade-offs a seller needs to weigh?

Is the claim worth pursuing at all? For most sellers, yes – but the calculus depends on the aggregate overcharge amount, the number of ASINs involved, and the account's current health status. A small single-ASIN claim on an otherwise healthy account is straightforward to file and worth the administrative effort. A multi-ASIN claim running across a long period on an account that has also experienced recent policy actions is a more complex situation, because the reimbursement case and the policy matter can interact.

If the claim involves a significant aggregate amount, the decision between handling it internally and involving a specialist is partly about time and partly about documentation quality. Seller Support's standard process works for well-documented, straightforward claims. It becomes less reliable when the claim is complex, when multiple prior cases have been closed, or when the seller cannot produce the measurement documentation internally.

The BSA's dispute-resolution provisions are available as an escalation tool when Seller Support is unresponsive and the claim amount justifies the process. The path depends on the BSA version that applies to the account, which we check first in any matter. A pre-arbitration Notice of Dispute is a fixed-fee engagement, far below the cost of full arbitration, and it signals a formal posture that Seller Support escalations sometimes cannot replicate. For sellers also dealing with removal order discrepancies – a separate but related issue – our guide on responding to removal order discrepancies covers that escalation path in detail, and some of the same documentation principles apply.

The myth worth addressing directly: held funds and unresolved reimbursement claims are not gone for good. The belief that once Amazon has closed a case or held a balance the money is permanently unavailable is, in our experience, the single most expensive misconception a seller can hold. Cases can be reopened. Escalation paths exist. The BSA provides formal mechanisms. The limiting factor is documentation, procedure, and in some cases, timing – not a categorical bar.

A second micro-case reinforces the point. An apparel FBA seller on Amazon US (spring 2026) contacted us after being told by Seller Support that a reimbursement case was "not eligible for further review." The account had also been subject to a brief payment hold the prior quarter. We separated the hold question from the fee claim, mapped the transaction data for the prior eight months, and identified that the core overcharge traced to a single size-tier misclassification applied at the start of a new product launch. The reimbursement case was refiled with a clean documentation set and a specific escalation to the appropriate team. The claim was acknowledged for payment review.

What should you do before filing your claim?

Before opening a single Seller Support case, complete the following preparation steps. Skipping them does not save time; it costs it.

• Pull and export the full fee transaction history for the period you want to claim, filtered by ASIN and fee type.
• Pull the Fee Preview report and identify every ASIN where stored dimensions or size-tier classification diverges from the actual packaged product.
• Physically measure each affected ASIN using Amazon's methodology – weight and all three dimensions – and document with photographs and dates.
• Calculate the overcharge delta per ASIN and in aggregate before opening any case; you need this figure to write a precise case description.
• Check whether each ASIN's measurement has previously been updated or disputed; prior case history affects the documentation strategy.
• Confirm the account's current health status and whether any payment hold is active; if it is, plan both processes separately before filing either.
• Identify the relevant period boundary for your claim – going back as far as the available transaction data and the applicable reimbursement window allows.

Once this preparation is complete, open the measurement correction cases first. Wait for confirmation. Then open the reimbursement cases, with the complete documentation package attached in the first message. A case that opens with full documentation has a materially better outcome trajectory than one that starts sparse and tries to build the record through follow-up messages.

If you have reached this point in the guide and your situation involves multiple ASINs, a prior case closure, or a parallel account issue, that is the point at which a short review with a specialist – to check the documentation and sequence before you file – is usually worth the time. The cost of a procedural error on a fee overcharge claim is not just the rejection; it is the time lost and the possibility that the case history complicates a subsequent filing.

For a broader look at how FBA reimbursement claims interact with disbursement holds and fund recovery more generally, our complete guide to frozen funds recovery for sellers sets out the full picture.

The steps above describe the standard path. Your situation turns on the exact fee data, the account history, and the documentation you have on hand – which is what we review first. To have us map your fee claim and assess the best filing sequence, email info@tutamenlaw.com.

Related areas

• Frozen Funds & Recovery – recovering held balances, reserves, and FBA reimbursements on Amazon US and other surfaces
• Account Reinstatement – appealing Section 3 deactivations and restoring suspended Amazon seller accounts

Frequently asked questions about FBA fee overcharge refunds

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

Resolution timelines vary considerably depending on the complexity of the claim and whether the underlying measurement records need to be corrected first. A straightforward single-ASIN claim with clean documentation can move through Seller Support review within a few weeks. Multi-ASIN claims, or cases that require escalation past the first-tier response, typically take longer – often several weeks to a few months. Claims that involve a prior account action or require escalation to Executive Seller Relations will generally take additional time on top of the standard cycle. Filing with complete, precise documentation at the outset shortens the cycle; filing incomplete and trying to build the record through follow-up usually extends it.

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

The most common risk is a procedural error that closes a valid claim: filing the reimbursement case before the underlying measurement record is corrected, submitting documentation that does not meet Amazon's evidentiary standard, or scoping the claim incorrectly. A second risk is timeline: sellers working without a clear sequence often let cases go dormant between follow-ups, and Amazon's case-management system can close inactive cases. A third risk is conflating the fee reimbursement claim with a disbursement hold or account policy issue – these are different mechanisms, and mixing them in a single case description typically results in neither being addressed properly.

Do I need a lawyer for fba fee overcharge refund?

Not always. A well-documented single-ASIN overcharge on a healthy account, filed correctly through Seller Support, is something many sellers handle without outside help. A lawyer becomes relevant when the aggregate claim is significant, when prior case attempts have been closed without proper review, when the account also has an active hold or policy issue that intersects with the fee claim, or when escalation to a formal pre-arbitration Notice of Dispute is the appropriate next step. In those situations, the cost of a professional review is usually small relative to the amount at issue and the risk of a second procedural error.

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. Every matter is handled by a qualified attorney – not a consultant or account service – and every engagement begins with a candid assessment of the realistic options, not a promise of outcome. 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.