Shopify order on hold or fulfillment-hold email not sending — after the paid order already stopped moving.

A hold email is not shipping confirmation and not WISMO. Shipping confirmation fires when a fulfillment with tracking exists — that playbook is shipping confirmation email not sending. WISMO is the buyer asking where the package is after (or without) tracking — see WISMO email not sending and WISMO. The staff Slack when Unfulfilled sits too long is unfulfilled order alert— internal, not the customer. This page is the buyer-facing “your order is on hold / we have not shipped yet” path: native Notifications and/or Shopify Flow Send customer email on Order put on hold / Fulfillment order on hold / a timed Unfulfilled delay.

Also not this page: abandoned checkout, refund / cancel, gift card, draft order invoice, return request / label. Six ordinary reasons hold mail never lands: the order was never put on hold, the template or Flow send is off, Notify customer was unchecked, Flow never matched, you tested the wrong email, or sender / spam hid a send that did fire. Walk them in that order. You already pay for Shopify. You do not need a second delay-email app to read the notification list.

Paid + Unfulfilled is the default after checkout. It is not the same as Order on hold or a Fulfillment order on hold. Native hold notifications and most Flow workflows trigger on the hold event (fraud review, payment authorization hold, manual Put on hold, or a fulfillment-hold reason) — not on “warehouse has not picked it yet.” Open the order. If there is no On hold / Hold reason on the timeline, hold-mail templates have nothing to send.

A sticky note in Slack (“wait for restock”) or a tagged order in a spreadsheet is not a Shopify hold. Put the order on hold in admin (or fix the Flow / app that should), then re-read sections 03–05. If your product is an internal ping when Unfulfilled sits past an SLA with no hold at all, use unfulfilled order alert — that page is staff email / Slack, not the buyer.

Preorder, backorder, and “ships in 2 weeks” SKUs that never create a hold also never fire hold mail unless you built a separate Flow on Order paid + wait + still Unfulfilled. Name which path you intended before you debug the wrong template.

Open Settings → Notifications → Customer notifications. Look for order / payment / fulfillment hold related templates (wording varies by Shopify plan and which hold types you use). Read the on/off state, not Order confirmation next to them, not Shipping confirmation, not a preview. Disabled does not send. A staffer who turned native hold mail off “so Flow can own it” and then never activated the workflow leaves a hole that looks like Shopify is broken.

Many shops never enable a native hold template and instead send a custom delay message with Shopify Flow → Send customer email. If that is your path, a missing native template is expected — the bug is Flow (section 05), not Notifications. Do not leave both native and Flow on unless you want two emails for one hold.

Order confirmation can be on and hold mail still off. Shipping confirmation can be on and hold mail still off. Refund and return templates are different events again. Do not debug this page on an Order confirmation toggle.

The template can be on and still not send. Putting an order on hold, releasing a hold, or applying a fulfillment hold often includes Notify customer / Send a notification to the customer. Unchecked means no email, even with a live template and a real hold on the order. Ops who hold orders “quietly” for fraud or inventory often never email the buyer.

This is the warehouse / risk trap. Someone holds forty orders at 9am with the box off, then never sends. A saved browser that remembers the last hold dialog state will keep it off. Restock and capture checkboxes are inventory and money — they do not send the hold email.

For the next test: pick one paid order, put it on hold with Notify customer on (or run the Flow path), to an inbox you control, wait a minute, then read that inbox — not the order timeline alone. The timeline can show “Order put on hold” without “Hold email sent to…”.

Some shops skip native templates and send delay copy with Shopify Flow: trigger Order put on hold / Fulfillment order on hold / Order paid + wait N hours + still Unfulfilled, then Send customer email. If that is your path, a disabled native hold template is expected — the bug is Flow, not Notifications.

Open Shopify Flow → the workflow → Run history. Inactive workflows never run. A condition that requires hold reason = “Out of stock” will skip fraud holds. A wait step that has not elapsed looks like silence. An action that failed (missing customer email, template variable error) shows in the run, not in the buyer’s inbox. Full Flow debugging is Shopify Flow not running— use that page when the workflow itself never fires.

Flow “Send internal email” or Slack is staff mail. It is not the customer hold template. Do not treat a Slack ping to ops as proof the buyer got a delay email — that is the unfulfilled order alert product, not this one.

Placing a test order proves Order confirmation, not hold mail. Fulfilling with tracking proves Shipping confirmation, not a delay email. Issuing a refund proves Order refund. Preview in the notification editor and Send test email prove the template renders. They do not prove a live hold fires it. A staff email on the order is not the customer.

Honest test: checkout from a phone that is not logged into admin, put the paid order on hold with Notify customer on (or run the Flow delay path), to an inbox you own that is not the store’s staff address. Wait. Then search that inbox and spam for the store name. If Order confirmation arrived and the hold / delay mail did not, the bug is hold event / template / notify box / Flow — not “Shopify email is down.”

Missing customer email on the order has nowhere to send — same failure mode as order confirmation, different event. Digital auto-fulfilled SKUs that never stay Unfulfilled also never need a delay email.

Shopify (or Flow) can send and the customer still reports nothing. Open Settings → Notifications and read the sender email. A custom from-address without authenticated DNS (SPF / DKIM for the domain Shopify tells you to add) lands in spam, or is dropped. A shared @shopifyemail.com from-address also gets filtered on some inboxes. BCC to the owner is not proof the customer got it — BCC can arrive while the To: line bounced.

On the order timeline, look for a notification sent event, not just Order put on hold. If Shopify says it sent, have the customer search spam, promotions, and the exact from-address. If Shopify does not say it sent, go back to hold event / template / notify box / Flow — do not buy a deliverability app for a mail that never left.

Do not install a second delay-email app to “make sure it fires.” You will double-email the next customer who was never the bug. Shopify Email (marketing campaigns) and Klaviyo “shipping delay” flows are also not this native hold template — mixing them is how you pay for two products and still send none, or send three.

Stay DIY if you can spend one afternoon on the list above: real hold (or a deliberate Unfulfilled delay Flow), templates / Flow on, notify box on, Flow run history if you use Flow, sender/spam. Put one live order on hold from a phone. Read the inbox. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related troubleshooting: unfulfilled order alert (staff Slack, different audience), shipping confirmation not sending, WISMO email not sending, Shopify Flow not running, order confirmation not sending.

Pay for help when the work is not the notification toggle — it is connecting the stack you already have so hold / delay mail is one live path instead of a native template plus a Flow draft plus a Klaviyo delay flow 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 notification rebuild, 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 recovery-app install typically runs $500–$2,500. A Klaviyo-only rebuild typically runs $2,000–$5,000. $997 is the cheap end of that work, sold as a 72-hour install of three systems — not as a ticket-cut number or recovered checkout revenue.

What it does not buy: fewer WISMO tickets, 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.