THE OUTNET Product Data
Prices, variants, availability, and images from theoutnet.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- theoutnet.com
- Segment
- Luxury marketplace & e-tail
- Origin
- United Kingdom — off-season luxury, launched 2009
- Categories
- Off-season luxury, Womenswear, Shoes, Bags
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What THE OUTNET sells, and how its catalogue behaves
THE OUTNET is the off-season outlet arm of the NET-A-PORTER group, selling previous-season designer stock at structural discounts. Every listing carries both an original price and a clearance price, which makes it one of the few catalogues where markdown depth is explicit rather than inferred.
why teams track it
Why THE OUTNET data is worth having
Clearance is where luxury inventory risk becomes visible. Tracking THE OUTNET tells you which designers are over-producing, how deep the market will discount them, and how long stock sits before it clears — none of which is observable from full-price channels.
Visit theoutnet.comcollection method
How we collect THE OUTNET
THE OUTNET is collected through product page collection with the discount structure preserved, so original and clearance price arrive as separate fields. 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 theoutnet.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 THE OUTNET 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 THE OUTNET
- Original price and clearance price as separate explicit fields
- Discount depth directly computable per listing
- Designer attribution across the clearance assortment
- Season attribution where published
related sources
Tracked alongside THE OUTNET
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.
