Audit FBA dimensions before small fee errors become a margin line

FBA fee leakage rarely looks dramatic on one order.

An extra fifty cents can disappear inside a settlement report. A dollar may look too small for a support case. But multiply the variance by one thousand monthly units and a “small” measurement problem becomes a recurring five-hundred-dollar margin line.

Sellers often notice the problem only when a fee suddenly looks higher than they remember. Memory is not an audit. The business needs an expected measurement, an expected fee, and a repeatable way to compare both with what Amazon charged.

Start with the packaged unit

The relevant product is not the item on the design table. It is the unit Amazon receives and measures.

Use current production inventory with all retail packaging, protective material, inserts, polybags, labels, and prep included. Measure multiple units when packaging can flex or suppliers have loose tolerances. Record length, width, height, and weight using a consistent method and calibrated equipment.

Keep photographs that show the unit, measurement points, scale display, SKU or FNSKU, and production lot. The goal is not to manufacture evidence for a dispute. It is to know what the operation is actually sending.

If two factories or packaging runs produce different measurements, that is a sourcing-control problem before it is an Amazon problem.

Build an expected-fee baseline

For each active FNSKU, store verified package dimensions, unit weight, shipping weight where applicable, expected size tier, current rate source, and expected fulfillment fee. Add an effective date so the team can distinguish a new rate card from an unexplained measurement change.

Do not compare today’s charge with a screenshot from six months ago. Fees can change because Amazon’s rates changed, because the product moved into another tier, because packaging changed, or because the recorded measurement drifted. The baseline should let an operator identify which event explains the difference.

Refresh it after packaging revisions, prep changes, supplier transitions, and announced rate updates. High-volume and near-threshold SKUs deserve more frequent checks because a few millimeters can carry more economic weight than a large change on a safely positioned item.

Rank variance by dollars, not surprise

Pull the account’s current fee and transaction data, then compare charged fees with the baseline by FNSKU.

Calculate two values: variance per unit and estimated monthly impact. A three-dollar error on a slow seller may matter less than a forty-cent error on a hero ASIN. Rank the queue by recoverable dollars, cash-flow urgency, and risk of continuing exposure.

Use exception bands. A small tolerance may be monitored. A size-tier jump needs immediate review. A measurement that changes repeatedly should be escalated even when the current dollar impact is modest because it signals an unstable process.

The audit should also catch favorable variances. If Amazon records a smaller package than the current production unit, investigate before assuming the lower fee will continue. An eventual correction can destroy a margin model built on an error.

Prepare a clean remeasurement case

Before opening a case, confirm the account’s current remeasurement and fee-dispute workflow. Amazon processes change, and repeated low-quality submissions can create more noise than progress.

Assemble one concise evidence pack: ASIN and FNSKU, Amazon’s recorded values, your verified packaged measurements, photographs, affected fee period, unit variance, and requested action. State facts without writing a long story about profitability.

Track the case ID, submission date, response, remeasurement result, and any reimbursement separately. A measurement correction and a historical fee adjustment are different outcomes. Make sure the team knows which one has occurred.

After a correction, verify it in the live fee preview or relevant report rather than relying only on the support response.

Fix the source of measurement drift

Winning a reimbursement does not fix unstable packaging.

Trace the exception. Did a supplier substitute a thicker insert? Did prep add a polybag or protective corner? Did a master-data feed publish case-pack dimensions as unit dimensions? Does one warehouse compress the package while another does not? Is the item packed differently after a return?

Assign corrective action to the team that controls the cause. Update packaging tolerances, quality-control checks, product records, and contribution-margin models. If a package sits just below a tier boundary, consider whether a small redesign can create a safer margin buffer instead of depending on perfect measurement forever.

The objective is not merely to recover yesterday’s fee. It is to keep tomorrow’s fee predictable.

The Operator Read

Marketplace margin is often lost in fractions.

A reliable FBA fee audit begins with the physical packaged unit, converts that truth into an expected-fee baseline, and compares the expectation with actual charges every month. It prioritizes exceptions by total impact, submits evidence cleanly, and closes the operational cause after the account is corrected.

Do not wait for a fee to look outrageous. The best audit finds quiet leakage while it is still small, recoverable, and easy to explain.