top of page
Oct 23
7 min read

Updated: 10 hours ago

Klaviyo Replenishment Flow: Time the Reorder Around Product Use


Updated 21 November 2026


Thrivelia guide: Klaviyo Replenishment Flow: Time the Reorder Around Product Use

A Klaviyo replenishment flow should remind a customer to reorder before their usable supply runs out. Start with the product, purchased quantity, likely usage and delivery time. Then check that the customer still needs the reminder when it is due. A universal 30-day delay misses those decisions.


Replenishment fits products with a credible repeat-use cycle. Winback addresses a customer who has gone beyond a reasonable return window. Keep those purposes distinct so two journeys do not make the same reorder request. Our Klaviyo winback guide covers the later lapse question.


Is a Klaviyo reorder flow worth adding SMS to?


I’d start with one SKU and one question. Does a refill text earn an extra order from a one-time buyer who already receives the reminder email? If a customer placed a second order before the scheduled text, the answer for that person is already clear. Stop the reminder and keep them in the measurement group they were originally assigned to.


With supplements, a two-pack, a single bottle and a subscription can look similar in the order feed. The reminder date and the reason to send it are different for all three. See the supplement reorder SMS timing, sample copy and holdout test.


Estimate the buying interval before building the timer


Review repeat purchases by product or useful product family, separating pack sizes and quantities. Give recent buyers enough observation time before judging whether they returned. Compare first-time buyers with established repeat customers, and inspect the range rather than relying on one average.


Use expected consumption as a starting hypothesis when purchase history is limited. Account for delivery, delayed first use, household sharing and stockpiling. Observed buying intervals can include behaviour beyond consumption, such as waiting for a promotion. Record the assumption you are testing instead of presenting it as a known depletion date.


Use the qualifying order to start the flow


Klaviyo's replenishment setup guide uses Placed Order as the metric trigger. For a product-specific flow, qualify the triggering order with a trigger filter, such as Items contains the relevant product name. Start from an integration-matched template where available and inspect its defaults.


A historical profile condition saying someone once bought the product does not establish that the new order contains it. Trigger filters and profile filters serve different purposes: use event data for the qualifying purchase and profile eligibility for conditions that must remain true later.


Validate quantity before promising quantity-based timing


Inspect the integration's actual event payload and available filters. Shopify's data reference says Item Count counts line items, not units. It also says each Shopify Ordered Product event has Quantity equal to one, including when multiple units of an item are purchased. Do not assume either field gives you the total supply of a specific SKU.


Build separate timing paths only when the relevant product quantity or pack-size information is exposed in a usable, tested form. If it is missing, work with the integration owner to supply reliable data or begin with a simpler product cohort. An impressive branch diagram cannot compensate for the wrong quantity.


A fictional tablet refill example


Imagine a fictional household brand selling packs of 30 dishwasher tablets. For this example only, assume one tablet per day, three days to receive the original order, three days for replacement delivery and a two-day buffer. These are planning assumptions, not benchmarks or client results.


Verified purchase

Estimated runout from order

First reminder hypothesis

One pack: 30 tablets

Day 33: delivery plus 30 days of use

Day 28: runout minus replacement delivery and buffer

Two packs: 60 tablets

Day 63: delivery plus 60 days of use

Day 58, subject to observed buying behaviour


The one-pack message might say: “Time to check your tablet supply? Reorder your usual pack here.” It asks the customer to assess their stock without claiming they are definitely running out. Show the correct pack and a clear product link. Test a follow-up only if it adds value; an automatic discount is unnecessary.


Keep reorder checks specific to the product


For a product-specific reminder, start with Placed Order zero times since starting this flow, narrowed to orders containing that product or an intentionally defined substitute family. Otherwise, an unrelated accessory purchase can stop a useful refill reminder. Keep the trigger and purchase check on the correct integration's Placed Order metric.


The Shopify reference warns that Placed Order and Ordered Product sync seconds apart: mixing the first as the trigger with the second as a since-entry exclusion can skip recipients because of the original purchase. Test actual events rather than treating similarly named metrics as interchangeable.


Profile filters are checked again before actions. A failed check skips that action, rather than necessarily removing the customer from every later step. A correctly scoped reorder condition should keep the old reminder sequence ineligible after the relevant repurchase.


Check current re-entry criteria in your account. New metric flows default to Allow re-entry, while rollout and existing configurations can differ. Permit future qualifying purchases to start an appropriate cycle; an arbitrary long frequency gate can block a legitimate early reorder. Test the old and new cycles together.


Coordinate subscriptions, multiple products and channels


  • Exclude an active subscription for the relevant product when reliable current subscription data supports that decision. Someone subscribing to a different product may still need this reminder.

  • For mixed baskets, choose which product reminders can run together. Define message priority and frequency rather than launching overlapping timers without coordination.

  • Treat cancelled orders, returns and refunds as changes to the supply assumption. Use the data your integration actually provides and a documented fallback for missing information.

  • Check email marketing eligibility separately. Klaviyo's SMS replenishment guidance requires SMS marketing consent; possessing a phone number is insufficient.


