FBA fee overcharge refund: a seller's checklist

TL;DRAn FBA fee overcharge refund is a reimbursement Amazon owes a seller when its automated systems have billed the wrong fulfillment, storage, or surcharge rate – most commonly because Amazon measured or classified an item incorrectly. The money is recoverable, but only if the seller identifies the gap, gathers the right evidence, and files through the correct channel before the claim window closes. This checklist walks through each phase in the order it matters.

The invoices look small. A few cents on one ASIN, a dollar or two on another. Then someone runs the numbers across a full catalog and a year of shipments, and the overcharge is not small at all. That is the moment most sellers realize they have been leaving their own money inside Amazon's system – not because Amazon took it deliberately, but because the burden of spotting the error sits entirely with the seller.

In matters we handle, the most common culprits are weight and dimension remeasurements that never made it back into the fee engine, storage-tier misclassifications, and surcharges that continued long after the qualifying period ended. Each category has its own audit path and its own filing channel. Getting the wrong channel means the case stalls or closes without resolution.

This checklist is organized as a sequence of phases. Work through them in order. Each phase has a set of concrete checks, a short explanation of why the check matters, and a flag for where the process tends to break down.

Phase 1: Understand what an FBA fee overcharge refund actually is

An FBA fee overcharge refund is Amazon's return to the seller of fees charged at a rate that was incorrect under Amazon's own published fee schedule – not a discount, not goodwill, but a correction of a billing error.

Amazon's fulfillment fee for a given unit is calculated from the product's tier, which in turn comes from its dimensions and weight as measured in the fulfillment center. When a remeasurement changes those numbers, the fee engine is supposed to update automatically. In practice, it sometimes does not. The result is that a seller continues to pay a higher rate on a product that, by Amazon's own recorded measurements, should attract a lower one. The same logic applies to storage fees billed at an incorrect tier, to Peak Fulfillment surcharges applied outside the published window, and to aged-inventory surcharges triggered by incorrect inbound receipt dates.

What an FBA fee overcharge refund is not: it is not a lost-inventory FBA reimbursement (that is a separate claim path), not a chargeback reversal, not a dispute over A-to-z Guarantee charges, and not a request to renegotiate Amazon's fee schedule. Conflating these categories is the first way sellers slow themselves down. Each has its own reporting tool, its own evidence standard, and its own review team on Amazon's side.

A disbursement hold or frozen-funds situation arising from an account deactivation is a different matter again. If you are dealing with both – a suspended account and fee overcharges – the two claims need to be managed in parallel, because the overcharge refund timeline runs independently of the reinstatement timeline. For a full picture of how disbursement issues interact with account status, the complete guide to frozen-funds recovery for sellers sets out the full landscape.

• Confirm the overcharge is a fee billing error, not a policy penalty or an A-to-z claim.
• Note whether the affected ASINs are still active, suppressed, or in an account that is itself deactivated – each state affects which tools are available.
• Confirm the marketplace is Amazon US; the fee schedules, the reporting tools, and the claim routes differ across Amazon's international stores.

What records do you actually need before you start?

The single biggest reason FBA fee overcharge claims fail or stall is that the seller files before gathering the right documentation, forcing multiple follow-up rounds that exhaust the review period.

Amazon's fee reconciliation tools generate reports – the Fulfillment Fee Preview Report, the FBA Fee Preview, and the transaction-level data in Payments – but these are snapshots, not audit trails. You need to pull them at a point in time and preserve them locally, because historical data in Seller Central can roll off. The standard workflow is:

