FWRD Product Data
Prices, variants, availability, and images from fwrd.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- fwrd.com
- Segment
- Luxury marketplace & e-tail
- Origin
- United States — luxury arm of Revolve Group
- Categories
- Luxury womenswear, Menswear, Shoes, Bags
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What FWRD sells, and how its catalogue behaves
FWRD is Revolve Group's luxury division, carrying established designer houses with the same social-first merchandising instincts that built its sister site. It sits deliberately above Revolve on price while sharing an audience and an operating model.
why teams track it
Why FWRD data is worth having
FWRD is the clearest example of a contemporary retailer moving upmarket without changing its playbook, and running it alongside Revolve shows exactly where a single group draws the line between the two tiers. That separation is hard to observe anywhere else.
Visit fwrd.comcollection method
How we collect FWRD
FWRD is collected through server-rendered listing fragments, collected per category so the full designer assortment is enumerated. 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 fwrd.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 FWRD 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 FWRD
- Designer attribution across the luxury roster
- Price positioning directly comparable to the Revolve feed
- Both womenswear and menswear on one schema
- Markdown timing across sale windows
related sources
Tracked alongside FWRD
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.
