Why weight and dimension fee overcharge happens on Amazon UK

TL;DRWeight and dimension fee overcharge on Amazon UK occurs when the measurements held in Amazon's fulfillment system do not match the physical reality of a seller's product – and the wrong number drives a higher fee on every single unit sold or stored. Amazon calculates FBA fees from its own scan data, not the seller's declared specs. When that scan is inaccurate, the overcharge compounds silently across months of transactions until a seller reconciles their fee statements or is alerted by a cash-flow gap.

This page covers what is actually happening when the measurement data goes wrong, why the UK marketplace has its own procedural specifics, how sellers can build a credible claim, and what the realistic options look like at each stage. If your disbursements are running below what the volume would suggest, a fee-measurement discrepancy is one of the first places to look.

What is weight and dimension fee overcharge on Amazon UK?

An FBA fulfillment fee overcharge is the difference between what Amazon charged per unit based on its recorded dimensions and weight and what it should have charged based on accurate measurements. On Amazon UK, as in other FBA programs, fulfillment fees are tiered by size band and weight band – the specific thresholds differ from the US program and are revised periodically. When a unit is remeasured and placed in the wrong band, every subsequent charge tracks the wrong rate.

The practical definition matters because sellers often confuse this with a storage fee dispute or a co-mingling issue. Fee overcharge tied specifically to weight and dimension is a measurement-data problem. The measurement sits in a catalog record inside Fulfillment Center systems. It was captured during a scan – sometimes at receipt, sometimes later during a quality audit – and it may be wrong because the scanner captured a partial carton, a bundled unit rather than a single unit, or a product in non-standard packaging.

In matters we handle, the discrepancy is not usually obvious from a seller's dashboard. The nominal per-unit fee looks plausible for a product in that general category. The problem surfaces only when you pull a fulfillment fee breakdown and map each ASIN's charged weight-band against the product's actual specification. Many sellers discover the issue months or even a full disbursement cycle late.

A concrete illustration: a compact home-accessories product sold in standard packaging falls, by its true dimensions, into a lighter size band. Amazon's system carries a scan that captured the product inside a multi-pack prep bag, adding volume. Every unit sold since that scan went into the wrong band. The overcharge per unit may be small – but across several thousand units, it becomes a material balance that belongs to the seller.

Why does Amazon UK's measurement system produce errors?

Amazon's physical measurement process is automated and high-throughput; scanning errors are an inherent by-product of operating at fulfillment-center scale. Several structural factors make UK inventory specifically prone to this.

First, the UK program applies its own size-band thresholds, which are set in metric units and differ from the North American tiers. A product that sits safely within a lighter size band in the US may cross a threshold in the UK system if the measurement tolerance is even slightly off. The margin for scan-error impact is, in some categories, narrower in the UK than in other Amazon marketplaces.

Second, UK FBA inventory often enters the network via multiple inbound routes: direct seller shipment to a UK fulfillment center, pan-European transfers from a DE or PL originating FC, or inventory enrolled in the European Fulfillment Network (EFN). Each transfer point is a potential re-measurement event. We regularly see sellers whose original declared dimensions were correct at UK inbound, but a subsequent inter-FC transfer triggered a re-scan that produced an erroneous record.

Third, seller-declared dimensions in the catalog are not always the controlling data. Amazon's policy is that its own remeasurement supersedes seller-declared specs when there is a discrepancy, and the system typically applies the Amazon measurement without any active notification to the seller. The seller is left paying the new rate, often unaware that a re-scan occurred.

Fourth, bundled and multi-pack products carry a structural risk. If a product is sold as a two-pack but stored individually and then paired at pick, the fulfillment-center scan may have captured any of several configurations. The measurement in the system reflects whatever the scanner saw on that occasion – not necessarily the standard unit the seller intended.

What drives the commercial pain is that the overcharge is not a one-time event. It is a rate applied to every subsequent transaction until it is corrected. In terms of the seller's cash flow, a measurement error that has been running for two disbursement cycles has already silently diverted a material portion of the margin that should have reached the disbursement account.

How does fee overcharge connect to frozen funds and disbursement shortfalls?

Fee overcharge is not a frozen-funds situation in the strict sense of a Section 3 deactivation or a payment hold. But it produces the same commercial symptom: the money the seller expected to receive does not arrive. Understanding the distinction matters because the procedural path is different.

