Shopify Flow's Product Updated Trigger: Pick Your 5 Fields Wisely
Shopify Flow's new Product Updated trigger caps you at five monitored fields and only ever shows the new value. Here's how to choose well.

Shopify rolled out a new “Product Updated” trigger for Flow on October 28, 2026 — it starts a workflow whenever a product or variant field changes. That sounds like a general change feed. It isn’t. The trigger requires selecting at least one field to monitor, and it caps you at five. Changes to any field you didn’t select never fire the workflow, full stop.
For ops teams wiring Flow into an ERP, 3PL, or marketplace sync, that cap means the first real decision isn’t “what should this workflow do” — it’s “which five fields actually matter enough to watch.”
What Counts Against Your Five
Shopify groups the monitorable fields into six buckets: Product (title, tags, status, handle, productType, and others), Media, Options, Variants (price, compareAtPrice, barcode, and more), Bundles, and Combined listings. Each metafield definition or namespace you choose to monitor — via metafield.value or variants.metafield.value — also counts as one of your five. Watch three metafield namespaces and you’ve used three-fifths of your budget before touching a single built-in field.
The grouping also decides whether adding a brand-new product fires the workflow at all. Setting plain Product fields like title or tags when a product is first created doesn’t start it. But every product has at least one variant, so monitoring a field like variants.price does fire the workflow the moment that product is added — because the variant itself counts as a change.
You Only Get the New Value
The trigger hands your workflow only the current values of the product, its variants, options, and media. There’s no “before” state. If you monitor variants.price, you can read the new price in a condition or action, but you can’t compare it to what it used to be. Any automation that needs to react to the direction or size of a change — say, flagging a price drop over 20% — has to source the previous value somewhere else: a database snapshot, a separate webhook, or a lookup against your own system of record.
That matters more when you’re monitoring several field types at once. The Product Variant, Product Option, Media, and Combined Listing Product fields are only populated when a related field you’re watching actually changed. Monitor both tags and variants.price, and the Product Variant field is empty on a run triggered by a tag edit. Every action downstream of one of those fields needs a defensive “has a value” check before it runs.
Treat the Five Fields Like a Governance Decision
Five fields isn’t a technical nuisance to work around — it’s a forcing function. Before building the workflow, write down every field your integration actually needs to react to, rank them, and expect to leave some out. If you need more than five signals, you’re probably looking at more than one workflow, each scoped to a specific sync responsibility, rather than one trigger trying to watch everything your catalog can do.