Average Order Value (AOV)

AOV

Average Order Value (AOV) is the mean revenue generated per individual transaction or purchase event. In SaaS, it most commonly applies to one-time purchases, annual plan upfronts, add-on purchases, and non-recurring charges. For subscription businesses, AOV is most relevant when tracking checkout transactions or annual plan conversions rather than monthly recurring revenue.

formula.sh

AOV = Total Revenue from Transactions / Number of Transactions

> Total Revenue from Transactions — sum of all transaction values in the period
> Number of Transactions — count of individual purchase events (not customers)
> One customer can have multiple transactions (upgrades, add-ons, renewals)
> For annual SaaS plans, AOV = annual plan value; useful for understanding checkout size distribution

example

example.sh

SaaS tool with 200 checkout transactions in Q1. Mix of monthly ($99), annual ($899), and enterprise ($4,999) plans. Total checkout revenue: $180,000.

$180,000 / 200

→ $900 AOV — skewed up by enterprise deals. Median order value may be closer to $99–$899 for typical distribution insight.

why it matters

AOV matters most in SaaS contexts where transaction size varies significantly — usage-based billing, professional services add-ons, annual vs monthly plan mixes, or per-project pricing. It helps identify whether customers are choosing premium options and whether your pricing presentation is effectively driving higher-value transactions.

Increasing AOV is often more efficient than increasing transaction volume because it does not require more traffic or leads. Tactics like annual plan incentives, bundle packaging, and strategic add-on placement at checkout can increase AOV by 20–50% with minimal engineering investment.

For products like mrrsucks.com with per-project pricing at $9, AOV tracks whether users purchase one project or multiple at checkout. A user buying three projects at once has an AOV of $27 — understanding this informs whether to offer bundle pricing.

common mistakes

✗Conflating AOV with ARPU — AOV measures transaction size, ARPU measures recurring revenue per user per period; they answer different questions.

✗Optimizing AOV without considering conversion rate impact — raising minimum order values or eliminating low-price tiers can increase AOV while decreasing total transaction volume.

✗Not segmenting AOV by customer type — first-time buyers, existing customers, and enterprise buyers will have very different AOV profiles.

pro tips

✓Test annual plan discount levels (20% vs 30% vs 40%) against AOV and conversion rate to find the optimal offer that maximizes expected value per checkout.

✓Build an AOV histogram to understand the distribution of transaction sizes — the shape reveals whether most revenue comes from many small transactions or few large ones.

✓Track AOV by acquisition channel to understand whether different channels attract higher-value buyers.

the mrrsucks take

AOV is proof of what customers think the value exchange is worth at the moment of purchase. If your AOV is low, your pricing presentation is either unclear or your perceived value at checkout doesn't match reality.

faq

Is AOV relevant for subscription SaaS?+

Less relevant than for ecommerce, but useful for SaaS when tracking annual plan checkouts, one-time add-on purchases, or multi-project pricing (like mrrsucks.com). Monthly subscription MRR is better tracked via ARPU/ARPA. AOV answers checkout-level questions.

How do I increase AOV?+

Annual plan incentives (discount for upfront payment), bundle pricing (combine plans at a discount), checkout upsells (add-ons shown during purchase flow), minimum quantity requirements for volume discounts, and enterprise packaging that bundles more value at higher price points.

$1K MRR milestone›

related metrics

./install-the-daemon

$9. 365 roasts. one public endpoint of pure shame.