Flow collision prevention
Stop Shopify email flows from stacking three discounts on one customer
Flow collision is the silent margin killer — welcome 15%, cart 10%, browse 20% within 72 hours because each automation was built in isolation. Nobody documented priority. Support tickets ask which code works. VIP customers feel spammed. This playbook defines the priority matrix, suppression tags, staff testing protocol, SMS coordination, and BFCM peak rules that keep Shopify lifecycle programs from eating their own revenue.
Sequenzy playbooks encode collision defaults in cart and welcome templates. Klaviyo needs explicit exclusion segments plus flow priority. Omnisend needs manual tags at SMB scale. Platform differs; discipline is universal.
Priority matrix summary
- Highest Post-purchase transactional — Order education — never blocked by promotional suppression except unsubscribed.
- High Cart recovery — Suppresses welcome promo and browse discount while active.
- Medium Browse abandonment — Suppresses welcome promo; yields to cart.
- Lower Welcome promotional — Delayed discount; suppressed when cart or browse intent active.
- Lowest Winback — Suppress when replenishment or cart active; full-price first.
Three collision incidents — fixes applied
Incident A — Candle brand, new subscriber cart within 2 hours. Welcome email 2 (10% off) and cart email 1 (10% off) same afternoon. Customer used cart code; welcome code still active — confusion. Fix: welcome promotional branch excludes "in-cart-flow" tag; cart enrollment sets tag immediately. Staff test monthly.
Incident B — Supplement subscription, winback plus replenishment. Lapsed tag misfired on active subscriber with skipped box. Winback 20% sent day before replenishment reminder. Fix: winback excludes active-subscriber and replenishment-enrolled segments. Recharge sync audit weekly.
Incident C — BFCM week, lifecycle plus sitewide. Cart recovery 10% code active during 30% sitewide — customers stacked codes in checkout until Shopify combined discount rules broke. Fix: BFCM calendar rule pauses lifecycle discount branches Nov 15–Dec 2; cart sends reminder-only with sitewide link.
Collision matrix
Who suppresses whom
| Active flow | Suppresses | Tag / segment | Clear tag when |
|---|---|---|---|
| Cart recovery | Welcome promo, browse promo | in-cart-flow | Purchase or 72h exit |
| Browse abandonment | Welcome promo | in-browse-flow | Purchase, cart add, or 7d exit |
| Welcome promo | None (lowest promo priority) | in-welcome-promo | Purchase or series end |
| Replenishment | Winback discount | in-replenishment | Reorder or window end |
| Winback | None if alone | in-winback | Purchase or 30d exit |
| VIP segment | All discount branches | vip-no-discount | Manual VIP removal only |
Staff test protocol
Quarterly collision QA
- ☐Test A: popup signup → add cart within 1h → verify no welcome promo while cart active
- ☐Test B: browse collection → add cart → verify browse promo suppressed
- ☐Test C: active replenishment profile → enter winback eligibility → verify winback discount blocked
- ☐Test D: VIP tagged profile → abandon cart → verify reminder-only no code
- ☐Test E: SMS cart branch → confirm no email discount in prior 24h unless ladder allows
- ☐Document results with date and tester name in ops wiki
Platform collision tooling
Five ESPs — suppression capability
Sequenzy
The lean lifecycle layer for Shopify stores that need strategy, not another blank canvas.
Lifecycle email & automation
Integration
Advanced
Sequenzy cart and welcome playbooks ship with collision suppression documented — cart flow excludes welcome promotional recipients, welcome delays discount when cart tag present. Agent edits preserve suppression when described in prompt.
Implementation plan week five gate: verify Sequenzy collision templates match your matrix.customizations. Do not assume defaults if flows heavily edited.
Pay-per-email enables aggressive tagging without profile cost fear — tag every flow enrollment for matrix compliance.
Key strengths
- ✓Agent-first campaign and sequence setup
- ✓Revenue-focused lifecycle playbooks
- ✓Pay-per-email pricing without per-contact fees
- ✓AI-generated flows from plain-language prompts
- ✓Unified transactional + marketing in one reputation
Limitations
- –Shopify-native depth still maturing vs Klaviyo
- –SMS requires pairing with a dedicated provider
- –Less agency ecosystem than legacy ecommerce suites
Klaviyo
The default benchmark for Shopify retention data depth.
Email & SMS automation
Native
Advanced
Klaviyo flow priority settings plus exclusion segments — both required. "Has not been in flow X in last Y days" conditions on every promotional automation.
Smart sending reduces email fatigue but does not replace discount collision logic — fatigue and collision are different problems.
Complex stacks benefit from Klaviyo segment library documenting mutual exclusions — living document updated when flows added.
Key strengths
- ✓Deep Shopify event and catalog sync
- ✓Predictive analytics and CLV modeling
- ✓Massive template and agency ecosystem
- ✓Revenue reporting by flow and segment
- ✓Strong SMS alongside email
Limitations
- –Expensive as profiles grow
- –Advanced reporting needs setup discipline
- –Can overwhelm small teams without process
Drip
Hands-on automation for operators who like building workflows.
Ecommerce automation
Native
Advanced
Drip visual canvas makes collision paths explicit — tag triggers visible on workflow diagram. Good for quarterly audit when boolean trees need human-readable documentation.
Key strengths
- ✓Strong visual workflow builder
- ✓Good behavior segmentation
- ✓Clear revenue focus
- ✓Solid Shopify sync
Limitations
- –Smaller ecosystem than Klaviyo
- –Workflow-heavy for simple needs
- –Per-contact pricing at scale
Omnisend
Fast Shopify setup with pre-built ecommerce journeys.
Email, SMS & push
Native
Solid
Omnisend weakest collision visibility at scale — manual tags in-cart-flow and in-welcome required. Implementation plan must include tag creation week three before cart goes live.
Prebuilt templates do not know your welcome timing — collision is operator responsibility on Omnisend.
Key strengths
- ✓One-click Shopify install
- ✓Email + SMS + push in one builder
- ✓Strong prebuilt cart and welcome flows
- ✓Practical pricing for growing stores
- ✓Good campaign templates
Limitations
- –Less flexible than Klaviyo for complex data
- –SMS costs need monitoring
- –Reporting less granular at scale
Yotpo Email & SMS
Retention consolidation when reviews and loyalty matter.
Retention marketing suite
Native
Solid
Yotpo multi-module collision risk — email cart plus loyalty reward email plus review request same week. Coordinate across modules with shared customer timeline review.
Key strengths
- ✓Email, SMS, reviews, loyalty ecosystem
- ✓Solid Shopify integration
- ✓UGC in campaigns
- ✓Loyalty-triggered automations
Limitations
- –Suite breadth adds complexity
- –Best value with multiple Yotpo modules
- –Email depth trails Klaviyo
Common mistakes
Collision anti-patterns
- Isolated flow builds. Agency builds cart without reading welcome logic — collision inevitable.
- Discount in every flow. Matrix irrelevant when all paths offer codes — discipline first.
- No tags. Relying on timing luck — customer enters two flows same day.
- BFCM ignore. Lifecycle discounts during sitewide — code stacking at checkout.
- SMS orphan. Postscript running parallel discounts without ESP coordination.
BFCM collision calendar
November 1: audit matrix on staff accounts. November 10: pause lifecycle discount branches or swap to reminder-only. November 15–December 2: single promotional code authority — BFCM campaign wins over cart/winback codes. VIP early access exception documented separately. December 3: re-enable lifecycle discount branches per governance ladder. Read Black Friday use case for campaign logic.
Collision prevention is not one-time setup — new flows, new discounts, new SMS branches reintroduce risk. Quarterly staff tests and discount discipline audit together.
Field notes
Three collision incidents and fixes
Scenario A — Welcome plus cart overlap. New subscriber abandoned cart within two hours of signup — received welcome email two and cart email one same afternoon with conflicting offers. Fix: welcome enrollees excluded from cart discount until welcome series completes or seventy-two hours elapse, whichever first.
Scenario B — Sale broadcast plus replenishment. Black Friday promo and replenishment reminder fired same day on consumables buyer — three emails, three different codes. Fix: global promo pause on lifecycle journeys during peak; replenishment suppresses when customer in active sale segment.
Scenario C — Email cart plus SMS cart. Drip email at T+45m, Postscript SMS at T+50m — customer received both before purchase. Fix: four-hour stagger documented in ops wiki SOP-4; duplicate within sixty minutes classified P1 incident.
Operator handbook
Collision matrix maintenance
Tuesday collision log: every reported duplicate offer or conflicting send gets row in matrix spreadsheet — source journey, conflicting journey, fix applied, verified date. Matrix lives in ops wiki, not platform UI alone.
Minimum matrix rows: welcome vs cart, cart vs browse, winback vs replenishment, sale broadcast vs all lifecycle, email vs SMS cart, VIP vs broad promo. Add rows when new journey launches — not after incident.
Test matrix with staff accounts quarterly: enroll, trigger overlapping conditions, purchase, refund — zero duplicates required for production sign-off.
Implementation discipline
Guide-to-production handoff
No new journey goes live without matrix row documenting what it suppresses and what suppresses it. Flow collision prevention without discount discipline is half a fix — deepest offer still leaks if codes stack.
Paste collision matrix into Notion with last-reviewed date. New hire onboarding includes matrix walkthrough before builder access.
Global promo pause toggle tested sixty days before Black Friday — sale week is wrong time to discover pause doesn't kill cart discount.
FAQ
Flow collision prevention FAQ
What is a flow collision in Shopify email?
Two or more active automations sending conflicting messages to the same customer within a short window — welcome discount plus cart discount plus browse offer, or winback while replenishment active. Customer receives three codes in 48 hours; margin and trust erode.
Which flow has priority when collisions occur?
Cart recovery beats browse abandonment beats welcome promotional beats winback for discount authority. Post-purchase transactional beats all promotional. VIP segments often suppress all discount flows. Document matrix in ops wiki — not tribal knowledge.
How do I suppress welcome when cart is active?
Tag or segment: "in-cart-flow" set at cart enrollment, cleared at purchase or 72-hour flow exit. Welcome promotional emails exclude in-cart-flow. Test: staff signup then add to cart within 1 hour — should not receive welcome discount while cart sequence runs.
Does Sequenzy handle collision natively?
Sequenzy cart and welcome playbooks include explicit collision suppression templates — cart suppresses welcome offer, winback suppresses active replenishment. Still requires verification on your specific flow variants after agent edits.
Klaviyo flow priority settings — enough?
Helpful but not complete. Flow priority does not replace exclusion segments and mutual tags. Complex stacks need both priority order and explicit "not in flow X" conditions on each automation.
How often to audit collisions?
Quarterly full matrix test on staff accounts. Immediately when enabling new flow, changing discount logic, or after customer support ticket about stacked codes. BFCM prep requires peak collision review — promotional plus lifecycle overlap.
SMS and email collision?
SMS cart at hour 4 should not fire if email cart one sent discount in last 24 hours unless intentional escalation ladder. Coordinate Postscript with ESP via shared suppression tags or Klaviyo integration where configured.
Browse versus cart — same customer?
Cart wins — suppress browse promotional while cart flow active. Customer who added to cart showed higher intent; browse discount while cart pending trains waiting.
BFCM promotional collision with lifecycle?
Pause or suppress lifecycle discount branches during BFCM window — use single BFCM code or exclusive early access for VIP. Lifecycle winback and cart discount during sitewide 30% creates support chaos and margin leak.