1. Download the FBA Inventory Measurement Audit report for the affected ASINs. This is the record Amazon holds of the measured dimensions and weight at each fulfillment center. Compare it against the published fee tiers for the period in question.
2. Pull the transaction-level fee data from the Payments reports for the same period. Filter by fulfillment fee type. The per-unit amount charged should match the tier implied by the measurement audit. Where it does not, that gap is the overcharge.
3. Record your own physical measurements of the product in its standard packaging, with photos, a calibrated scale reading, and the measurement date. This is your counter-evidence if Amazon disputes the remeasurement data.
4. Pull any Amazon remeasurement notices from Account Health or from prior cases in the case log. If Amazon previously acknowledged a measurement change, that notice is strong corroborating evidence that the fee engine should have updated.
5. Calculate the per-unit overcharge against Amazon's published fulfillment fee schedule for the relevant period – the difference between what was charged and what the correct tier would have cost. Multiply by units affected.
6. Note the date the overcharge began – this anchors the look-back window for the claim.

Keep every file in a single folder with a clear naming convention. Amazon's reconciliation team will ask for this evidence in a specific format, and having it organized before the first filing avoids the most common delay.

Phase 2: Check the claim window

The look-back window for FBA reimbursement claims is one of the most misunderstood constraints in the process. Missing it closes the claim permanently, regardless of how well-evidenced the overcharge is.

Amazon's published look-back period for fee-related reconciliation requests has historically been 18 months from the date of the transaction. This means the relevant question is not when you discovered the overcharge, but when it occurred. Overcharges older than the look-back window are generally not recoverable through Seller Central's self-service tools, even with strong evidence.

In our practice, we regularly see sellers who discovered a systematic overcharge late – often because a catalog review or third-party audit surfaced it years after the billing began. For those claims, the recoverable portion is limited to the period within the look-back window, not the full history. The earlier you start this checklist, the more of the overcharge is inside the recoverable window.

A separate consideration: if the account is currently deactivated and funds are on hold, the clock does not pause. Disbursement holds and the reimbursement look-back window run on different tracks. Waiting for reinstatement before starting the fee audit can result in losing months of otherwise-recoverable overcharges. For context on how removal-order discrepancies interact with the broader funds picture, see our piece on what to know about removal order discrepancies.

• Identify the earliest date of the overcharge from your transaction data.
• Calculate how many months of that history are within the look-back window as of today.
• Prioritize the oldest qualifying transactions in the filing, not the most recent ones.
• If the account is deactivated, note that the fee claim and the reinstatement are independent tracks – do not wait on one to start the other.

Phase 3: File through the correct channel

Amazon offers more than one path for fee-related disputes, and filing through the wrong one is the second most common reason claims stall.

For weight and dimension overcharges, the standard path starts with a case opened through the FBA Inventory Measurement Audit request tool in Seller Central, not a generic Seller Support ticket. Generic tickets almost always route to agents who lack the authority or the tooling to approve a fee correction; they will close the case or redirect it, and the redirect itself consumes days or weeks. The detailed account of how the measurement audit and remeasurement request process plays out in practice is worth reviewing before you file – see the explanation in our write-up on how one seller resolved a weight and dimension fee overcharge.

For storage-tier overcharges and surcharge errors, the path is different: the right starting point is the Payments report reconciliation request, supported by the transaction data and, where applicable, the inbound shipment records showing the correct receive date.

The practical filing sequence looks like this:

1. Open the case through the correct tool (measurement audit for dimensional errors; Payments reconciliation for storage/surcharge errors).
2. In the first message, include: the ASIN list, the date range, the per-unit overcharge calculation, and the supporting data (measurement audit export, transaction-level fee report, your own measurement photos).
3. State the specific error type clearly: "Amazon billed at [Tier X] but the recorded measurements qualify for [Tier Y] under the published schedule for [period]."
4. Request a specific remedy: a credit to the seller account equal to the calculated overcharge, applied to the affected transactions by date.
5. Note the case number and the date opened. Set a calendar reminder for the escalation point (see Phase 4).

The first filing is the most important. Amazon's review teams prioritize complete, first-contact submissions over back-and-forth corrections. Submitting a partial filing and adding documents later typically resets the internal queue.

Phase 4: Manage the escalation path

