Process
How a price monitoring project runs.
Six steps, in the order they happen. Product matching comes before anything is built, because that is where monitoring projects go wrong.
1. Scope the products and the competitors
You give us your product list and the retailer and marketplace sites you want watched. We agree which prices matter (list price, sale price, multi-buy and member prices, delivery cost), whether stock status is needed, how often each site should be captured, and the change threshold that should trigger an alert.
2. Product matching
Where a retailer publishes a GTIN or EAN we match on that. Where it does not, we match on manufacturer part number or SKU, then on title similarity (brand, model, size, colour, pack size). Ambiguous matches go to a manual review queue and are checked by a person. You sign off the matched list before monitoring starts, because a wrong match produces a confident, wrong alert.
3. Free sample extract
A few hundred rows across your competitors so you can check the matches, the fields and the price handling before committing to anything.
4. Build
A collector per site, capturing the current price, any was/now or promotional price, promotion text, stock status and delivery cost for each matched product and variant. Sites that hide the real price behind a basket, a postcode or a login are handled case by case and noted in the method.
5. QA against prices you can see
We compare a sample of captured prices with what you see in a browser at the same time, and check variant handling, VAT presentation and promotions that only apply in the basket. Discrepancies are explained before the first delivery.
6. Ongoing operation
Captures run on the agreed schedule (daily, hourly, or every 15 minutes on the plans that include it). Every capture goes into a price history table per product per retailer, and an alert goes out when a price moves by more than your threshold or a product changes stock status. Retail sites change layouts often, so we watch field-level fill rates on each run: a broken selector shows up as a drop in coverage, not a silent gap. Every change and fix goes in a change log you can read.