How AI Agents Collect and Reconcile E-commerce Data at Web Scale
Everyone who buys e-commerce data eventually learns the same lesson: the hard part was never downloading pages. The hard part is that a product page is an argument, not a fact.
Open the same product on two days, from two cities, in two currencies, and you will get different answers to what should be simple questions. What does it cost? Is it in stock? Is this even the same product? After a decade of collecting this data for consulting firms, retailers, and investors, I can tell you where the real work lives, and why AI agents are changing its economics.
The unit of e-commerce data is the sellable variant
Catalogs are organized around products; commerce happens in variants. A "product" is one page; the things people actually buy are the size 9 in black, the 12-pack, the refurbished unit. A million-product catalog is routinely five to ten million sellable rows once variants are expanded, each with its own price, availability, and identifiers.
Most low-quality datasets in this market share one root cause: they stopped at the product level because variant expansion is expensive. Every variant is another request, another chance to be blocked, another row to verify. When you evaluate a dataset, ask how it handles variants before you ask how many products it covers. The number of pages collected is a vanity metric; the number of correct sellable rows is the product.
View data table
| Period | Price lifespan | Monthly repricing frequency |
|---|---|---|
| 2008–2010 | 6.48 months | 15.43% |
| 2011–2013 | 4.47 months | 22.39% |
| 2014–2017 | 3.65 months | 27.39% |
Price is a set of numbers, not a number
A modern retailer shows different prices to a signed-in member, a first-time visitor, a shopper in another region, and a bulk buyer. None of these is the "real" price; the set of them is. Serious price intelligence records which price it captured and under what conditions: geography, account state, quantity, currency, timestamp.
This is where naive collection quietly fails. A scraper that always looks like the same anonymous visitor from the same place captures one thin slice of the pricing surface and labels it "the price." The gap between that slice and what real customers see is often larger than the price movements the dataset is supposed to detect.
View data table
| Year | Human | Bad bots | Good bots |
|---|---|---|---|
| 2016 | 61 | 20 | 19 |
| 2017 | 58 | 22 | 20 |
| 2018 | 62 | 20 | 18 |
| 2019 | 63 | 24 | 13 |
| 2020 | 59 | 26 | 15 |
| 2021 | 58 | 28 | 15 |
| 2022 | 53 | 30 | 17 |
| 2023 | 50 | 33 | 18 |
| 2024 | 49 | 37 | 14 |
Sites drift; pipelines rot
E-commerce sites change their markup constantly, and not politely. A field moves, a label changes language, an A/B test rewrites the page for 10% of visitors. Traditional pipelines fail loudly when the page breaks and, far worse, silently when it half-breaks: the extractor still returns something, and that something is wrong.
This is the first place AI agents genuinely change the economics. Extraction used to be code that a human repaired every time a site changed. Now an agent can read the changed page the way a person would, repair the extraction, and prove the repair against historical data before it ships. What used to be a maintenance team's week is becoming a system's afternoon. The cost curve of breadth has bent: covering five hundred retailers no longer costs fifty times what covering ten did.
View data table
| Attack type | Share |
|---|---|
| Data scraping | 31% |
| Payment fraud | 26% |
| Account takeover | 12% |
| Scalping | 11% |
| User-details harvesting | 6% |
| File upload / remote code execution | 4% |
| Other | 10% |
Verification is the actual product
The second change is deeper. Agents don't just collect; they check. Cross-validate a price against the same item seen through a different path. Flag a catalog whose availability flipped implausibly overnight. Reconcile identifiers across retailers so that "the same product" is a claim backed by evidence, not string matching.
A useful way to think about it: collection answers "what did the site say?"; verification answers "what is true?" Buyers pay for the second question. The datasets that survive procurement diligence are the ones that can show their work: when each row was observed, under what conditions, what checks it passed, and what changed since last time.
What to ask a vendor (or build into your own pipeline)
- How are variants modeled, and what fraction of rows are variant-level?
- Which pricing conditions are captured: geo, membership, quantity, currency?
- How is silent breakage detected, and how fast is it repaired?
- Can any row be traced to an observation time and collection context?
- What does coverage completeness mean here, and how is it measured against the retailer's real catalog?
Vendors who answer these crisply are selling data. Vendors who answer with page counts are selling exhaust.
The web is the largest commercial dataset on earth, and e-commerce is its most liquid corner. AI agents are making it possible to collect that corner with the breadth of a crawler and the judgment of an analyst. The winners in this market will not be whoever collects the most pages. They will be whoever can prove the most rows true.
New essays by email, on AI for data collection and analysis.