Updated · 7 min read
Replenishment emails: the lifecycle flow that buys itself
A user buys coffee beans. Three weeks later, they're running low. Four weeks later, they've bought another brand from a grocery store because yours didn't ask. Replenishment is the low-cost intervention that prevents that switch — and it's the highest revenue-per-send lifecycle flow most programs aren't running.
By Justin Williames
Founder, Orbit · 10+ years in lifecycle marketing
What makes replenishment different
Replenishment applies to consumable products: coffee, skincare, pet food, vitamins, contact lenses, household supplies. Purchase cycle is predictable — buy, use, run out, buy again. The email catches users at the "run out" moment.
User has already chosen your product once. They're satisfied enough to be re-orderable. The replenishment email doesn't persuade. It reminds, and makes the re-order one click.
Revenue per send in replenishment is typically 5–15× marketing broadcast because the intent is already there. The email's job is closing the gap between "user is running out" and "user notices they're running out and remembers where to buy". That's a smaller gap than any other lifecycle trigger closes, which is why the revenue per send is so high.
The three-message structure
Message 1: Anticipated depletion reminder. Timing: 5–7 days before the user's typical re-order window, calculated from purchase history. Subject: "Running low on [product]?" Content: one-click re-order of the same product, estimated delivery date, link to adjust quantity or subscription if relevant.
Message 2: "You might be out by now" nudge. Timing: 10 days after message 1 if no re-order. Subject: "Time to restock [product]". Content: re-order CTA, subtle urgency, alternative sizes if relevant. Catches users who meant to re-order and forgot — a non-trivial share.
Message 3 (optional): Subscription nudge. Timing: 30 days after original purchase if still no re-order. Subject: "Never run out — set up auto-delivery". Content: subscription pitch with discount, explaining the convenience. Converts one-time buyers into subscribers. Lower conversion than messages 1 and 2, but higher LTV impact when it lands.
,
The timing calculation
"Anticipated depletion" date is the hardest part. Three approaches, simple to sophisticated:
Category default. Every product has a default depletion window — coffee 30 days, skincare moisturiser 45 days, 5kg dog food 60 days. Use the category default unless you have user-specific data. Simple, fast to ship, acceptably accurate for most products.
Per-user average. For a user who's re-ordered multiple times, use their own average re-order interval. Someone who reliably re-orders coffee every 21 days gets message 1 on day 15. More accurate for returning customers. Requires historical data.
Product-plus-size-plus-household. Someone who buys the 1kg bag depletes faster than someone who buys 5kg. A household-size signal (from signup data or past purchases) refines further. Lifts accuracy 20–30% over category default but requires attribute data most programs don't have cleanly.
Start with category default. Move to per-user average once you have six-plus months of repurchase data. Only build the size/household model if the revenue justifies the engineering. Most programs don't need to, and most programs that do it anyway don't measure the actual lift.
Subscription as the endgame
Replenishment email is fundamentally a workaround for users who haven't subscribed yet. Long-term play is subscription — auto-ship at the predicted interval, clear path to pause or cancel.
Treat replenishment as subscription-funnel touches, not just one-off reminders. Every replenishment email should have a subtle "or set up auto-delivery and skip the reminders" option. Path from one-time buyer → replenishment responder → subscriber is the LTV compound that makes consumable businesses actually work.
Measure subscription conversion from replenishment separately from one-time re-order conversion. A 10% subscription conversion is worth 3× more LTV than a 30% one-time re-order.
Why not push everyone to subscription from day one? Subscription has higher commitment cost for the user. Many first-time buyers aren't ready. Replenishment bridges the commitment gap — get them through a second and third one-time purchase, then convert when the product is clearly part of their routine. Pushing subscription too early actually suppresses first-purchase conversion, which is the worst of both worlds.
Measuring the flow
Re-order rate in next 14 days (holdout test): with replenishment sent vs suppressed holdout. Expected incremental lift: 15–30% on 14-day re-order rate for consumable categories.
Time-to-reorder: median days from previous purchase to next. Replenishment should shorten this by 5–10 days. Reminded users re-order sooner.
Subscription conversion from replenishment: percent of message recipients who set up auto-delivery. 2–8% is healthy. Below 1% means the subscription CTA isn't being noticed — usually because it's buried at the bottom of message three.
Revenue per replenishment send: typically $2–$10 per send for consumer consumables, vs $0.10–$0.50 for marketing broadcast. Order-of-magnitude difference is why programs that ship replenishment often see it as their largest lifecycle revenue line.
Some practical edge cases: if a user buys multiple consumables, run replenishment per-product, not per-user. Coffee buyer who also bought filters gets two parallel flows with different schedules. Cap combined frequency (no more than two replenishment messages per week per user) to avoid flooding high-LTV customers.
For non-consumables, replenishment works less directly. Closest analogue for durable goods is an "accessory or refill" prompt — camera owners buy SD cards, printer buyers need toner. Weaker signal than consumable depletion (timing less predictable, correlation weaker), but the structural play is the same.
For cancellation saves: the pattern is similar but the trigger is different. User about to cancel gets a "before you cancel" email. User who just cancelled gets a "we'll miss you + here's how to resume" email. These are cancellation-save flows and belong in their own sequence, not blended with replenishment.
places replenishment almost always first or second for programs with repeat-purchase consumable products. It's the flow with the clearest line from "user behaviour" to "revenue per send" and the rare flow where the ROI math is obvious inside the first month.
Related guides
Browse allBrowse abandonment: the program that sits between ads and cart
Browse abandonment catches the users who viewed a product and left without adding to cart. Smaller per-user lift than cart abandonment. Ten to twenty times the trigger volume. For most programs it's the biggest revenue lever you haven't shipped yet.
Referral program emails — the three flows that make it work
Referral programs live or die on the lifecycle messaging wrapped around them. Three flows matter: inviter prompt, invitee welcome, reward confirmation. Get the timing and copy right on each and you double conversion without touching the offer.
Trial-to-paid: the seven-email sequence that converts 20%+ of free users
Trial conversion is the most financially leveraged flow in SaaS — every percentage point compounds directly against CAC. Here's the seven-email sequence that reliably moves trial conversion from 5% to 20%+.
Price increase emails: how to raise prices without a churn spike
A price increase is one of the highest-risk lifecycle moments your program will ever run. Done wrong, it triggers churn, public complaints, and a reputation dent that outlasts the extra revenue. Done right, most users accept the change without friction. Here's the sequence that works.
Free shipping threshold emails: the cart-value nudge that reliably lifts AOV
A user with $45 in their cart and a $50 free-shipping threshold will add another item to cross the line — if they realise it. The right email at the right moment surfaces the gap and reliably lifts AOV by 5–15%.
Review request emails: the timing that actually produces reviews
A review request at the wrong time gets ignored. At the right time, it converts at 15–25% into a submitted review. Here's the timing, the message pattern, and why incentivising reviews almost always backfires.
Found this useful? Share it with your team.
Use this in Claude
Run this methodology inside your Claude sessions.
Orbit turns every guide on this site into an executable Claude skill — 54 lifecycle methodologies, 55 MCP tools, native Braze integration. Pay what it's worth.