COS Product Data
Prices, variants, availability, and images from cos.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- cos.com
- Segment
- High street & fast fashion
- Origin
- United Kingdom — launched 2007, H&M Group
- Categories
- Womenswear, Menswear, Shoes, Accessories
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What COS sells, and how its catalogue behaves
COS — Collection of Style — was H&M Group's first move upmarket, and it defined the architectural minimalism that a decade of contemporary labels went on to copy. The assortment is deliberately small, heavily repeated season to season, and priced at a premium that the group protects carefully. Very little of it is ever deeply discounted.
why teams track it
Why COS data is worth having
COS is the reference point for minimalist contemporary pricing, and because its core styles persist across seasons its catalogue makes an unusually clean longitudinal series. Brands positioning in the same space use it to check whether their own price ladder reads as premium or as high street.
Visit cos.comcollection method
How we collect COS
COS is collected through COS's internal search API plus the Next.js data endpoints behind its product pages, so the structured payload is read directly. 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 cos.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 COS 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 COS
- Stable product identifiers across seasonal carry-over styles
- Composition and care detail from the structured page data
- Colourway variants with per-colour image sets
- Category taxonomy as COS classifies it
related sources
Tracked alongside COS
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.