With a deactivation hold, funds are withheld pending an investigation or account closure process – a scenario covered in depth in our guide to frozen funds recovery for sellers. With a fee overcharge, funds were never retained by Amazon in a reserve. They were charged as a fee. The question is whether those charges were correct and whether an adjustment is owed.

This distinction affects who inside Amazon Seller Support can address the claim, what documentation is required, and what relief is actually available. An overcharge is pursued as a fee adjustment and a reimbursement claim – not as an account appeal or a reserve-release request.

The practical overlap with frozen-funds scenarios is that fee overcharges discovered during an account deactivation often complicate the overall recovery picture. A seller dealing with a deactivation-related disbursement hold may discover, on close analysis, that the account balance they are trying to recover is itself lower than it should be because of measurement errors running through the prior trading period. The two claims need to be separated and pursued in parallel through different channels.

Inventory-level discrepancies raise a related but distinct set of questions. Sellers who have also encountered stock that went missing or was removed should review the practical steps in our material on removal order discrepancies, which touches on the evidence-gathering overlap between removal and reimbursement claims.

What is the procedural path for pursuing an overcharge claim?

The realistic path for a UK fee overcharge claim moves through several defined stages, each with its own evidence requirements and time sensitivities. No stage offers a guaranteed outcome, and the seller's ability to succeed depends heavily on the quality of documentation and the precision of the claim as presented.

Stage 1: Build the measurement record. Before any claim is filed, the seller needs a product-level reconciliation: the declared dimensions and weight (from the catalog or original inbound documentation), the dimensions and weight Amazon currently has on record in its system, the date of any remeasurement event if identifiable, and a fee calculation showing the overcharge per unit at the correct versus the charged rate. This is not documentation Amazon supplies proactively. It requires a systematic pull from the Seller Central fee reports, the fulfillment fee breakdown, and the ASIN's measurement record.

Stage 2: Physical remeasurement request. Amazon's process allows sellers to request a remeasurement of inventory held in a UK fulfillment center. The seller submits a request through Seller Central and Amazon's fulfillment operations will remeasure the product. If the remeasurement confirms the seller's spec, that creates the foundation for a fee-adjustment claim. Critically, a successful remeasurement corrects fees going forward – it does not automatically generate a retroactive adjustment for the overcharge already incurred.

Stage 3: Reimbursement claim for historical overcharge. Recovering the historical overcharge requires a separate case opened with Seller Support, supported by the reconciliation built in Stage 1 and the outcome of the remeasurement. The claim should specify the ASIN, the period of overcharge, the number of units affected, and the per-unit discrepancy. Claims that arrive as vague "I was overcharged" requests without a unit-level breakdown are routinely declined or only partially resolved.

Stage 4: Escalation and dispute options. If the Seller Support case closes without full resolution, the seller has escalation routes: an executive escalation through Amazon's own internal escalation path, or – depending on the version of the Business Solutions Agreement applicable to the account – the dispute-resolution mechanism that applies. The path depends on the BSA version that applies to the account, which we check first in any engagement.

Timing matters throughout. Amazon maintains a lookback window for fee-related claims; the exact length can vary by claim type and account status, but it is not unlimited. A claim filed after significant delay may recover only a portion of the total overcharge even if the measurement error is fully established. Acting promptly once an overcharge is identified preserves more of the potential recovery.

In matters we handle, the most common reason a self-filed claim underperforms is not that the seller was wrong about the overcharge – it is that the claim as submitted was incomplete, miscategorized, or filed through the wrong channel, leading to a partial resolution or an automated decline that the seller accepts as final.

What evidence do you need to build a credible claim?

The strength of a fee overcharge claim tracks directly to the specificity of the underlying evidence. A credible claim is one that Amazon's internal review team can evaluate numerically, without needing to conduct independent research into the seller's account.

