Klaviyo and Shopify notifications that overlap — or one of them is silent.

These are two different bugs. Treating them as one “our emails are a mess” problem is how you buy another app and still send the wrong mail.

• Overlap: Shopify’s shipping confirmation and a Klaviyo “your order is on the way” both fire on the same fulfillment. The customer gets two emails that almost agree, and they write because they do not.
• Silence: Shopify shipping confirmation is off because “Klaviyo handles it,” and the Klaviyo flow is still a draft, filtered to the wrong list, or triggered on Placed Order instead of Fulfilled Order. Day 0 they get the receipt. Day 1–3 nothing. Day 4 they write “where is my order?”

You already pay for both tools. The job is not “add notifications.” The job is to make each event fire once, from one owner, with a working tracking link. Pre-purchase overlap is a different page — the abandoned-checkout playbook. Post-purchase inbox replies sit in the WISMO playbook. This page is only the mail that is supposed to fire after they already paid.

Shopify customer notifications live in Settings → Notifications. Order confirmation, shipping confirmation, shipping update, out for delivery, delivered. They are transactional. They ship with the order number and, when fulfillment wrote tracking back, a tracking URL.

Klaviyo is marketing email and SMS. Flows triggered on Placed Order, Fulfilled Order, or a Shopify “shipped” metric can look like the same mail. They are not the same system of record. Klaviyo does not buy the label. Shopify does. If the Klaviyo email is not gated on an actual fulfillment, it is a story, not a status.

Neither tool is broken when the mail overlaps or goes silent. The usual failure is nobody owned the event: Shopify was on at launch, a Klaviyo partner later published a post-purchase flow, and both are “working.”

The order confirmation is the receipt. It is also the first place the order status page is linked. Keep it in Shopify. Do not send a second “thanks for your order” from Klaviyo on Placed Order.

If you already have a Klaviyo Placed Order flow, open it. If email 1 is a receipt with the order number and line items, that is the overlap. Turn that email off. A review ask, a how-to-use note, or a cross-sell can wait until they have the shipping confirmation — or sit in a later email that is clearly marketing, not a second receipt.

Place a $1 test order to yourself. Confirm one confirmation arrives, from the Shopify sender, with a working status-page link, on a phone that is not logged into admin. The flow canvas is not the proof. The inbox is.

Most “where is my order?” threads start as a notification gap, not a helpdesk gap. Silence after the receipt. Or two shipping emails that disagree on the tracking URL. The WISMO playbook covers the inbox reply. This section is the mail that should have made that reply unnecessary.

Shopify shipping confirmation should fire when the label exists, with a tracking URL that opens. If you buy a label and the box sits until pickup, say that in the email. “Label created” and “picked up” are different events. Customers can tell.

A Klaviyo “your order is on the way” that is not tied to an actual fulfillment creates WISMO. It tells them the box is moving when it is still on a shelf. Do not run that flow on Placed Order. If you keep a fulfillment flow in Klaviyo, it must wait for Fulfilled Order (or the equivalent Shopify metric) and it must not duplicate Shopify’s shipping confirmation. One shipping email. Shopify is the default owner because it has the tracking number first.

Open both places the same afternoon. Do not trust memory.

• Shopify admin: Settings → Notifications → Customer notifications. Note which of Order confirmation, Shipping confirmation, Shipping update, Out for delivery, and Delivered are on.
• Klaviyo: Flows. Find anything triggered on Placed Order, Fulfilled Order, a Shopify “shipped” / “order fulfilled” metric, or a flow named “post-purchase” that still sends a receipt. Live, manual, or draft — write it down.
• Any 3PL, shipping app, or Shop app message that can email the same customer on the same event. If it can send, it counts.

Then fulfill one real test order (or a $1 order to yourself) and watch the inbox for 24 hours. Count the emails. Click every tracking link on a phone that is not logged into admin. If two shipping emails arrived, that is the overlap. If none arrived, that is the silence.

Pick one sender for each event. Write it down. Then turn the other off for that event.

• Order confirmation: Shopify. Klaviyo Placed Order does not send a second receipt.
• Shipping confirmation: Shopify, unless you have a specific reason Klaviyo owns it and Shopify’s template is off. Not both.
• Shipping update / delivered: Shopify if the carrier integration supports it. Do not stack a Klaviyo “out for delivery” on top unless Shopify’s is off.

Two systems on the same trigger is the overlap bug. Shopify off because “Klaviyo handles it,” Klaviyo still a draft, is the silence bug. They are the same missing decision: who owns this event.

This page is not “turn Klaviyo off.” Klaviyo is the marketing tool you already pay for. It should keep the mail that is not a status update:

• A how-to-use or education email after they have tracking, not instead of tracking.
• A review ask after a delivered event you can actually see — not on day 2 while the box is still in transit.
• A replenishment or cross-sell that is clearly marketing. Do not dress it as “your order update.”

SMS on the same fulfillment is extra cost and extra consent rules. Skip it until email arrives once, on time, with a working tracking link. A text on top of two shipping emails is not a notification strategy.

• Do not run Shopify shipping confirmation and a Klaviyo “on the way” flow on the same fulfillment.
• Do not send a Klaviyo “your order is on the way” on Placed Order. That email creates WISMO.
• Do not turn Shopify notifications off until you have watched a real Klaviyo fulfillment email land with a working tracking link.
• Do not stand up Gorgias to answer mail that a working shipping confirmation would have prevented.
• Do not buy a third notification app to paper over a draft flow and a native toggle you never opened.
• Do not promise fewer WISMO tickets, recovered checkout revenue, or a lift. This page will not either.

Stay DIY if you can spend one afternoon on the audit above: list every live notification, pick one owner per event, turn the other off, fulfill a test order, and click the tracking link on a phone. That is the whole playbook. No agency required.

Pay for help when the work is not the email template — it is connecting the stack you already have so post-purchase mail is one workflow instead of a draft in Klaviyo plus a native toggle you forgot, lead capture is not dying in DMs, and exceptions show up in a channel you already check. That is the Latch AI Ops install.

What $997 USD one-time buys: lead capture on the live store, ops alerts in a channel you already check, and a checkout-ready workflow. 72 hours after collaborator access, not after payment. One live Shopify store. Access plus a delivery thread. Store URL collected at checkout. Not a SaaS seat, not a Klaviyo rebuild, not a Gorgias implementation, not a support VA, not a brand or theme job.

Other shops’ public ranges, not testimonials: a Shopify Flow or notification-app install typically runs $500–$2,500. A Klaviyo-only flow rebuild typically runs $2,000–$5,000. Dedicated Gorgias implementation shops start around $3,750. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as recovered revenue or a ticket-volume cut.

What it does not buy: fewer WISMO tickets as a guarantee, recovered checkout revenue, a lift in conversion, or a case study. Latch AI Ops has not published customer proof because there are no customers yet. You are buying the install.

Checkout is on Whop. Operator is Nico. United States offer. You can revoke collaborator access after handoff. We do not take owner passwords.