[Retention & lifecycle]() / [Use cases]() / [Replenishment timing]() [How it works]() [What you get]() [Scope]() [Start a review]() [Retention & lifecycle]()[Second orders]() # 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. [Start with a retention review]() [How it works]() Fernway Outfitters Day 45 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. Care KitCanvas wash and wax bar · $28 · $10 off Send another 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. ShowTodayWith the engine Timing The same delay after every order Each product’s cycle, counted from delivery What was bought One reminder for one bottle or three Days of supply from the quantity and the date it arrived When we’re unsure A guess, sent anyway A question: need more, or have enough? Stopping The reminder lands after they’ve reordered It stops on a reorder, a subscription or a “later” ## How it works. 6 steps, 4 stages. - AI**2** - Rules and automation**2** - Your team**2** - Approval 1. 1 Record 1. Rules and automation ### Record what arrived, and when Delivered quantities, subscriptions and returns, by product and customer. - Shopify - Recharge 2. Your team Approval ### Set each product’s cycle Merchandising decides how long a product lasts, and which ones don’t need a reminder. 2. 2 Estimate 1. AI ### Estimate days of supply left From the cycle, the quantity and the delivery date. Gifts and missing dates are flagged, not guessed. 3. 3 Ask 1. 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 4. 4 Adjust 1. AI ### Read the answer A “later” sets a new date, “have enough” pauses the reminder, and anything unclear goes to your team. 2. 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. Eligibility record · Care Kit 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. Cycle rule Care Kit 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. 1. Repeat purchasers per eligible customer Counted against a held-back group, so the reminder isn’t credited for orders that were coming anyway. 2. Time to the repeat order Shows whether the reminder lands before customers run out, or after. 3. 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. 1. 1 Design 2. 2 Build 3. 3 Run it, or hand it over [Start with a review]() [Scope this build]() ### 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]() 1. [Second orders **3**]() 2. [Subscribers **3**]() 3. [Contact that fits **1**]() 4. [Owners & loyalty **2**]() 5. [Lifecycle production **1**]() 6. [Proof & decisions **2**]() In second orders - **Replenishment timing**You’re here - [**Second orders**Turn first orders into second orders]() - [**Winback**Win back customers at the right moment]() Works with - [**Subscriber control**Let subscribers skip, delay and swap without canceling]() - [**Retention proof**Prove which messages and discounts earn their cost]() See it at work - [**In Fernway’s ninety days**Day 45: the reminder asked if she needed more]() ## Remind them when it’s time. Start with a retention review. [Start with a retention review]() [**Talk it through first**15 minutes]() We reply within one business day. --- Source: [https://www.thekeating.co/use-cases/replenishment-timing/]() [Contact Keating & Co](mailto:nelson@thekeating.co) · [Agent guidance](https://www.thekeating.co/llms.txt)