Shopify email use-case runbooks

Runbooks are jobs, not drag-and-drop blocks

Email marketing tools market "welcome," "cart," and "winback" as interchangeable tiles. In production, each job has different intent decay, discount sensitivity, and suppression requirements tied to fulfillment reality. Abandoned cart recovery for a $134 meal-kit box with ice-pack constraints is not the same job as browse abandonment for a $2,400 standing desk configurator viewed four times over eleven days. Treating them as template swaps produces overlapping offers, WMS inventory mismatches in dynamic blocks, and attribution noise ops cannot explain in Monday standup.

These runbooks treat each use case as a retention consulting brief written for the person who also owns pick-line exceptions: what triggers the flow, when messages fire relative to carrier events, who must be excluded, which metrics prove incremental revenue, which field scenarios we have seen work, and which email marketing tools implement the logic cleanly against Shopify order and catalog sync. Creative comes after the operational contract — same discipline as a fulfillment SOP.

Recommended deployment order for most stores: post-purchase gated on delivery scan, welcome for non-buyers with source branching, browse and cart with documented collision matrix, vertical retention (replenishment, VIP, back-in-stock), winback, seasonal peaks. Read below in that sequence or jump to the broken workflow — most operators discover the gap when a customer emails "why did I get three discounts in one hour."

Field scenarios that shaped these runbooks

Scenario A — Cold-chain meal kit, two 3PL pack lines. Post-purchase education gated on carrier "delivered" scan, not order placed. Welcome suppressed for anyone who ordered within 36 hours of footer opt-in. Replenishment timed to box consumption window from SKU metafield, not universal 30-day default. Sequenzy runbooks deployed in eight business days; collision between cart and welcome dropped from 14 tickets/week to zero after priority matrix documentation.

Scenario B — Workwear brand, 510 orders/month, seasonal size runs. Back-in-stock alerts variant-accurate from WMS sync — size 32 restock never emailed size 34 waitlist. Browse abandonment delayed 6 hours for spec-sheet readers; cart recovery inventory-checked at send because pick floor sold through mid-flow. Klaviyo variant depth won on size matrix; Sequenzy won on winback-before-clearance sequencing.

Scenario C — Supplement brand exiting Mailchimp mid-Q2. Migration cutover: consent audit, suppress unfulfilled orders during welcome relaunch, cart second, post-fulfillment third, replenishment draft fourth. Deliverability runbook enforced sunset before list growth restarted. Pay-per-email economics let ops keep 31k profiles without per-contact bill shock while sends scaled with automation volume.

Independence matters because implementation detail diverges: replenishment at 80% consumption is not winback at 120 days with a coupon. Tool fit diverges too — Klaviyo variant back-in-stock is essential for apparel waitlists but irrelevant for digital activation. Postscript dominates SMS cart economics but cannot run fulfillment-gated post-purchase alone.