Every consumable Shopify brand has the same flow: an email that fires 30 days after purchase, built in an afternoon, named something like "Replenishment v2." And every operator who checks honestly finds the same thing — it converts a little, annoys a little, and mostly gets ignored. The flow isn't broken. The assumption under it is: that your customers consume on the same clock. They don't, and that single fact is the gap between a timer and a revenue channel.
What a fixed-delay flow actually assumes
A 30-day replenishment flow encodes three guesses: that everyone finishes the product in 30 days, that everyone bought one unit, and that a reminder is welcome regardless of what happened since. All three fail constantly. The customer who bought three bottles gets nudged with two still sealed on the shelf. The daily user ran out on day 22 and already reordered from an Instagram ad — your email arrives as noise after the sale you lost. The gift buyer was never going to reorder at all. Multiply those misses across a five-figure customer base and the "working" flow is leaking most of its potential — timing errors don't just miss revenue, they train customers to skim past you.
What per-customer timing changes
Replenishment AI inverts the model: instead of one timer for the list, it builds one schedule per customer-product pair from actual order history. Bought the 90-serving tub twice, 41 days apart? The model knows your real consumption isn't the label's suggested 90 days, and the nudge lands around day 38. First-time buyer? Start from the product's typical window, tighten with every reorder. The mechanics that matter on top of the timing:
- One-tap reorder carts — the message carries the customer's own products, prefilled, Shop Pay ready. Every step you remove between "oh right, I'm almost out" and a paid order shows up directly in conversion.
- Suppression as a feature — any purchase, support ticket, or unsubscribe instantly silences the sequence. Fewer, better-timed messages consistently beat volume; send counts typically drop while revenue rises.
- A winback ladder past the reorder window — customers two cycles overdue get an escalating sequence where the discount is the last step, not the opener, so recovered orders mostly return at full margin.
The honest comparison
To be fair to Klaviyo: it's excellent infrastructure, and none of this replaces it — in our builds Klaviyo or Postscript usually remains the sending layer. The gap is intelligence, not delivery. Klaviyo's native flows give you segments and fixed delays; predicted-date features help but stay coarse and list-shaped. What they don't do is model consumption per customer per SKU, build the one-tap cart, orchestrate winback escalation, and self-correct as buying rhythms drift. That layer — the replenishment engine — sits above the sender and makes it precise.
In revenue terms, the published typicals for reason-timed replenishment across consumable brands: 15–25% of reminded customers place a reorder, and repeat-purchase revenue lifts 20–40% within a quarter or two. Our supplements deployment landed at 21% and +34% — with total send volume down versus the blast calendar it replaced.
How to know which one your store needs
Fixed flows are the right tool when your catalog has one dominant SKU with a genuinely uniform consumption cycle and your customer base is small enough that timing errors cost little. The moment you have multiple consumables, size variants, or enough history that customers visibly buy on different rhythms, the fixed timer is leaving the majority of your repeat-purchase opportunity on the table. Quick self-test: export reorder intervals for your top SKU and look at the spread. If the histogram is a spike, keep the flow. If it's a hill — and it's almost always a hill — your customers just told you why the 30-day timer can't work.