7 Klaviyo Flows to Fix Before BFCM

Short answer. Audit seven Klaviyo flows before Black Friday Cyber Monday: welcome, checkout abandonment, cart abandonment, browse abandonment, post-purchase, winback, and sunset. Start 6 to 8 weeks before the promotion, verify every event and flow filter, align evergreen offers with the BFCM deal, and set a rule for campaign and flow overlap. Do not wait for peak week to discover that purchasers still receive abandonment emails.

BFCM increases traffic, list growth, checkout activity, order volume, and message frequency at the same time. That makes it a stress test for lifecycle architecture. The objective is not to create seven new automations in the final week. It is to make the flows already touching customers accurate under peak conditions.

Klaviyo's June 2026 Black Friday sending guide recommends coordinating automated messages with holiday promotions, reviewing delays, replacing conflicting evergreen offers, and monitoring overlap across channels. Use those ideas as tests, not as universal settings. Your inventory, sale window, margin, buying cycle, and audience pressure still determine the final plan.

The seven-flow BFCM map

The first four flows respond to current intent. Post-purchase responds to conversion. Winback and sunset prepare the older audience before the busiest sending window.

1. Welcome flow: align the promise with the sale

The welcome flow should trigger when an eligible profile subscribes to the intended email list. During BFCM acquisition, the form promise may change from an evergreen incentive to early access, a gift, free shipping, or a holiday offer. The first email must deliver that exact promise.

Pre-BFCM checks

• Confirm the correct list triggers the flow.
• Test a new subscriber from each active form and checkout path.
• Exclude or branch existing customers when first-purchase copy would be inappropriate.
• Remove evergreen coupon language that conflicts with the BFCM offer.
• Verify coupon eligibility, expiration, stacking, and product exclusions.
• Decide what happens when a subscriber purchases during the sequence.

A practical BFCM welcome path can use three or four messages: immediate promise delivery, product or category guidance, proof, then a final next step. Do not add a resend solely because a profile appears not to have opened. Apple Mail Privacy Protection can create automatic opens, so open-based routing is not a dependable proxy for human attention. Use clicks, purchases, and the Apple Privacy Open property when open data matters. Klaviyo explains the limitation in its MPP identification guide.

2. Checkout abandonment: protect the purchase exit

Checkout abandonment is the highest-intent recovery flow in this set. For Shopify, use the checkout metric actually present in the account. Klaviyo documentation may refer to Checkout Started or Started Checkout in different contexts, so verify the integration's metric instead of creating a similarly named custom event.

The essential profile filter is:

Placed Order zero times since starting this flow

Klaviyo rechecks profile filters before each actionable flow step. A shopper who purchases during a delay should therefore be skipped from the next recovery message. Review the current behavior in Klaviyo's flow trigger and filter guide.

BFCM adjustments to test

Klaviyo's 2026 BFCM guide describes shortening abandonment delays as one possible holiday adjustment. Treat that as a test. A 30-minute example from another brand is not automatically right for yours.

3. Cart abandonment: make checkout the stronger signal

Cart abandonment begins when an identified shopper triggers Added to Cart but has not progressed into checkout. It should complement checkout recovery, not race it.

At minimum, check these profile filters using the exact metric names in your account:

Checkout Started zero times since starting this flow
Placed Order zero times since starting this flow

Add a re-entry rule that reflects purchase frequency and campaign pressure. During BFCM, some shoppers create or modify carts repeatedly. Letting every event restart the same message sequence can produce duplicate reminders.

Do not automatically disable cart abandonment for the whole weekend. First evaluate whether the flow adds incremental reach, whether checkout identification is reliable, and whether its filters prevent overlap. If the audience is small or the message creates noise, pausing selected messages may be reasonable. Document the decision and restore the evergreen configuration after the sale.

Our Klaviyo abandonment flow guide covers the hierarchy among checkout, cart, browse, and site signals in detail.

4. Browse abandonment: lower intent deserves lower pressure

Browse abandonment uses Viewed Product for an identified profile. It is useful only when onsite tracking, identity resolution, privacy settings, and product data are working on the active storefront.

Use filters that stop the flow when a stronger action occurs:

Added to Cart zero times since starting this flow
Checkout Started zero times since starting this flow
Placed Order zero times since starting this flow

For BFCM, one focused product reminder may be enough. The message should reflect a view, not claim that the item was placed in a cart. Preview product name, image, price, availability, and URL against real events. A sale-price mismatch in a dynamic block can undermine the entire promotion.

If traffic increases but identified Viewed Product profiles do not, investigate tracking and consent before changing the flow. More sessions do not guarantee more identifiable flow entrants.

5. Post-purchase: separate service from promotion

Post-purchase communication has at least two jobs:

1. help the customer understand what happens next;
2. guide product use, support, review, replenishment, or a relevant next purchase.

Do not duplicate the order confirmation already owned by Shopify or another transactional system. Marketing eligibility and transactional necessity are different. Document which platform owns each message.

Branches worth validating

• First-time buyer versus repeat customer.
• Product or category purchased.
• Gift purchase versus likely self-purchase, when reliable data exists.
• High-touch product versus simple replenishable item.
• Customer who used the BFCM offer versus a full-price buyer.

