Amazon High-Volume Listing Fee Calculator

The calculation itself

The high-volume listing fee is a small monthly charge per active SKU once a seller's listing count exceeds a threshold, applied to listings that have not sold recently.

Cost = chargeable SKUs above the threshold × the monthly per-SKU rate. It is designed to discourage sellers from holding vast numbers of listings that never sell but consume catalogue resources.

It is trivial per SKU and meaningful across a large dormant catalogue.

Running the numbers

A seller with 180,000 active SKUs against a threshold of 100,000 has 80,000 chargeable listings. At a rate around $0.005 a month that is $400 monthly, or $4,800 a year.

Against a catalogue generating meaningful revenue that is negligible. Against a catalogue where most of those listings have never sold, it is $4,800 for nothing.

For the great majority of sellers the fee never applies at all, a private label seller with 40 SKUs is nowhere near any threshold, and the fee is aimed squarely at high-volume aggregators and repricers.

The useful exercise it prompts is worth doing regardless of the fee: what proportion of your listings have sold in the last year?

What gets missed

The threshold counts active listings rather than products, so variations, sizes and colours each count separately. A catalogue of 3,000 products in ten variants each is 30,000 listings.

Listings that sold recently are generally excluded from the chargeable count, so the fee targets dormancy rather than breadth as such.

What to do next

Run a report of listings with no sales in twelve months. Whether or not the fee applies, that list is the clearest available picture of catalogue bloat.

Then close or merge the dormant ones. Each carries a forecast, a price, a content record and a share of attention, and the ones that have never sold carry all of that for nothing.

Catalogue size and the attention it consumes

The fee is a small price signal attached to a much larger real cost. Every listing consumes content maintenance, pricing decisions, compliance checks and search-term management, whether or not it sells.

A catalogue that has grown by accretion: variants added for one customer, sizes extended for a season, listings created for products long since discontinued, carries that overhead across thousands of SKUs that contribute nothing.

Rationalising it is uncomfortable because each individual listing looks harmless, and the aggregate is what matters. The test worth applying is whether a listing has sold in a year and whether anyone would notice its absence, and the honest answer for a large share of most mature catalogues is no to both.

Beyond that, a smaller catalogue makes every other report usable. Search term reports, profitability rankings and inventory age reviews are all easier to act on when they cover 400 live listings rather than 40,000 mostly-dead ones.

The threshold is also worth watching if you sell variations at scale. A brand adding a size run to every product can multiply its listing count several times over in a single season without adding a single new product, and the count is what the fee measures.