← All articlesMarketplace insights

Shopify Flow Adds Update Triggers: Build Workflows Around the Change That Matters

Direct answer: Shopify announced eight new “updated” triggers in Flow on November 20, 2026. They cover customers, orders, refunds, fulfillment orders, returns, collections, locations and inventory items. A workflow can start when a selected field changes, with up to five monitored fields per trigger. For an established brand, the opportunity is to replace broad scheduled checks with a specific response to a meaningful change. The first step is to define the exact event and its owner before turning on an automation.

Why the field selection matters

An order is updated for many reasons. A workflow that reacts to every change can send duplicate alerts or take actions at the wrong time. Shopify’s Order updated trigger requires at least one selected field and allows up to five. Unselected changes do not start that workflow. The order guide lists fields such as tags, financial and fulfillment status, totals, line item quantities and shipping lines. Choose only the fields that support the decision you want to make.

For example, a brand may want a human review when a fulfillment-relevant order detail changes after the warehouse has received the order. That is an operating use case to evaluate, not a claim that Shopify automatically detects or resolves a warehouse exception. Map which system owns the order, whether the warehouse can still change it and who receives the alert. Then test with a real but controlled order change before enabling the workflow broadly.

Know what the order trigger gives you

Shopify’s Order updated documentation says the workflow receives current order and line item values, not the previous values of changed fields. Do not design an alert that promises to show “old versus new” using this trigger alone. If the team needs a before-and-after audit, plan a separate record of the prior state or use an integration built for that purpose.

Shopify also notes that the Line Item field is available when a line item field is monitored, but it can be empty in a workflow that watches both order and line item fields when only an order field changes. Add a condition before an action relies on that Line Item value. This is the kind of edge case that a quick test can expose before a busy promotion.

A practical rollout for a growing brand

  1. Pick one expensive exception, such as a change that currently requires someone to scan orders or a report.
  2. Choose the relevant update trigger and the smallest useful set of watched fields.
  3. Set conditions so the action runs only for the orders or items that need attention.
  4. Test a selected field change, an unrelated field change and a repeat change.
  5. Check for duplicate alerts, missing data and any action that could trigger the workflow again.
  6. Assign an owner to review early runs before extending the automation.

The last two checks are Etail Rocket’s implementation advice. Shopify’s announcement establishes the new trigger choices; it does not guarantee that every proposed workflow will be safe for a particular store’s integrations.

For teams with several sales channels, a Flow trigger can improve the speed of a Shopify-side handoff only if the receiving system and exception owner are clear. Etail Rocket can review those handoffs in a focused commerce operations audit.

Sources