Essential Klaviyo flows (and how to keep them firing)

---

title: "Essential Klaviyo flows (and how to keep them firing)" description: "The eight ecommerce flows every Klaviyo account needs, what each one does, where they commonly break, and the monitoring signals that tell you they're still firing." slug: "klaviyo-flow-checklist-essential-flows" publishedAt: "2026-05-19" updatedAt: "2026-05-19" painCluster: "meta" intent: 7 tier: 4 faq:

• q: "How many flows should an ecommerce store have in Klaviyo?" a: "Eight is the canonical essential set covered in this page. Sophisticated stores run 15-25 flows including segmented variants (VIP welcome, repeat-buyer post-purchase, lapsed-buyer winback at different decay intervals). The right number depends on list size, AOV, and operator bandwidth. Eight is the floor for any serious sender."
• q: "Which flow should I build first?" a: "Welcome flow, almost always. It's the flow that converts the most new subscribers, sets sender reputation with the right audience (engaged people who just opted in), and establishes the baseline for everything else. If you only build one flow, build the welcome flow."
• q: "How do I know if my flows are still firing?" a: "Open Analytics → Metrics for the trigger event each flow uses, and check the recent activity. If the metric has fired recently, the trigger is healthy. Inside each flow, the 'Latest entries' view shows whether profiles are actually entering. If a flow shows Live but the trigger metric is silent or zero profiles have entered in 24 hours, the flow is broken even though Klaviyo's UI looks healthy."
• q: "What's the biggest mistake stores make with flows?" a: "Building flows and then not monitoring them. The flow editor shows Live regardless of whether the underlying trigger event is still recording. Most silent failures happen because something upstream (integration, theme, plugin) broke the trigger; the flow itself is fine but never enters anyone. Building the flow is hours of work; keeping it firing is ongoing operational work."
• q: "Should I personalize every flow email?" a: "Personalization beats no personalization at the headline level — first name in subject lines, recent-purchase references in copy. Heavy personalization (deep product recommendations, AI-driven content variation) is high-leverage but only after the basics are solid. Build the eight essential flows with thoughtful copy and basic personalization first; layer in advanced personalization second."
• q: "How long should an abandoned cart flow be?" a: "Three emails over 24-48 hours is the standard. First send 30-60 minutes after abandonment, second send 24 hours later, third send 48 hours later with the strongest offer (usually a discount). Beyond three emails the marginal revenue drops and the complaint risk rises."
• q: "Should every flow have Smart Sending on?" a: "No. Smart Sending suppresses sends to profiles who've recently received another email — it's correct for broadcast campaigns and wrong for time-sensitive flows like abandoned cart. Default rule: Smart Sending on for newsletters and campaigns, off for cart recovery, browse abandonment, and any flow where timing matters."
• q: "What's a 'sunset' flow and do I need one?" a: "A sunset flow is an automated unsubscribe for chronically disengaged profiles — typically 'no opens, no clicks in 180 days, exclude from sends.' It's not a customer-facing flow; it's an operational flow that protects sender reputation by removing dead weight from your sending list. Every serious sender should have one. It's the ninth flow most operators end up adding." related:
• klaviyo-abandoned-cart-flow-not-firing
• klaviyo-welcome-flow-not-triggering
• klaviyo-flow-stopped-generating-revenue
• klaviyo-monitoring-tools-2026

---

There's a canonical list of ecommerce flows that every Klaviyo account should have running. The list is well-documented across the industry — Klaviyo themselves publish it, every agency publishes some variant of it, and the consensus on what belongs has been stable for years. What's less commonly covered is the second half of the question: once you've built the eight essentials, how do you know they're still firing six months later?

This page walks through the eight flows in order of importance, what each one does, where each one commonly breaks, and the monitoring angle for each. The build instructions are widely available elsewhere; we focus on the operational layer — what to watch and what to alert on.

The eight essential flows

1. Welcome flow

