NET-A-PORTER Product Data
Prices, variants, availability, and images from net-a-porter.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- net-a-porter.com
- Segment
- Luxury marketplace & e-tail
- Origin
- United Kingdom — founded 2000 in London
- Categories
- Luxury womenswear, Shoes, Bags, Jewellery, Beauty
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What NET-A-PORTER sells, and how its catalogue behaves
NET-A-PORTER invented luxury e-commerce as a category and remains its editorial standard, combining a tightly curated designer assortment with magazine-quality product content. Unlike a marketplace it owns its inventory, so its prices are buying decisions rather than aggregated seller listings.
why teams track it
Why NET-A-PORTER data is worth having
Because NET-A-PORTER buys rather than aggregates, its assortment is a direct read on what a leading luxury buyer thinks will sell — which no marketplace feed can tell you. Its markdown timing is also the one the rest of luxury e-commerce watches and follows.
Visit net-a-porter.comcollection method
How we collect NET-A-PORTER
NET-A-PORTER is collected through the structured product data behind NET-A-PORTER product pages, including the editorial detail the retailer publishes per product. 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 net-a-porter.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 NET-A-PORTER 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 NET-A-PORTER
- Editorial product copy carried through as structured text
- Designer as a separate field from product name
- Owned-inventory pricing without seller dispersion
- Size availability and sell-through state
related sources
Tracked alongside NET-A-PORTER
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.
