Retail & marketplaces
Competitive price and assortment monitoring across rival retailers.
Daily refresh across your named competitor set
Product & Ecommerce Data
Ecommerce web scraping, delivered to spec
Production-grade product data — composable, not packaged.
Build it yourself on Zyte API, or have it delivered to spec by Zyte Data.
Same foundation, your choice of who runs the pipeline.
The basics
What is product & ecommerce data?
Ecommerce product data is the structured record of an item as it is listed for sale online — its name, price, availability, identifiers, imagery, ratings and seller. It is collected from public product pages across retail sites and normalised into a consistent schema. Because the same product is listed differently on every site, the value is in the normalisation, not the raw page.
Who uses it
Use cases across industries
The same data type, put to work differently. Ordered by how directly it applies.
Consumer brands
MAP compliance and digital shelf monitoring across resellers.
MAP breaches surfaced within 24 hoursPricing software
Market price data feeding repricing and dynamic pricing systems.
Powers real-time repricing for end customersInvestment & research
Pricing and assortment signals as an alternative data source.
Used as a quarterly demand indicatorGrocery & q-commerce
Store-level price and availability tracking across delivery apps.
Prices captured from the buyer's region, not a proxy'sConsultancies
Market-wide pricing studies without standing up web data collection in-house.
Project-scoped feeds delivered in weeksThe hard part
Why product & ecommerce data is hard at scale
The problem is rarely a single page. It is keeping thousands of them flowing, correctly, while the sites underneath keep changing.
Site changes break parsers overnight
Zyte validates every feed run against your agreed schema.
Prices render in JavaScript
Zyte renders pages the way a real browser does, so client-side prices and stock are captured as reliably as static fields — and the right regional value, not a placeholder.
Pricing is region- and session-locked
Zyte collects each price from the region and context you specify, and tags every record with the market it belongs to — so a US price is never silently compared against a UK one.
Anti-bot defences are dynamic
When a request is blocked, Zyte automatically re-routes and retries with a different approach, and persistent blocks escalate to the team running your feed.
Schemas fragment across marketplaces
Zyte resolves each source into one consistent schema and one product identity, so a product is a product no matter how many sites it came from.
Reviews and detail sit behind gates
Zyte collects the full set — paginating reviews, expanding Q&A and specifications — so the feed reflects what the page can show, not just what it shows first.
The cost of getting it wrong
What poor data quietly costs the business
Revenue impact
31%Price against week-old data and roughly a third of your prices are already wrong.
Analytics integrity
1 in 6A silent coverage drop hides one in six SKUs — dashboards still look clean.
ML reliability
2–4 wksA model retrained on a gappy feed degrades for weeks before anyone traces it.
Regulatory exposure
€20MCollecting personal data or ignoring site terms risks GDPR penalties up to €20M.
See the Schema
The request you send and the data that comes back. Pick the standard schema or a custom one mapped to your model, and read the response as a table or JSON.
Zyte API
REQUEST
POST https://api.zyte.com/v1/extract
{
"url": "https://shop.example.com/p/compact-smart-speaker",
"product": true
}RESPONSE
Standard product schema
Field
Type
Example
url
string
https://shop.example.com/p/compact-smart-speaker
name
string
Compact Smart Speaker (2nd Gen)
brand
object
{ … }
name
string
Example Audio
price
string
49.99
regularPrice
string
59.99
currency
string
USD
availability
enum
InStock
sku
string
EX-4471-BLK
gtin
array
[{"type":"gtin13","value":"2004471000000"}]
aggregateRating
object
{ … }
ratingValue
number
4.7
bestRating
number
5
reviewCount
number
1284
Reviews
What our users say
I have been working with Zyte's team for the last few months, and their team is fantastic. I appreciate their development speed and quality, and they run a very robust platform, producing very satisfactory results. I love the ease of the initial setup with Zyte, as they took care of all the development, and we only needed to communicate what data we needed and set up the necessary processes on our end.
David P.
Frequently asked questions
How fresh can ecommerce product data be?
Price and availability are typically delivered daily or several times a day; full catalogue attributes are usually re-crawled weekly. Real-time and on-event delivery is available where a use case needs it. We scope frequency per site to how often that site actually changes.
How do you handle site changes that break extraction?
Every run is validated against your schema. When a site redesign changes or removes a field, validation fails closed and the feed is held rather than shipping broken data. Extraction is repaired and re-validated, usually within the same delivery window.
What about anti-bot measures and blocks?
Blocked requests are automatically re-routed and retried, and persistent blocks escalate to the team running your feed. Because we operate many feeds across the same retailers, defence changes on major sites are usually handled centrally before they affect your feed.
What formats and delivery methods do you support?
JSON, JSON Lines, CSV and Parquet, delivered to Amazon S3, Google Cloud Storage, Azure Blob, a webhook, or pulled from an API — on a real-time, hourly, daily, weekly or custom schedule.
How do you approach compliance for product data?
Product feeds do not collect personal data. Every project is reviewed against our ethical web data principles before kickoff, and Zyte is a founding member of the Ethical Web Data Collection Initiative.
How long does setup take?
Scoping happens in week 1, sample data in week 2, and a monitored production feed in week 3. Larger multi-region projects can take longer to reach full coverage; we confirm the timeline during scoping.
What does an ecommerce data feed cost?
Projects are scoped on volume, complexity and frequency, then run on a predictable monthly fee after kickoff. Zyte Data is priced on successful delivery, not per request. A data specialist can give you a scoped figure after a short call.
Can I see a sample before committing?
Yes. You can request sample data for a specific URL or site below, and you receive sample data in your target schema in week 2 of any engagement before the feed goes live.