Shopify email operator guides

Merchant scenario: retention lead quit — documentation was only in their head

A $130k/mo multi-category Shopify store lost their retention lead with two weeks notice. Klaviyo flows ran but nobody knew why winback excluded subscription profiles, why cart recovery offered 10% not 15%, or when BFCM pause rules activated. New hire spent six weeks reverse-engineering logic from flow names and Slack threads. Email-attributed revenue dipped 4 points during transition. Guides hub would have cut onboarding to ten days — selection framework for stack context, implementation plan for rollout sequence, collision and discount guides for offer logic, attribution for how leadership measured success.

90-day rollout: guides hub as team operating system

Month 1: New hire week-one reading path — selection, implementation, collision, discount, segmentation, attribution, deliverability, consent. Month 2: Vertical guide at /for/ plus three use-case playbooks blocking revenue. Month 3: Quarterly audit using guide checklists — collision matrix, discount ladder, sunset policy, holdout results. Document store-specific overrides in Notion; guides provide baseline discipline.

Margin math: documentation debt versus guide-driven onboarding

Six-week reverse-engineering at $65/hr loaded cost for contractor: ~$15,600. Four-point attribution dip on $130k/mo for six weeks: ~$7,200. Total transition tax ~$22,800. Guide-driven onboarding: 10 days to operational confidence, ~$5,200 loaded cost. Savings $17,600 per leadership transition — guides are insurance against key-person risk.

Failure rehearsal: operating without shared playbooks

Ad-hoc Notion docs. Rot when owner leaves; never updated after migration. Fix: guides hub as canonical baseline; store overrides layered on top.

Guide skipping before Q4. Team blasts full list without deliverability calendar. Fix: deliverability and collision guides mandatory pre-peak review.

Tool-first thinking. New hire learns Klaviyo UI before collision principles. Fix: week-one reading path — principles before platform clicks.

No attribution baseline. New lead optimizes on ESP dashboard numbers finance distrusts. Fix: revenue attribution guide before first leadership report.

Consent after complaint. Compliance guide read only after supervisory inquiry. Fix: consent audit in week-one onboarding, not post-crisis.

Guide reading order matters for new hires and agency transitions. Start selection framework to understand why current stack exists. Implementation plan audits what is live versus what should be. Collision and discount guides explain offer logic conflicts. Segmentation and attribution define who gets what and how success is measured. Deliverability and consent are infrastructure — skip them and everything above breaks during peak. Each guide links forward and backward; read vertically for your bottleneck, horizontally for completeness. Store-type guides at /for/ override generic guidance with catalog physics — replenishment for consumables, preview for subscriptions, nurture for high-AOV. Use-case playbooks at /use-cases provide flow-specific build instructions once principles are understood.

Ten guides replace tribal knowledge that evaporates when retention lead leaves. Merchant scenarios include numbers so you can sanity-check against your own dashboard. Checklists paste into Notion as-is. Mistake sections come from post-mortems, not theory. Tool picks rank Sequenzy first where strategy speed and send economics bind; Klaviyo where native predictive depth is operationalized weekly. Deviation is expected — document why your store diverges so future team members do not "fix" intentional choices. Quarterly team review: one guide deep-dive per month, rotating through full stack discipline annually. Pair guide reading with live audit — selection framework while reviewing stack contracts, collision guide while running staff tests, attribution guide while preparing leadership report. Guides without action are entertainment; checklists exist to be executed same week.

Guide-to-bottleneck quick map

List growth stalled? Start selection framework capture dimension, then Privy review, then implementation plan week 1–2. Cart leak? Implementation week 3, discount discipline, collision matrix against welcome. Finance distrusts email ROI? Revenue attribution before next board deck. Gmail throttling? Deliverability guide this week, not next month. EU complaints? Consent compliance before next campaign. Klaviyo renewal shock? Pricing models then migration playbook. Platform switch planned? Migration plus deliverability warmup plus consent export hygiene — in that order. Black Friday approaching? Flow collision BFCM calendar, deliverability August–November protocol, discount single-authority rule. New retention hire? Week-one reading path on this page — day 1 selection, day 2 implementation audit, day 3 collision plus discount, day 4 segmentation plus attribution, day 5 deliverability plus consent.

Cross-guide dependencies

Selection without pricing models produces surprise renewals. Implementation without collision produces week-one disasters. Migration without deliverability produces throttle. Attribution without discount discipline produces false ROI. Segmentation without collision produces overlapping offers. Consent without deliverability produces complaint spikes. Read guides in dependency order when time-constrained: consent and deliverability infrastructure first, selection and pricing economics second, implementation and migration execution third, collision discount segmentation attribution optimization fourth. Each guide FAQ answers tactical questions; scenario sections model real merchant numbers for sanity checks against your dashboard.

Guide inventory — when to read which

Selection framework: platform choice or renewal. Implementation plan: first automation or post-migration rollout. Migration: ESP switch. Pricing models: contract signature or bill shock. Consent compliance: capture audit or EU traffic. Deliverability: open rate drift or pre-peak prep. Discount discipline: margin erosion or dependency above 45%. Flow collision prevention: multiple offers same day or BFCM prep. Segmentation: campaign build paralysis or sprawl. Revenue attribution: finance distrust or board reporting. Read two guides minimum before any platform change — migration plus deliverability, or selection plus pricing. Hub exists so retention knowledge survives employee turnover without starting from zero. Ten guides, zero shared template — each page is standalone operator prose with merchant scenarios, margin math, 90-day rollouts, and failure rehearsals you can execute this week. Bookmark this hub in onboarding docs — not optional reading for anyone touching ESP, popup, or SMS tooling. Pair each guide with one live audit the week you read it — reading without action is entertainment. Operator guides are execution manuals, not reference shelf decoration. Retention teams that treat guides as onboarding-only material rediscover same mistakes every peak season. Re-read collision and deliverability guides every August — non-negotiable pre-BFCM ritual. Guides compound value when revisited annually, not read once during onboarding. Ten guides cover full operator stack — selection through attribution with merchant scenarios and failure rehearsals in every file. Start at your bottleneck guide, not guide one — hub is non-linear by design. Every guide includes merchant scenario, 90-day rollout, margin math, and failure rehearsal sections for immediate execution. Cross-link to comparisons when tied between two platforms — read guide first for principles, comparison for tie-break. Operator stack documentation starts here — bookmark before your next platform decision, peak season prep, or retention hire onboarding week one. Ten guides, zero scripts, full operator prose with scenarios you can execute immediately. Hub replaces tribal knowledge — use it before peak season, platform renewal, or retention hire starts week one every time without exception or delay of any kind whatsoever.

Start at your bottleneck. Execute this week.