How to find the revenue trapped in your order data
Years of order history is a balance-sheet asset nobody reads. Here are the five queries that turn it into segments, reorder windows, and win-back lists, plus the industry benchmarks that say how much that work is worth.
Who this is for: Distributors, retailers, and operators with 2+ years of order history and no analyst reading it
Why the value is invisible
Every order your company has ever shipped is a record of someone deciding to pay you. Stacked up over years, those records hold your best customers, your natural reorder cycles, the products that pull repeat business, and the exact accounts that quietly stopped buying. None of it shows up in your accounting reports, because accounting answers “what did we earn?” and not “who buys what, how often, and who is about to leave?”
The reason this matters is in the benchmarks. Industry retention studies consistently put 60 to 80 percent of revenue in mature businesses with repeat customers, and keeping an existing customer is widely cited as roughly five to seven times cheaper than acquiring a new one. The cheapest growth you have is usually revenue you already earned once. It is sitting in the order table, unread.
What trapped value actually looks like
Read a typical order history closely and four things tend to fall out:
- Two different businesses hiding in one P&L. Consumer and business buyers usually have very different average order values and reorder rhythms, and marketing often treats them the same. The gap between segments is your misallocation number. RFM segmentation (ranking customers by recency, frequency, and monetary value) commonly produces double-digit revenue lift over generic campaigns in vendor benchmarks, for this reason.
- Reorder windows nobody is using. Consumable and replaceable products get bought on cycles. A customer who bought N months ago is due, and a due customer who does not hear from you buys from whoever’s ad they see that week.
- Lapsed accounts with real history. Customers with multiple past orders and a long silence are the cheapest revenue available anywhere. Win-back programs report reactivation rates around 15 percent when they are sequenced rather than sent as a single blast.
- Product affinities that sell themselves. What gets bought together, and what a first purchase predicts about the second, is sitting in plain rows. It just has to be counted.
The five queries that find it
You do not need a data team for the first pass. You need order date, customer identifier, order total, and line items, exported to anything queryable.
- Segment split. Separate customer types (consumer vs business, or your equivalent) and compare average order value, order frequency, and lifetime total. The gap between segments is your marketing-misallocation number.
- Top-decile concentration. Rank customers by lifetime revenue. A small set of accounts usually carries an outsized share of the total. Name them, and ask when each last ordered.
- Reorder interval. For repeat customers, compute the median days between orders, per product category. That median is your contact calendar: anyone past their window is a win-back candidate.
- Lapse list. Multi-order customers whose silence exceeds twice their own median interval. Sort by lifetime value, descending. This is the win-back list, pre-prioritized.
- First-to-second order map. Of customers who only ever bought once, what did they buy? Of those who came back, what did they buy first? The difference tells you which first purchase predicts a relationship, and which products to put in front of new buyers.
From finding it to capturing it
The queries are the cheap half. Turning them into revenue means the segments feed your ad platforms as audiences, the reorder windows trigger contact on schedule, and the win-back list becomes a sequence someone actually sends every month, without a person remembering to do it. That is a system, and a spreadsheet is not. It is the difference between an interesting afternoon and a different P&L.
| Phase | Doing it yourself | With an operator |
|---|---|---|
| Export, clean, match identities | 1–3 weeks of evenings | Days, with the matching pitfalls already known |
| The five queries | A long weekend if SQL is comfortable | Included, with the numbers pressure-tested |
| Audiences + triggered sequences | 4–8 weeks, usually stalls here | Built and running in production |
| Keeping it alive | Whoever remembers | Automated; your team trained on it |
From raw export to revenue-generating system.
Not ready to talk to anyone?
Run the Capacity Check: five inputs, your number, no email required.
Referenced by