Start monitoring

Monitoring starts on its own once the workspace is ready. There is no switch to flip: a product added with monitoring on is scanned from its next scheduled slot, in every marketplace the Amazon authorization covers.

What has to be true

• Amazon is connected and the last test succeeded.
• At least one product is in the catalog with monitoring on.
• A MAP policy is in force for the product. Without one, the scan still records what it saw, and every observation reads Not evaluated.

The schedule

Each monitored product has a scan schedule: weekly slots in an explicit timezone, at the cadence your plan allows. Monitoring › Scans shows the schedules and the targets, the health of each target after its latest scan, and Never scanned for a product that has not had one yet — which is not a finding of compliance.

Every instant the scheduler acts on is UTC. A disabled day has no slots and produces no due times.

Running a scan now

A product’s own page has Run now for a listing you are watching closely. It queues a scan outside the schedule; the schedule is unchanged. Analysts, Compliance Managers and Brand Admins can use it.

Reading the first results

1. Open Monitoring › Scans. Each target shows its last scan: succeeded, degraded or failing, how many offers were read, how many distinct sellers were resolved, how many offers were below the effective MAP, and how many were indeterminate.
2. Open Monitoring › Observations. Every offer the scan read is one row: the seller, the price, the effective MAP, the gap, the coverage, and the outcome.
3. Open Compliance › Violations. Any below-policy observation that passed the eligibility gates is waiting here as a violation candidate. See Violation candidates.

If nothing appears

• Check the Amazon connection on Overview: Needs attention means a failed verification.
• Check that the product’s marketplace is one the authorization covers.
• Check the target on the Scans page: Disabled means monitoring is off for that product.