Prep Padding vs Size Tier: How 0.5 Inch of Bubble Wrap Becomes a $40K Mistake

Amazon computes the size tier from packed dimensions. Packed = raw + prep padding. If your catalog stores raw length, width, and height and you forget to add prep padding before reading the tier table, you are off by anywhere from 0.25 inch to 3 inches per side, and sometimes by a full tier.

A Reddit case from late 2025 made the number concrete. One seller documented a $40,000 single-shipment overcharge after a prep-padding change pushed a high-velocity SKU from small-standard into large-standard across a 60-day window before anyone noticed.

This post covers how prep padding interacts with tier boundaries, what each prep type adds, and the catalog workflow that catches creep at entry time.

Why packed dimensions are the only number that matters

Amazon's FC measures what arrives. What arrives is your product plus whatever prep was applied: poly bag, bubble wrap, label overwrap, and any custom padding. Every one of those adds material thickness on all six sides.

Catalog entries and manufacturer spec sheets record raw dimensions. The FC sees raw plus prep. Every fee Amazon charges reads the packed number.

A product with 12.5 x 8 x 5 inch raw dimensions in poly bag prep (add 0.125 inch per side) has packed dimensions of 12.75 x 8.25 x 5.25. That stays in the small-standard tier if weight is in range. In bubble wrap (add 0.5 inch per side), it becomes 13.5 x 9 x 6, which on some weight bands lands in a higher tier entirely.

What each prep type adds

These are the numbers we encode in our size-tier calculator. Treat them as a starting model; thick bubble wrap can run closer to 0.75 inch per side, and custom prep varies by provider.

Prep type	Per-side addition	L/W/H delta
None	0 inch	0 / 0 / 0
Poly bag	0.125 inch	0.25 / 0.25 / 0.25
Bubble wrap	0.5 inch	1.0 / 1.0 / 1.0
Custom (specify)	variable	2 x entered value on each axis

Bubble wrap adds 1 full inch to every dimension. A product that sits 0.75 inch inside the small-standard boundary on all three dimensions will cross into large-standard once it leaves your prep station.

Where this compounds into real dollars

Three amplifiers turn a single bad tier read into a five-figure overpayment:

1. Volume. A 1,000-unit replenishment priced at the wrong tier costs between $0.80 and $3.20 per unit extra. Multiply.
2. Duration. Size-tier errors stick on the ASIN until someone notices. The median catch interval on public Reddit anecdotes runs 30 to 90 days.
3. Recurrence. The same prep SOP ships every replenishment at the same wrong dimensions.

The $40K case was the collision of all three: a high-volume SKU, a 60-day detection window, and a prep SOP that nobody reviewed after changing suppliers.

All our products have been moved to a different fee category, and now Amazon charges us 2x fees.

Where products are most at risk

A product is in the prep-creep danger zone if any of these are true:

• Packed dimensions within 1 inch of a tier boundary on any axis. Ordering a slightly thicker bubble wrap puts you in the higher tier.
• Recent prep SOP change. New supplier, new poly bag spec, new automation. Verify the packed measurement before the next replenishment.
• Packed weight sitting near a fulfillment-fee weight band. A weight-band crossing leaves the size tier unchanged while still raising the per-unit fulfillment fee.

The catalog-side workflow

The cheapest fix is to stop storing raw dimensions as the authoritative number. Two steps:

1. Store both raw and packed dimensions separately. Raw is what your spec sheet says. Packed is raw plus the actual prep type for that SKU. Both columns, always.
2. Compute tier live off packed. Tier classification in any tool you use should read packed dimensions and ignore raw ones. If a tool reads raw and applies padding at fee-calculation time, it will disagree with Amazon's measurement after any prep change that did not get reflected in the padding field.

Catch it before the next replenishment

Our free size-tier calculator takes raw dimensions, prep padding type, and weight, computes the packed size, and runs it through the April 2026 tier table. If the packed size lands within 1 inch of a tier boundary on any axis, the result page shows an amber warning with the packed number, the boundary, and the closest size change that would keep you safe.

Run the size-tier check

No signup. Three inputs. Runs against the live fee schedule.