Data types · Product Details
Every product page, as a clean record. Identifiers, specs, variants, prices and images, field by field.
A product detail page carries more decisions than any other page in commerce: the price, the promise, the content that sells or doesn’t. Import.io turns those pages into typed records across every retailer and marketplace you care about, with variants split out and products matched to your own catalogue.
| Field | Value | Source on page |
|---|---|---|
| gtin | 0045242566151 | JSON-LD + spec table |
| title | M18 FUEL ½ in. Hammer Drill Kit | h1 |
| brand | Milwaukee | breadcrumb + JSON-LD |
| price / was | $159.00 / $179.00 | price block |
| variants | Tool only · Kit (2 batteries) | selector |
| specs | Chuck ½ in · 1,400 in-lbs · 4.4 lb | spec table |
| images | 9 · 1600 px | gallery |
| availability | In stock · pickup today | fulfilment block |
The page is the product.
For most shoppers, the product detail page is the product: its title, images, specifications and price are all they will ever see before buying. For retailers that page is a competitive surface; for brands it is a compliance problem; for data companies it is raw material.
The difficulty is completeness. Conventional scrapers miss fields on a large share of pages — lazy-loaded prices, variants behind selectors, specs rendered by scripts. Import.io captures the whole record, validates it against a schema, and matches it to your catalogue.
- Retail pricing and category teams
- Brand ecommerce and content teams
- Digital shelf and commerce-intelligence platforms
- Marketplace operators
- Data science and AI teams
What product details data answers.
Six questions teams use it for most.
Competitive product intelligence
Every competitor’s specs, prices and positioning for the products you compete on.
competitionCatalogue enrichment
Missing attributes, images and specifications filled from manufacturer and retailer pages.
enrichmentContent compliance
Titles, images and specs on every retailer checked against your master data.
complianceAssortment matching
Product-to-product matches across retailers by identifier, attributes and image.
matchingNew product detection
Launches, discontinuations and range changes as they appear.
launchesTraining data for commerce AI
Structured product records with provenance for search, recommendation and agent use.
AIThe data, field by field.
| field | type | example |
|---|---|---|
| gtin / mpn | str | 0045242566151 / 2904-22 |
| title | str | M18 FUEL ½ in. Hammer Drill Kit |
| brand | str | Milwaukee |
| category_path | list | Tools › Power Tools › Drills |
| price | num | 159.00 |
| was_price | num | 179.00 |
| currency | str | USD |
| variants | list | tool_only · kit_2x5ah |
| specifications | obj | {chuck: “½ in”, torque: 1400} |
| images | list | 9 URLs |
| description | str | main content, cleaned |
| retrieved_at | ts | 2026-09-25T16:14:02Z |
- Retailer product detail pages
- Marketplace listings
- Manufacturer and brand sites
- Distributor and B2B catalogues
- Product feeds and structured markup
The hard parts, handled.
What breaks when this is done with scripts, and how Import.io handles it.
Complete, not partial
Lazy-loaded prices, script-rendered specs and tabbed content are rendered and captured, and fill rates are checked per field on every run.
Variants split out
Size, colour and pack variants are captured as separate records with their own price and availability, not just the default.
Structured specs
Specification tables are parsed into typed attributes with units normalised, so 1,400 in-lbs and 158 N·m compare.
Matched to you
Records are matched to your catalogue by GTIN and model first, then attributes and image, with confidence scores.
Three ways to get it.
Same capture engine underneath each one.
Managed feeds
Teams who want complete product records from many retailers delivered on schedule, under an SLA.
learn more →Aperture
Pricing and category teams who want product, price and availability data in a ready-made application.
learn more →Self-service platform
Analysts who want to build product extractors themselves, from $199 a month.
learn more →Programs collect publicly displayed product information. Product images and descriptions remain the property of their owners; how they may be reused is agreed per program.
Product details data questions.
Straight answers.
Which fields can you extract from a product page?
Everything the page shows: identifiers, title, brand, category, price and was-price, variants, specifications, images, description, availability, delivery, seller, ratings and review counts — typically 25 to 40 fields.
How do you handle variants?
Each size, colour or pack variant is captured as its own record with its own price and availability, linked to its parent product.
Can you match products to our catalogue?
Yes: by GTIN and model number first, then attributes, text and image, each match with a confidence score and a review queue.
How complete is the data?
Fill rates are measured per field on every run and failures are held back in managed programs. In a published study, Import.io delivered twice as many complete product records as conventional scraping.
Which retailers can you cover?
Any retailer or marketplace you name, subject to feasibility per source, which is confirmed in writing before anything is quoted.