Size-tier audits belong in your monthly FBA close

Size tier is one of the most leveraged fields in an FBA operation. It affects fulfillment fees, storage economics, shipment planning, box compliance, and sometimes whether a product is eligible for certain programs. A small measurement change can push a SKU into a different fee tier, and the seller may not notice until margin has already moved.

The audit should not be annual. It belongs in the monthly close, next to settlement reconciliation.

Build a variance report

Compare seller catalog dimensions against Amazon measured dimensions for every active FBA SKU. Flag three cases:

• any dimension changed by more than your tolerance
• unit weight changed enough to alter carton planning
• measured tier differs from expected tier

The tolerance should be practical. A tiny measurement change may not matter. A change that crosses a fee threshold matters immediately.

Tie the variance to dollars

A report that only says "dimension mismatch" creates work without priority. Recompute the expected fee at the old and new tier, multiply by recent shipped units, and rank by dollar impact. A SKU with low volume can wait. A high-velocity SKU that crossed a tier last week needs a case package and pricing review.

Close the loop in catalog data

If Amazon is right, update your internal dimensions so shipment plans, carton weights, and margin forecasts stop using stale values. If Amazon is wrong, prepare evidence: product photos with measuring tape, scale readings, packaging specs, and fee lines. Track the case outcome and retroactive recovery separately.

Size-tier drift is boring until it becomes a margin problem. A monthly audit keeps it boring.

Prioritize the evidence package

Do not file every variance with the same urgency. Start with SKUs where the measured tier changes the fee materially and recent sales volume makes the impact meaningful. For those SKUs, build a clean evidence package: packaged product dimensions, packaged weight, scale photo, ruler or caliper photo, packaging specification, and the fee lines that show the impact.

The evidence package should be repeatable. If each case is assembled differently, the team spends too much time deciding what to attach and too little time recovering the overcharge. A template also helps operators avoid weak disputes. If the team cannot produce clear photos and a consistent measurement method, the first action may be to remeasure internally before opening a case.

Watch for operational side effects

Size-tier changes do more than change fulfillment fees. They can alter carton planning, storage forecasts, placement economics, and pricing decisions. When Amazon's measurement is correct, update every downstream model that depends on size and weight. Otherwise the SKU may keep creating bad inbound plans even after finance accepts the new fee tier.

When Amazon's measurement appears wrong, track the case outcome and the date the correction applies. Fee recovery may be retroactive only for a limited window, and future settlements still need to be watched to confirm the tier actually changed. A good audit closes only when catalog data, fee expectations, and settlement charges agree.

Add supplier packaging review

Size-tier drift is sometimes caused by Amazon measurement, but it can also be caused by supplier packaging changes. A thicker insert, larger polybag, new bundle configuration, or changed carton presentation can move the packaged unit across a fee threshold. Include supplier packaging in the audit instead of assuming the catalog record is the only source of truth.

When a supplier change is legitimate, update cost and pricing assumptions before the next order. When the change was not approved, send the evidence back to sourcing and decide whether the supplier should correct future production. The audit is stronger when it connects fee movement to the physical product flow.