Monitoring
Monitoring cadence
How often each listing is scanned on each plan, what a scan slot is, and how cadence interacts with cure detection and freshness.
Last revised
Cadence is how many times a day each monitored listing is scanned. It is set by your plan and applied to the workspace’s schedule; the Scans page shows the slots and the next due instant for every target.
Cadence by plan
| Plan | Cadence | Monitored products |
|---|---|---|
| Starter | Twice a day | Up to 250 |
| Growth | Every 6 hours | Up to 1,000 |
| Professional | Every 4 hours | Up to 2,000 |
| Enterprise | Agreed per contract | Agreed per contract |
The plan sets the ceiling. The cadence is enforced when a schedule is created or changed, so a workspace cannot be scheduled faster than its plan allows. Moving to a plan with a higher cadence lets the schedule be raised; moving down lowers it at the change.
Why cadence matters beyond “sooner”
- Freshness. A violation candidate is only generated from an observation less than seven days old, and an enforcement notice can only cite an observation that is still fresh under your enforcement settings. A listing scanned twice a day is always inside both windows.
- Cure detection. A breach period closes only after a run of compliant observations — by default two, at least twelve hours apart, each less than seventy-two hours old. At twice a day, a seller who corrects their price is recorded as cured within roughly a day. See Case lifecycle.
- Repricers. Sellers using automated repricing can move several times a day. A higher cadence sees the shape of that movement rather than a single sample of it.
On-demand scans
Run now on a product’s page queues a scan outside the schedule. It is the right tool for a listing you are watching closely today; it is not a substitute for cadence, and it does not raise the schedule.