Intimissimi Product Data
Prices, variants, availability, and images from intimissimi.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- intimissimi.com
- Segment
- High street & fast fashion
- Origin
- Italy — Calzedonia Group, Verona
- Categories
- Lingerie, Loungewear, Hosiery
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What Intimissimi sells, and how its catalogue behaves
Intimissimi is the Calzedonia Group's lingerie chain and one of the largest specialist intimates retailers in Europe. Its catalogue is structured around size and cup grids rather than the simple size runs used in outerwear, which makes it a genuinely different shape of data from a typical apparel feed.
why teams track it
Why Intimissimi data is worth having
Lingerie pricing is difficult to benchmark because assortment depth sits in the size grid, not the style count — two brands with the same number of styles can differ enormously in inventory commitment. Intimissimi is the European volume reference for that category, and the grid detail is what makes the comparison meaningful.
Visit intimissimi.comcollection method
How we collect Intimissimi
Intimissimi is collected through category page collection with per-product enrichment, tuned for a catalogue where size and cup variants matter as much as colour. Every source gets a dedicated collector rather than a generic crawler, because the field detail that makes this data useful only survives if the extraction is built for the site it runs against.
Structured at the source
Records are read from intimissimi.com's own structured responses wherever they exist, rather than reconstructed from page markup. That keeps the feed stable across visual redesigns.
Validated every run
Each field is checked against expected types and historical ranges. A collector producing anomalies is quarantined and repaired upstream instead of emitting bad prices into your pipeline.
Normalised to one schema
Every brand in the catalogue lands on the same schema, so adding a source is a configuration change on your side rather than another integration to write.
what you get back
Fields in the Intimissimi feed
A normalised core that is identical across every source, plus the attributes that are specific to this one.
Standard across every source
- Product name, brand, and source URL
- Current price, original price, and currency
- Category and subcategory as the source classifies them
- Colour, size, and variant availability
- Product images, deduplicated across variants
- Description, composition, and care text
- Collection timestamp on every record
Specific to Intimissimi
- Size and cup grid depth per style, not just a style count
- Colourway variants with per-colour imagery
- Category classification across lingerie, loungewear, and hosiery
- List and promotional price captured separately
related sources
Tracked alongside Intimissimi
A single brand is a data point. These are the sources customers most often take with it, all delivered on the same schema.
SOC 2 Type II
Audited controls across security, availability, and confidentiality. Report available under NDA.
GDPR & CCPA
Public catalogue data only. No personal data collected, and a DPA is available on request.
99.9% Uptime SLA
Contractual availability with monitored collectors and a public status page.
Data residency
Choose EU or US processing and storage regions to match your obligations.
questions
Frequently Asked Questions
Everything you need to know before you send us your first request.
Still have questions?
Talk to an engineerReady to Get Started?
Talk to us about your sources and volume. We'll return a sample dataset from your target sites before you commit to anything.
