> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getclaro.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitor

> Continuous observation operations — Price and Competitor.

Monitor watches your catalogue and the outside world on a schedule. Where Analyse produces a one-time assessment, Monitor produces a continuous stream of recurring runs that feed alerts into Notifications.

***

## Price

Track prices across a configurable cadence. Flag drifts, deltas, and anomalies relative to history or competitor data.

### What it watches

* **Internal prices** — your own price attribute on a catalogue.
* **Marketplace prices** — Amazon, Shopify, and configurable URL templates.
* **Competitor prices** — when paired with the Competitor surface, side-by-side history per matched SKU.

### Configuration

Per Price monitor, you configure:

* **Catalogue and filter** — which records to watch.
* **Sources** — which marketplaces or URLs to pull.
* **Cadence** — hourly, daily, or weekly per source.
* **Alert rules** — threshold-based (e.g. *alert when delta > 10%*), absolute (e.g. *alert when price \< cost + margin*), or anomaly-based (statistical outliers vs. history).
* **Recipients** — Notifications, Slack, email.

### Outputs

* **Price history** — full time series per record per source.
* **Drift alerts** — pushed to Notifications when a rule fires.
* **Pricing dashboards** — distribution, outliers, gap-to-competitor views.

***

## Competitor

Pull competitor listings for matched SKUs, normalize them, and surface side-by-side comparisons.

### What it does

* Identifies the competitor listing for each SKU using the similarity graph and configured match rules (GTIN, MPN, name + brand).
* Pulls listing data (title, description, images, price, availability, rating) on a schedule.
* Normalizes competitor fields against your schema so comparisons are apples-to-apples.
* Surfaces side-by-side views: yours vs. each tracked competitor.

### Configuration

Per Competitor monitor, you configure:

* **Catalogue and filter** — which of your records to track.
* **Competitor sources** — domains, marketplace seller IDs, or scrape templates.
* **Match strategy** — which similarity threshold, which fields drive matching.
* **Cadence** — daily or weekly per source.
* **Alert rules** — new listings appearing, listings disappearing, content drift, image changes, rating shifts.

### Outputs

* **Side-by-side record view** — yours vs. competitors with diff highlights.
* **Competitor catalogue** — a parallel catalogue object holding normalized competitor records.
* **Drift alerts** — fed into Notifications and/or Slack.

***

## Alerts vs. review items

Monitor alerts are *informational*: they tell you something happened. They surface in Notifications but don't block anything — you don't have to approve them.

If a Monitor alert needs to *change* a record (e.g. update internal pricing in response to a competitor drop), the alert can trigger a downstream operation — typically Bulk Enrichment with a pricing rule — whose outputs go through the normal review gate.

***

## Combining Monitor with other modules

A common pattern: **Monitor → Analyse → Bulk Enrich → Push & Sync**.

1. **Monitor → Competitor** detects a competitor description has been updated.
2. **Analyse** flags that your description no longer covers a feature the competitor mentions.
3. **Bulk Enrichment** rewrites the affected records, gated by review.
4. **Push & Sync** publishes the approved updates to your storefront.