Last quarter I kept hearing "traffic looks fine, new customers look fine" from an EC operator I was advising. Revenue still drifted down month after month. No one could explain it until we split the revenue line in two: new customers versus repeat customers. The repeat line was falling. Churn was eating the business quietly, and new acquisitions were papering over the gap.
TL;DR
- Churn rate = the share of customers who stop buying in a given period — not just subscription cancellations, but EC repeat buyers who quietly disappear
- New customers offset the loss, so total customer count stays flat while the quality degrades inside
- Two types with different fixes — voluntary churn (customers leave by choice) vs. payment-failure churn (card expired, nobody noticed)
- Three reasons it's hard to see — averages dilute the signal, there's a time lag, and failed payments are silent
- First move — track repeat-customer revenue separately over time; if the total is flat but the repeat line is falling, that's the signal
Why new customers hide the problem
When new inflow equals outflow, customer count stays flat. The leaky-bucket intuition is real: you can keep pouring water and the level never moves. What changes is the composition. Long-term repeat buyers — who buy more often and spend more per order — get replaced by brand-new buyers who've only ordered once.
Acquiring a new customer costs more than retaining an existing one, so the swap is doubly expensive: you pay more for a customer who buys less.
Voluntary churn vs. payment-failure churn
These two look the same in your revenue report but need opposite responses.
Voluntary churn is intentional: the customer decided to leave. Fixing it means improving your product, pricing, or loyalty loop — real work on the underlying experience.
Payment-failure churn is accidental: the customer's card expired or hit its limit. They didn't decide to leave. A simple notification — "update your card" — brings many of them back. No product changes needed.
Mixing the two wastes effort. Sending loyalty re-engagement offers to people whose card just expired changes nothing.
Three reasons churn stays invisible
Averages smooth it out. "Average purchase count" blends your loyal high-frequency buyers with churned customers who bought once. The loyal buyers carry the average. By the time the average dips, the damage is already months old.
Time lag. Customers don't announce they're leaving. They drift away. The revenue impact shows up three to six months after the behavior change — by which point the gap is large.
Payment failures are silent. A failed charge doesn't appear in your revenue report as "lost revenue." It just doesn't appear at all. Unless you actively check the payment-failure list, you won't know it's accumulating.
Three moves in order of priority
- Split repeat-customer revenue over time. Don't wait for the total to fall. Watch the repeat-only line month by month. If it bends down while total is flat, you have a churn problem.
- Pull the at-risk segment. RFM analysis surfaces customers who used to buy regularly but haven't recently. Flag them early, before the recency gap widens into permanent departure.
- Check payment failures weekly. Pull the list, send the update-card email. This is the fastest ROI move in churn management.
One thing to be honest about
I should be clear: churn rate as a precise number — down to the decimal — requires a CRM-level model per customer. What I'm building with RevenueScope isn't that. It shows revenue split by new vs. repeat customers, by channel, over time — enough to catch the signal early, before the precise diagnosis is needed.
Most EC operators don't need the decimal first. They need to know whether repeat revenue is bending down or not. That's the thing to fix before optimizing anything else.
What's the earliest signal you've found for catching churn before it shows in the revenue line?
Top comments (0)