Purpose. Convert new subscribers into first-time buyers. The first email is structured to confirm their subscription and deliver any signup incentive (discount code, free shipping, content). Subsequent emails build the brand relationship and nudge toward first purchase.

Trigger. Profile added to your main list, or specific list (depending on your form structure). Some stores use Created event from Klaviyo as the trigger; most use list membership.

Where it commonly breaks. Double opt-in confirmation email never arrives (custom domain DKIM issue), list assignment from forms broken (Klaviyo.js not loading), or Smart Sending suppressing the welcome email because the profile received a recent campaign. Also: the flow is set to Manual or Draft instead of Live, which is shockingly common.

Monitoring angle. Watch for "Live welcome flow, 0 entries in 24h despite N new subscribers added." This is the highest-confidence break signal in the entire flow library; it almost always means the trigger event isn't firing or the flow filter is blocking everyone.

2. Abandoned cart flow

Purpose. Recover revenue from carts that started checkout but didn't complete. Highest-leverage flow most stores run — recovers 5-15% of abandoned carts when configured well.

Trigger. Started Checkout event. Some flows are wired to Added to Cart as a secondary trigger for earlier-funnel recovery.

Where it commonly breaks. Started Checkout metric stops recording (Shopify token expired, theme stripped the Klaviyo snippet, WooCommerce plugin conflict). Flow filter blocks every profile (the classic "Started Checkout zero times since starting this flow" pattern). Smart Sending suppresses sends when it shouldn't.

Monitoring angle. Watch the Started Checkout metric for sudden silence. Watch the flow's Latest Entries tab for sudden zero entries. Either signal precedes revenue impact by hours to days.

3. Browse abandonment flow

Purpose. Recover revenue from product views that didn't add to cart. Earlier in the funnel than abandoned cart, conversion rate is lower but volume is higher.

Trigger. Viewed Product event. Usually filtered by category, price tier, or recency.

Where it commonly breaks. Viewed Product is the most fragile trigger event in Klaviyo — it depends on the client-side JS snippet firing on every product page view. Theme updates regularly strip it. Page-builder apps (PageFly, GemPages) sometimes interfere with snippet load order. Conflicting popups (Justuno, OptiMonk) sometimes break the snippet's namespace.

Monitoring angle. Watch Viewed Product event volume against trailing-7-day baseline. Sudden 50%+ drop typically means the snippet stopped firing for at least a subset of traffic.

4. Post-purchase flow

Purpose. Build customer lifetime value through post-purchase content — order confirmation context, product education, review collection, cross-sells. Sets the stage for replenishment and winback.

Trigger. Placed Order event. Some stores split into first-purchase post-purchase (longer, more educational) and repeat-purchase post-purchase (shorter, more focused).

Where it commonly breaks. Placed Order event syncs from Shopify webhook; broken webhook means delayed or missed entries. Order-data fields not populating in templates (variant SKU, fulfillment status) when product schema changes. Review-collection email arriving before product is delivered, especially for slow-shipping items.

Monitoring angle. Watch Placed Order event for delivery delays (Klaviyo is normally within seconds; delays of hours suggest webhook trouble). Watch post-purchase open rate for sudden drops, which often indicate template-data fields are broken.

5. Winback flow

