How to Trigger Shopify Flow When a Product Price Changes (2026)

It is 9:04 AM on the first day of your sale. 

Prices went live overnight. Your category page still shows a product in the "10 to 20% off" bucket when it is actually sitting at 45% off, because that filter runs off a metafield that a nightly job updates. 

Every shopper who filtered for the deepest discounts just missed it. You will catch it by lunch. 

The traffic spike will be over by then.

That gap between a price moving and the store reacting to it is exactly what Shopify Price Flow automation is meant to close. Most merchants open Flow to build it and find the same thing waiting for them: the trigger they need does not exist.

Does Shopify Flow have a price change trigger?

No. Shopify Flow has no native trigger that fires when a product or variant price changes. Flow reacts to orders, inventory quantity, fulfilments, customer events, product status and tags. Price is not on that list. Neither is the part that matters more: Flow keeps no record of what the price was a moment ago.

Shopify has said so on the record. In a thread on the Shopify Community forums, a merchant building wishlist price-drop notifications asked for this in 2020, and a Shopify staff member confirmed no such trigger existed, either manually or through the API, then asked the merchant to describe the use case in case the product team ever built one. The Shopify Help Center's Flow trigger reference still lists no price event. Someone new asks the same question every few months, and most Shopify Partners have written the workaround for three different clients by now. 

The workaround everyone builds, and where it cracks

The standard answer is a scheduled trigger. Run a workflow hourly, use Get Product Data to pull products updated since the last run, loop through them, compare price against compare-at price, then tag or move collections accordingly. It works. Thousands of stores run some version of it right now.

Then the cracks show up. It is not real time, so a price that lands at 9:00 does nothing until 10:00. The query filter merchants reach for, is_price_reduced, has a habit of returning products with no compare-at price set at all, so the results need cleaning before the logic can trust them. 

Get Product Data returns limited batches, and past a few thousand SKUs, the loop starts quietly skipping items. And "updated in the last hour" catches inventory changes too, so the workflow burns through hundreds of products whose price never moved.

A version of this costs real money, and a merchant described it on the Shopify Community forums. Their product data sits on a local server. When a product code disconnects during sync, a price of 0 gets pushed into Shopify, and customers can buy at zero. They wanted a workflow that unpublished the product and emailed the team the second it happened. 

There was no trigger to hang it on. That thread is still open. If you are scoping this with an outside team, most Shopify Development Companies will quote the scheduled version first, simply because it needs no extra app. 

What Shopify price flow automation actually needs

A working price trigger needs three values: the previous price, the current price, and the compare-at price. Everything else gets derived from those. Change amount. Change percentage. True discount against MRP. Direction of the move.

Skip the previous price and you cannot write the condition "dropped by more than 30%", which is the condition almost every real pricing rule is built on. Direction matters more than people expect too, because a price going up and a price coming down should almost never run the same workflow. One is a promotion. The other is a margin decision somebody upstairs needs to know about.

The second requirement is noise control. Catalogue integrations rewrite the same price repeatedly. Multi-currency stores round differently between syncs. Bulk editors touch thousands of variants in one go. Without a percentage threshold sitting in front of the trigger, a 40,000 SKU catalogue will drown Flow in workflow runs that mean nothing. A threshold turns a firehose into a signal, because you only react to changes a customer would actually notice.

What you can automate the moment a price moves

The obvious one is tagging. On-sale, price-drop, and deep-discount tags apply and remove automatically, then drive theme badges, upsell rules, and segment logic without anyone touching a product page.

Collection membership is the one merchants underrate. Adding products to Sale or Clearance is easy to remember. Removing them when the promo ends is what everybody forgets, and a stale sale collection two weeks after Diwali is a genuinely common merchandising complaint.

Then there is the discount facet on category pages. Price change fires, Flow calculates the discount against compare-at, writes the bracket into a product metafield, and Search & Discovery uses that metafield as a filter. The facet becomes accurate within seconds of the price landing, not the next morning. Beyond that: internal Slack or email alerts when a price breaches a floor, MAP and MRP compliance flags, a feed refresh so Google Shopping and marketplace listings aren't sitting on yesterday's price, and bundle checks so a component SKU moving doesn't silently break kit pricing.

Zapier vs Shopify Flow: which one for price automation

Zapier and Make can both watch a Shopify product update webhook and act on it, so they are a legitimate route. You pay per task, though, and price changes at catalogue scale generate many tasks. Flow costs nothing on the plans that include it and runs inside the admin, which makes it faster and cheaper for anything happening thousands of times a month.

The honest comparison usually ends the same way. Zapier can see the change but gets expensive. Flow is cheap but cannot see the change. Which is why most teams end up back in Flow, building the scheduled workaround, and living with the hour of lag.

Low-cost Shopify price flow automation that scales

The third route is to stop working around the gap and just add the trigger Flow is missing. This is the only option that reacts the second a price lands rather than an hour later, and it costs less than people expect, because you are not buying an automation platform. You are buying one event.

