Value Metrics
ASP vs AOV: Average Selling Price vs Average Order Value
Understand the difference between Average Selling Price (ASP) and Average Order Value (AOV). Formulas, when to use each, and how they connect to CAC, LTV, and paid media.
Value Metrics
Understand the difference between Average Selling Price (ASP) and Average Order Value (AOV). Formulas, when to use each, and how they connect to CAC, LTV, and paid media.
ASP (Average Selling Price) is total revenue divided by the number of deals (or closed contracts) in a period. It is the standard lens for SaaS, B2B, and sales-led motions where “a unit” is a deal or subscription.
AOV (Average Order Value) is total revenue divided by the number of orders (checkouts). It is the standard lens for ecommerce and retail where “a unit” is a cart purchase.
They look similar mathematically, but they describe different business models. Reporting AOV for a SaaS sales team—or ASP for a Shopify store—creates confusion about packaging, media efficiency, and forecasting.
<h2>The Detailed Comparison</h2>
<table>
<thead>
<tr>
<th>Dimension</th>
<th>ASP</th>
<th>AOV</th>
</tr>
</thead>
<tbody>
<tr><td><strong>Definition</strong></td><td>Average revenue per closed deal / contract</td><td>Average revenue per order / checkout</td></tr>
<tr><td><strong>Formula</strong></td><td>Total Revenue ÷ Number of Deals</td><td>Total Revenue ÷ Number of Orders</td></tr>
<tr><td><strong>Primary model</strong></td><td>B2B, SaaS, sales-led</td><td>Ecommerce, retail, self-serve</td></tr>
<tr><td><strong>Unit of analysis</strong></td><td>Deal, contract, or subscription</td><td>Order / cart</td></tr>
<tr><td><strong>Common owners</strong></td><td>Sales ops, revenue, founders</td><td>Growth, merchandising, media buyers</td></tr>
<tr><td><strong>Pairs with</strong></td><td>Win rate, sales cycle, CAC, LTV</td><td>Conversion rate, CPA, ROAS, purchase frequency</td></tr>
</tbody>
</table>
<h2>Formulas</h2>
<div class="not-prose mt-4 mb-6 space-y-3">
<div class="rounded-lg bg-gradient-to-r from-primary/5 to-primary/[0.02] border border-primary/10 px-5 py-3.5 font-mono text-sm">
ASP = Total Revenue ÷ Number of Deals Closed
</div>
<div class="rounded-lg bg-gradient-to-r from-primary/5 to-primary/[0.02] border border-primary/10 px-5 py-3.5 font-mono text-sm">
AOV = Total Revenue ÷ Number of Orders
</div>
</div>
<p>Prefer net revenue (after discounts and refunds) for operational targets. List-price averages can help packaging analysis, but net averages should drive CAC/CPA ceilings and ROAS targets.</p>
<h2>Worked Example</h2>
<p><strong>SaaS (ASP):</strong> $480,000 in closed-won ARR across 40 deals → ASP = <strong>$12,000</strong>. That ASP informs how much CAC the GTM team can afford and how many deals are needed for a revenue goal.</p>
<p><strong>Ecommerce (AOV):</strong> $240,000 in revenue across 3,000 orders → AOV = <strong>$80</strong>. That AOV informs free-shipping thresholds, upsell strategy, and maximum CPA for paid traffic.</p>
<h2>When to Use Each</h2>
<p><strong>Use ASP when:</strong> you sell contracts or subscriptions, forecast pipeline by deal size, set sales quotas, or compare packaging tiers.</p>
<p><strong>Use AOV when:</strong> you optimize carts and checkout, run ecommerce ads, set merchandising rules, or model revenue from traffic × conversion × AOV.</p>
<h2>Common Mistakes</h2>
<p><strong>Mistake 1: Treating ASP and AOV as interchangeable.</strong> They answer the same conceptual question in different models. Mixing labels confuses finance and marketing.</p>
<p><strong>Mistake 2: Optimizing ticket size without volume.</strong> Doubling ASP while halving closes leaves revenue flat. Always pair with deal or order count.</p>
<p><strong>Mistake 3: Using list price after heavy discounting.</strong> Net ASP/AOV is what should set acquisition ceilings.</p>
<p><strong>Mistake 4: Not segmenting.</strong> New vs returning, channel, and product mix often have very different averages. Blended figures hide the lever you can pull.</p>
<h2>How They Connect to Other Metrics</h2>
<ul>
<li><strong>CAC / CPA:</strong> Higher ASP or AOV generally supports a higher affordable acquisition cost.</li>
<li><strong>LTV:</strong> In SaaS, LTV often scales with ASP and retention. In ecommerce, LTV scales with AOV × purchase frequency × retention.</li>
<li><strong>ROAS:</strong> For paid media, revenue per conversion is often driven by AOV (or ASP if you sell higher-ticket self-serve plans).</li>
<li><strong>Budget planning:</strong> Revenue goal ÷ ASP (or AOV) = deals (or orders) required, which reverse-engineers traffic and spend needs.</li>
</ul>
<h2>Sources and Benchmarks</h2>
<p>ASP and AOV ranges vary widely by category and pricing model. Treat published benchmarks as directional only. For methodology and related definitions, see our <a href="/guides/asp-and-aov-guide/">ASP and AOV guide</a> and <a href="/disclaimer/">disclaimer</a>.</p>
<h2>The Bottom Line</h2>
<p>Use ASP for deal-based revenue and AOV for order-based revenue. Same math shape, different business unit. Calculate with our <a href="/calculators/asp/">ASP Calculator</a> or <a href="/calculators/aov/">AOV Calculator</a>, then connect the result to CAC, LTV, and ROAS.</p> No. Both measure average revenue per transaction unit, but ASP (Average Selling Price) is typically used for B2B and SaaS deals or contracts, while AOV (Average Order Value) is used for ecommerce and retail orders. Using the wrong label confuses teams and can distort forecasting.
Use ASP when revenue comes from closed deals, subscriptions, or contracts with a sales or packaging motion. Use AOV when revenue comes from cart checkouts and you care about revenue per order for merchandising and paid media.
Higher ASP or AOV usually supports a higher affordable CAC or CPA, and both feed lifetime value when multiplied by retention or purchase frequency. Always pair average ticket size with volume and margin—raising ASP while cutting deal count can leave revenue flat.
Use net revenue after discounts and refunds for operational accuracy. Gross list price can be useful for packaging analysis, but net ASP/AOV is what should inform CAC targets and ROAS.