Shopify Flow / New feature

Shopify Flow "Product updated" trigger
Run automations the moment a product changes

A new trigger that starts a workflow when a product or variant is updated. Choose up to 5 fields to watch, such as tags, metafields, and price.

On this page
  1. What's changing (in 30 seconds)
  2. How it works: from update to workflow run
  3. Fields you can watch
  4. What the post covers / doesn't cover
  5. How to use it (3 steps)
  6. 5 key points for developers
  7. 3 business use cases
  8. One-line summary for proposals

1What's changing

Shopify Flow now has a "Product updated" trigger .
You can run a workflow when specified fields change on a product or variant.

Scope: products and variants

Workflows can be triggered by updates to product variants, not just the product itself.

5

Watch: up to 5 fields

Choose up to 5 fields from tags, metafields, price, and more. The workflow starts when any of them changes.

2How it works: from update to workflow run

Product / variant is updated Watched fields (up to 5) ✓ Tags ✓ Metafields ✓ Price ... and more Did a selected field change? Starts only on Yes Workflow runs e.g., based on other fields Auto-set metafields Shopify Flow
The example given in the article is "automatically setting a metafield value that depends on the product's other fields" .
The key feature of this trigger is that you can narrow down which field changes start it.

3Fields you can watch

The article names the following 3. It says "and more," so there are others, but the full list isn't given in the article.

Tags
tags
Metafields
metafields
¥
Price
prices
And more
Full list not given
You can select up to 5 fields per trigger.If any one of the selected fields changes, the workflow starts.

4What the article does and doesn't say

ItemDetails
Trigger name Stated Product updated
What triggers it Stated Product or product variant updates
Number of watched fields Stated Up to 5 (tags, metafields, price, etc.)
Trigger condition Stated When any of the selected fields changes
Eligible Shopify plans Not stated
Whether previous values can be referenced Not stated
Whether the workflow's own updates retrigger it Not stated
Full list of watchable fields Not stated(see the documentation)

5How to use it (3 steps)

1

Choose a trigger

Create a workflow in Shopify Flow using the "Product updated" trigger.

2

Choose fields to watch

Pick up to 5 fields, such as tags, metafields, or price.

3

Connect actions

Example: Set a metafield value based on other fields.

The article doesn't cover the exact steps in the admin. See the Shopify Flow documentation for how to build it. Send questions and feedback to the Shopify Community.

65 key points for developers

1. Narrow down what changes trigger the workflow

Instead of firing on any update, it fires only when the selected fields change. This makes it less likely that workflows run needlessly on unrelated updates.

≤5

2. Up to 5 watched fields

If you need to watch 6 or more fields, one workflow isn't enough. Plan which fields to watch up front.

3. Applies to both products and variants

Changes to variant-level values such as price can also act as triggers. Confirm whether to build your actions at the product or variant level.

4. Test whether the workflow's own updates retrigger it

The article doesn't say whether an update made by the workflow fires the trigger again. Keeping watched fields separate from the fields you write to is the safer design.

DOCS

5. Check the documentation for details

The article doesn't list every watchable field, whether previous values are available, or which plans support it. Verify behavior in the Shopify Flow documentation and a test store before going to production.

73 practical use cases

Material Size meta
USE CASE 1

Automatically keep metafields derived from other fields in sync

Problem
A metafield's value depends on another field (such as tags), but someone rewrites it by hand every time the product is edited. Missed updates lead to inconsistent displays.
Solution
Watch the source field and build a workflow that sets the corresponding metafield value when it changes (the exact example from the article).
Impact
Less manual input and fewer missed updates, keeping product data consistent.
Technical notes
Don't include the destination metafield in the watched fields. Whether it retriggers isn't documented, so verify in a test store.
¥
USE CASE 2

Automate follow-up tasks triggered by price changes

Problem
After changing prices, related tagging and team updates are done manually, and steps get missed.
Solution
Select price as a watched field and run Flow actions (tagging, notifications, etc.) when it changes.
Impact
Follow-up work after price changes happens reliably, reducing manual checks for operations staff.
Technical notes
Price is often a variant-level value, so decide whether to process at the product or variant level. Whether previous values are available isn't documented.
USE CASE 3

Standardize product management around tag operations

Problem
After someone tags a product, the follow-up work (such as updating related fields) gets done by some people and skipped by others.
Solution
Select tags as a watched field, and have Flow run your rule-based actions whenever the tags change.
Impact
The process becomes "just add the tag and the rest happens automatically," so it no longer depends on who does it.
Tech note
You can watch up to 5 fields, so design your trigger around a focused set of fields such as tags.

8One-line summary for proposals

"Changes to a product or variant's tags, metafields, price, and more (up to 5 fields) can now trigger
Shopify Flow automatically with this new trigger.
Turns follow-up work on product data into "runs automatically when something changes.""