Netra: Price Signal does one thing, and it does it well. It watches variant prices in real time and fires a Shopify Flow trigger the moment one moves, carrying the previous price, the current price and the compare-at price into the workflow, which is what lets a condition finally say "dropped more than 30%" instead of guessing. Scope it to a single product, a collection, or the entire catalogue. Set a percentage threshold so ERP rewrites and currency rounding stop waking Flow up for changes no customer would notice. Trigger logs give you an audit trail of what moved, when, and by how much, exportable to CSV or Excel on the higher plan. Pricing is $4.99 and $9.99 a month.

The price is deliberate. Seventh Triangle built it after watching client category pages carry the wrong discount brackets during the exact hours a sale was live, and the brief was to fix that one problem cheaply enough that nobody has to defend it in a budget meeting. Broader trigger apps exist, Flow Trigger Extensions among them, and they earn their $25 a month if you are missing twenty events. If the only thing you are missing is price, that is a lot of platform to buy for one trigger.

Worth saying plainly: a discount filter that is right within seconds is not only an operations win. Shoppers who filter by discount convert harder than shoppers who scroll, and accurate structured product data is increasingly what search engines and AI answer engines read when they decide what your store sells and for how much, which puts this squarely in the same territory as SEO, AEO, GEO & AIO work. 

So the answer to the question in the title is that you cannot do it natively, not in 2026. You either accept an hour of lag with a scheduled workflow, pay per task outside Shopify, or add the trigger Flow is missing. Pick based on catalogue size and how often your prices actually move. Whichever route you take, Shopify price flow automation is only as good as the context it carries, so make sure whatever you build knows what the price was before it changed.

Frequently Asked Questions

1. Can Shopify Flow trigger when a product price changes?

No. Shopify Flow has no built-in trigger for product or variant price changes as of 2026. Its native triggers cover orders, inventory quantity, stock status, fulfilments, customers, tags and product status. Flow also keeps no record of what a price was before it changed, so even a workaround cannot calculate the size of a drop.

2. How do I automatically tag products as on sale in Shopify?

Compare the variant price against the compare-at price, then apply an on-sale tag when the price is lower. Natively, this needs a scheduled Flow with a Get Product Data step and a for-each loop, which runs at set intervals rather than instantly. Build the reverse condition too, so the tag lifts when the price returns to full.

3. Why does is_price_reduced not work reliably in Shopify Flow?

The is_price_reduced query filter sometimes returns products with no compare-at price set, so the result set includes items that aren't actually discounted. Add an explicit condition checking that compare-at price exists and is greater than the current price, rather than trusting the filter on its own.

4. Zapier vs Shopify Flow: which is better for price automation?

Zapier can detect Shopify price changes through product update webhooks, which Flow cannot do natively, but it bills per task and gets expensive at catalogue scale. Shopify Flow is free on eligible plans and runs inside the admin with lower latency, though it needs an app to see price events. For high volume, Flow plus a trigger app usually costs less.

5. Do I need Shopify Plus to automate price changes?

No. Shopify Flow is included at no extra cost on Shopify, Advanced, Plus and Commerce Components plans, and is unavailable only on Basic. Price automation is not a Plus-only capability. Smaller brands running frequent promotions often gain more from it, since there is no merchandising team catching stale sale collections by hand.

6. What is Netra: PriceSignal?

Netra: PriceSignal is a Shopify app that adds a price change trigger to Shopify Flow. It monitors variant prices in real time and passes the previous price, current price and compare-at price into the workflow. It includes scope rules, percentage thresholds, and exportable trigger logs. Built by Seventh Triangle Consulting, priced at $4.99 and $9.99 a month.

7. How do I set up a price change trigger in Shopify Flow?

Install Netra: PriceSignal from the Shopify App Store, open Shopify Flow, and create a workflow using the PriceSignal price change trigger. Set the scope to a product, a collection, or the full catalogue, then set a percentage threshold. Build conditions on the price values and attach your actions: tagging, collections, metafields or alerts.

8. Can Netra: PriceSignal update a metafield when a price changes?

Yes. The trigger fires the moment a price moves, so Flow can calculate the discount percentage against compare-at price and write the result to a product metafield immediately. Search and Discovery then serves an accurate discount filter within seconds, instead of on the next scheduled run.

9. How does Netra: PriceSignal stop Flow from running on every tiny price change?

A percentage threshold sits in front of the trigger, so only changes above the size you set will start a workflow. Catalogue integrations, currency rounding and bulk editors generate constant sub-1% noise on large stores. The threshold filters that out, keeping Flow runs tied to changes a customer would actually notice.

10. What does Netra: PriceSignal cost?

Netra: PriceSignal is priced at $4.99 a month for the Growth plan and $9.99 a month for Scale, with a free trial available. Scale adds unlimited triggers and CSV or Excel export of trigger logs. Pricing is flat, so a bulk edit across thousands of variants costs the same as a single price update.