Understanding unexpected changes
How Reqursor spots changes nobody asked for in your stores, automatically, on a schedule, and across all your stores.
An unexpected change is a change nobody asked for: a store's real setup no longer matches what is on record for it, in any of the six areas covered in How Reqursor confirms a store is set up as intended. This page covers how Reqursor finds unexpected changes before they become a problem you discover the hard way.
Reqursor checks automatically, not just when you ask
Every active store gets a light check on a regular schedule. The check only looks: it never touches or changes anything (see How a change is planned, made and checked for what a check like this actually does). Live stores are checked more often than test versions of a store, since an unexpected change on a store your customers use matters more urgently. Checks are spread out across all your stores so they don't all run at the same moment.
You don't have to wait for the next scheduled check, either. You, or the AI on your behalf, can start an immediate check on any store at any time: for example, right before you hand a store off to a client, or right after you suspect something changed. It's the same look-only check the schedule runs, just run on demand instead of waiting its turn.
What you see across all your stores, not just one
Unexpected changes are spotted store by store, but you manage many stores. Reqursor combines the individual checks into one view across all your stores:
- A summary of all your stores: how many are as expected, how many have an unexpected change, and how many are unclear right now.
- Where unexpected changes cluster: which of the six areas most often causes them across your stores, so you know where to look first.
- Whether it's getting better or worse: a rising number of unexpected changes signals an active, ongoing problem; a falling number means the fixes are working.
- A flag on out-of-date checks: if a store's last check is overdue, you're told its status might not be current, rather than being shown a falsely confident "healthy."
When an unexpected change is serious enough to flag you directly
See When unexpected changes trigger an alert for the exact numbers behind each row below.
| Situation | What happens |
|---|---|
| Any store shows a serious unexpected change | You're notified right away, and the AI proposes a fix. |
| A store has had an unexpected change for over an hour | Surfaced in your daily digest as worth reviewing. |
| A noticeable share of your stores have unexpected changes at once | Flagged as a possible shared problem, like a bad update reaching many stores, rather than treated as unrelated one-offs. |
| The same unexpected change keeps coming back after being fixed | Flagged as a recurring pattern (see Spotting unexpected changes that keep coming back) since something outside Reqursor may be repeatedly overriding the fix. |
Detecting isn't fixing
Every check above produces evidence, not action. Acting on an unexpected change (applying the store's setup again, or something else) is a separate, confirmed step. See How Reqursor fixes unexpected changes with AI for how that works.
Why this matters for your agency
- You hear it from Reqursor first. Problems surface on your dashboard, not from a customer complaint.
- 100 stores are as easy to watch as one. One store's unexpected change doesn't get lost in the noise of managing many.
- Patterns get flagged as patterns. A problem that keeps repeating, or hits many stores at once, is presented as one thing to investigate, not ten separate alerts.
Where to go next
How Reqursor confirms a store is set up as intended
The six areas where unexpected changes can appear, and exactly what "matches" means.
How a change is planned, made and checked
What a look-only check actually does, step by step.
How Reqursor fixes unexpected changes with AI
The full path from a spotted unexpected change to a confirmed fix.
When unexpected changes trigger an alert
The exact numbers behind every alert this page describes.
How Reqursor confirms a store is set up as intended
The exact conditions, across every area, under which a store matches its intended setup.
How Reqursor works with your store platform
Why adding support for another store platform does not mean changing the AI. It reads that platform's rulebook instead.