Where this page fits
/app/changes is the whole-store feed of every recorded change to a tracked field — not filtered to one product, which is what /app/products/:id is for. It has two tabs: All, every change in order, and Flagged, only the ones that matched a suspicious-change rule.
What makes a change "suspicious"
A flag isn't a generic "something changed" mark — every flagged row carries a specific reason, because an unlabelled warning is one a merchant eventually learns to ignore. The eleven rules cover things like:
- A price dropping past a set percentage with no compare-at price change in the same update (looks like a mistake, not a planned sale).
- A price falling under a fixed floor amount — often a decimal-point slip.
- A product going unpublished.
- Inventory policy flipping to allow overselling, without the variant having just gone out of stock in the same update.
- A title or description being emptied out.
- A compare-at price being cleared, a handle changing, or a vendor changing — each one common on purpose, which is why these three start switched off.
Why some rules default on and others default off
The rules that default ON are ones where a false positive is cheap and a missed real problem is expensive: a price drop, an unpublish, an oversell risk, an emptied title, a price under the floor, or a policy flip alongside going out of stock. These tend to mean something has probably gone wrong, and it usually costs real money if it's missed.
The rules that default OFF fire on changes that are frequently intentional: clearing a compare-at price is exactly what ending a sale looks like; changing a handle is often deliberate SEO work; changing a vendor is routine catalogue admin. Starting these on for every new install would mean the Flagged view is mostly noise in the first week, which teaches a merchant to stop checking it — the opposite of the point.
Adjusting it for your own store
Every rule and its current state is listed in Settings with a plain-language description of what it watches for. The two rules with a number attached — the price-drop percentage and the price floor — are adjustable, not fixed: a store that runs frequent, steep sales might raise the price-drop threshold so ordinary markdowns don't trigger it, while a store where prices almost never move might lower it to catch smaller drops.
Using the view day to day
The practical habit is checking Flagged, not All, on a normal day — it's the shorter list, and every row already has a reason attached, so you're reading "price dropped 40% with no sale set up" rather than parsing a flat stream of every edit made anywhere in the catalogue. All stays available for the times you actually want the complete picture, such as investigating a specific product's full history.