Amazon FBA Fulfillment Fee Overcharges: Finding Wrong Measurements, Disputing the Charge, and Using Prep Records as Evidence
Most FBA sellers never open the Fee Preview report. They see fulfillment fees as a fixed cost of doing business, absorb quarterly increases as policy changes, and move on. The problem is that some of those increases are not policy changes - they are measurement errors that began when a CubiScan scanner at a fulfillment center recorded the wrong dimensions for a packaged unit. The fee ran at the wrong rate from that moment forward, compounding on every order shipped, often for months before anyone noticed. This guide covers the full cycle: how the error enters the system, how to find it, what you can and cannot dispute in 2026, how the remeasurement and dispute tools actually work, and why a measurement record from your prep center is the most useful piece of evidence you can have in hand when you file.
Why Fulfillment Fees Drift: The CubiScan Measurement Lifecycle
Amazon uses CubiScan infrared laser hardware at fulfillment centers to record product dimensions. The scanner captures the smallest bounding box around the outer packaging of each unit. That reading is not an average. It is the scan of one unit on one day at one facility, and it becomes the dimension of record for your ASIN.
Three events can trigger a re-measurement after the initial intake scan, none of which generate a seller notification:
- Inbound quality audit: When Amazon samples incoming inventory, the audited unit often gets re-scanned. A unit sitting on a seam or with a slightly inflated poly bag can produce a different reading than the original.
- Return-loop processing: Customer returns go through a separate grading and repackaging workflow before re-entering sellable inventory. That workflow includes a scan. A returned unit repackaged slightly differently can produce a new dimension that replaces the old one.
- Random fulfillment center inspection: Amazon periodically re-measures ASINs during internal audits. No notice goes to the seller when this happens.
CubiScan machines have a documented limitation with irregular shapes, soft-sided packaging, and products with protruding parts. In those cases the scanner may read the longest diagonal of the item rather than the true bounding-box edges. The result is a recorded dimension longer than any actual edge of the product, which can push a unit into a larger size tier than its physical packaging warrants.
The core failure is the feedback gap. Amazon updates the dimension on file, the fee changes, and nothing alerts the seller. Orders continue shipping at the wrong rate until someone reads the right report.
Reading the Fee Preview Report: The Six Columns That Reveal an Overcharge
Go to Seller Central, open Reports, Fulfillment, then Fee Preview. Download the report as a spreadsheet. Each ASIN row contains six columns that drive fulfillment costs:
- Longest side
- Median side
- Shortest side
- Length and girth (the perimeter measurement used for large standard and large bulky items)
- Item package weight
- Product size tier
These six values, together, explain every fulfillment fee on your account. The size tier column tells you which bracket Amazon assigned your product, and the dimension columns show exactly why.
Compare Amazon's three dimension values against your own packaged product measurements. Use rigid calipers or a hard-sided ruler, not a soft tape measure. Measure the finished outer packaging after everything is applied - poly bag, FNSKU label, dunnage, any additional bundling material. The relevant unit is the packaged product entering the fulfillment center, not the bare product.
Pay close attention to the weight column. Amazon's shipping weight for fee calculation is the greater of the actual unit weight and the dimensional weight. Dimensional weight uses a formula that multiplies length by width by height in inches, then divides by a standard divisor published in Amazon's fee schedule - check the current divisor in Seller Central because it has changed before. If your product is light relative to its volume, dimensional weight is likely driving the fee, and an overread on any single dimension inflates it directly.
Identifying Tier-Boundary ASINs and Calculating the Real Cost
Not every measurement discrepancy is worth pursuing. The goal is to identify ASINs sitting near a tier boundary - products where a correction would drop them into a lower fee bracket.
Map Amazon's recorded dimensions against the current size tier thresholds in the published fee schedule. For each ASIN, calculate how far Amazon's reading sits above the nearest lower-tier boundary. Products where any single dimension is close to a tier cutoff are candidates for review.
Once you identify a candidate, the math is straightforward. Find the per-unit fee difference between the tier Amazon assigned and the tier your actual packaged dimensions place you in - check the current rate card in Seller Central for the figures. Multiply that difference by monthly unit volume. Multiply by twelve for an annual view. Third-party fee audit tools and Amazon specialist services regularly surface measurement-based overcharges as a contributor to unclaimed FBA fee discrepancies. Even a small per-unit discrepancy repeated across high-volume ASINs creates a substantial annual loss - build the number before deciding whether the dispute is worth your time.
What You Can and Cannot Dispute in 2026
Two significant fee changes in 2026 have created real confusion about what qualifies as a disputable overcharge. Sellers file cases on policy changes and lose time. Sellers also incorrectly dismiss legitimate measurement overcharges because they assume every fee increase is a policy update. The distinction is worth getting right.
What you cannot dispute:
- Fuel and logistics surcharge (April 2026): Amazon applied a surcharge on top of fulfillment fees. This is a policy charge applied uniformly. It is not a measurement error.
- Price-band fee changes (January 2026): Amazon's January 2026 update made fulfillment fees partially dependent on selling price in addition to size tier and weight. If your fee went up because your price moved into a different band, that is a correct application of the new rate structure.
- Standard fee schedule updates: When Amazon adjusts the fee schedule itself, all resulting fee changes are policy decisions, not errors.
What you can dispute:
- Fees charged using dimensions that do not match your actual packaged product
- Fees charged using a weight that differs from the actual packaged weight
- Size tier assignments that result directly from an incorrect dimension or weight reading
Amazon will reimburse the FBA fees if we confirm that they were charged using inaccurate weight or dimensions.Amazon Seller Central fee dispute policy
When you review your Fee Preview report, separate the question of whether Amazon's numbers are accurate from the question of whether the fee is higher than it was last year. Those are different questions, and only the first one opens a dispute path.
Requesting a Remeasurement: The Tool, the Quota, and the Limits
Amazon provides a remeasurement tool called 'Remeasure FBA products and confirm fees.' Find it by typing 'remeasure' in the Seller Central help search bar. The tool submits an ASIN for a fresh physical measurement at the fulfillment center where your units currently live.
Three constraints govern what you can submit:
- Monthly quota: Each seller account has a cap on remeasurement submissions per month. The quota resets on the first of each month. The current limit is displayed inside the tool - check it before prioritizing which ASINs to submit, and use your quota on the highest-impact candidates first.
- Per-ASIN frequency cap: An ASIN that has been remeasured too recently cannot be submitted again. The tool shows whether a given ASIN is currently eligible or locked out. Attempting to file a dispute while an ASIN is locked does not bypass the restriction.
- Inventory requirement: An ASIN with no units currently at an Amazon fulfillment center cannot be submitted. There is nothing for the scanner to measure.
When a remeasurement confirms that Amazon's numbers were wrong and the correction moves the ASIN to a lower tier, Amazon updates the dimension on file and applies the corrected fee going forward. The remeasurement result itself does not automatically generate a reimbursement for past charges. That requires a separate fee dispute case.
Filing the Fee Dispute Case
Amazon's dispute window for fee errors tied to incorrect weight or dimensions is time-limited. Charges beyond the eligible cutoff date before your case submission are ineligible regardless of the size or duration of the error. Check the current window in Seller Central's fee dispute help documentation - this window is the controlling factor in how much of a past overcharge you can actually recover. If the error has been running for a year and you are filing now, most of that loss cannot be recovered. That math is the strongest argument for running the Fee Preview audit quarterly.
- Download the Fee Preview report and record the ASIN's current on-file dimensions, weight, and size tier before anything changes. Date-stamp the download.
- Measure the actual packaged unit yourself - all three dimensions and the packaged weight - with a dated written record.
- If you have prep center measurement logs for this ASIN, gather the dated weight and dimension documentation.
- Open a case in Seller Central via Help, then Contact Us. Navigate to the FBA or Shipping section and look for the option covering fees charged in error or incorrect measurements - the exact menu labels change with Seller Central interface updates, so use the Contact Us search bar if you cannot locate it immediately.
- State the ASIN, the current on-file dimensions, your actual measured dimensions, the resulting tier difference, and the date range for the charges you are disputing.
- Attach your evidence: the dated Fee Preview report, any remeasurement confirmation if available, and third-party measurement records from your prep center.
- Monitor the case. When Amazon confirms the dimensions were inaccurate, a reimbursement is issued for the charges within the dispute window.
Do not wait for a remeasurement result before opening the dispute. The two processes can run in parallel. Waiting delays the case and may push additional charges outside the eligible window.
How Prep Center Measurement Records Strengthen a Dispute
When you submit a fee dispute, Amazon's reviewer sees their own system's records on one side and your claim on the other. A seller-produced photo of their own measurements is easy to question. A dated record from an independent third party - a prep center that logged every dimension and weight before the shipment left their facility - carries different evidentiary weight.
| Evidence Type | Source | Timing Relative to Amazon Intake | Independence |
|---|---|---|---|
| Fee Preview report screenshot | Amazon's system | After intake | None - Amazon's own record |
| Seller's own measurement | Seller | Usually after dispute arises | Low |
| Prep center measurement log | Third party | Before Amazon takes possession | High |
| Remeasurement confirmation | Amazon | After submission | Amazon confirms its own error |
A prep center log works well for three reasons:
- It predates Amazon's intake: The record was created before the CubiScan ever read the unit. It cannot be dismissed as a reaction to the dispute.
- It is third-party sourced: It comes from a business independent of the seller, with its own operational records and no stake in the dispute outcome.
- It reflects the packaged unit: It captures the product after poly bagging, FNSKU labeling, and any bundling - the same state the CubiScan should have recorded.
When a dispute reviewer sees a prep center log placing a unit in a lower tier, against Amazon's on-file dimensions showing a tier-bumping overread, the discrepancy is concrete and externally documented. One important limitation: Amazon's stated policy is that its own fulfillment center measurement governs the final determination. If Amazon remeasures the unit and records the same dimensions again, prep center records alone will not override that result. What prep center documentation does is make the discrepancy credible and strengthen the case for a remeasurement - which is the step that ultimately determines reimbursement eligibility.
Ask your prep center to record all three final dimensions and the packaged weight on the documentation for each ASIN, after all prep work is complete. Many prep centers track this internally. The question is whether they can produce it in a format attachable to a Seller Central case - a dated PDF or spreadsheet showing the ASIN, all three measurements, and the packaged weight is enough. SNS Prep Center maintains pre-shipment weight and dimension records for every ASIN it processes. If your current prep center does not retain these records, ask now, before you need them for a case.
Monitoring Tier Drift Over Time
The Fee Preview report shows what Amazon has on file today. It does not show when that number changed. For historical visibility, sellerboard's FBA fee audit tools - check sellerboard's current documentation for the report name and navigation path, as these change with product updates - can surface size tier, shipping weight, and actual per-unit charges across a date range. When you plot those values, tier drift becomes visible: an ASIN that moved from one tier to another at a specific point shows a step change in the per-unit charge column.
Use this data to narrow down when a measurement error was introduced. If the tier changed in a specific month, that month is likely when a re-measurement event - a return scan, an audit scan, or a random fulfillment center inspection - produced the wrong reading. Knowing the approximate start date helps you calculate how much of the overcharge falls within the dispute window and how much has aged out.
After a successful remeasurement and dispute, download the Fee Preview report again to confirm the correction is reflected in the system. Then set a quarterly reminder to run both reports across your highest-volume ASINs. Measurement errors can recur on the same ASIN when a subsequent scan at a different facility reads differently. Quarterly checks catch the problem before another long window of charges accumulates.
Packaging Decisions That Prevent the Problem
CubiScan errors are not random. Specific packaging characteristics make them more likely. Understanding those characteristics lets you reduce their frequency through packaging design.
The scanner struggles most with:
- Soft poly bags with excess material gathered at the top or sides - the scanner reads the gathered material as part of the bounding box
- Irregular product shapes with handles, antennas, or protruding corners - the laser may read a diagonal span rather than the true longest edge
- Multi-unit bundles where individual items can shift position inside the outer packaging, changing the apparent bounding box from one scan to the next
Spec-first packaging design addresses this directly. Before finalizing a package design for an ASIN, calculate where the tier boundaries fall. Design the outer packaging so all three finished dimensions sit with clear margin inside the target tier. A unit whose largest dimension sits meaningfully below the next-tier threshold will not be bumped into a higher tier by a small scanning error. Prep centers are positioned to help with this - because they handle the final-packaged unit before it ships, they can flag ASINs where dimensions sit dangerously close to a tier boundary, giving the seller time to adjust before the shipment reaches the fulfillment center.
The combination of margin-aware packaging, pre-shipment measurement documentation, and regular Fee Preview audits closes the loop. It reduces the frequency of CubiScan errors, catches the ones that occur before they compound for a full year, and ensures usable evidence is already on file when a dispute is warranted.
Frequently Asked Questions
With a large catalog, how do I decide which ASINs to audit first?
Sort the Fee Preview report by size tier descending, then focus on ASINs where any single dimension from Amazon's record sits close to the boundary between the assigned tier and the next lower tier. Those are the candidates most likely to have been bumped by a small scanning error. Within that set, multiply the per-unit fee difference by monthly unit volume to rank by financial impact. Audit the highest-impact boundary cases first - a discrepancy on a low-volume ASIN may not justify the time even if the measurement is off.
My fees went up after January 2026 and I am not sure how much is policy versus a measurement error. How do I separate the two?
Pull the current rate card from Seller Central and calculate what the fee should have been at your actual packaged dimensions under both the pre-January and post-January rate structures. If the fee under the new rate structure at your correct dimensions is lower than what Amazon charged, the difference is a disputable measurement error. If the fee at your correct dimensions matches what Amazon charged, the entire increase is a policy change and not disputable. Running the calculation at your own dimensions - not Amazon's on-file dimensions - is the step most sellers skip.
What do I do if my ASIN hits the per-ASIN remeasurement frequency cap?
You can still open a fee dispute case using your own dated measurements and any prep center documentation you have on file. Remeasurement confirmation from Amazon strengthens a case but is not required to open one. While waiting for the per-ASIN cap to reset, gather your evidence and begin the case with the documentation you have. Do not delay opening the case - charges continue to age toward the dispute window cutoff.
If a measurement error and the January 2026 price-band change both contributed to a higher fee, can I dispute the measurement portion while accepting the policy portion?
Yes. The two components are independent. Use the current rate card to calculate the fee your actual packaged dimensions would have generated at the correct size tier, under the same price-band that applied during the disputed period. The difference between that figure and the fee Amazon actually charged is the measurement-based overcharge you can dispute. Submit that calculation with your case. The price-band portion of the increase is not disputable and should not appear in your claimed amount.
My prep center does not retain measurement records. What evidence can I use instead?
Your own dated measurements of the packaged unit can be submitted as supporting context when explaining the discrepancy and prompting Amazon to investigate. Be aware that Amazon's stated policy is that personal measurements are not used as the basis for determining eligibility - only a fulfillment center remeasurement can confirm the error and qualify you for reimbursement. This makes using the remeasurement tool the essential step. When Amazon's own remeasurement confirms the on-file dimensions were wrong, that result functions as Amazon confirming its own error and does not depend on any external measurement record. Run the dispute case in parallel rather than waiting for the remeasurement result - both processes can proceed simultaneously as described in the filing steps above.
After a dispute resolves, how do I confirm the corrected dimensions are actually being applied to new orders?
Download the Fee Preview report again after the dispute closes and check the three dimension columns and the size tier for the ASIN. The corrected values should appear there. If the report still shows the pre-dispute dimensions, follow up with Seller Central before additional orders ship at the wrong rate. After confirming the correction, note the date so you have a baseline to compare against in future quarterly audits - if the tier column changes again between audits, that is your signal that a new scanning event introduced another error on the same ASIN.
You May Also Like
Amazon FBA Inbound Receiving Discrepancy: What to Do When Amazon Checks In Fewer Units Than You Shipped
A meaningful share of FBA shipments produces some kind of gap between the quantity a seller declares...
Amazon FBA Prep for OTC Drugs and Over-the-Counter Medicine: The Complete 2026 Compliance Guide for Sellers
Most FBA prep guides treat over-the-counter drugs as a slightly stricter version of beauty products....
Amazon FBA Prep for Toys and Games: The Complete 2026 Compliance and Prep Guide
Selling toys on Amazon FBA in 2026 requires passing two distinct sets of checkpoints: the federal an...