Purpose. Re-engage lapsed customers — typically defined as "purchased in the last 12-18 months but not in the last 90 days." Lower conversion rate than welcome or cart flows, but the audience is qualified (they've bought before).

Trigger. Time-based on Placed Order — "90 days since last Placed Order, no Placed Order since." Sometimes wired via a dynamic segment that updates daily.

Where it commonly breaks. Segment update lag (relative-time conditions in Klaviyo update once per 24h, not real-time). Discount code expired inside the template. Offer copy stale because the flow was built two years ago and never updated.

Monitoring angle. Watch winback flow entries against the size of the lapsed-buyer segment. If the segment is growing but entries are flat, the segment-to-flow handoff is broken.

6. Replenishment flow

Purpose. For consumable products (supplements, beauty, food/bev, pet food), prompt re-order around the expected depletion timeline. Highest-leverage flow for subscription-leaning brands.

Trigger. Time-based on last Placed Order, with timing keyed to expected product duration (30 days for daily supplements, 60-90 days for less-frequent consumables).

Where it commonly breaks. Product duration estimate is wrong (you set it at 30 days but customers actually go 45). Subscription-platform integration (ReCharge, Skio, Bold) double-counting orders and breaking the timing logic. Filter excluding active subscribers not working correctly, so subscribers get reminded to re-order something they're already auto-receiving.

Monitoring angle. Watch replenishment conversion rate against history. If it drops sharply, either timing has drifted (audit the duration assumption) or the segment exclusion for active subscribers is broken (audit the filter).

7. Sunset flow

Purpose. Operationally protect sender reputation by removing chronically disengaged profiles from sending. Not a customer-facing revenue flow; it's a list-hygiene flow.

Trigger. Time + engagement-based: "180 days since last engagement, no opens, no clicks, currently subscribed." Some flows send a final "are you still interested" email; most just unsubscribe silently.

Where it commonly breaks. Filter logic too aggressive (suppressing engaged subscribers who just don't open frequently because of Apple MPP). Filter logic too loose (never suppressing anyone, defeating the purpose). Configuration drift over time as engagement thresholds change.

Monitoring angle. Watch monthly suppression volume from sunset flow. A spike (1,200 suppressed in a day vs trailing average of 50) usually means the filter logic just changed or the threshold was misconfigured. A flat zero means the filter is too restrictive and the flow is doing nothing.

8. Customer winback / VIP flow

Purpose. For high-LTV customers (top 5-10% by total spend), provide differentiated treatment — early access, exclusive offers, personal-feeling communications. Often manual one-off campaigns rather than a flow per se, but the persistent flow version is worth running.

Trigger. Segment membership in a VIP segment, typically defined by total spend, order frequency, or both. Updates daily as new customers cross into the segment.

Where it commonly breaks. Segment definition stale (was right two years ago, no longer right). Personalization tokens (first name, recent product) broken. The whole flow neglected because it's "low priority" — but the LTV per profile in this flow is 10-20x the average list LTV.

Monitoring angle. Watch segment size against historical average. Watch flow engagement rate (this segment should outperform every other on open and click).

How to know if your essentials are healthy

Four checks. Each takes under five minutes if you know where to look.

Check 1: Are the trigger metrics firing? Open Analytics → Metrics. For each of the trigger events your flows depend on (Started Checkout, Placed Order, Viewed Product, Added to Cart), check the most recent activity. A flat right edge — no events in the last 12 hours — for any of these is a flag.

Check 2: Are flow entries landing? Open each flow → Latest Entries. Compare today's entry count against last week's entry count for the same day-of-week. A 50%+ drop is a flag. Zero entries when there should be many is a fire alarm.

Check 3: Are flow conversions holding? Open each flow → Performance. Look at revenue-per-recipient or conversion rate for the last 7 days vs the previous 30 days. A 30%+ drop usually means content has gone stale, offers expired, or sender reputation is degrading.

Check 4: Are the segments these flows depend on still healthy? Open Lists & Segments. For each segment your flows reference (engaged 30-day, VIP, lapsed buyers), look at the size trend. A sudden shift suggests either the segment definition changed or the underlying data feed changed.

If you're doing these checks manually, plan on 30 minutes a week to run them across an established account. If you're at agency scale across 10+ clients, that's 5 hours a week of operator time you're spending on monitoring instead of strategy. That math is the structural argument for an always-on monitoring layer — it runs these checks every hour and surfaces the exceptions.

The flows themselves are well-defined. The hard operational question is not "what flows should I build" but "how do I know they're still working." Building is finite work. Monitoring is the ongoing work most operators underestimate.