ASP is computed as net revenue / units sold over a defined period, with net revenue taken post-discount, pre-shipping, and pre-tax. As with most rate metrics, period and numerator convention must be held constant — quarter-over-quarter comparisons only mean something if both sides were computed the same way.
ASP is a per-unit measure; AOV is a per-order measure. They move independently whenever units-per-order shifts. Bundles, upsells, and free-shipping thresholds lift AOV without touching ASP — more units in the basket, same price per unit. Conversely, price increases or a mix shift toward premium SKUs lift ASP while AOV barely moves, if units-per-order stays roughly flat. Knowing which lever pulled is the point.
Most operators report ASP net of promo — the price the customer actually paid per unit. Some teams track gross ASP (list-price-weighted) alongside, to isolate how much realized price is being given back as discount depth. Both are legitimate; label which one the dashboard shows.
ASP is the operating number for merchandising — assortment, price-pack architecture, premium-tier launches — and feeds gross margin forecasting: a 5% ASP lift at flat units and stable COGS flows nearly one-for-one to gross-margin dollars. It also anchors revenue-bridge analysis, where a topline move decomposes into price, units, and mix; without ASP, operators can’t tell whether revenue growth was earned or discounted into existence.
One caveat: an ASP rise can come from catalog pruning — cutting low-priced SKUs entirely — rather than pricing power on retained ones. Read it alongside unit volume by SKU price tier.