Shopify Flow not triggering — the order, tag, or inventory event never starts the workflow.

Several products can look like “Shopify automation did not fire.” They do not share a canvas or a run log. This page is only Shopify Flow in admin when the workflow never starts (or starts and is immediately filtered) on an order, tag, or inventory event. Customer order confirmation, shipping, abandoned checkout, gift card, staff invite, collaborator request, and every other notification silence page is a different product with a different toggle.

The general inactive / wait-step / failed-action overview is Shopify Flow not running— use that when you need the full six-cause walkthrough. Hiring someone to build Flow workflows versus buying a 72-hour ops install is Shopify Flow agency vs ops install— that comps page is not trigger debugging. Merchant low-stock Slack / staff email that never pings is low stock alert not firing. Klaviyo marketing / transactional Flow silence is Klaviyo flow not sending. This page is only: the Shopify Flow trigger you expected on order / tag / inventory never started a useful run.

Seven ordinary reasons that trigger never lands usefully: the event never happened, the trigger name is wrong for the event you produced, conditions filtered every candidate, app / connector permissions are revoked, run history is empty or shows condition not met / failed action and you misread it, you tested a customer email path or Klaviyo instead, or you compared agency quotes instead of reading Flow. Walk them in that order. You already pay for Shopify. You do not need another automation app to open run history.

Flow cannot trigger on fiction. A draft order sitting in admin is not Order paid. An abandoned checkout is not an order event. A tag typed into a note field, a spreadsheet, or Slack is not Customer tagged or Order tagged. Restocking a sibling SKU while Flow watches a different variant / location is not Inventory quantity changed on the object you care about.

Honest proof before you touch conditions: open the order / customer / inventory history in Shopify admin and confirm the event exists with a timestamp after the workflow was Active. If the event is missing, finish producing it — place a paid test order, apply the tag on the correct object, move quantity on the watched location — then re-check Flow. Do not buy a connector to “fix” a test that never created the event.

Admin-created orders, POS vs online channel, and gift-card-only orders are ordinary misses: your trigger may be scoped to Online Store or require a paid financial status that those paths never set. Match the proof event to the trigger, not to the story you told yourself in Slack.

Order created is not Order paid. Order paid is not Fulfillment created. Customer tagged is not Order tagged. Inventory quantity changed is not the same check as “available crossed my threshold” if your condition watches a different field. Templates copied from a gallery often keep the demo trigger while you changed the action — the canvas looks like your ops path and still waits on the wrong event.

Open the workflow → Trigger card. Read the exact trigger title. If you expected a paid-order Slack ping and the trigger is Order created, unpaid drafts and pending payments will either fire too early or never match how you test. If you expected an order tag branch and the trigger is Customer tagged, tagging the order does nothing. If you expected a stockout ping and the trigger is Order created with an inventory condition, you are not on an inventory event at all — that mix-up belongs on low stock alert not firing once the trigger is correct.

Fix is boring: change the trigger to the event you can prove in admin, save, keep the workflow Active, and force one real event. Do not stack a second workflow “just in case” until the first trigger name matches reality.

A trigger can fire and still produce silence if every Check / condition fails. Common filters: tags must include an exact string (case, spacing, or plural mismatch), order total must be greater than a number your test order never hits, channel must be Online Store while you tested on POS, fulfillment status must be unfulfilled while Shopify already auto-fulfilled a digital item, customer tags must match a segment that is empty.

Open Flow → the workflow → Run history. If you see runs marked condition not met / skipped / filtered, the trigger worked — the condition is the bug. Loosen one condition at a time on a test path (throwaway tag, personal Slack, personal staff email), prove a green run, then tighten production filters. Empty history with zero rows is a different story (event never happened, inactive, or wrong trigger) — do not “loosen conditions” on a workflow that never started.

AND vs OR mistakes are ordinary: three AND checks that each look reasonable alone exclude every live order. Prefer the smallest condition set that still protects you from spam tags / test orders, then add filters after you have one successful production run.

Shopify Flow itself can be installed while a Slack, email, or third-party connector lost scopes after a staff change, an app reinstall, or a permissions cleanup. The workflow toggle still says Active. Run history may show failed actions, or the run may never complete the first action. From Slack or staff inbox that looks identical to “Flow is not triggering.”

Re-open the action cards that talk to outside systems. Reconnect Slack / the destination channel. Confirm Flow (and any helper app) still has the admin permissions it needs for tags, metafields, or inventory reads. If a Partner removed collaborator scopes or a staff account that owned the Slack install left, reconnect under an account that still has access — do not rebuild the whole canvas first.

Permissions bugs are also why people bounce to agency vs ops install quotes. Most of the time the fix is reconnect + one proven run, not a multi-thousand-dollar Flow rebuild.

Run history is the only honest debugger. Three different states get called “not triggering” in Slack:

• Zero runs — trigger never matched (wrong event, inactive, or event never happened). Fix the trigger / event first.
• Runs with condition not met — trigger matched; conditions filtered. Loosen checks.
• Runs with failed action — trigger and conditions passed; destination / permission / action config failed. Fix the action or connector.

Open the newest run. Expand the step that stopped. Screenshot it for your team so nobody “fixes deliverability” on a Flow that never intended to send customer mail. If you need the broader inactive / wait-step walkthrough after history is clear, use Shopify Flow not running.

Placing a test order and waiting for buyer order confirmation is order confirmation email not sending— not Flow trigger silence. Shipping / WISMO silence is shipping confirmation or WISMO email not sending. Abandoned checkout is abandoned checkout email not sending. Klaviyo canvas silence is Klaviyo flow not sending. Merchant inventory Slack that never pings after you already know Flow triggers work is low stock alert not firing. Comparing Flow agency quotes is Flow agency vs ops install.

The only honest test for this page: produce the exact order / tag / inventory event your Trigger card names, with the workflow Active, then read run history. Anything else is a different product.

Stay DIY if you can spend one afternoon on the list above: prove the event, match the trigger name, loosen conditions until run history shows success, reconnect permissions, force one live order / tag / inventory move. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: Shopify Flow not running, low stock alert not firing, unfulfilled order alert, Flow agency vs ops install.

Pay for help when the work is not the trigger toggle — it is connecting the stack you already have so order / tag / inventory exceptions land in a channel you already check, lead capture is not dying in DMs, and checkout-ready ops paths are one live workflow instead of a draft Flow plus a Slack bot you forgot. 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 Flow agency retainer, 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 ops-alert install typically runs $500–$2,500. A full ops consulting block 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 an earnings number or ticket-cut claim.

What it does not buy: more orders, recovered revenue, fewer tickets, 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.