Farfetch Product Data
Prices, variants, availability, and images from farfetch.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- farfetch.com
- Segment
- Luxury marketplace & e-tail
- Origin
- United Kingdom — founded 2007 in London
- Categories
- Luxury womenswear, Menswear, Shoes, Bags, Watches
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What Farfetch sells, and how its catalogue behaves
Farfetch is the largest luxury marketplace in the world, aggregating stock from hundreds of independent boutiques and brand partners into a single storefront. Because inventory is federated rather than owned, the same designer product frequently appears at different prices from different sellers in different countries.
why teams track it
Why Farfetch data is worth having
That federated structure is exactly what makes Farfetch valuable as data: it is the widest available view of luxury inventory and the only practical way to observe cross-boutique price dispersion on the same SKU. Brands use it to monitor how their products are actually being priced in the wholesale channel.
Visit farfetch.comcollection method
How we collect Farfetch
Farfetch is collected through Farfetch's internal JSON API, which returns the multi-boutique inventory with seller attribution intact. 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 farfetch.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 Farfetch 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 Farfetch
- Seller and boutique attribution per listing
- Designer and brand as separate fields from the product name
- Cross-boutique price dispersion on identical products
- Size availability per seller
related sources
Tracked alongside Farfetch
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.