A filed case that goes quiet is not a closed case. But it can become one if the seller does not manage the escalation timeline.

Amazon's case management system has internal routing steps, each with its own expected turnaround. When a case sits past those checkpoints without movement, the practical options are: a direct escalation within the existing case thread, a secondary case referencing the first, or an escalation through Account Health. Each option has trade-offs. Duplicate cases can be linked and closed; escalations through Account Health are sometimes faster for active-account sellers but carry their own attention risks for sellers whose accounts have any open compliance issues.

For accounts that are currently deactivated, the escalation path for fee claims is narrower. The standard Seller Support escalation tree may be partially or fully unavailable. In that scenario, the claim preserves its evidence record, but active pursuit may need to wait for reinstatement – or be routed through a formal dispute mechanism depending on the BSA version that applies to the account, which we review at the outset of any matter.

Escalation checklist:

• If the case has not moved in a week, add a clear follow-up to the case thread: restate the specific question, the evidence provided, and the requested credit. Do not open a new case.
• If there is no substantive response after a second follow-up, escalate within the same thread to the next queue level, citing the original case number and the days elapsed.
• If the case is rejected without a substantive explanation, request the specific grounds for rejection in writing. A generic "we have reviewed your account" response is not an answer; push for the specific finding on the overcharge data.
• Document every response – date, case number, agent ID if visible, and the text of the response. This record matters if the matter moves to a formal dispute or arbitration.

Phase 5: Assess whether the disputed amount warrants a formal dispute

Not every rejected fee claim justifies escalating to a formal dispute mechanism. But some do, and knowing the threshold matters for a seller who is deciding how to spend time and resources.

The Amazon Business Solutions Agreement (BSA) contains a dispute-resolution mechanism for disagreements between Amazon and sellers. The path depends on the BSA version that applies to the account – we check that at the outset of any matter, because the BSA terms are a volatile fact that has changed over time and varies by account vintage. A pre-arbitration demand – a structured Notice of Dispute that puts Amazon on formal notice of the claim – is often enough to resolve a fee dispute that Amazon's internal teams have rejected, because it moves the matter to a different part of Amazon's legal organization with different decision-making authority.

The realistic options, depending on the amount at stake and the strength of the evidence, are:

• Self-service persistence: continue through the internal escalation tree. Low cost, slow, and appropriate when the claim is straightforward and the amount is modest.
• Formal notice letter: a lawyer's demand letter that puts the overcharge claim on record in writing, outside Seller Central. This sometimes breaks a stall at the internal review level without triggering full dispute resolution.
• Pre-arbitration demand (Notice of Dispute): the formal first step under the BSA's dispute process. Typically a fixed fee engagement. This is the threshold at which many disputed amounts become worth pursuing formally – the informal period that follows a Notice often resolves matters without arbitration.
• Arbitration: the full formal track, appropriate for larger disputed amounts where internal and pre-arbitration steps have not resolved the claim.

A seller who has never done this before often assumes that a rejected internal claim is the end of the road. That belief is the most common myth we encounter: that held funds or denied refunds are permanent once Amazon's internal process closes the case. They are not. The BSA's dispute pathway and, in appropriate cases, the courts, remain available after internal rejection.

The decision to file a Notice of Dispute should be based on the amount in dispute, the quality of the evidence, and a realistic read of what Amazon's internal record of the case looks like. We map every held balance and reserve, and press the disbursement and reimbursement claims through the path that fits the facts and the numbers – which is what we review first on any matter that comes to us at this stage.

Phase 6: Prevent the next overcharge

Recovering a past overcharge without fixing the underlying cause means the same error recurs on the next fee cycle. This is where sellers who handle these claims alone most often leave money behind.

