Klaviyo flows that earn their keep - the stack every Shopify brand needs

Every Shopify brand on Klaviyo needs a live core stack before campaign theater: welcome (value + first purchase), browse abandonment, abandoned cart / checkout (separate intents), post-purchase, and win-back or sunset. Propeller builds Klaviyo as a retention system — segmentation, suppression, and measurement tied to LTV — not a pretty newsletter factory.

If flows “exist” but revenue per recipient is soft, the usual culprits are duplicated triggers, missing purchase suppressions, broken events after privacy changes, or discounts that trained your list to wait. Fix the stack before you redesign templates. Connect the same discipline to storefront friction via the ecommerce CRO checklist.

The flow stack in priority order

• Identity: profile completeness, consent, SMS where lawful, suppression lists shared with ads.
• Welcome: 3–5 messages — brand, proof, offer or bestseller path, social proof, soft close.
• Browse abandonment: Viewed Product without cart; helpful, specific, no panic coupon.
• Abandoned cart: Added to Cart; item truth; shipping/returns objections; incentive last if ever.
• Abandoned checkout: Checkout Started; urgency on incomplete checkout, not generic cart copy.
• Post-purchase: shipping expectations, care, cross-sell, review ask timed to delivery.
• Replenishment / subscription: cadence by product use, not arbitrary weekly blasts.
• Win-back + sunset: RFM branches; stop mailing zombies to protect the domain.
• Transactional-adjacent: back-in-stock, price-drop, VIP early access — only after the core is live.

Abandonment without training discount hunters

Separate browse, added-to-cart, and started-checkout. First touch is a helpful reminder with the exact items — usually within an hour — not a 15% coupon. Second touch handles objections: shipping, returns, reviews. Reserve incentives for the last touch, and only if margin allows. Suppress anyone who purchased since the trigger. Confirm events actually fire after privacy changes; a beautiful flow on broken data recovers nothing.

• Margin rule: if contribution cannot absorb the discount + send cost, skip the coupon and fix PDP trust instead.
• Inventory rule: do not email OOS items; swap to adjacent in-stock recommendations.
• Frequency rule: exclude active win-back and active checkout flows from overlapping cart spam.
• Creative rule: match ad promise and PDP imagery so the email does not feel like a different brand.

Segmentation is the product

RFM, VIP, first-time vs returning, product affinity, and engagement health should branch inside flows — not only sit as campaign lists. Don’t spam low-AOV carts that can’t pay for the send. Connect the same discipline to SMS where consent is clean. That is what a Klaviyo agency in Los Angeles should mean by “lifecycle.”

For club and allocation businesses, lifecycle must respect membership state — see spirits club commerce on Shopify. For paid acquisition, align audience suppressions with Meta CAPI so you are not paying to reacquire people mid-flow.

Measurement that proves the stack

Flow dashboards lie when attribution windows and Shopify timelines disagree. Track revenue per recipient, conversion rate by message, unsub/spam rates, and incremental lift where you can hold out. Compare flow revenue to campaign revenue monthly — if campaigns dominate while core flows are dusty, you are entertaining the list instead of operating lifecycle.

• Health: deliverability, bounce, spam complaint trends by flow.
• Commerce: placed order rate and AOV by flow message.
• Hygiene: profile growth vs engaged profiles — vanity list size is not a KPI.
• Ops: time-to-fix after checkout or theme releases that break events.

Creative and offer rules inside flows

Lifecycle creative should inherit brand craft without becoming a monthly photoshoot bottleneck. Modular blocks — hero product, proof strip, objection FAQ, single CTA — let you refresh without rebuilding every flow. Offers follow margin: VIP gifts, shipping upgrades, and bundles often beat blanket percentages. Never let a flow promise something the PDP cannot fulfill on mobile.

When subscription or club states exist, flows must read membership flags before sending cart discounts. Alcohol and regulated categories need extra care — see spirits club commerce. Propeller’s Klaviyo engagements ship the core stack, wire suppressions to ads, and leave you with a written offer policy — not a folder of pretty orphans.

SMS, push, and channel manners

SMS earns a place when consent is explicit, cadence is sparse, and messages carry time-sensitive utility — cart recovery, shipment, drop alerts — not weekly chatter. Push follows the same manners. Never clone email copy into SMS; length and intent differ. Keep a single suppression brain so a buyer who just purchased does not get a texted coupon ten minutes later.

• Consent source captured and auditable.
• Quiet hours respected by region.
• Link shorteners and landing parity with email and PDP.
• Frequency caps shared across email and SMS.
• Club/membership flags respected before any win-back text.

Propeller implements channels as one lifecycle, not separate vendors optimizing their own open rates. If Meta is acquiring into the same profiles, suppressions must sync — otherwise you pay twice for the same conversion. That is the commercial standard behind our Klaviyo practice in Santa Monica.

Ninety-day lifecycle roadmap

Days 1–30: event QA, kill duplicate flows, ship welcome and cart/checkout with purchase suppressions. Days 31–60: browse, post-purchase, and replenishment with RFM branches. Days 61–90: win-back/sunset, SMS where consent is clean, and a written offer policy shared with media. Exit criteria: core flows live, deliverability stable, and revenue-per-recipient reviewed in a standing meeting — not a one-off audit PDF.

• Owner named for events, creative modules, and offer approvals.
• Changelog after every checkout or theme release.
• Holdout or geo tests when traffic supports incremental reads.
• Hand-off notes so CS knows what the email promised.

Ready to rebuild the stack? Talk Klaviyo or start a project. Bring flow analytics exports and your top SKUs — we’ll kill duplicates and put margin rules in writing.