PuppyIP Resource Center
Cross-Border Platform Rules 5 min Published 2026-11-18

Shopify Flow Product Updated Trigger: Fields, Prices, and Metafields

Use Shopify Flow's Product updated trigger to respond to changes such as tags, variant prices, or metafields. Choose one to five monitored fields. Before writing conditions, check which objects the change supplies and whether your workflow needs a previous value.

Shopify Flow Product updated Variant prices Metafields

Service eligibility and regional restrictions

PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.

Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.

Key Takeaways

  • A change to any selected field can trigger a run. A change to an unselected field does not start one on its own.
  • Each metafield definition or namespace takes one slot. A namespace includes metafields without a definition.
  • When a flow monitors both tags and variant prices, a tags-only update can leave Product Variant empty.
  • Product updated exposes current values. Inventory quantity has a dedicated trigger, and some variant fields can also trigger a run when a product is created.

Choose the fields that should start a run

In the workflow editor, select Product updated and open Select fields under Select product fields. Choose at least one field and up to five. A change to any selected field can start the workflow.

Select tags for product tags and variants.price for a variant's selling price. If the workflow only handles price changes, start with the price field. Add tags when you need to handle those changes too, and set the relevant conditions separately. Changes to unselected fields do not start a run on their own.

Monitor a metafield or a namespace

Select metafield.value for a product metafield or variants.metafield.value for a variant metafield. To watch one attribute, such as a season, select its definition. To watch a group, choose Use namespace only and enter the namespace.

A definition or a namespace uses one of the five slots. A namespace covers every metafield in it, including those without a definition. Choose the scope you need so unrelated changes don't start the rest of the workflow.

Check which objects are present

Product and Shop are always available. Variant, option, media, and combined listing objects depend on the monitored fields and what changed. For example, if you monitor both tags and variants.price and only the tags change, Product Variant can be empty.

Add a condition to check that Product Variant has a value before an action uses it. The trigger exposes current values, such as the new price. To determine whether the price went up or down, use a previous value your workflow already recorded. The data in this run alone cannot establish the size of the change.

Handle new products and inventory quantities separately

Setting a title or tags when adding a product does not start this workflow through those product fields. However, the variants, options, media, bundle components, or combined listing products added with it can count as updates. Shopify's example shows that a workflow monitoring variants.price runs when a product with a variant is added.

Use Product created when every new product should be handled. To watch a variant's stock quantity, use Product variant inventory quantity changed. The variants.inventoryPolicy field describes inventory policy and does not report stock quantity.

Verify the trigger with one test product

Use an authorized test store or test product. Review what the actions do, then follow Shopify's instructions to turn on the workflow and change one monitored field. Check that the run appears in history, which conditions it follows, and whether the action can read the object it needs. If you monitor tags and prices, change each separately.

Change an unselected field as a control. If the workflow writes a metafield, check whether that field is also monitored and guard the write with a condition. Confirm separately that the trigger ran, the intended condition passed, and the action completed.

Sources

Frequently Asked Questions

Is a variant's compare-at price the same field as its selling price?

Shopify lists two fields. Use variants.compareAtPrice for compare-at price and variants.price for selling price. Monitoring both uses two slots.

Can one workflow monitor two namespaces?

Yes. Add them separately, allowing one slot per namespace and reserving room for any other fields you select.