Should You Suppress Native Emails for a Custom ESP Flow?
Suppressing native transactional emails is a CUSTOMIZE on Shopify Plus: have Shopify Support turn off one specific notification at a time, after the replacing ESP flow has run clean for 30 days. Keep the order confirmation native the longest. Suppression is a Plus entitlement executed by Support at the store owner's request, not an admin toggle (per Shopify help, Sep 2026). Below Plus the order confirmation always sends, so brand the Liquid templates instead.
Your profile — see how the verdict shifts
- Confidence
- High — Shopify's Plus plan page lists suppressing specific Shopify notification emails from being sent to customers as a plan feature (verified Sep 2026). Shopify's customer-notifications help page, read 2026-09-05, states that on the Shopify Plus plan the store owner can contact Shopify Support to turn off specific email and SMS notifications, that the order confirmation is sent when a customer places an order, that six notifications (order canceled, order refund, shipping confirmation, shipping update, out for delivery, delivered) can be deactivated when performing specific actions in the admin, and that Shop app tracking notifications can't be deactivated or edited by merchants. Klaviyo (4.7★, 3,264 reviews) and Omnisend (4.8★, 2,965 reviews) were checked as the ESPs whose flows replace those notifications. The verdict is high-confidence because the mechanism is documented; the boundary (prove each flow first) comes from how a paused flow fails, silently and completely.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · DTC · Klaviyo or Omnisend running a branded post-purchase journey · single storefront · agency dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| Not on Shopify Plus | WAIT | The order confirmation can't be turned off below Plus. Brand the native Liquid templates, and skip the six per-action notifications your ESP replaces by unchecking the send box when you fulfill, refund or cancel. |
| Plus · ESP used for marketing only | WAIT | Keep every transactional email native and brand the templates for $3,000–$10,000 (Deploi estimate, illustrative). Duplicate-free by construction, no Support request, no flow to babysit. |
| Plus · a proven ESP post-purchase journey | CUSTOMIZE | Have Support suppress the specific notifications your flows replace, one at a time after each has run clean for 30 days. The order confirmation moves last, if at all. |
| Plus · several brands or a headless storefront | BUILD | One webhook-driven transactional pipeline with your own templates gives every brand and storefront the same email stack, at $15,000–$40,000 (Deploi estimate, illustrative), with native notifications suppressed through Support. |
What Native Transactional Email Suppression Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | One confirmation and one shipping update, in one design, instead of two systems announcing the same event minutes apart in different voices. |
| Revenue — indirect | Medium | Transactional emails are opened far more often than campaigns, so cross-sell and replenishment blocks inside the ESP's shipping emails earn revenue the plain native template can't. |
| Operational efficiency | Medium | Fewer duplicate-order tickets asking whether the purchase went through twice, and one template system for the marketing team to maintain. |
| Data & insight | Medium | Engagement on transactional emails inside the ESP feeds segmentation; a custom pipeline puts the same signals in your warehouse next to the orders they belong to. |
Spend ceiling: Spend on the cutover discipline, not the emails. Template branding is $3,000–$10,000 (Deploi estimate, illustrative) and the ESP is already paid for; only a multi-brand or headless stack justifies a $15,000–$40,000 pipeline (Deploi estimate, illustrative).
What buying enables (top apps)
- + One designed post-purchase journey with tracking, cross-sell and review blocks in the ESP your team already runs
- + Flow-level segmentation on transactional sends: first order versus repeat, subscriber versus not
- + Engagement data on receipts and shipping emails inside the ESP's customer profiles
What building additionally unlocks
- + One transactional stack across brands and storefronts, including headless, with per-locale and per-brand templates
- + Send logs, opens and bounces in your own warehouse next to the orders they belong to
- + A sending provider you can swap without rebuilding flows, because templates and handlers are your code
Find Your Verdict in 3 Questions
Is your store on Shopify Plus?
Yes: Go to question 2.
No: Your verdict: WAIT — the order confirmation can't be turned off below Plus; brand the native templates and skip the six per-action notifications your ESP replaces.
Has an ESP post-purchase flow (Klaviyo, Omnisend) run clean alongside the native email for 30 days?
Yes: Go to question 3.
No: Your verdict: WAIT — keep everything native, brand the Liquid templates ($3,000–$10,000, Deploi estimate, illustrative), and run the ESP flow to a test segment first.
Do several brands or a headless storefront need one transactional email stack?
Yes: Your verdict: BUILD — a webhook-driven transactional pipeline, $15,000–$40,000 (Deploi estimate, illustrative), with native notifications suppressed through Plus Support.
No: Your verdict: CUSTOMIZE — have Support suppress the specific notifications your ESP replaces, one at a time, and keep the order confirmation native the longest.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | ESP flows plus a Support request are days of work; a custom transactional pipeline is 4–8 weeks (Deploi estimate, illustrative). | ||
| Recurring fees | Klaviyo and Omnisend price by contacts, and the transactional sends ride on a subscription marketing already pays; a custom pipeline pays per-send rates and hosting. | ||
| Maintenance & upgrades | ESP templates are marketing's to maintain; a custom pipeline owns webhook version moves, template code and deliverability monitoring. | ||
| Switching & exit | One more Support request restores the native notifications, but ESP flows and templates rarely port between vendors; a pipeline's templates and sender configuration move with you. | ||
| Risk | |||
| Vendor risk | An ESP outage or a paused flow now means no order confirmation rather than a late campaign; native notifications fire with the order and need nobody awake. | ||
| Security & compliance surface | Transactional emails carry order and address data, and both paths move that data out of Shopify, into an ESP or into your own sender. | ||
| Platform-deprecation exposure | Notification templates, webhooks and the Plus suppression entitlement are stable, undated features; neither path sits on a sunset. | ||
| Value | |||
| Fit to requirement | ESP flows deliver one branded journey with tracking and cross-sell blocks; a pipeline adds per-brand, per-storefront and per-locale control the ESP template model resists. | ||
| Time to market | Flows this week and a suppression request after the 30-day proof; a pipeline takes a quarter. | ||
| Performance & scale | Neither path touches the storefront; both scale with order volume at the sender's rate limits. | ||
| Data ownership & AI-readiness | Engagement on transactional emails lands in the ESP's profiles; a pipeline keeps opens, clicks and bounces in your own warehouse next to the orders. | ||
| Focus & opportunity cost | Marketing already owns the ESP; a transactional pipeline is an engineering product with an on-call rota. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Klaviyo: Email Marketing & SMS | Live — 4.7★, 3,264 reviews. Journey logic, segmentation and send-time control live in Klaviyo's own canvas, not in Flow's editor, so ops staff work in two tools. Contact-based pricing means the bill tracks list growth rather than message volume. | Free forever for up to 250 email contacts and 150 SMS/MMS credits; SMS from $15/month for up to 1,250 credits with carrier fees included; Email from $20/month for 251–500 contacts, scaling with the list (verified Sep 2026) | A branded post-purchase journey already running in the ESP your marketing team lives in |
| Omnisend Email Marketing & SMS | Live — 4.8★, 2,965 reviews. Pre-built automations on the free tier make it the cheapest way to test whether a journey belongs outside Flow. Starting prices cover a contact count and rise as the list grows, so model the list you expect in a year. | Free to install for up to 250 contacts and 500 emails/month; Standard from $16/month for up to 500 contacts with 6,000 emails/month; Pro from $59/month for up to 2,500 contacts with SMS from $0.007/message (verified Sep 2026) | The lower-priced ESP route to the same suppress-and-replace pattern |
| Shopify notification templates + Plus email suppression | Native — First-party Shopify. Every plan edits the Liquid templates for order, shipping and account notifications. Six notifications (order canceled, order refund, shipping confirmation, shipping update, out for delivery, delivered) can be skipped per action in the admin; the order confirmation always sends. On Shopify Plus, the store owner can contact Shopify Support to turn off specific email and SMS notifications, which the Plus plan page lists as suppressing specific notification emails. Shop app tracking notifications can't be deactivated or edited by merchants (per Shopify help, Sep 2026). | Included on every plan; suppression is a Plus entitlement (verified Sep 2026) | Duplicate-free transactional email with zero ESP dependency, branded through Liquid |
| Custom transactional pipeline | Build lane — Order, fulfillment and refund webhooks into your own service, rendering your templates and sending through a transactional provider, with native notifications suppressed through Plus Support. Worth it for headless or multi-brand stacks that need one email system across storefronts. | $15,000–$40,000 one-time plus roughly $2,500–$8,000/yr upkeep and per-send fees (Deploi estimate, illustrative) | Headless or multi-brand Plus organizations standardizing transactional email across storefronts |
The Build Path
- Brand the native templates first: Edit the Liquid templates for order confirmation, shipping confirmation and refund so they match the ESP's design system. This costs $3,000–$10,000 (Deploi estimate, illustrative), fires with the order, and needs no suppression at all. Even a store that later suppresses should keep these current as the fallback.
- Suppress one notification at a time, with proof: Run the ESP flow to a test segment alongside the native email, compare delivery timing and inbox placement for 30 days, then have the store owner ask Shopify Support to turn that specific notification off. Repeat per notification. The order confirmation is the receipt customers depend on, so it moves last, if at all.
- Guard the gap: A paused flow fails silently. Add monitoring that alerts when hourly orders outpace ESP transactional sends by more than a few percent, and write the runbook for asking Support to re-enable the native notification during an ESP incident. For a multi-brand or headless pipeline, add a reconciliation job, since webhook delivery isn't guaranteed.
- Effort band
- $3,000–$10,000 for template branding and the suppression cutover, or $15,000–$40,000 for a custom transactional pipeline — Deploi estimate (illustrative); the $10–25K and $25–75K contact-form bands respectively
- Typical timeline
- 2–3 weeks for templates and cutover; 4–8 weeks for a pipeline (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $500–$1,500/yr for templates and $2,500–$8,000/yr for a pipeline plus per-send fees (Deploi estimate, illustrative).
- What you own — and what you take on
- You own: the templates, the cutover order and the proof that each replaced notification performs. You take on: an ESP or a sender in the path of the order confirmation, and the monitoring that catches a silent flow failure.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $3,000–$10,000 (templates, flows, cutover) | $15,000–$40,000 |
| Years 1–3 (recurring) | $1,500–$4,500 (template upkeep) | $7,500–$24,000 (upkeep and per-send fees) |
| 3-year total | ≈$4,500–$14,500 | ≈$22,500–$64,000 |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Buy column: Klaviyo or Omnisend already paid for marketing (entry tiers verified Sep 2026; mid-market pricing scales with contacts), so only template work and the cutover labor are new money; three-year horizon.
- † Build column: custom transactional pipeline with a per-send provider; native suppression through Plus Support on both paths.
What the Sticker Price Hides
On the buy path
- — Suppression is a Support request by the store owner, not a toggle, so rolling back during an ESP incident takes a ticket rather than a click
- — A paused or errored flow means no order confirmation, and nothing in Shopify tells you
- — Shop app tracking notifications keep sending regardless, so the duplicate you were trying to remove survives for Shop users
- — ESP entry tiers ($16–$20/month, verified Sep 2026) bear no relation to a mid-market list; the transactional sends ride on whatever contact tier you've grown into
On the build path
- — You inherit deliverability: sender reputation, authentication and bounce handling for the one email every customer expects
- — Webhook delivery isn't guaranteed; Shopify's own guidance is a reconciliation job so no order goes unconfirmed
- — Template parity across order, shipping, refund and cancel events is more surface than it looks
- — ~$2,500–$8,000/yr upkeep plus per-send fees (Deploi estimate, illustrative)
What Merchants Say
The duplicate-confirmation complaint is constant in ESP communities: one receipt from Shopify, one from the flow, minutes apart in two designs, and for Plus stores the answer turns out to be a Support request rather than a setting.
Merchants who moved the confirmation into a flow describe the day the flow was paused by mistake and no customer received a receipt, which nobody noticed until the tickets arrived.
If You Change Your Mind Later
If you bought and outgrow it
One more Support request turns the native notifications back on, so leaving suppression is cheap. The flows and templates inside the ESP are what you lose on a vendor change, since neither Klaviyo nor Omnisend templates port cleanly. Keep the native Liquid templates branded even while suppressed, so the fallback looks like you on the day you need it.
If you built and want out
Templates, sender configuration and send logs are yours and move to any provider; the webhook handlers are ordinary code. If you retreat to native notifications, a Support request re-enables them and the branded Liquid templates you kept current take over the same day.
When This Answer Changes
We're watching for:
- ▸ Shopify exposing notification suppression as a self-serve admin setting instead of a Plus Support request
- ▸ Shopify allowing the order confirmation to be deactivated below Plus (today only six fulfillment, refund and cancel notifications can be skipped per action)
- ▸ Shop app tracking notifications becoming merchant-editable, which would close the one duplicate you can't control today
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Can you turn off Shopify's order confirmation email?
Shopify's order confirmation email can be turned off only on Shopify Plus, and only by request. Shopify's help states that on the Plus plan the store owner can contact Shopify Support to turn off specific email and SMS notifications (per Shopify help, Sep 2026). Below Plus the order confirmation always sends when a customer places an order. Six other notifications, including shipping confirmation and order refund, can be skipped per action on any plan.
Should order confirmations come from Klaviyo or from Shopify?
Order confirmations should stay native until your ESP flow has proven equal deliverability for 30 days. Shopify's notification fires with the order, needs no subscription and is branded through Liquid for $3,000–$10,000 (Deploi estimate, illustrative). Klaviyo (Email plan from $20/month, verified Sep 2026) or Omnisend flows deliver one designed journey, but a paused flow means no receipt at all, so suppress that notification last.
What can't be suppressed even on Shopify Plus?
Shop app notifications can't be suppressed on any plan. Shopify's help states that notifications sent from the Shop app for tracking updates and order statuses can't be deactivated or edited by merchants (per Shopify help, Sep 2026). Customers who track through Shop still receive its updates alongside your ESP's shipping emails, so design the ESP shipping flow to add information the Shop app doesn't show rather than repeating the tracking number.
Your Next Steps
If you're going with CUSTOMIZE(matches your selected profile)
- Brand the native Liquid templates first, so the fallback matches the ESP's design
- Map every native notification to the ESP flow that replaces it, and mark the ones with no replacement as keep-native
- Run each ESP flow to a test segment for 30 days and compare delivery timing and inbox placement against the native email
- Have the store owner ask Shopify Support to turn off one proven notification at a time; the order confirmation goes last
- Add monitoring that alerts when orders outpace ESP sends, and write the re-enable runbook before the first suppression
If you're going with WAIT
- Brand the native templates for order confirmation, shipping confirmation and refund
- Uncheck the send-notification box (or your fulfillment integration's equivalent) for the six per-action notifications your ESP replaces
- Keep the ESP for marketing-adjacent post-purchase emails: review requests, cross-sell, replenishment
- Revisit suppression at your Plus renewal, once the ESP flows have a deliverability record to show
Official Docs & Sources
- Shopify Plus plan features — Shopify Help Center
- Webhooks (Shopify dev) — shopify.dev
- Shopify Flow — Shopify Help Center
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build a Custom Flow Connector on Shopify Plus?
Only Plus stores can use Flow tasks from custom partner apps. Build one when an outside event must start a workflow; Send HTTP Request covers outbound calls.
Plus's 30-Day Card Authorization vs. a Custom Reauth Flow?
Plus stretches Shopify Payments authorizations from 7 to up to 30 days for some payment types. Nothing to build inside that window; past it, buy a deposit app.
Should You Build or Buy Flash-Sale Scheduling on Shopify Plus?
Launchpad, free on Plus, schedules publishing, prices, theme and inventory for a drop. Move Scripts-era rules to Discount Functions; buy a queue only for huge drops.
Shopify Audiences vs. a CDP: Which Builds Better Ad Lists?
Shopify Audiences is included with Plus but gated to US and Canada stores on Shopify Payments. Switch it on first; a CDP answers a different question.
Should You Build or Buy Abandoned Checkout Recovery on Shopify?
Abandoned checkout recovery belongs in the email/SMS platform you already pay for, with an audited tracking layer underneath.
Ready to end the duplicate-email problem for good?
We brand the native templates, prove each ESP flow against them, run the suppression cutover through Plus Support, and add the monitoring that catches a silent flow failure.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.