Dataset example

Price data pulled on your schedule, from any store

A one-off price snapshot or a daily, weekly or hourly re-scrape across the retailers and marketplaces you name. Delivered as rows in your storage.

Price monitoring, for us, is a dataset: the same product pages pulled again and again, with every price, discount and stock state stamped with the time we saw it. You tell us which stores, which products or categories, and how often. We build the scrapers, match products across sites where that is possible and deliver each run as a file or a load into your storage. What you do with the numbers is yours; we make sure they arrive complete and on time.

In detail

How it works

01

Any store, any cadence

Marketplaces, brand stores, comparison sites and grocery chains all work. Runs can be one-off, daily, hourly or triggered by you. Each run is a separate file or table partition with a run timestamp, so you can diff two snapshots without extra work.

02

Prices as the shopper sees them

Many stores show different prices by region, currency, login state or delivery postcode. We scrape from the geography you care about, capture list price, sale price and member price separately and record which variant and seller each number belongs to.

03

Product matching across sites

When the same product appears on several stores we match it on GTIN, MPN or model number where those exist and flag fuzzy matches for review. You get one product key across sources, plus the original identifiers from each site for traceability.

04

Stock, promotions and history

Availability, delivery estimates, coupon text and bundle offers are captured alongside price. Historical runs stay in your bucket or database, so a year of price history is simply the files that accumulated, not a feature you pay extra for.

Schema

Fields we typically deliver

Starting point only. You name the columns; we keep the names stable across every run.

  • product_id
  • gtin
  • title
  • store
  • url
  • list_price
  • sale_price
  • currency
  • in_stock
  • promo_text
  • region
  • scraped_at

Questions

About price monitoring

How often can prices be refreshed?

As often as the site can reasonably be read: hourly for a few thousand pages, daily for hundreds of thousands. We size proxy pools and concurrency so the target site is not hurt, and the quote states the cadence.

Do you provide a dashboard or alerts?

No dashboard. We deliver the data to your storage and can send a change alert by webhook or email when a price moves past a threshold. Charting and reporting happen in whatever tool you already use.

Can you match the same product across stores?

Yes. When sites expose identifiers like GTIN, EAN or MPN, matching is exact. Without those we match on title and attributes and mark the confidence so you can decide what to trust.

What does a price dataset cost?

A one-off snapshot of one store starts at $500. Recurring pulls are quoted monthly based on store count, page volume and frequency, and the first sample run is included in the scoping.

Tell us the site. We'll tell you what it takes.

Send a URL and the fields you need. An engineer looks at it the same day and replies with a plan and a price.