Tired of Shopify and Klaviyo sending duplicate order confirmation emails? I’ll walk you through three real-world fixes, from the simple toggle to a resilient, code-level solution to silence Shopify for good.

Dueling Notifications: How to Stop Shopify From Emailing Customers When Klaviyo Is in Charge

I remember a launch a few years back. Codenamed ‘Project Apollo’. We’d spent months building out a beautiful, on-brand customer journey in Klaviyo. The transactional emails were works of art. The launch button was pressed, sales started pouring in, and the Slack channel was full of rocket emojis. Then, about ten minutes later, the first message hit the #support channel: “Hey, a customer is asking why they got two order confirmations. They think they were double-charged.” Then another. And another. A junior engineer on my team, bless his heart, had followed the standard Klaviyo integration guide, but we’d missed one critical detail. We were spamming our brand new, high-value customers on day one. It’s a small oversight that makes you look amateur, fast.

So, What’s Actually Happening?

This isn’t a bug; it’s a feature collision. Shopify is built to be a self-contained universe. Its notification system is deeply integrated and enabled by default because it assumes you have nothing else. When you plug in a powerhouse like Klaviyo to take over email duties, Shopify doesn’t automatically know to stand down. It still sees an order get created and dutifully fires off its own plain, unbranded “Order Confirmation” email, moments before or after your slick Klaviyo template arrives. You end up with two systems trying to do the same job, and the customer is caught in the crossfire.

Let’s walk through how to fix this, from the quick band-aid to the permanent, resilient solution I deploy now.

Solution 1: The Quick & Dirty Toggle

This is the first thing everyone tries, and it’s what you’ll find in most basic guides. It works, but it has its pitfalls.

The process is simple: you navigate to your Shopify Admin, go to Settings > Notifications, and find the customer notifications you want to stop (like ‘Order confirmation’, ‘Shipping confirmation’, etc.). You then click on each one and simply disable it.

• Pros: It’s fast, requires no code, and immediately stops the duplicate emails.
• Cons: It’s fragile. A theme update, a new app installation, or another admin accidentally “fixing” the disabled notification can re-enable it without you knowing. You’re flying blind until customers complain again.

Warning: I consider this a temporary fix. Use it to stop the bleeding during an incident, but plan to implement a more robust solution when you’re out of the hot seat.

Solution 2: The ‘Gut The Template’ Method

This is a much safer approach. Instead of disabling the notification, you effectively “empty” it. This prevents Shopify from sending anything, and it’s much less likely to be accidentally reverted because the template itself is changed.

Here’s the plan:

1. Navigate to Settings > Notifications in your Shopify Admin.
2. Click on the notification you want to silence (e.g., ‘Order confirmation’).
3. Select ‘Edit code’.
4. Delete the entire content of the Email body (HTML).
5. Replace it with a single comment explaining why it’s empty. This is for your future self and your team.

Just paste this into the editor:

<!--
Shopify Notification Disabled.
This email is handled by our primary marketing automation platform (Klaviyo).
Do NOT add content back to this template.
Ref: Darian Vance - 2023-11-15
-->

Now, if the notification trigger fires, Shopify has nothing to send. The “notification” is still technically active, but it’s an empty shell. Problem solved, and you’ve left a clear breadcrumb for anyone who comes after you.

Solution 3: The ‘Conditional Logic’ Fix (My Preferred Method)

This is the real DevOps approach. It’s resilient, auditable, and even provides a fallback. The idea is to have Klaviyo “tag” the order after it successfully sends its email. We then modify the Shopify template to only send if that tag is missing. This means if Klaviyo ever fails, Shopify can step in as a backup. No more missed notifications.

Step 1: Set up a Klaviyo Flow

In Klaviyo, create a flow that is triggered by a Shopify order. The last step in that flow should be to “Update Shopify Customer Properties” and add a tag to the customer, like klaviyo_confirmation_sent.

Step 2: Modify the Shopify Template with Liquid

Now, go back to your Shopify notification template (Settings > Notifications > Order confirmation > Edit code). Instead of deleting everything, you’ll wrap the entire email body in a conditional Liquid tag.

Find the beginning of the email body and add this line at the very top:

{% unless customer.tags contains 'klaviyo_confirmation_sent' %}

Then, scroll to the absolute bottom of the template and add the closing tag:

{% endunless %}

Now, Shopify will only process and send the email if the customer does not have that tag. It’s the best of both worlds: Klaviyo handles the primary communication, and Shopify serves as an automatic, zero-effort failover.

Comparing The Solutions

Here’s a quick breakdown to help you decide which path is right for your team.

Don’t let your tools fight each other. Take a few minutes to implement one of the more permanent fixes. It will save you from that frantic, sinking feeling when the support tickets about duplicate emails start rolling in during your next big launch.

Darian Vance

Lead Cloud Architect & DevOps Strategist

With over 12 years in system architecture and automation, Darian specializes in simplifying complex cloud infrastructures. An advocate for open-source solutions, he founded TechResolve to provide engineers with actionable, battle-tested troubleshooting guides and robust software alternatives.

🤖 Frequently Asked Questions