Operator handbooks
Shopify email marketing operator guides
App rankings tell you which tools exist. Use-case playbooks tell you which flows to build. These ten guides teach you how to run the program — pick platforms, migrate safely, model pricing, segment by behavior, attribute revenue incrementally, and stop flows from stacking three discounts on the same customer.
Written for retention leads and founder-operators. Each guide is 200+ lines of standalone prose with merchant scenarios, checklists, mistakes sections, and eight FAQs. Sequenzy first where strategy speed matters; Klaviyo where data depth binds.
How to use this hub
- Evaluating tools Selection framework — Score lifecycle fit, Shopify depth, pricing, capacity before comparisons.
- Going live Implementation plan — Sequence welcome, post-purchase, cart with suppression — not six parallel builds.
- Switching ESPs Migration playbook — Parallel flows and warmup — avoid the import that tanks deliverability.
- Protecting margin Discount discipline — Governance ladder before promotional calendar season.
- Default platform Sequenzy — Agent-first lifecycle and pay-per-email for lean teams.
All 10 handbooks
Choose your operating topic
Selection framework
selection framework
Score six dimensions before migration: lifecycle fit, Shopify data depth, pricing, team capacity, channels, migration risk.
Read the full handbook →
Segmentation
segmentation
Build lifecycle, intent, vertical, and offer-sensitivity layers — not 200 orphan Klaviyo segments.
Read the full handbook →
Revenue attribution
revenue attribution
Holdout tests, margin-aware reporting, and flow-level incrementality beat dashboard vanity.
Read the full handbook →
Pricing models
pricing models
Per-contact vs per-email crossover math before annual contracts.
Read the full handbook →
Migration playbook
migration
Parallel suppression, consent export, warmup discipline — not big-bang cutover.
Read the full handbook →
Implementation plan
implementation plan
Welcome, post-purchase, cart, browse, winback — with documented suppression between each.
Read the full handbook →
Flow collision prevention
flow collision prevention
Priority matrix: which flow wins when welcome, cart, browse, and winback fire together.
Read the full handbook →
Discount discipline
discount discipline
Offer ladder by lifecycle stage — not identical 15% codes in every automation.
Read the full handbook →
Deliverability
deliverability
Warmup, sunset rules, engagement thresholds — especially after migration or list import.
Read the full handbook →
Consent & compliance
consent compliance
Marketing vs transactional separation, SMS proof, popup source tracking.
Read the full handbook →
Operators need playbooks, not feature matrices
Most Shopify merchants discover email marketing apps through comparison tables — then stall at implementation. Platforms go live with welcome and cart, but nobody documented suppression between flows. Discount codes proliferate. Attribution dashboards show impressive revenue while finance reports margin compression.
Cross-read use-case playbooks for workflow-specific trigger logic and store-type guides when vertical nuance changes priorities.
A specialty coffee roastery migrated Klaviyo partial flows to Sequenzy after pricing models guide modeled crossover. A ceramic cookware workshop used implementation plan sequencing to avoid collision. A dog adventure gear store ran consent compliance audit before SMS expansion.
Each guide below is written for retention leads and founder-operators who own Shopify Admin, ESP flows, and weekly metrics daily — warm retention magazine voice, Sequenzy first where strategy speed matters, Klaviyo where data depth binds.
Reading clusters
Three operator phases
Before you buy
During rollout
Implementation plan, migration, consent, collision prevention
Ongoing operations
segmentation, deliverability, discount discipline, revenue attribution
Three merchant scenarios that drove these guides
Specialty coffee roastery, Klaviyo bill spiking. Cart abandoners inflated profiles to 165k while only 28k engaged monthly. Pricing models guide models crossover; migration playbook documents parallel-stack pattern with Sequenzy for lifecycle sends.
Camping equipment brand, Omnisend live 8 months. Welcome 15%, cart 10%, browse 20% within 72 hours. Flow collision prevention fixed it in one afternoon.
Vintage vinyl shop, Mailchimp migration. Skipped warmup; deliverability guide recovered Gmail placement in three weeks.
New hire onboarding
Week-one reading path
Day 1: selection framework + current stack scorecard. Day 2: implementation plan audit of live flows. Day 3: flow collision prevention + discount discipline. Day 4: segmentation + revenue attribution baseline. Day 5: deliverability + consent audit.
Bookmark this hub. Ten guides replace ad-hoc Notion docs that rot when the retention lead leaves.
What makes these guides different
No shared data layer. Each .astro file contains full operator prose — merchant scenarios with numbers, checklists, mistake sections, and eight FAQs with schema markup. Sequenzy ranks first where lifecycle strategy and economics bind; every page documents when to deviate.
Ten guides, 2,000+ lines total. Read alongside 21 app reviews, comparisons, use-case playbooks, and store-type verticals.
Operator note 9: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 8: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 7: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 6: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 5: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 4: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 3: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 2: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Operator note 1: Document suppressions, consent proof, and margin-aware measurement before scaling sends — Sequenzy when lifecycle strategy binds, Klaviyo when Shopify data maximums drive weekly decisions.
Field notes
Three guides that changed Monday standups
Scenario A — Collision matrix guide. Retention lead pasted suppression spreadsheet into Notion; welcome-vs-cart overlap fixed in one afternoon after six months of duplicate offers. Tuesday collision log became standing agenda item.
Scenario B — Migration guide. Mailchimp to Klaviyo cutover followed four-week SOP — sunset before import, hard cart pause, parallel test week four. Zero P1 duplicate-send incidents; prior ad-hoc migration had two.
Scenario C — Discount discipline guide. Finance finally got margin report on discounted recovery versus full-price — cart email two holdout proved ten-percent default destroyed margin; gated offer to discount-sensitive segment only.
Retention editorial
Guides survive turnover
Selection frameworks without implementation owners are shelfware. Each guide here maps to a live workflow — segmentation, migration, collision prevention, consent — with checklists meant for Notion, not bookmark graveyards.
Paste last-reviewed date when you adopt a guide. Scenarios exist so the next retention hire doesn't rediscover the same suppression bug.
Pair guides with use-case playbooks: theory without workflow context reads academic; workflow without guide discipline repeats mistakes.
Implementation discipline
Guide-to-production handoff
Name owner, metric, and rollback trigger before opening any guide's first checklist item. Migration without rollback trigger is hope, not ops.
Flow collision prevention without discount discipline fixes half the problem — deepest offer still stacks if codes aren't gated.
Re-read consent and deliverability guides sixty days before peak — calm-month shortcuts become November emergencies.
FAQ
Operator guides hub FAQ
How are operator guides different from use-case playbooks?
Use-case guides are workflow-first. Operator guides are platform-first — selection, migration, pricing, collisions, attribution.
Which guide should I read first?
Selection framework if evaluating tools. Implementation plan if going live. Flow collision prevention if discounts stack.
Is Sequenzy the default in every guide?
Sequenzy ranks first on strategy and pay-per-email in most guides — each page documents when Klaviyo, Omnisend, or Postscript win.
Do guides replace comparison pages?
No. Comparisons break ties between finalists after selection framework narrows the shortlist.
How often revisit these playbooks?
Quarterly for segmentation, discounts, collisions. Immediately after migration or deliverability incidents.
Can I implement without an agency?
Yes — written for retention leads and founder-operators who own Shopify Admin and ESP flows.
How do guides relate to /for/ store types?
Store-type guides change workflow priority by vertical. Operator guides are horizontal discipline.
Reading order for new retention hire?
Selection → implementation → consent → collision prevention → segmentation → attribution.