Amazon Price Tracker Watchlist Alerts

What this pipeline does

An Amazon watchlist is most useful when it answers a narrow question: did a product change in a way someone should act on? Price, availability, seller, rating, and review-count changes all matter, but they should not land in the same messy alert.

Amazon Price Tracker & Watchlist tracks ASINs by Amazon domain and returns current product state plus change signals from the previous run. It is designed for recurring checks where the output needs to be small, consistent, and easy to compare.

Best first run

Start with a watchlist small enough to review by hand.

{
  "asins": ["B0EXAMPLE1", "B0EXAMPLE2"],
  "amazonDomain": "amazon.com",
  "maxProducts": 10,
  "watchMode": true,
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": ["RESIDENTIAL"]
  }
}

The first run should show clean current state. The second run is where change fields become useful, because the actor can compare against prior values.

Watchlist row shape

{
  "asin": "B0EXAMPLE1",
  "title": "Example Product",
  "price": 49.99,
  "availability": "in_stock",
  "previous_price": 54.99,
  "price_changed": true
}

Keep current-state fields and change fields in the same row. That lets a dashboard show what happened without forcing the analyst to join against the last run manually.

Alert rules that stay useful

Good price alerts are specific:

• Price dropped below a target threshold
• Price increased by more than a chosen percentage
• Availability moved from in stock to unavailable
• A watched ASIN returned valid product data after a blocked or invalid page
• Seller, rating, or review-count changes are large enough to explain a rank move

For most teams, a daily check is enough. High-velocity products can run more often, but the alert threshold should become stricter as frequency increases.

Where this fits beside Amazon Product Scraper

Use Amazon Product Scraper when you need broader product research, competitor discovery, BSR fields, reviews, or category exploration. Use Amazon Price Tracker & Watchlist when you already know the ASINs and want a recurring monitor that explains changes.

That split keeps the workflow cleaner. Research finds candidates. Watchlists protect the products that already matter.

Deployment notes

Store one history table keyed by ASIN, Amazon domain, and run time. Store one current-state table keyed by ASIN and domain. The current table powers dashboards and alerts; the history table explains the change when someone asks why the alert fired.