Executive summary
- What: Shopify Flow now has a Product updated trigger that starts a workflow when one of up to five selected product or variant fields changes.
- Why: Catalog state can finally drive automation directly, without polling, a scheduled workflow or a custom app listening to product webhooks.
- Who: Merchandising and operations teams maintaining large catalogs, and the developers who have been writing middleware to watch product changes.
What changed
Flow previously had a Product created trigger and a variant inventory quantity trigger, but nothing for general product edits. The new trigger closes that gap. You select at least one field and at most five, and the workflow runs only when one of the selected fields changes. Edits to anything you did not select do not start a run.
The selectable set is broad. Product level fields include category, status, tags, title, vendor, product type, handle and metafield values. Variant level fields include price, compare at price, barcode, taxable, inventory policy and variant metafield values. Options, media, bundle components and combined listing relationships are also available. Metafields can be targeted by definition, or by namespace so every metafield in that namespace is watched, including ones created later.
The mandatory field selection is the important design detail. This is not a general product webhook with filtering bolted on afterwards. Scope is declared up front, which keeps run volume proportional to what you care about.
Why it matters
Most enterprise catalogs carry derived data that someone maintains by hand or by cron: a badge metafield that depends on price, a tag that reflects category, a sync flag an ERP or PIM reads, a collection rule that needs a nudge after a vendor change. Each previously justified a custom app or a scheduled workflow that scanned the catalog and did nothing most of the time.
Doing this in Flow moves the logic somewhere the merchandising team can read and change it, which matters more than the engineering saved. A tagging rule in a workflow is visible and editable without a deploy. Teams already automating enterprise operations with Shopify Flow can retire a meaningful share of their scheduled jobs.
The constraint to respect is run volume, since field scope is your only real control. Choose it deliberately and watch the run log after launch.
Role-specific impact
- Marketers: Badge, tag and collection logic can respond to price and category changes within minutes, so merchandising stops depending on someone remembering to re-run a job.
- Developers: Several custom apps built purely to listen for products/update webhooks are now replaceable. Check that your downstream actions are idempotent, because a workflow that writes a metafield on a monitored field can retrigger itself.
- Store admins: Bulk catalog edits now carry automation consequences. Coordinate large imports with whoever owns the workflows.
Use-case example
Real-world scenario
A home goods brand carries 6,000 SKUs and maintains a price band metafield used by storefront filters and by its ad feed. A nightly scheduled workflow scanned the catalog and corrected the band, so a price change made at 10am was wrong in the feed for the rest of the trading day. Rebuilding this on the Product updated trigger with variants.price and variants.compareAtPrice monitored brings correction time down from about 14 hours to under five minutes, and removes roughly 180,000 unnecessary product reads a month from the nightly scan.
Implementation checklist
- List the derived product data you currently maintain on a schedule, and note which source field each one depends on.
- Pick at most five fields per workflow. If a use case needs more, split it into separate workflows rather than widening the scope.
- For metafield monitoring, decide between a specific definition and a whole namespace, remembering that namespace monitoring picks up future metafields.
- Guard against self-retriggering: avoid writing to a field the same workflow monitors, or add a condition that exits when the value is already correct.
- Test with the trigger's own test tooling before activating, then watch the run log through a full bulk edit cycle.
- Retire the scheduled workflows or app listeners this trigger replaces, and remove their access scopes.
FAQ
Q: What happens during a large bulk edit or CSV import?
A: Each product whose monitored field changed starts a run, so a 20,000 variant price change produces runs at that scale. Keep the monitored set narrow, make downstream actions cheap, and schedule large imports when you can watch the run log.
Q: Can one workflow watch both product and variant fields?
A: Yes. The five field budget is shared across product, variant, option, media, bundle and combined listing fields, so a workflow can monitor a mix such as tags plus variants.price.
Resources
Product updated trigger reference
Need guidance? Talk to Makro.