Plan what happens when a stockout interrupts the cycle

A replenishment timer can reach its due date while the product is unavailable. That does not make the customer uninterested, and returning inventory does not prove they are still waiting. They may have bought a substitute elsewhere, changed their routine or placed another order through a different channel.

Define a deliberate unavailable-product treatment with the implementation and merchandising owners. Pause the purchase invitation, offer a genuinely suitable available alternative, or direct the customer to a requested restock notification where that route exists. Do not promise an automated stock check unless the integration and flow actually support it. Review the exact product or variant, market and buying destination.

Do not release every overdue reminder on restock day

Before resuming, review the waiting population, current marketing eligibility, recent purchases, product availability and overlapping messages. A requested stock alert and a general replenishment reminder should not create two competing conversations about the same item. Choose the appropriate treatment and document which journey owns it.

Klaviyo's back-in-stock behaviour documentation says the initial stock-waiting step does not recheck inventory before a second message after the alert. A later replenishment or recovery message therefore needs its own validated availability decision; the earlier alert is not ongoing proof of stock.

A new qualifying purchase can establish a new supply cycle under the tested purchase rules. A restock event by itself cannot. Keep the product-specific reorder exclusion aligned with the actual purchase, so an unrelated accessory order does not accidentally remove the customer from the relevant refill journey.

Keep the interruption visible in reporting

Compare customers with complete observation windows and record when their relevant products were unavailable. A restock campaign can capture accumulated demand while new acquisition is still recovering. That does not establish a normal campaign-to-flow revenue mix or prove a new message caused the rebound.

Retain the actual retention result and show availability as context. The retention-measurement guide explains how to avoid rewriting the denominator around an inconvenient stockout. Use the restock implementation guide for the separate request, inventory and notification checks.

Launch tests that catch expensive mistakes


Test one pack, multiple packs, a mixed basket, an unrelated purchase and a same-product reorder during the delay. Add an active product subscriber, cancelled order, full refund, partial refund and unsubscribed profile. Shopify's Refunded Order event covers full refunds; a partial refund needs separate verification.


Test missing data, discontinued products and the exact variant's availability. Shopify's catalog publication rules do not make a product-level availability check proof that every variant is purchasable. Inspect the final link, product selection, mobile rendering and recipient skip reasons. Use our flow build guide for the wider implementation process.


Measure whether the reminder changes customer behaviour


Track product-level reorder rate, time to reorder and contribution after discounts and relevant variable costs, using a complete observation window. Monitor complaints and unsubscribes. Where volume permits, randomly assign eligible customers to a reminder group and a holdout, keeping other treatment comparable.


Attributed revenue can include orders customers would have placed anyway. Compare outcomes over enough time to distinguish additional purchases from purchases merely brought forward. Connect replenishment to the education and product experience in your post-purchase strategy.


Frequently asked questions


Should every replenishment flow send after 30 days?


No. Set the hypothesis from product use, quantity, delivery and comparable customers' buying intervals. Validate the timing before applying it across pack sizes or categories.


Should any new order stop the reminder?


Only if that matches the intended journey. A product-specific replenishment flow usually needs a product-qualified reorder check so unrelated purchases do not suppress it. Define whether substitutes count as replenishment.


How is replenishment different from winback?


Replenishment helps maintain a plausible product-use cycle. Winback investigates a lapse after a reasonable return opportunity has passed. Coordinate the handoff instead of escalating the same reminder indefinitely.


Thrivelia's Klaviyo agency services and focused flow rebuild connect the buying-cycle diagnosis to the data, messages and eligibility rules required to run it.

Check subscription incentives and changing product paths

A replenishment message can conflict with the commercial objective if a one-time campaign offers a better deal than the intended subscription path. Review the whole offer calendar, eligible customer state and retained contribution before adding another incentive.

Use observed paid orders and current product usage rather than assuming a nominal 30-day supply is reordered in 30 days. New acquisition bundles, different delivery cadences and stock changes can make old SKU paths a poor guide. Separate active subscription status from a paid repeat order, and give cohorts equal time to mature.

Thrivelia connects product-path analysis with the actual message, offer and exclusion logic. The subscription journey guide sets out the wider state model; our baseline guide explains why natural cohort maturation must be treated carefully in a performance agreement.


Compare predicted timing with the product cycle


Klaviyo’s expected next-order date does not consider which products were bought. The predictive analytics guide explains when that estimate can support a timing test and why a known replenishment cycle may provide better evidence.

 
 
 

Recent Posts

See All

Comments


Commenting on this post isn't available anymore. Contact the site owner for more info.
bottom of page