The failure this is about
A variant's price gets changed by a staff member, a bulk CSV edit, or a third-party app — and it's wrong. Maybe a decimal point moved, maybe a bulk price update targeted the wrong collection, maybe an integration pushed a stale number. Nothing about the storefront looks broken; the product page loads fine, checkout works fine, the price is just wrong. Orders start coming in at that price, and nobody notices until a customer asks about it, or until someone happens to look at the product again.
What a suspicious-change flag is checking for
The signal that separates an accidental price drop from a deliberate sale is whether the compare-at price moved with it. When a merchant genuinely puts a product on sale in Shopify, the normal way to do it is to set (or keep) a compare-at price above the new selling price — that's what shows the "was $40, now $28" style strike-through to a shopper, and it's a clear signal the price change was intentional.
A price that drops sharply while the compare-at price stays exactly where it was doesn't carry that signal. Nothing marked it as a planned discount. That combination — a price fall past a set percentage, with no compare-at change in the same update — is what gets marked suspicious and surfaced in a flagged view, separate from the ordinary stream of changes.
Why it's a proxy, not a certainty
This isn't a claim that every unflagged price change is safe or every flagged one is a mistake. It's a heuristic built from an ordinary pattern: deliberate sales usually move compare-at price too, so a drop that doesn't move it is more likely to be worth a second look. A merchant who runs sales differently, or who has a specific reason for a change that doesn't fit the pattern, can adjust the threshold or ignore the flag on read.
What happens once it's flagged
The flagged change sits in a dedicated view, separate from the general list of everything that changed, so it doesn't get lost in ordinary catalogue activity. From there, seeing what the price was before the change and reverting it back is a single action — the point of flagging it quickly is to shrink the window between "the wrong price went live" and "the wrong price got fixed," since every order placed inside that window went out at the mistaken number.
The practical takeaway
A price typo or bad bulk edit is not rare, and by the time a customer flags it, the cost has usually already been paid on however many orders came in before someone noticed. A flag built around the same signal a merchant would use to eyeball it — a drop with no matching compare-at movement — catches the pattern automatically, instead of relying on someone happening to look at the right product at the right time.