SafeSale · Blog

Flow's Product updated trigger and a SafeSale price rewrite

Shopify Flow can now run when a price changes. What a SafeSale price rewrite looks like to that trigger, which mechanism stays silent, and three safe workflows.

On 28 October 2026 Shopify added a Product updated trigger to Shopify Flow. Pick up to five fields on a product or variant, among them tags, metafields and prices, and a workflow starts whenever one of them changes. Until now, reacting to a price change meant polling or a custom app. Now it is a checkbox.

That matters for anyone running sales with SafeSale, because one of its two mechanisms changes prices on purpose, hundreds at a time, twice per sale. This post walks through what those writes look like to the new trigger, which mechanism makes no noise at all, and the handful of workflows that are worth building on top of it.

What the trigger sees when a price rewrite sale starts

A price rewrite sale works in three moves. Before anything changes, SafeSale takes a snapshot of every targeted variant: the current price and the current compare-at price, including an empty compare-at. Then it writes the sale prices to Shopify, product by product, through the Admin API's bulk variant update, which accepts up to 250 variants per product in one call. Variants that are already at the planned price are skipped. When the sale ends, the same call runs in reverse and writes the snapshot values back.

So a sale on 300 products produces a burst of at least 300 product updates at the start and another at the end. Each one changes the variant price, and usually the compare-at price too, since the rewrite mechanism puts the old price into compare-at so the storefront shows a strike-through. If your Flow workflow monitors either of those fields, it is going to run for every product in the sale, in a cluster that lasts as long as the apply does. Shopify's Flow documentation covers how runs are queued; the practical point is that a workflow with a slow action in it, such as sending an e-mail per product, will be busy for a while.

The changelog does not say whether the trigger distinguishes a change made by staff in the admin from a change made by an app through the API. Nothing in the announcement suggests it does, and other product triggers have never made that distinction. Plan as though every app write counts, then confirm with a one product sale before you trust a workflow with anything that costs money.

The mechanism that stays silent

SafeSale's other mechanism is an automatic discount. It creates a discount in Shopify that applies at the cart and checkout; the product itself is never written. Price and compare-at stay exactly as they were, and the Product updated trigger has nothing to notice. If you have workflows that watch prices for an unrelated reason, say a margin check that messages a buyer whenever a price moves, a discount sale will not set them off and a price rewrite sale will.

That is one more line in the already long list of trade-offs between the two, which automatic discount or compare-at price rewrite goes through in full. It is not a reason to choose one over the other on its own. It is a reason to know which one you picked before you wonder why Flow ran three hundred times on a Friday evening.

Workflow 1: a sale badge the theme can read

The most useful thing to do with a price change is to tell the theme about it in a way a template can test cheaply. Many themes already show a Sale badge when compare-at is higher than price, and if yours does, you need nothing. If it does not, or you want something richer, such as a "Ends Sunday" line, a metafield is the clean route.

  1. Trigger: Product updated, monitoring Compare-at price.
  2. Condition: the variant's compare-at price is not empty and is greater than its price.
  3. Action: update a product metafield, for example custom.on_sale set to true. Add a second branch for the opposite condition that sets it back to false, so the end of the sale cleans up after itself.

The theme then checks one boolean instead of comparing two prices across every variant. Because SafeSale restores compare-at to its snapshot value when the sale ends, the opposite branch fires on its own and the badge disappears without anyone remembering to remove it.

Workflow 2: a tag for apps that filter by tag

Search and filter apps, feed apps and some e-mail tools segment by tag and nothing else. The same trigger and condition, with the action Add product tags instead of a metafield, gives them a sale tag that appears when the price drops and goes away when it comes back. Use a tag you do not use for anything else, and give the removing branch a Remove product tags action with the exact same string.

One caution about tags specifically. Tags is also one of the fields the trigger can monitor. If your workflow both monitors Tags and adds a tag, it will trigger itself. Flow has protections against runaway loops, but the clean answer is to monitor price fields only and write tags, never the other way round in the same workflow.

Workflow 3: a heads-up to a person

A single Slack or e-mail message per sale would be ideal, and the trigger cannot give you that, because it runs per product. What it can do is catch the unexpected. A workflow that monitors Price, with the condition that the product is not tagged with your sale tag from workflow 2, and the action of sending a message, tells you when a price moved outside a sale: a staff edit, a CSV import, another app. During a SafeSale sale the tag is present and the workflow stays quiet; the rest of the year it is a cheap alarm.

The one workflow not to build

Do not build a workflow that writes a price in reaction to a price change. The tempting version is "when price changes, round it to .99". During a sale, SafeSale writes 23.60, the workflow writes 23.99, and the storefront shows a number nobody planned. SafeSale does not fight it: it receives the product update, sees that the live price differs from the one it applied, and records an external change in the sale's changelog, which is the behaviour described in what happens when a price is edited during a sale. There is no loop, because SafeSale only writes at apply and revert. But the sale price is now wrong, and you will find out from a customer.

If you want .99 endings, set them in the sale itself. The rounding belongs where the price is decided, not in a workflow that runs after the fact.

What this changes about the revert

Nothing, mechanically. The revert writes the snapshot back and the trigger fires again for each product, so every workflow above runs its opposite branch and the store ends up where it started. The one thing worth checking after your first sale with Flow in the picture is the Flow run history for the revert window. If a run failed, say because a metafield definition was missing on one product, that product's badge or tag is stale while its price is correct. SafeSale's changelog will show the revert succeeded; Flow's history shows whether the decoration followed.

Do you even need Flow for this?

For the single most common wish, a Sale collection that fills and empties itself, no. An automated collection with the condition Compare-at price is not empty has done that for years, and it reacts to SafeSale's writes the same way it reacts to anyone else's. Reach for Flow when you need a side effect a collection cannot produce: a metafield, a tag another app reads, a message to a human, a publication to a channel. The new trigger makes those possible from a price change. It does not make them necessary.

Frequently asked questions

Does Shopify Flow run when an app changes a price, or only when a person does?

The changelog describes the trigger as running when one of the monitored fields changes, and says nothing about who changed it. Treat it as firing for app writes too, and confirm with a one product test sale before you rely on a workflow either way.

Will a SafeSale discount sale set off a Product updated workflow?

No. The automatic discount mechanism creates a discount in Shopify and never writes to the product, so the product's price and compare-at fields do not change and the trigger has nothing to react to. Only the price rewrite mechanism touches those fields.

What if my workflow edits the price back after SafeSale changes it?

SafeSale receives the product update, compares the live price with the one it applied, and records an external change in the sale's changelog. It does not rewrite the price again, so there is no loop. The pre-sale snapshot is untouched and is what gets restored when the sale ends.

Do I need Flow to build a Sale collection from compare-at prices?

No. An automated collection with the condition Compare-at price is not empty already does that, with no workflow. Flow is for the things a collection cannot do: a metafield, a tag another app reads, a Slack or e-mail message, or a channel publication.