Replenishment and win-back emails depend on one number: how long customers usually wait before ordering again. Get the time between orders wrong and the reminder lands too early, when the customer still has plenty, or too late, after they bought elsewhere. Hello Retail’s guide to replenishment puts the problem simply: a single interval cannot fit a population with different consumption rates.
Most stores pick that interval from a benchmark or from the average gap between orders in their own data. Both are a start. The second has a flaw that is easy to miss, and fixing it changes the answer. This guide shows how to measure time between orders properly with a survival curve, using order data you already have in WooCommerce or Magento.
Benchmarks give you a starting range
Eightx published a 2026 benchmark of the median days between orders by vertical. It uses the median because order gaps are skewed, and it states that no single public report publishes this table, so the figures are assembled from several sources and portfolio observations.
| Vertical | Median days between orders | Typical range |
|---|---|---|
| Supplements and vitamins | 30 | 28 to 35 |
| Pet food and supplies | 30 | 25 to 45 |
| Food and beverage | 45 | 30 to 60 |
| Beauty and skincare | 75 | 60 to 120 |
| Apparel and fashion | 120 | 90 to 180 |
| Home goods and furniture | 270 | 180 to 365 |
| Consumer electronics | 365 | 270 to 730 |
The ranges are wide, and Eightx itself recommends calibrating against your own cohort data. Two stores selling skincare can differ by months depending on pack sizes and product mix.
Why the average gap between orders is too short
The obvious calculation takes every customer with two or more orders and averages the days between them. It ignores everyone who has bought once and not yet bought again. Some of those customers will reorder next week; others never will. Leaving them out keeps only the people who came back, and among recent customers the only ones who have come back are the quick ones. The result is an interval that is too short.
Statisticians call those dashed lines censored observations, and the problem is old. Drye, Wetherill and Pinnock wrote in 2001 that, for this kind of time-to-event data, simple means and summary statistics can be seriously biased and misleading. In one of their examples, a simple mean put average membership at just over four years, while the estimate that accounted for censoring was nearly seven. Our post on lost sales from stockouts deals with the same kind of hidden data on the demand side.
Measuring time between orders with a survival curve
A survival curve, usually estimated with the Kaplan-Meier method, answers a better question: of the customers who bought on day 0, what share has not yet reordered by day t? Customers who have not reordered still count, up to the day you observe them, and then drop out of the calculation without being treated as either reorders or losses.
Build the durations
Each row is one order, the number of days to that customer’s next order, and whether the next order has happened. In WooCommerce, wc_order_stats carries a customer_id that points to wc_customer_lookup, the table WooCommerce Analytics uses to identify customers, including guests by email. This query needs MySQL 8 or MariaDB 10.2 or later.
WITH o AS (
SELECT s.customer_id, DATE(s.date_created) AS order_date
FROM wp_wc_order_stats s
WHERE s.status IN ('wc-completed', 'wc-processing')
AND s.parent_id = 0
),
seq AS (
SELECT customer_id, order_date,
ROW_NUMBER() OVER (PARTITION BY customer_id ORDER BY order_date) AS n,
LEAD(order_date) OVER (PARTITION BY customer_id ORDER BY order_date) AS next_date
FROM o
)
SELECT customer_id, n,
DATEDIFF(COALESCE(next_date, CURDATE()), order_date) AS days,
next_date IS NOT NULL AS reordered
FROM seq;
For product-level replenishment, add a filter so the next order must contain the same product or category. On Magento, the same query runs on sales_order, grouped by customer_email so guest orders are included.
Fit the curve
The Python library lifelines has a ready-made KaplanMeierFitter that takes exactly these two columns.
import pandas as pd
from lifelines import KaplanMeierFitter
df = pd.read_csv("order_gaps.csv") # customer_id, n, days, reordered
first = df[df.n == 1] # time from first to second order
kmf = KaplanMeierFitter()
kmf.fit(first["days"], event_observed=first["reordered"])
print(kmf.survival_function_at_times([14, 30, 45, 60, 90, 180]))
Fit separate curves for first-to-second and later orders. A first-time buyer and a fifth-time buyer behave differently, and the second purchase is usually the one a flow is trying to win.
Reading send times off the curve
When fewer than half of customers ever reorder, the median time to reorder does not exist, because the curve never falls below 50 percent. A more useful approach is to work with the share who eventually reorder. In the example below, 38 percent of first-time buyers reorder within six months. The timing points are read as fractions of those eventual reorders.
| Measure | Naive average | Survival curve |
|---|---|---|
| Customers used | 1,100 who reordered | All 4,000 first-time buyers |
| Share who reorder within 180 days | Not available | 38% |
| Day by which a quarter of reorders have happened | Not available | Day 30 |
| Typical gap | 34 days (mean of repeaters) | Day 41 (half of eventual reorders) |
| Day by which 90% of reorders have happened | Not available | Day 95 |
Those numbers translate directly into a flow. Send the replenishment reminder a few days before reorders start to pick up, here around day 26 to 28. Send the win-back after most reorders that are going to happen have happened, here around day 95; a customer who has not ordered by then is behaving like the 62 percent who never do. Hello Retail’s guide also recommends suppressing the reminder if the customer bought in the last seven days, and adjusting for pack size, since a larger pack lasts longer.
Segments worth a separate curve
| Segment | Why it differs | What changes in the flow |
|---|---|---|
| Product or category | Consumption cycles differ | Separate reminder day per product |
| Pack size | A larger pack lasts longer | Scale the day by quantity bought |
| Order number (first, second, later) | Loyal customers reorder faster and more reliably | Shorter interval and less incentive for repeat buyers |
| First order on a discount | Discount-led buyers often reorder less | Expect a lower plateau; judge the flow on its own baseline |
| Acquisition channel | Gift buyers and marketplace shoppers rarely replenish | Exclude or send a different message |
To compare segments over time, line them up by the month of first order. QuantumLayers covers how to read that kind of table in Cohort Analysis; a survival curve is the same idea measured in days instead of calendar months.
Checking that the new timing works
- Keep a random 10 percent of eligible customers out of the flow as a holdout.
- After two full cycles, compare the survival curves of the emailed group and the holdout.
- Look at the gap between the curves, not the email’s click or conversion rate; some of those orders would have happened anyway.
- If the curves only separate after the reminder date, the timing is right. If they separate before it, customers were already reordering and the reminder came late.
- Refit the curves each quarter; pack sizes, prices and the product mix change the answer.
Sources
- Hello Retail, Replenishment emails: How to time re-orders to each customer’s refill moment
- Eightx, Average Days Between Orders by Vertical: 2026 Benchmark (June 2026)
- Drye, Wetherill and Pinnock, When are customers in the market? Applying survival analysis to marketing challenges, Journal of Targeting, Measurement and Analysis for Marketing, 2001
- lifelines, KaplanMeierFitter documentation
- WooCommerce, Installed database tables
- QuantumLayers, Cohort Analysis


