How to Build a Klaviyo Win-Back Flow for Lapsed Customers

What is a Klaviyo win-back flow?

A Klaviyo win-back flow is an automated sequence sent to customers who haven’t ordered for longer than they normally would. In Klaviyo it’s usually built as a metric-triggered flow on Placed Order, with a long time delay before the first email and a filter that drops anyone who orders again in the meantime.

Win-back is for lapsed customers. It’s different from re-engagement or sunset flows, which deal with subscribers who have stopped opening and clicking, whether or not they’ve ever bought. The two often get blurred together. They have different triggers, different audiences and different end points, and this guide covers the first. The sunset side is in our Klaviyo deliverability guide.

How the Placed Order trigger works for win-back

The trigger looks backward at first. Why start a win-back flow when someone buys? Because the time delay does the work.

Here’s the mechanism:

1. Every time a customer places an order, they enter the flow.
2. They wait in a time delay that’s longer than your normal buying cycle, say 120 days.
3. The flow has a profile filter: Placed Order zero times since starting this flow.
4. If they order again during the wait, the filter fails and they drop out of that entry. The new order has already started a fresh entry with a fresh 120-day clock.
5. Only customers who reach the end of the delay without ordering get the first win-back email.

So the flow effectively resets with every purchase, without anyone maintaining a list of lapsed customers. Because Klaviyo checks profile filters before every message, a customer who buys after the first win-back email is also skipped from the rest.

If you sell through Buy with Prime, Klaviyo recommends adding a filter for Placed Order (Buy with Prime) zero times since starting this flow, and running a separate win-back on Buy with Prime’s own order event. Otherwise customers who reorder through Amazon look lapsed.

What about customers who lapsed before the flow went live?

A Placed Order flow only knows about orders placed after it’s live, so customers who were already lapsed on launch day won’t be picked up. Handle that backlog once with a campaign to a segment of lapsed customers, then let the flow handle everyone from here on. Don’t import the problem into the flow.

How long should the win-back delay be?

Set the first delay a little longer than your average buying cycle. That’s Klaviyo’s guidance, and it’s right: reaching out at exactly the average time catches customers who were about to reorder anyway, so you pay for a message (and maybe a discount) you didn’t need.

You can find your buying cycle without predictive analytics. Klaviyo suggests creating a segment of people who have placed an order at least twice in the last two years, exporting it, and averaging the Average Time Between Orders column. If you don’t have enough repeat customers for that to mean much, estimate from the product: how long it takes to run out, wear out, or want the next thing.

A few cautions from accounts we’ve reviewed:

• One average rarely fits a whole catalog. A store selling both 30-day supplements and a once-a-year kit has two buying cycles. Replenishable products belong in a separate replenishment flow, and Klaviyo recommends the same.
• First-time buyers lapse faster. Customers with one order typically drift sooner than repeat customers. Some stores run a shorter-delay path for single-order customers, using a split on order count.
• Seasonal brands need a different frame. If most customers buy once a year before winter, a 120-day silence is normal, not lapse.

Using predictive analytics instead

If your account qualifies for Klaviyo’s predictive analytics, profiles get an Expected date of next order, based on that customer’s own order pattern and the behavior of your whole customer base. You can trigger a date-based flow from it, for example sending the first win-back email some days after the expected date passes.

Klaviyo’s eligibility bar for CLV predictions is real: at least 500 customers who have ordered, an ecommerce integration or orders sent by API, at least 180 days of order history with orders in the last 30 days, and some customers with three or more orders. Note too that the prediction doesn’t account for which products someone bought. For a varied catalog, a rule-based delay per product type can still be more accurate.

What should win-back emails say?

Three emails is a reasonable shape, and it’s what Klaviyo’s own guidance uses.

Email 1: a light touch. Short. Show what’s new or what’s selling, three to six products, and give a reason to look. If you use an incentive, it can appear here, but it doesn’t have to. Many lapsed customers simply forgot about you.

Email 2: a reminder with a reason to act. Different products from the first email. If you offered something, remind them it has an end date, and make sure it actually does.

Email 3: a last call. Make it clear this is the final message in the series and make the unsubscribe link easy to find. That sounds counterintuitive, but someone who genuinely doesn’t want your emails anymore is better unsubscribing than marking you as spam.

Space them out. A week or more between emails suits most brands, because the customer has already been quiet for months and three emails in five days reads as panic.

Split by who the customer was

A lapsed VIP and a lapsed one-time buyer are different situations. Klaviyo’s multi-branch split lets you route on total spend, order count or other profile properties.

A short scenario: a customer who spent heavily across eight orders over two years stops buying. The standard win-back sends her “We miss you! Here’s 15% off” alongside a grid of best-sellers she already owns. A better path for her might be a plain-text email from the founder or customer service asking if something went wrong, with no discount at all. Lapsed high-value customers sometimes left because of a bad experience, and a coupon doesn’t address that.

Check recent activity before assuming lapse

A customer who hasn’t ordered in 150 days but viewed three products yesterday isn’t lapsed in the way the flow assumes. A split on recent site activity (Active on Site or Viewed Product in the last few days, if your onsite tracking sends them) can route them to a gentler message or straight to your browse abandonment flow logic. Be cautious with opens as a signal: Apple Mail Privacy Protection inflates open rates, which Klaviyo itself notes, so clicks, site visits and orders are more trustworthy.

Should a win-back flow include a discount?

Often yes, but deliberately. A win-back offer is reasonable because you’re trying to restart a relationship that has stopped. The risk is the pattern it creates.

If customers learn that going quiet for four months produces a 20% code, some of them will wait for it. You’ll see it as a cluster of orders arriving just after win-back emails, from customers who used to buy at full price on a regular rhythm.

Ways to limit that:

• Only include the incentive in the second or third email, so customers who come back from the first email don’t need one.
• Exclude customers who have used a win-back code before, using a filter or split on past orders with that discount.
• Use non-price incentives for some segments: free shipping, a gift with purchase, early access to something new.
• Size the offer by margin, not by what competitors do.

What happens after the win-back flow?

Customers who don’t respond to win-back aren’t automatically lost, but they shouldn’t stay in your regular campaign audience forever either. The natural next step is your engaged-segment and sunset logic.

If they’re still opening or clicking campaigns, they’re interested in the brand but not buying, and they can stay in campaign audiences. If they’ve stopped engaging entirely, they’ll eventually qualify for your sunset flow. That handoff protects your sender reputation. The Klaviyo deliverability guide explains how sunset flows and suppression work.

On the other side, customers who do come back should land in the post-purchase flow like any other buyer, and the win-back flow’s own clock restarts with that order. The post-purchase flow guide covers that side, and the Klaviyo segmentation guide covers building active, at-risk and lapsed segments for reporting and campaigns.

How to measure win-back

Win-back is the flow where attributed revenue overstates impact most. Some customers in it were going to come back anyway, and the delay is a guess at when.

Better measures:

• Reactivation rate: of customers who reached the first email, how many ordered within, say, 30 days of it.
• Discount dependence: what share of reactivated orders used the win-back code, and whether those customers order again at full price.
• Second-order after reactivation: a customer who comes back once and lapses again hasn’t really been won back.
• A comparison group if you can create one, such as a small share of lapsed customers who deliberately receive nothing. Even a rough comparison tells you more than attributed revenue alone.

Klaviyo’s flow A/B testing is useful for timing, subject lines and offers. Test the delay itself if you can. It’s the setting most likely to be wrong and the one teams rarely revisit.