Why price scrapers get the price wrong
Old and new price. A promotion shows both. Grab the first one and you compare against a price nobody pays.
Split prices. Euros and cents in two elements: "2" and "69" become 2 or 269.
Other products on the page. Related products, bundles and "often bought together" all carry prices of their own.
Price per unit. Per kilo or per litre next to the price per pack. Both are useful, as two fields, not mixed up.
What a price scraping tool should tell you
Not only the price, but how sure it is. A price that comes back "fallback" or "conflict" is a page to look at; a price that silently changed format is a bad row in your comparison.
sure. the main rule matched, as on every example
fallback. a backup rule matched: the page changed, the value is probably still right
conflict. rules that fit your examples disagree: look before you use it
none. the value isn't there (sold out, removed, other layout)
Price scraping tools compared
Reading 1 million product pages, per run. Fetching is extra in every row.
| Setup | Per page | 1 million pages |
|---|---|---|
| A large AI model on raw HTML | 1 cent a page and up | €10,000+ a run |
| A small AI model on trimmed HTML | 0.05 to 0.5 cent a page | €500 – €5,000 a run |
| A headless browser | seconds and hundreds of MB a page | servers that grow with the crawl |
| An extraction script | €0 a page, under 1 ms | €78 once (5 fields) |