← All projects

Python · Playwright · PostgreSQL

Amazon Price & Seller Monitor

A scheduled pipeline that tracks price, stock, Buy Box owner and seller count for a list of Amazon listings, and alerts the team when something moves.

PythonPlaywrightProxiesPostgreSQLCelerySlack / Email
Tracked listings with price and Buy Box
Price history and seller count
Collection and alert pipeline

Screens are illustrative layouts of the product, not client screenshots.

Overview

What it is

A monitoring pipeline for Amazon sellers and brands. It checks a list of listings on a schedule, stores every price, stock and Buy Box change, and alerts the team when something important moves.

The problem

Why it was needed

Checking competitors and unauthorised sellers by hand was slow and always late. Prices changed several times a day and the team only noticed after sales dropped.

Scheduledevery listing checked on its own cadence
Historyevery change stored for trends
Alertsprice, stock and seller changes pushed to the team

Features

What We Built

Listing tracking

Price, stock, Buy Box owner, seller count and rating.

Resilient collection

Rotating sessions, retries and layout-change detection.

Change history

Every observation stored for charts and audits.

Alert rules

Per-product rules for drops, stock-outs and new sellers.

Reports

Daily summaries by email or Slack.

API and export

CSV and API access for other tools.

Architecture

How It Fits Together

  1. SchedulerCelery beat
  2. CollectorsPython + Playwright
  3. Proxy poolrotating sessions
  4. PostgreSQLlistings and history
  5. Rules enginechange detection
  6. Slack / Emailalerts and reports

Collection, storage and alerting are separate steps, so a blocked page never loses data already collected.

Roadmap

From Idea to Launch

A typical delivery roadmap for a project of this kind.

  1. 1

    Scope

    3-5 days
    • List the ASINs and fields to track
    • Agree cadence and alert rules
    • Review terms and allowed use
  2. 2

    Collector

    1-2 weeks
    • Playwright collectors with retries
    • Session and proxy handling
    • Parsing and validation
  3. 3

    Storage and rules

    1 week
    • PostgreSQL schema and history
    • Change detection
    • Alert rules
  4. 4

    Reporting

    1 week
    • Slack and email alerts
    • Daily summary report
    • CSV and API
  5. 5

    Hardening

    1 week
    • Monitoring of the monitor
    • Layout-change alarms
    • Handover and runbook

Want something like this?

Tell us what it should do and we'll come back with a stack, a scope and a timeline.