Filippa K Product Data
Prices, variants, availability, and images from filippa-k.com — normalised, validated, and delivered into your stack. No collector to build, and none to maintain.
source specification
- Source
- filippa-k.com
- Segment
- Contemporary & direct-to-consumer
- Origin
- Sweden — founded 1993 in Stockholm
- Categories
- Womenswear, Outerwear, Knitwear, Tailoring
- Formats
- JSON · CSV · Parquet
- Refresh
- Continuous to daily
about the source
What Filippa K sells, and how its catalogue behaves
Filippa K is a Stockholm label built on Scandinavian minimalism, longevity, and a deliberately restrained seasonal palette. Its assortment is small and heavily repeated, with tailoring and outerwear carrying the price ladder and core pieces persisting across years rather than seasons.
why teams track it
Why Filippa K data is worth having
Filippa K anchors the premium end of Scandinavian minimalism, and its slow-moving catalogue makes it an unusually stable comparison point over time. Brands positioning against COS or Arket use it to check what the tier above those charges for comparable pieces.
Visit filippa-k.comcollection method
How we collect Filippa K
Filippa K is collected through Salesforce Commerce Cloud's Search-UpdateGrid endpoint, which returns the paginated listing grid as structured data. 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 filippa-k.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 Filippa K 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 Filippa K
- Stable identifiers across carry-over core styles
- Composition and fabric detail from product data
- Colourway variants with dedicated imagery
- SFCC pagination handled server-side for complete enumeration
related sources
Tracked alongside Filippa K
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.
