Use cases / Product data enrichment
One model for every catalog you collect.
Turn inconsistent product details into records your team can filter, compare and build with. Categories, attributes and matching variants in one ecommerce model.
Matched variant3 listings
Nike Air Max 90 · Black · EU 42
- north.example“Nike Air Max 90 - Black”
- €129.99lowest
- field.example“Air Max 90 / Black”
- €139.99
- tempo.example“NIKE Air Max 90 Black”
- €134.99
↳ €129.99 – €139.99 · same model, colour and size
The record
The page’s words in. One schema out.
A French store writes “Taille 42” under “Homme › Chaussures › Baskets”. Its Item stores EU 42 in the Sneakers category, in the same fields as every other store, with the original title kept beside it.
// what the page said, in its own words
{
"url": "https://tempo.example/products/airmax90-black-42",
"title": "NIKE Air Max 90 Black",
"breadcrumbs": "Homme > Chaussures > Baskets",
"options": { "opt1": { "name": "Taille", "values": ["42"] } },
"skus": [{
"opt1": "42",
"offers": [{
"price": { "amount": "134.99", "currency": "EUR" },
"availability": { "in_stock": true, "quantity": "En stock" },
"seller": "Tempo"
}]
}],
"extracted_at": 1788253200000
}
1 Item per page. One language, one format per value and one taxonomy, imported catalogs included.
Browse the taxonomyCompare the right configuration
Same shoe. Same size. Different stores.
A lower price is only useful when the products match. Enrich uses identifiers, product details and selected options to connect equivalent variants while keeping each store’s listing.
Options stay distinct
Size, color, width and material stay with the variant. Compare the configuration your customer would actually buy.
Offers keep their context
Price, currency, seller, availability and observation time remain attached to the offer.
Matching stays inspectable
Review the original records and matching coverage. Incomplete product details can leave records unmatched.
Categories work across stores
Use a shared taxonomy and category attributes instead of remapping every merchant’s navigation.
Start with what you have
Your catalog is the starting point.
Already have product data? Import your catalog as CSV, JSON or JSONL, then enrich the valid records through the same pipeline as extracted pages. You do not need to crawl your own storefront first.
Add competitor pages to compare product details, prices and availability around your catalog. A shared structure means your team can reuse the same filters across stores.
FAQ
Questions about product data enrichment.
Go deeper
More on product data.
Start with your catalog
Make your next catalog comparable.
Start with your product data or a public store URL. Give your team consistent records and matching variants to build on.
Start for free · No credit card · Plans from $30/month