The Klaviyo Flow Stack for Shopify: 8 Sequenced Automations That Quietly Add 30% Revenue

Marco runs Solbar, a $1.6M ARR clean-skincare brand on Shopify Plus. Klaviyo revenue share had been parked at 22 percent for nearly six months. He had every flow the agency before us recommended. Twelve flows live, every one with copy that took weeks to polish. Two of them fired on the same subscriber within ninety minutes of an abandoned cart. When we pulled the dashboard apart on the discovery call, four flows were producing eighty-one percent of attributed revenue. The other eight were either silent or actively cannibalizing each other.

That is the most common pattern we see on Shopify Klaviyo audits in 2026, and it is not a copy problem.

Why sequencing beats copy

Founders ship flows the way agencies sell them: as individual deliverables. Welcome flow, three weeks. Cart abandonment, two weeks. Win-back, one week. Each one gets its own brief, its own copy review, its own A/B test plan. By the time it is all live there are twelve to fifteen flows running and no one has a map of what fires when, who gets suppressed, or which flow is stealing credit from which.

That is the failure mode. Not weak copy.

Sequencing is the architecture: which flow has priority on which subscriber, how long the cooldowns are, what events suppress what. The copy comes after. We have A/B tested rewriting the welcome series copy three times on the same brand and moved revenue per recipient by under four percent. We have added a single suppression rule and moved it eighteen percent. Different leverage, same calendar quarter.

Marco’s stack had no architecture. Cart and checkout abandonment shared the same audience. Browse abandonment fired on customers who had just placed an order. Win-back targeted subscribers who were still actively buying.

Honestly, it would have done less damage if half of it had been turned off.

Welcome and browse abandonment, the top-of-funnel pair

Welcome series gets the most attention and earns the least leverage. Most brands rewrite it three times in two years and never move the conversion number meaningfully. The variable that actually moves welcome conversion is the offer. Not the copy length, not the imagery, not the day-three storytelling email. The offer.

We run two welcome variants on most engagements. Variant A is ten percent off, twenty-four hour expiry, three emails over four days. Variant B is free shipping plus a sample, no expiry, five emails over twelve days. Variant A wins on first-purchase conversion almost every time. Variant B wins on first-purchase AOV and ninety-day retention. The right pick depends on whether the brand is acquisition-constrained or LTV-constrained. Most $1M to $3M ARR brands we audit are sitting on the wrong one.

Browse abandonment is the flow founders have the most wrong assumptions about. The Klaviyo Viewed Product event fires on product detail pages, which sounds useful until you realize it fires for customers who are already in checkout, who just placed an order, and who came in from a transactional email. A standard browse-abandonment flow without exclusion logic will email the customer who just bought a $90 serum twelve minutes after the order confirmation, asking if they are still interested. We have seen this exact mis-send four times in 2026 alone.

The fix is two suppression conditions. Exclude anyone who has triggered the Started Checkout event in the last forty-eight hours. Exclude anyone who has placed an order in the last seven days. Both should already be on the flow. They almost never are.

Cart and checkout abandonment, and the duplicate-email trap

These are two different Klaviyo events. Started Checkout fires when the customer enters the checkout funnel. Abandoned Cart fires earlier, on cart creation. Klaviyo treats them as separate flows, so brands run both, and the same subscriber gets two reminders within an hour of leaving the same session. We see this on roughly seventy percent of audits.

The duplicate-email trap matters because it doubles unsubscribe rates on the segments that recover the most revenue. Cart and checkout recoveries are the highest-intent emails Klaviyo will ever send. Burning the subscriber on two competing reminders in the same window costs you the renewal email a month later.

The architecture we use: cart abandonment runs first, with a four-hour delay. Checkout abandonment runs at six hours, with a hard exclusion on anyone who triggered the cart flow in the prior eight hours. Net result, one reminder per session, and the reminder you keep is the one tied to the higher-intent event. Recovery rate on Marco’s account moved from 4.1 percent to 5.9 percent in three weeks with no copy changes. The copy was fine. The architecture was the problem.

The second piece is timing. Klaviyo’s Smart Sending feature caps the same subscriber at one message per sixteen hours by default. Brands turn this off because it suppresses transactional-feeling reminders, and then they wonder why their open rates collapsed. Leave Smart Sending on. Build your suppression logic at the flow level instead.

Post-purchase and replenishment, the repeat-rate engine

If you are leaving money on the table, this is where you are leaving it. Most $1M to $3M ARR Shopify brands ship one post-purchase email (the order confirmation) and call the sequence done. We have audited two dozen brands in this band and the median post-purchase revenue contribution is under three percent. It should be twelve to eighteen.

The minimum viable post-purchase sequence is four touches over forty-five days. Education on day two. Review request on day twelve. Cross-sell on day twenty-five. Replenishment trigger on day thirty-five for consumables, or category re-engagement on day forty for apparel.

