See all services → Shopify Plus Partner
Apps Global

Automate Order and Inventory Changes With New Flow Triggers

Shopify Flow adds eight "updated" triggers for orders, customers, inventory items and more, letting workflows react to a single field change instead of running on a schedule.

Executive summary

What changed

Flow has long fired on creation events and a short list of state changes. The "Product updated" trigger, released in late October, introduced a different model: you nominate the fields that matter, and the workflow runs only when one of them changes. That model now covers eight more resources: Customer updated, Order updated, Refund updated, Fulfillment order updated, Return updated, Collection updated, Location updated and Inventory item updated.

Each trigger needs at least one monitored field and accepts at most five, chosen in the trigger card. Metafields can be targeted by single definition or by whole namespace, which helps when a PIM or ERP writes into a namespace you do not fully control. The order trigger exposes order level fields such as tags, note, email and financial status, the monetary totals, and line item fields including current quantity.

Two constraints deserve attention. The trigger supplies current values only. The previous value of a changed field is not available in the workflow, so comparisons against prior state still need a metafield or an external record. And when one trigger monitors both order and line item fields, the Line Item field can arrive empty, so guard it with a condition before an action reads it.

Why it matters

The practical win is retiring scheduled workflows. Many Plus merchants run nightly jobs that scan orders or variants for what moved, then act late and in bulk. Field level triggers invert that. The workflow runs once, promptly, against the record that actually changed.

Inventory item updated is the quiet standout for ERP integrations. It watches SKU, unit cost, weight and customs fields rather than quantity, so a cost change from finance can drive margin recalculation or a landed cost metafield write with no nightly export. Collection updated closes an old merchandising gap by reacting when products enter or leave a curated collection. For where Flow ends and custom code should begin, see our notes on automating enterprise operations with Shopify Flow and Scripts.

Role-specific impact

Use-case example

Real-world scenario

A B2B distributor with roughly 9,000 SKUs receives supplier cost updates from its ERP several times a week. A nightly workflow used to read every variant and recalculate a margin metafield, about 40 minutes of runtime touching thousands of records to find the 60 that had moved. Rebuilt on Inventory item updated with unit cost as the only monitored field, the same logic runs within seconds of each write and touches only the affected items. Margin flags that were up to 24 hours stale are now current.

Implementation checklist

  1. Inventory your scheduled Flow workflows and mark any that exist only to detect a field change.
  2. Name the resource and fields that drive each one, then confirm they appear in that trigger's monitorable list.
  3. Rebuild on the matching "updated" trigger with the fewest fields possible. Five is the ceiling. One or two is usually right.
  4. Where previous values are needed, write prior state to a metafield so the next run can compare.
  5. Guard the Line Item field with a condition on any order trigger that mixes order and line item fields.
  6. Test one controlled change, read the run history for loops where a workflow writes a field it also monitors, then decommission the replaced job.

FAQ

Q: Can one workflow monitor more than five fields on the same resource?

A: No. Five is the per trigger limit. For wider coverage, build separate workflows on the same trigger with different field selections, each running independently.

Q: Do these triggers fire when an app or API call changes a field, or only on admin edits?

A: Each maps to the update action of the resource topic in the Shopify Events reference, filtered to your chosen fields, so it responds to the record changing rather than to who changed it. Loop protection matters accordingly.

Resources

Shopify Flow trigger reference

Need guidance? Talk to Makro.