Skip to content

Systems Stack

Email: when to use native, when to upgrade, when to kill the app.

Shopify Email vs Klaviyo vs Mailchimp. When native is enough, when to upgrade, and when to replace automations with custom Flow or theme code.

Last updated: September 10, 2026

Shopify rebranded Shopify Email to Shopify Messaging in 2024 (it now also sends SMS and WhatsApp from the same app). Same free native tool. We still call it Shopify Email below since that's what people search.

Email stack recommendations by revenue band
Band Install / use Skip Replace with
$50K/year Shopify Email (free) Klaviyo, Mailchimp, Omnisend Nothing yet, stay native
$250K/year Klaviyo (or stay on Shopify Email) Mailchimp Flow for discount/tag triggers
$1M/year Klaviyo or custom ESP Paying ESP only for triggers Flow + theme forms for capture

Email stack at $50K/year

Install: Shopify Email (free, native). Covers abandoned cart, welcome series, and order confirmation. Templates are basic but that's fine. You're sending maybe 500–1000 emails a month, nowhere near the 10,000 free sends included every month (then $1 per 1,000 after that). Segmentation is "bought once" or "hasn't bought" which is enough at this band.

Skip: Klaviyo, Mailchimp, Omnisend. At $50K/year (roughly $4K/month), you're not justifying $60–$300/month for advanced segmentation you won't use. Klaviyo makes sense when you're doing $15K–$20K+/month and need win-back flows.

Kill signal: You're paying for features you haven't configured. If you installed Klaviyo 6 months ago and you're still using the default abandoned cart template, downgrade to Shopify Email and save $100+/month.

Email stack at $250K/year

Install: Klaviyo (roughly $60–$150/month at this band). You're doing $20K/month. Advanced segmentation (RFM, predicted LTV, engagement-based), post-purchase flows, and win-back campaigns pay for themselves. Browse abandonment (separate from cart) is worth building. A/B testing on send time and subject lines matters now. Klaviyo bills on total active profiles in your account, not revenue, so check your actual profile count against Klaviyo's tiers. A list-heavy, low-AOV store can land in a higher tier than these numbers suggest.

Or stay: Shopify Email if campaigns aren't the job. If you're only sending abandoned cart and order confirmation, Shopify Email still works. Don't install Klaviyo just because competitors have it. Install when you're ready to use segmentation and campaigns.

Skip: Mailchimp, usually. Mailchimp's Shopify integration now handles abandoned-cart and post-purchase automation, but you need the Standard plan ($20+/month) to get any of it, and segmentation still trails Klaviyo. If you're already on Standard+ and it's working, that's fine. Don't add it new for this job.

Kill signal: Duplicate sends. If you're running Shopify Email and Klaviyo, both send abandoned cart. That's duplicate sends. Pick one sender per automation type. Turn off Shopify Email's cart automation or Klaviyo's. Customer gets two emails 10 minutes apart = trust lost.

Replace with Flow: Discount code triggers. If you're using Klaviyo just to send a welcome discount after email signup, move that to Shopify Flow. Flow triggers the discount code, sends it via Shopify Email or Klaviyo. Don't pay Klaviyo for logic that Flow does free.

Watch for: Events that never fire. If Started Checkout or Placed Order don't match the store, flows look fine and still miss people. Shopify Klaviyo events covers that store-side gap.

Email stack at $1M/year

Install: Klaviyo (roughly $200–$700/month at this band). You're doing $80K+/month. You need campaigns (weekly sends, product launches, seasonal), predictive analytics, and deep segmentation. You're testing send time optimization, dynamic content blocks, and conditional splits. Klaviyo's cost is high but justified when email drives 15–30% of revenue.

Consider: Custom ESP (SendGrid, Postmark, AWS SES). If you're sending 500K+ emails/month and Klaviyo's pricing hits $1K+/month, a custom ESP with Flow + metafields for segmentation can cut costs 60–80%. This is a project (2–4 weeks), not a DIY weekend. Only worth it when Klaviyo's pricing is absurd for your volume.

Replace with Flow: Non-email automations. If Klaviyo is triggering Slack pings, tagging customers, or updating metafields, move that to Shopify Flow. Use Klaviyo for email content and audience building. Use Flow for store-side logic (tags, metafields, webhooks).

Replace with theme code: Email capture popups. Most popup apps (Privy, Justuno, OptinMonster) slow the page by 300–800ms. Build a native email capture form in the theme footer or a drawer. Use Shopify's Customer API to subscribe. No third-party JavaScript. If you need exit-intent, use theme-based scroll triggers (lightweight JavaScript in the theme).

Kill signal: Customer complains "I got this twice." Duplicate sends (cart email from Shopify Email + Klaviyo, or post-purchase from both) mean you never turned off one sender. Or leftover Klaviyo snippets in the theme still fire after you switched to Shopify Email. Duplicate cart emails explains the fix.

Duplicate senders (kill signal)

Kill signal: Shopify Email and Klaviyo both send abandoned cart (or welcome). Customers get two emails for one cart. Pick one owner per job. Turn the other off for that automation, then hunt leftover theme scripts if the second sender still fires.

At this ICP: Stay on Shopify Email until segmentation or volume actually needs Klaviyo. Don't buy Klaviyo because a podcast said so. If you're on Klaviyo and still paying for flows you never opened, that's the kill, not the ESP itself.

When to call us

We wire the store side: flows that match checkout, events that fire correctly, no duplicate sends. We also audit the stack and replace the app when that's the job. Storefront, business automations, and email. A project or a retainer.

Straight answers.

When you need segmentation beyond 'bought once' or when you're sending more than basic abandoned cart and post-purchase. Usually around $100K–$250K/year when the revenue justifies the cost.

Next step

Contact us.

A short note about the store is enough.