Replenishment is the highest-leverage of the four. The mechanic is boring: figure out the median re-order interval for each consumable SKU, then trigger a replenishment reminder seven days before that interval expires. On a $54 serum that lasts forty-five days, the trigger fires on day thirty-eight. We have never seen this flow under-perform when the interval data is clean. The reason most brands do not run it is they do not have the interval data, not that the flow does not work.

For non-consumables, run a category re-engagement flow instead. Customer bought from category X, has not bought from category Y or Z, here is what is new in Y and Z. Apparel brands we work with run this on a sixty-day delay. Beauty brands run it on thirty.

Win-back and sunset, where most brands give up too early

Win-back targets the segment of subscribers who used to engage and have stopped. The trigger we use is straightforward: no open or click in the last sixty days, no purchase in the last ninety. The sequence is three emails over fourteen days, with an escalating offer or escalating value content depending on brand voice. Recovery rate on win-back is rarely above two percent, which is the reason brands give up on it. The math still works because the cost of the email is zero and the segment is large.

Sunset is the flow nobody runs and everybody needs. A subscriber who has not opened in 180 days is poisoning your sender reputation. Klaviyo will deliver to their inbox at a steadily lower rate, and the cost gets spread across every email you send to every subscriber. The sunset flow gives them one final chance to re-engage and removes them from active sends if they do not.

Brands resist this because the list shrinks. The deliverability lift more than pays for it. We have measured the lift at six to eleven percent on overall list open rate within sixty days of running sunset.

Cross-flow suppression, the quiet multiplier

The single change that adds the most revenue to a Klaviyo stack is not a new flow. It is the suppression rules across the flows that already exist. We add three rules to almost every account we touch.

The earliest rule protects the welcome series window. A subscriber inside welcome is suppressed from browse, cart, and checkout abandonment for the opening seven days. The welcome series is doing the work. Stacking lifecycle on top of it is what creates the “I am getting six emails a day from this brand” complaints that drive unsubscribes.

The next rule shields recent purchasers. A subscriber who placed an order in the last seven days gets suppressed from every promotional flow, not just from the post-purchase sequence. From everything.

Then there is the rule most brands fight us on. A maximum frequency cap at three flow emails per subscriber per week, enforced at the Klaviyo profile level. It is also the cap that lifts unsubscribe rates the most predictably when we install it.

The dashboard that lets you defend the spend

If the Klaviyo dashboard you ship to the founder shows total flow revenue and nothing else, you are going to lose the budget conversation. The dashboard we hand to clients shows per-flow revenue attribution, revenue per recipient, click-to-conversion rate, and unsubscribe rate per flow, all benchmarked against the latest Klaviyo benchmarks numbers.

The benchmark that actually matters is revenue per recipient, not open rate. A welcome flow at 38 percent open and $0.40 per recipient is worse than a welcome flow at 28 percent open and $1.10 per recipient. Founders default to optimizing open rate because it is the number they see first. Do not.

What we keep telling clients

If you have more than eight flows running, you do not have a Klaviyo problem. You have an architecture problem dressed up as one. Kill what is not producing, add suppression to what is, and refuse to ship a new flow until the existing ones have documented audiences.

Marco killed eight flows on Solbar. We kept the welcome, cart abandonment, post-purchase, and win-back, rewrote the suppression rules from scratch, and added a replenishment flow on a forty-five day cycle. Klaviyo revenue share moved from 22 percent to 28 percent in ninety days. He sent forty percent fewer emails to do it.

The number that finally moved was not the one he was watching.

Questions we get every week

Should I run a separate flow for SMS or build it into the same flow? Build it into the same flow as conditional branches. SMS and email subscribers overlap heavily, and running parallel flows means duplicate suppression logic in two places. Klaviyo’s flow builder handles the branching natively. The exception is if your SMS list and email list have less than thirty percent overlap, in which case parallel flows are fine.

How long should I wait before declaring a new flow a failure? Six weeks at minimum, twelve if the segment is small. Klaviyo’s revenue attribution settles slowly because click-to-conversion windows are seven days. A flow that looks dead at week three often looks healthy at week eight.

Is it worth paying for a Klaviyo agency, or can my in-house team run this? If your in-house team has run flow architecture before, keep it in-house. If they have only run copy and design, the architecture work is the gap you need to fill, not the copy. The cost difference is real and it shows up in revenue per recipient, not in deliverable quality.

Does Klaviyo’s AI feature suite (predicted CLV, predictive segments) actually work in 2026? Predicted CLV is reliable for accounts with more than 18 months of purchase data and over 10,000 customers. Under either threshold the predictions wobble. The predictive segments are useful as a starting point but should be treated as hypotheses, not segmentation truth. We use them to size potential audiences, then build the actual segments by hand.

Want help auditing the architecture under your Klaviyo flows before you commission another copy rewrite? Talk to us at monkeyman.agency/contact and we will spend a week pulling your stack apart and hand you a sequencing map you can defend at the next board meeting.