At minimum, the evidentiary package should contain: a product specification document (the original product spec sheet, brand packaging dimensions, or manufacturer's technical sheet showing weight and dimensions); the ASIN's current measurement record from Amazon's system; a fee simulation showing what the correct fee band should be at the accurate measurement; and a transaction-level export of fulfillment fees for the affected ASIN over the relevant period, showing the total overcharge.

Supporting evidence strengthens the claim further. If the product was inbounded in the UK with accurate dimensions confirmed at receipt, the inbound shipment records showing those dimensions are valuable. If the overcharge began after a specific transfer event – an inter-FC move, a re-inventory event – any system record linking the timing of the fee change to a fulfillment-center event helps establish causation, not just discrepancy.

Physical evidence is the most unambiguous. A remeasurement by Amazon that confirms the seller's spec is close to definitive proof within the Seller Support process. Where a remeasurement is not yet available – for instance, the inventory has already been removed or sold through – a third-party measurement report prepared by a logistics company with a verifiable chain of custody can serve a comparable function.

What weakens a claim: relying only on the seller's self-declared catalog dimensions without any external corroboration; submitting a total overcharge figure without showing the per-unit calculation; or submitting through a general Seller Support ticket without correctly categorizing the claim as a fee measurement dispute. Amazon's internal routing is consequential – a fee measurement claim routed through account health or performance channels reaches the wrong team and often produces a generic non-response.

What are the real decision points and trade-offs for UK sellers?

Once the overcharge is documented, a UK seller faces a set of practical decisions. None of them has a universally correct answer – the right choice depends on the size of the overcharge, the seller's account standing, the state of their relationship with Seller Support, and how much time and attention the business can allocate to the process.

The first decision is whether to attempt Seller Support resolution alone or to bring specialist input at the outset. The Seller Support path is available without legal assistance, and for smaller, clearly documented overcharges – a single ASIN, a short affected period, a clean remeasurement result – a well-constructed self-filed claim may succeed. The risk of proceeding alone is analyzed in the FAQ below.

The second decision is whether to pursue a retroactive reimbursement claim or to focus only on correction going forward. Some sellers, under time pressure, accept the correction of the fee going forward and write off the historical overcharge. That can be a reasonable commercial decision for a small overcharge. For material amounts, the write-off is avoidable. We map every held balance and press the disbursement and reimbursement claims that the documentation supports – the question is always whether the recovery value justifies the effort and cost, which we assess after reviewing the account data.

The third decision is whether the fee overcharge is a standalone issue or part of a broader account health or funds-recovery situation. A seller whose account is also subject to a reserve, a deactivation, or a related IP dispute should treat the fee overcharge as one component of a coordinated claim strategy, not a separate case to be filed in isolation. Claims filed piecemeal through different Seller Support channels often produce conflicting outcomes and, in some cases, one resolution can inadvertently close off another.

If you have already filed a claim that was rejected or partially resolved, a second read of the claim record can identify the specific failure point – whether the claim was miscategorized, the remeasurement was not linked to the reimbursement request, or the historical period was incorrectly scoped. A rejected first filing does not close the claim permanently in most cases, but timing constraints on refiling make it important to understand the failure mode quickly.

The decision matrix in brief: if the notice or fee data confirms a measurement discrepancy across a significant transaction volume, the route is a structured claim built on the Stage 1 reconciliation and a remeasurement request, on a timeline of several weeks to several months for full resolution. If the discrepancy is limited to a single ASIN and a short trading period and the remeasurement is already confirmed, a seller-filed Seller Support case may achieve resolution without specialist involvement. If the overcharge is material, involves multiple ASINs or periods, or sits alongside other account issues, coordinated specialist handling preserves the full recovery potential.

Consider also the situation facing sellers across other platforms. While the mechanics differ, inventory discrepancies that affect FBA reimbursement have structural parallels elsewhere. The approach to disposed inventory claims on Walmart illustrates how measurement and inventory accuracy issues translate across marketplace models.

Common mistakes sellers make when handling this alone

Fee overcharge claims look procedurally straightforward until they are not. In matters we handle, the same failure patterns recur across otherwise well-prepared sellers.

The first is filing too early, before the remeasurement result is in hand. A claim submitted without a confirmed remeasurement typically produces a conditional response – Amazon notes the discrepancy is under investigation and the case is left open or closed without a decision. The seller has used one of their available escalation contacts for the ASIN without advancing the claim.

The second is combining the reimbursement claim with an unrelated complaint in the same Seller Support case. Amazon's internal teams have narrow mandates. A case that opens as a fee measurement issue and then references a disbursement hold, an inventory discrepancy, or an IP dispute is likely to be passed between teams or closed on the basis that it contains issues outside the handling team's scope.

The third is accepting an underpayment without checking whether the recovery was correctly scoped. Amazon may offer an adjustment that covers the most recent overcharged transactions but does not reach back through the full affected period. Sellers who accept the first offer and close the case have permanently limited their recovery to that subset.

A mid-market electronics accessories seller on Amazon UK (winter 2025) came to us after a self-filed overcharge claim produced an adjustment covering only three months of a discrepancy that had been running for considerably longer. We reconstructed the fee history by ASIN, mapped the re-scan event that triggered the measurement change, and filed a structured historical reimbursement case. The case required two escalations, but the final adjustment covered the full period and a material multiple of the original seller-filed recovery.

The fourth mistake is not documenting the claim history. If a first filing is rejected or only partially resolved, the record of how the claim was framed, what documentation was submitted, and what the response stated is essential evidence for any escalation or refiling. Sellers who do not retain a complete case record find themselves repeating the same Seller Support interactions without being able to demonstrate what was already submitted and what the prior response said.

How does this look across a selling year, and when should you review?

Fee overcharges are not uniformly distributed across a selling year. Several operational patterns on Amazon UK increase the probability of a measurement error appearing at specific points in the annual cycle.

Inbound shipments tied to peak-season inventory build – the period leading into the fourth quarter – bring a significantly higher volume of new stock into fulfillment centers in a compressed timeframe. Throughput pressure on the receiving and scanning process is at its highest during these periods. Sellers who ship new product configurations, updated packaging, or higher-volume multi-packs ahead of peak season should treat the weeks following the inbound confirmation as a monitoring window, not a settled state.

Pan-European inventory rebalancing events, which can occur at any point in the year but are often triggered by demand forecasting adjustments, are each a potential re-scan event. A UK seller whose EFN inventory is actively balanced across multiple European FCs should build a quarterly dimension-check into the account management routine, not an annual one.

A home-goods FBA seller on Amazon UK (spring 2025) first identified a fee discrepancy during a quarterly account review they had recently adopted after a previous overcharge experience. The discrepancy had begun only six weeks earlier – a short enough window that the remeasurement request and reimbursement claim could be filed as a single coordinated submission. Because it was caught early, the total overcharge was limited, and the case resolved through a single Seller Support interaction without escalation. The prior experience – where the same seller had let a similar discrepancy run for most of a trading year – had cost a multiple of what the early-detection approach recovered.

The practical recommendation: map at least two formal fee-reconciliation reviews into the annual operating calendar – one in the post-peak-season period, and one mid-year. Each review should include a pull of the ASIN-level fulfillment fee breakdown and a comparison against the seller's recorded product specifications. The effort involved in a structured review is modest. The cost of missing a running overcharge compounds with every transaction week that passes.

Related areas

• Frozen Funds & Recovery – recovering held balances and disbursement shortfalls on Amazon and other marketplaces
• IP & Brand Registry – handling rights-owner complaints, counter-notices and retraction requests

If a first appeal or filing already came back rejected, a second read can find the specific reason it failed and what, if anything, is still open. For claims that were partially resolved, reviewing the claim record often identifies the exact transaction window or ASIN set that the initial case missed. To have the full picture reviewed, contact Tutamen at info@tutamenlaw.com.

Frequently asked questions

How long does resolving weight and dimension fee overcharge usually take on Amazon UK?

Resolution timelines on Amazon UK vary depending on the complexity of the claim and whether escalation is required. A straightforward single-ASIN overcharge supported by a confirmed remeasurement can resolve through Seller Support within several weeks. Claims involving multiple ASINs, longer affected periods, or a disputed remeasurement result typically take several months, and cases that require escalation – either through Amazon's executive path or the dispute-resolution process under the BSA – may extend further. Acting promptly after identifying the discrepancy preserves more of the potential recovery and prevents additional overcharge from accruing while the claim is open.

What are the main risks if I handle weight and dimension fee overcharge alone?

The principal risks are: filing before the remeasurement result is confirmed, which produces an inconclusive or prematurely closed case; incorrectly scoping the historical period, leaving a portion of the overcharge unrecovered; combining the fee claim with other account issues in a single case, causing the claim to be routed to the wrong team; and accepting a partial recovery offer without checking whether the full affected period was covered. Each of these errors is addressable, but once a case is closed or a partial adjustment accepted, reopening requires additional evidence and escalation that could have been avoided.

Do I need a lawyer for weight and dimension fee overcharge?

Not in every case. A small, clearly documented overcharge on a single ASIN with a confirmed remeasurement can often be resolved through a well-structured Seller Support submission without specialist involvement. Where specialist input adds value is when the overcharge is material, spans multiple ASINs or a long trading period, sits alongside other account or disbursement issues, or where a self-filed claim has already been rejected or partially resolved. In those situations, the structure of the claim and the escalation path materially affect the outcome – and that is where attorney-led handling makes a practical difference.

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. 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.