Time the reorder to when customers actually run out.
A reorder reminder that waits until the customer is running low, and asks instead of guessing.
Running low?
Your Care Kit arrived on October 16. Need another, or do you have enough? Tell us either way. If you need one, here’s $10 off.
Held while a problem is open on the order
Sent when the kit is due to run low. One question, and it stops the moment they reorder.
Sound familiar?
- Everyone gets the same reminder 30 days after they buy.
- The predicted next-order date treats a 90-day kit and a 30-day refill the same.
- Customers who already subscribed still get nudged to reorder.
A reminder that lands too early gets ignored. One that lands too late arrives after they’ve bought somewhere else.
What changes.
- Timing
- The same delay after every orderEach product’s cycle, counted from delivery
- What was bought
- One reminder for one bottle or threeDays of supply from the quantity and the date it arrived
- When we’re unsure
- A guess, sent anywayA question: need more, or have enough?
- Stopping
- The reminder lands after they’ve reorderedIt stops on a reorder, a subscription or a “later”
How it works. 6 steps, 4 stages.
- AI2
- Rules and automation2
- Your team2
- Approval
1Record
Rules and automation
Record what arrived, and when
Delivered quantities, subscriptions and returns, by product and customer.
- Shopify
- Recharge
Your teamApproval
Set each product’s cycle
Merchandising decides how long a product lasts, and which ones don’t need a reminder.
2Estimate
AI
Estimate days of supply left
From the cycle, the quantity and the delivery date. Gifts and missing dates are flagged, not guessed.
3Ask
Rules and automation
Send the question
Need more, or have enough? One tap either way, by email or SMS. Held while anything is open on the order.
- Klaviyo
- Attentive
4Adjust
AI
Read the answer
A “later” sets a new date, “have enough” pauses the reminder, and anything unclear goes to your team.
Your team
Review the corrections
Lifecycle and merchandising see where estimates were off, and adjust the cycle.
Corrections tune each product’s cycle
What you get. Real work, every week.
| Customer | Supply left | Reason | Next step |
|---|---|---|---|
| Priya S. | 6 days | One kit | Ask now |
| Marcus T. | 9 days | One kit | Ask now |
| Jo R. | Unknown | Gift purchase | Broad message |
| Ellis K. | None needed | Already subscribed | Excluded |
The eligibility record. Your lifecycle lead sees why each customer is, or isn’t, getting a reminder.
Ask when about ten days of supply are left.
- Cycle
- About 90 days for a regular washer
- Clock starts
- At delivery, not at order
- Stops on
- A reorder, a subscription or “have enough”
- Unknown
- Gift, or no delivery date: ask, don’t guess
The cycle rule merchandising signs off, written so the next person can read it.
How you’ll know it’s working.
Repeat purchasers per eligible customer
Counted against a held-back group, so the reminder isn’t credited for orders that were coming anyway.
Time to the repeat order
Shows whether the reminder lands before customers run out, or after.
Timing corrections and unsubscribes
Replies like “still have plenty” show where the estimate was off, and unsubscribes show where it was too early.
Baselines agreed before we build.
Works with what you have.
Commerce
- Shopify
- Recharge
Email & SMS
- Klaviyo
- Attentive
- We configure first
- Klaviyo’s predicted next-order date and Shopify Flow cover a simple reminder. We start there, with one flow per product family.
- We build when
- Quantity, delivery dates or subscriptions change who should get a reminder, and the built-in prediction can’t see the product.
What a first build includes.
Built in your accounts, around your team. Scope, fee and baseline agreed before we start.
- 1Design
- 2Build
- 3Run it, or hand it over
We build
- A cycle table for each product family
- Days-of-supply logic from quantity and delivery date
- A reminder that asks, with one-tap replies
- An eligibility record and a correction log
We start from
- Order and delivery history
- Subscription records
- Klaviyo and Shopify access
From your team
- Owner
- Head of lifecycle or CRM lead
- Involves
- Lifecycle
- Merchandising
- Operations
Questions teams ask.
Does this only work for consumables?
It works wherever a product gets used up or worn down: care kits, refills, filters, supplements. For a jacket there’s no clock to time, so the better move is a care guide and a second order, which is a different job.
Can’t Klaviyo already predict the next order?
Klaviyo’s predicted next-order date is built from order history, not from which product was bought, so a 90-day kit and a 30-day refill can get the same reminder. Klaviyo’s own documentation recommends separate product-based flows for different cycles, which is what we’d configure first.
What if we don’t know when it arrived?
We use the carrier’s delivery date where we have it, and the order date plus shipping time where we don’t. For gifts and missing dates, the reminder asks instead of guessing.
Who owns it once it’s running?
You do. It’s built in your accounts, documented, with training for the people who run it. Ownership usually sits with your head of lifecycle or CRM lead. We can keep running it with you, or step back.
How do we start?
Usually with a retention review: two to four weeks, a fixed fee credited to the build, and a plan that’s yours. If the job is already clear, we can scope the build directly.
Part of your retention engine. One of 12 use cases, in 6 parts.
See the whole retention engine- Second orders3
- Subscribers3
- Contact that fits1
- Owners & loyalty2
- Lifecycle production1
- Proof & decisions2
In second orders
- Replenishment timingYou’re here
- Second ordersTurn first orders into second orders
- WinbackWin back customers at the right moment
Works with
Remind them when it’s time. Start with a retention review.
We reply within one business day.