During the promotion, remove cross-sell copy that offers a worse deal than the live sale. After BFCM, decide whether the customer's next message is onboarding, review request, replenishment, loyalty, or a carefully timed cross-sell. Do not push everyone into the same generic discount sequence.

6. Winback: run it before peak week

A winback flow targets prior customers who have passed the normal repurchase window. It should not use a universal 90-day delay. Calculate a starting point from your observed order intervals by product family or customer group.

Klaviyo's current winback flow guide uses Placed Order as the trigger, a profile filter of Placed Order zero times since starting this flow, and an initial delay slightly longer than the normal buying cycle. It recommends limiting the flow to three emails per recipient.

For BFCM, run the winback test early enough to learn before peak volume. Use a customer-value or purchase-count branch if the audience is large enough. A prior VIP may deserve new-product access or service, while a one-time bargain buyer may need a different reason to return.

Avoid sending a broad BFCM campaign to profiles that already completed a winback sequence without clicking, visiting, or purchasing. A major sale is not proof that every dormant address should be mailed again.

For implementation details, use the Klaviyo winback flow tutorial.

7. Sunset: clean before the traffic spike

A sunset flow is the final controlled attempt to identify whether a persistently inactive profile should remain marketable. It is not a revenue flow, and it should not be suspended merely to increase the apparent BFCM audience.

Klaviyo's March 2026 sunset flow guide recommends a segment-triggered flow, up to three final messages, and a profile property that tags people who remain unengaged. Those tagged profiles can then be suppressed in bulk.

Important current limitation: Klaviyo says suppression is not available as a native flow action. The standard process is to tag unengaged profiles, create a segment from that property, then choose Suppress current members. The bulk action affects current members only, so the process must run again for profiles who join later. API automation is possible, but it requires development and controls.

Finish this work before the most concentrated holiday sends. Do not revive people who ignored the sunset sequence simply because the discount is larger.

The Klaviyo sunset flow tutorial provides the exact implementation and suppression handoff.

Coordinate campaigns and flows

Flow filters solve behavioral conflicts, but they do not create a complete pressure policy. Klaviyo Smart Sending limits messages within a configured channel window. As of July 16, 2026, Klaviyo documents a default email Smart Sending window of 16 hours. Settings can be changed, and individual messages can have Smart Sending turned off.

Two details matter during BFCM:

• A message skipped by Smart Sending is not automatically sent later.
• Email, SMS, and push use separate Smart Sending windows.

Review the current Smart Sending documentation, then build an explicit priority table:

Do not turn off Smart Sending across every high-priority message without modeling the consequence. A profile can qualify for several channels and automations in one day.

A 6-week production plan

If a critical event is missing two weeks before launch, simplify. A smaller flow with verified logic is safer than a complex branch built on data that has never been tested.

BFCM flow QA checklist

• Every trigger exists in Analytics > Metrics and has recent test activity.
• Placed Order zero times since starting this flow protects recovery and winback messages.
• Cart and browse flows stop after stronger intent.
• Customer and prospect offers cannot conflict.
• Dynamic prices, images, URLs, coupons, and expiration dates pass QA.
• Campaign exclusions match the flow pressure plan.
• Smart Sending settings are documented message by message.
• SMS recipients have channel-specific eligibility and a separate pressure review.
• Manual and Live statuses are intentional for every message.
• Evergreen versions and restoration owners are documented.

FAQ

How early should I prepare Klaviyo flows for BFCM?

Start 6 to 8 weeks before the sale when possible. That gives you time to verify events, repair filters, observe real entrants, test dynamic content, and learn from normal-volume behavior. A team starting later should prioritize checkout, welcome, and post-purchase rather than rushing all seven flows live.

Should I pause Klaviyo flows during Black Friday?

Not by default. Review each message. Keep flows whose intent, offer, and filters complement the promotion. Pause or replace messages that conflict with the sale, create duplicate pressure, or rely on stale content. Record every temporary change so the evergreen setup is restored.

Should BFCM abandonment delays be shorter?

Possibly. The promotion window and inventory pressure can shorten consideration time, and Klaviyo lists shorter abandonment delays as a BFCM tactic. Test the change against your traffic and order pattern. Do not copy another brand's 30-minute delay without evidence.

Can Smart Sending prevent every duplicate BFCM email?

No. Smart Sending can skip messages within a channel window, but it does not replace flow filters, campaign exclusions, or cross-channel planning. Skipped messages are not automatically rescheduled, and separate channels use separate timers.

Should I send BFCM campaigns to unengaged profiles?

Expansion beyond the normal engaged audience requires caution. Exclude profiles with sustained inactivity, no site or purchase behavior, and no response to re-engagement. A larger send count is not useful if it increases complaints or damages reach to active subscribers.

Make peak week a controlled system

BFCM performance is easier to improve when each flow has one job, one owner, verified data, and a documented relationship with campaigns. Deliver can audit the seven-flow architecture, event paths, exclusions, creative variants, and restoration plan before peak volume arrives.

Review your BFCM Klaviyo setup with Deliver.

Continue with:

• Build the nine BFCM Klaviyo segments
• Set up Klaviyo correctly on Shopify
• Build coordinated abandonment flows

Charlotte Rodrigues, CRM Lead at Deliver. Updated July 16, 2026.