A home-goods seller on Amazon US came to us in fall 2025 after self-filing a weight and dimension overcharge claim that Amazon's internal team rejected. We reviewed the original filing, identified that the seller had used the wrong report (a Fulfillment Fee Preview snapshot rather than the Inventory Measurement Audit export), and refiled with the correct data and the remeasurement notice Amazon had issued two years earlier. The claim was processed. More importantly, the ASIN catalog had several other items with the same error pattern, and a systematic audit caught them before the look-back window closed on those transactions too.

Prevention checklist:

• Set a recurring calendar reminder to pull and review the FBA Inventory Measurement Audit report – quarterly for active catalogs, monthly if you are frequently adding new ASINs.
• Each time Amazon issues a remeasurement notice, confirm within seven days that the fee engine has updated to reflect the new tier. Do not assume the update is automatic.
• For new ASINs, record your own measurements and photos at the time of first inbound shipment. This is the baseline evidence for any future overcharge claim on that item.
• Track the aggregate fee per unit over time in a simple spreadsheet. A sudden increase in per-unit fulfillment cost without a published fee schedule change is the clearest early signal of a new overcharge.
• If you use a third-party inventory management platform, confirm whether it ingests the Inventory Measurement Audit data or only the Fulfillment Fee Preview. The former is the audit-grade source; the latter is a forward projection and is not a substitute.

A second micro-case: a media and collectibles seller on Amazon US (spring 2026) identified an aged-inventory surcharge overcharge that had been running for several months. The root cause was an inbound shipment where Amazon's receive date was recorded incorrectly by one day, triggering the surcharge earlier than the published threshold. We mapped the transaction records, matched them against the inbound shipment confirmation, and filed through the Payments reconciliation path with the shipment record as the primary exhibit. The corrected amount was credited to the seller's account.

Related areas

• Frozen Funds & Recovery – mapping all held balances and pressing disbursement and reimbursement claims
• Account Reinstatement – restoring a deactivated Amazon account when funds are also on hold

If a first filing on an overcharge claim came back rejected, or if the amount at stake has grown to the point where internal escalation no longer feels adequate, a second read by someone who handles these claims as a primary practice area can identify the specific gap in the filing and the path still open. To get a read on where your claim stands, email info@tutamenlaw.com.

Common questions about FBA fee overcharge refunds on Amazon US

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

Resolution time varies considerably depending on the claim type, the completeness of the initial filing, and whether the claim moves through internal Seller Support or escalates to a formal dispute path. A well-documented, complete filing through the correct tool for a straightforward dimensional overcharge can move in a matter of weeks. Claims that require escalation, involve multiple ASINs, or are filed through the wrong channel typically take longer – often several months. Formal dispute steps through the BSA's dispute mechanism add further time but also bring a different level of decision-making authority on Amazon's side.

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

The three most common failure modes for self-represented sellers are: filing through the wrong tool (causing the case to stall or be closed without substantive review), submitting incomplete documentation that forces multiple follow-up rounds and resets the queue, and missing the look-back window on older transactions because the audit started late. A more structural risk is accepting a rejection as final when the BSA's dispute path remains available. Each of these is recoverable if caught early, but harder to fix once the window has closed or the case log shows repeated misfiled attempts.

Do I need a lawyer for FBA fee overcharge refund?

Not every FBA fee overcharge claim requires legal representation. A single ASIN with a clearly documented dimensional error and a clean filing may resolve through Seller Central's self-service tools. A lawyer adds the most value when the internal process has already failed, when the aggregate amount justifies formal dispute steps, or when the overcharge is one component of a broader situation – an account hold, a funds reserve, or a disbursement dispute – where the legal and procedural picture is more complex. In matters we handle, the trigger is usually a rejected internal claim or an amount that makes it worth filing a Notice of Dispute to move to a different decision-making track.

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. Our fee overcharge and funds-recovery practice is led by qualified attorneys with direct experience in Amazon's reconciliation process, and every engagement is handled on a confidential basis. To discuss your situation, email info@tutamenlaw.com.

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.

Written by Claire Donnelly, arbitration & disputes analyst, Tutamen. Published June 2, 2026.