Quick answer
ASP (average selling price) is the average price at which a product or service actually sold in a period: net revenue divided by units sold. It is net of discounts, a per-unit figure, and it moves with the product mix even when no price changes.
Formula: ASP = net revenue ÷ units sold
What does ASP mean in sales?
ASP stands for average selling price: the average price at which a product or service actually sold in a period, found by dividing net sales revenue by the number of units sold. It is a per-unit number. A company that sold 1,000 units for $39,000 has an ASP of $39.00, whatever the list prices were.
Two details separate ASP from a price list. First, it is built from what customers paid, so discounts and promotions pull it below list price. Second, it is an average over a mix of products, so it moves when the mix moves, even if no price on the shelf changes. Most mistakes with ASP come from forgetting one of those two facts.
How do you calculate ASP?
The formula has one numerator and one denominator, and both must cover the same period and the same set of sales:
ASP = net revenue ÷ units sold
Sample data: a store sells three plans in a quarter. Prices are the amounts customers actually paid after discounts.
| Product | Price paid | Units sold | Revenue |
|---|---|---|---|
| Basic | $20 | 600 | $12,000 |
| Plus | $50 | 300 | $15,000 |
| Pro | $120 | 100 | $12,000 |
| Total | 1,000 | $39,000 |
ASP = $39,000 ÷ 1,000 = $39.00. Notice that no customer paid $39. The ASP is a summary, not a price anyone sees, which is why it needs the table behind it before anyone makes a decision from it.
If you also have a list price, compute the discount separately: with $48 average list price and a $39 ASP, the average discount is $9, or 18.75% of list. Keep list price, discount and ASP as three numbers so you can tell which one moved.
Why can ASP fall when no price changed?
Because ASP is a weighted average, a shift toward cheaper products lowers it even when every individual price stays flat. This is the single most useful thing to know about the metric.
Sample data, continuing the store above. In the next quarter, prices are identical, but customers lean towards the entry plan:
| Product | Q1 units | Q2 units | Q1 share | Q2 share |
|---|---|---|---|---|
| Basic ($20) | 600 | 800 | 60.0% | 72.7% |
| Plus ($50) | 300 | 250 | 30.0% | 22.7% |
| Pro ($120) | 100 | 50 | 10.0% | 4.5% |
| Total units | 1,000 | 1,100 |
Q2 revenue is 800 × $20 + 250 × $50 + 50 × $120 = $34,500, so Q2 ASP is $34,500 ÷ 1,100 = $31.36, which is 19.6% lower than Q1 with no price cut at all. Units grew 10%, yet revenue fell 11.5%.
You can split the $4,500 revenue drop into a volume part and a mix part:
- Volume effect: (1,100 − 1,000) × $39.00 = +$3,900. More units, at the old average.
- Mix effect: 1,100 × ($31.36 − $39.00) = −$8,400. The same units sold at a lower average.
- Price effect: $0, because no unit price changed.
- Check: +$3,900 − $8,400 = −$4,500, which matches the revenue change.
A real filing shows both directions. In its annual report for 2010, a chip company explained that revenue rose $24.3 million on a 66% increase in units sold, partly offset by a 15% decrease in average selling price. For 2009 it reported a 7% unit increase together with a 29% ASP increase, "primarily due to changes in product mix". Because the two effects multiply, 1.66 × 0.85 = 1.41 (about +41% revenue) for 2010, and 1.07 × 1.29 = 1.38 (about +38%) for 2009. Both are in the company's 10-K; the 2009 sentence is the same company moving the other way for the same reason.
How is ASP different from AOV and ARPU?
ASP, average order value (AOV) and ARPU all divide revenue by something, but they divide by different things and answer different questions.
| Metric | Formula | Unit of analysis | Question it answers |
|---|---|---|---|
| ASP | Revenue ÷ units sold | One unit | What does one unit sell for on average? |
| AOV | Revenue ÷ orders | One order | How much does one checkout bring in? |
| ARPU | Revenue ÷ active users | One user | How much does one user bring in over the period? |
ASP and AOV are linked by units per order: AOV = ASP × units per order. Sample data: 100 orders contain 250 units and bring in $10,000. AOV is $10,000 ÷ 100 = $100. ASP is $10,000 ÷ 250 = $40. Units per order is 250 ÷ 100 = 2.5, and $40 × 2.5 = $100.
That identity tells you where to look. If AOV rose while ASP stayed at $40, customers are putting more items in each basket (a bundling or free-shipping-threshold effect). If AOV rose because ASP rose, the products or prices changed. The same $100 AOV means different things in the two cases.
What goes into the numerator and the denominator?
Define these choices once, write them down, and use them every period. Otherwise two people will report different ASPs from the same data.
- Discounts and coupons. Use net revenue, after discounts. Keep a separate column for list price if you want to see discount depth.
- Refunds and returns. Match both sides. Sample data: of the 250 units above, 20 were returned and refunded for $800. Net of refunds on both sides, ASP is ($10,000 − $800) ÷ (250 − 20) = $40.00, unchanged. Subtracting the money but not the units gives $9,200 ÷ 250 = $36.80, a fake 8% drop.
- Bundles. Decide whether a bundle counts as one unit or as its parts. If you count the bundle as one, ASP rises whenever bundles sell more, with no real price change.
- Free units. Giveaways and free trials either stay out of both numerator and denominator, or go into both. Counting the unit but not the zero revenue drags ASP down.
- Currency. Convert to one currency before averaging, at a stated rate. Mixing currencies produces a number with no unit.
- Period. Compare the same length of period. Quarterly ASP against monthly ASP is only safe if the mix does not change with the season.
Is the "average" in ASP a mean or a median?
It is a mean, and a mean is pulled up by a few expensive sales. Public statistics show the size of that gap. In its September 2026 release, the US Census Bureau reported the median sales price of new houses sold as $400,400 and the average sales price as $472,800. The average, which is the ASP of those sales, was $72,400 or 18.1% higher than the median, because a minority of high-priced homes lifts the mean.
For your own business the same rule applies. If a handful of large deals sit among many small ones, report the median (or a few percentiles) next to the ASP. When the two are close, the mean is a fair summary. When the mean is far above the median, one number hides two kinds of customers, and the next section applies.
How should you use ASP to make decisions?
Use these rules rather than staring at the trend line:
- If ASP falls and units rise, check the mix before the price. Compute the share of units by product, as in the table above. A rising share of the entry plan is a mix effect, not a pricing problem.
- If ASP rises and units fall, check whether you lost the low end. You may have raised the average by shedding small customers, which is fine only if revenue still grew.
- Always read ASP with units and revenue. Revenue = ASP × units, so any two of the three give you the third. A change in revenue should be explainable as volume, mix and price, as in the $4,500 example.
- Segment by channel or customer type. A blended ASP of $31 can be $18 for one acquisition channel and $55 for another, and only the second may be worth paying for.
- Mark price changes on the chart. An ASP shift after a known price change is a price effect; a shift without one is mix or discounting.
ASP is not a profit measure. A rising ASP says nothing about cost, and a falling one can still be healthy if the cheaper products have better margins.
Tracking ASP with TapCub
Suppose you want to answer the Q2 question above: did revenue fall because of price, or because customers shifted to the entry plan? TapCub gives you the order side of that answer; the unit counts come from you.
TapCub does not show an ASP card. In All-platform analytics › Business › Commerce & revenue it reports revenue, orders, buyers and the average order (revenue divided by orders), which is AOV, not ASP.
- Send each purchase from your server with the order id, amount and currency when payment succeeds. The order id is the dedupe key, so a retry does not create a second order. See track e-commerce purchases.
- Add the line items in an
itemsarray. Item, category and brand ranks come from the line items on each purchase, so you can see which plan carries the revenue. - Send refunds with the same order id. TapCub reports refunds separately and does not subtract them from revenue, so net them yourself on both the money and the unit side, as in the refund example above.
- Read average order and revenue by period, then divide revenue by your own unit count to get ASP. Compare it with the share of revenue by item to tell mix from price.
- Mark price changes in Configuration › Annotations so a later ASP move can be matched to a date.
TapCub does not set prices or run discounts; it only measures what customers paid.
Sources
- Inphi Corp, Form 10-K for fiscal 2010, SEC EDGAR (revenue discussion: units sold, average selling price and product mix, 2010 and 2009).
- US Census Bureau, New Residential Sales, September 2026 (median and average sales price of new houses sold; release of 27 October 2026).
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Product Experience Specialist
Explores usability, user journeys, and feature adoption through practical examples of onboarding and everyday product use.