Demo Scenario

Competitor prices every week, not once a quarter

A pharmacy chain compared prices with competitors by hand once a quarter. We collect open prices on a schedule and show the changes.

This is a demo scenario: how we would build the solution. Names and data are illustrative — it is not a specific client’s story.

01Task

Task

See where our prices are above the market on key items, and learn about competitor promotions the same week.

Constraints

  • Competitors name products differently from our catalogue.
  • Only open data is collected, following each site’s rules.
02Solution

Solution

  1. 01

    Scheduled collectors of open prices, keeping the history of every value.

  2. 02

    Item matching to the catalogue: rules plus manual review of disputed matches.

  3. 03

    A price-position dashboard and a change feed with alerts.

03Architecture

Architecture

Architecture: Competitor prices every week, not once a quarter
  1. Open price sources → Collectors · schedule
  2. Own catalogue → Item matching
  3. Collectors · schedule → Item matching
  4. Item matching → Price history
  5. Price history → Price dashboard, Change alerts
  6. Price dashboard
  7. Change alerts
Integrations
Open web sources · Product catalogue · Email / Telegram alerts
Stack
Python · PostgreSQL · SQL · Docker
04What it demonstrates

What it demonstrates

Demonstrates: regular collection of external data, matching it to your own catalogue and a history of price changes.