Monitoring
Scans
How a scheduled scan runs, what the Scans page reports about each target, and what a degraded or failing scan means.
Last revised
A scan reads every offer on one monitored listing through your Amazon authorization and writes one observation per offer. Scans run from a schedule, or on demand from a product’s page. Nothing about a scan is inferred: a scan that did not run leaves a gap, never a zero.
Targets
A monitoring target is one product on one marketplace. Monitoring › Scans lists every target with the state of its latest scan.
| State | Meaning |
|---|---|
| Healthy | The most recent scan succeeded. |
| Degraded | Recent scans have failed consecutively; coverage may be incomplete. Nothing already observed has been discarded. |
| Failing | Scans have kept failing. Earlier observations stand; nothing new is being recorded until the cause is fixed. |
| Disabled | Monitoring is switched off for this target. No scan is due. |
| Never scanned | No scan has run yet. This is not a finding of compliance. |
Beside the state, each target shows what the latest scan found: the offers read, the distinct sellers resolved, the offers judged below the effective MAP, and the offers nothing could be determined about — shown separately, because an undecided offer is not a compliant one.
Schedules
A schedule is a set of weekly slots in an explicit timezone — for example every day at 06:00 and 18:00 Eastern — rather than a single “every N hours” setting, so a day can be quiet and a weekend can differ. Your workspace’s schedule is configured at the cadence your plan allows; see Monitoring cadence. Every due instant the scheduler acts on is computed in UTC from the slot and the timezone, so daylight-saving changes are handled rather than drifted through.
Running a scan now
- Open the product from Monitoring › Products.
- Under its monitoring target, choose Run now. The scan is queued immediately; the schedule is unchanged.
- Watch the result under Scans › Scan history, which lists each scan with its status, the provider executions it took, and how many times the queue handed it to a worker.
Turning monitoring off for a product
A product’s page lets a Compliance Manager or Brand Admin disable its target. A disabled target is not scanned and does not count against the plan’s monitored-product limit. Archiving a product does the same and also retires it from the working catalog; archiving needs the catalog: archive permission, which Analysts do not hold.
When a scan fails
- The Amazon authorization may have lapsed. Overview shows Needs attention; test the connection from Configuration › Amazon.
- The marketplace may be outside the authorization. A target on a marketplace Amazon did not grant will not complete.
- The source may have been unavailable. The scan is retried on the next slot; the history keeps the failed attempt.