Weekly ecommerce tips, deals & news.
Average revenue per user (ARPU) stands for average revenue per user. It’s your total revenue for a period divided by the number of users or customers in that same period.
Where average order value looks at a single transaction, ARPU looks at a person. It answers a different question: what is one customer actually worth to you each month?
Average revenue per user came out of telecoms and subscription software, where every customer pays on a cycle. It’s since crossed into ecommerce, and it fills a genuine gap in most stores’ reporting.
Divide total revenue for a period by the number of users in that period. The maths is trivial, and the definition is where it gets messy.
“User” can mean several things. It might be every registered account, every customer who ordered, or every unique visitor to the site.
Those produce completely different figures from identical revenue. Take a store with 50,000 visitors and 900 buyers. Counting buyers gives a number roughly 55 times larger than counting visitors.
So write your definition down and never change it quietly. Most stores are best served counting customers who placed at least one order in the period.
If you sell a monthly box or a recurring plan, average revenue per user is arguably your most important metric. Revenue arrives per customer per cycle by design.
It tells you immediately whether your customer base is getting more or less valuable. Growing subscriber counts with falling ARPU means you’re adding cheaper customers.
That’s a common trap during a discount-heavy push. Subscriber numbers look fantastic in the board pack while the unit economics quietly deteriorate.
For a subscription box, tracking ARPU alongside subscriber count catches that within a month or two.
Order-level metrics can look healthy while the business slowly weakens. Average revenue per user catches the difference.
Imagine your average order value holds steady all year. That sounds like stability, and it might be hiding a real problem.
Say customers used to order three times a year and now order twice. ARPU falls even though order value didn’t budge, and the per-transaction view can’t see it.
That’s why ARPU pairs naturally with repeat purchase rate and churn rate. Together they explain whether the change came from frequency, basket size, or people leaving.
Only three things raise average revenue per user, and it’s worth being clear about which one you’re pulling.
Retention is usually the cheapest lever of the three. Advanced Coupons has a useful rundown of the benefits of customer retention, including why repeat buyers upsell more readily.
The economics back that up. Harvard Business Review reports acquiring a new customer costs five to 25 times more than keeping an existing one.
Average revenue per user is an average, and averages hide their extremes. A handful of large accounts can carry the figure while most customers barely spend.
So look at the distribution occasionally, not just the mean. If your top 5% of customers generate most of your revenue, that’s a concentration risk your ARPU won’t mention.
Seasonality distorts it too. Compare the same period year on year rather than month against month.
A single store-wide average revenue per user tells you something changed. It rarely tells you what to do about it.
Split it by acquisition channel first. Customers from paid social often show a very different ARPU from those arriving through search.
That comparison changes budget decisions. A channel with lower acquisition cost can still be the worse investment if the customers it brings spend far less.
Splitting by cohort helps too. Group customers by the month they first bought, then watch each group’s ARPU over time.
Healthy cohorts hold steady or climb as customers settle into a buying habit. A cohort whose ARPU drops sharply after month one was probably bought with a discount rather than won.
Imagine a WooCommerce store called Kelburn Coffee, selling beans on both one-off orders and a monthly subscription. They want to know whether their customer base is improving.
In one quarter they take $180,000 from 4,000 customers who placed at least one order. Average revenue per user is $45.
Their average order value over the same quarter is $30. So the typical customer orders about one and a half times a quarter.
Those two numbers together are more useful than either alone. One describes the basket, the other describes the relationship.
The next quarter they run heavy discounting and revenue climbs to $210,000. That looks like a clear win.
However, customer count jumped to 5,600. Average revenue per user has fallen to $37.50.
They acquired 1,600 extra customers who each spend less than the existing base. Revenue rose while the average customer got less valuable.
That matters because acquisition isn’t free. If those cheaper customers cost the same to acquire, the payback on each one just got much worse.
Kelburn stops discounting to acquire and pushes the subscription instead. Subscribers order every month by default rather than when they remember.
They also add a grinder and filter range as cross-sells. That lifts basket size without touching the coffee price.
Two quarters later, revenue sits at $205,000 from 4,300 customers. ARPU has recovered to $47.67, above where it started.
Slightly less revenue than the discount quarter, from 1,300 fewer customers to serve. In practice, that’s a healthier business with lower fulfilment and support costs.
The subscription shift did most of the work. A subscriber contributes revenue every month without needing a fresh marketing touch.
Kelburn now reports ARPU beside revenue in every monthly review. Revenue alone had been telling them a story the second number corrected.
These are the two most commonly confused revenue averages, and the difference is simply what you divide by.
Average order value divides revenue by number of orders. It describes the size of a typical basket.
Average revenue per user divides revenue by number of customers. It describes the value of a typical relationship over a period.
Use order value when you’re optimising the checkout and the basket. By contrast, use ARPU when you’re judging marketing, retention, and customer quality.
ARPU also sits between order value and customer lifetime value. It’s a periodic snapshot, whereas lifetime value projects the whole relationship.
That middle position is why ARPU is easier to trust. Lifetime value depends on forecasting how long customers stay, and those forecasts are often optimistic.
ARPU only reports what already happened in a closed period. It’s less ambitious and considerably harder to fool yourself with.
There isn’t a cross-industry benchmark worth quoting. A furniture store and a coffee subscription will never be comparable.
Judge it against your own trend and against your acquisition cost. ARPU only really matters relative to what you paid to get that customer.
Customers, for most stores. Counting visitors turns ARPU into a blend of conversion rate and spending, which is harder to act on.
Whichever you choose, keep it consistent forever. A definition change mid-year makes your historical trend meaningless.
Yes, though you need a sensible period. Quarterly or annual works better than monthly for stores with infrequent purchases.
It’s most valuable when you’re spending on acquisition. Pair it with customer acquisition cost to see whether the customers you’re buying are worth the price.
Average revenue per user shifts your attention from transactions to relationships, which is where most ecommerce growth actually comes from. It’s the metric that exposes revenue growth built on cheaper customers rather than better ones. Define your user carefully, hold that definition steady, and watch the direction rather than the absolute figure.
Copyright © StoreOwnerTips.com. All Rights Reserved.
