A single hoodie can be thirty products. Five sizes, six colours, a different photo set for each colour, a sale price on two of them, and a stock status that changes every time someone checks out a medium in black.
That is what makes apparel product data different from almost any other category. In electronics, one model is one record with a specification table. In fashion, one style is a grid of variants, and most of the commercially useful information — which sizes are selling out, which colours went on markdown, which styles were quietly dropped — lives at the level of that grid, not the product.
This guide is for e-commerce, pricing, and merchandising teams that need data from fashion stores: their competitors', their suppliers', or a marketplace's. It covers what you can collect, where to collect it from, why fashion sites are harder to scrape than a typical online store, and how to turn raw variants into a dataset that is consistent enough to compare.
Why Apparel Product Data Is Harder Than Other Categories
Most product data problems get worse in fashion. A few reasons stand out.
The variant matrix. A style multiplied by sizes and colours produces dozens of SKUs, each with its own price, availability, and sometimes its own images. Data collected at the product level hides almost everything that matters. Data collected at the variant level is correct but needs structure to be usable.
Fast assortment turnover. Fashion catalogs rotate by season, drop, and collaboration. Products appear for eight weeks and disappear. A dataset that is a month old describes a store that no longer exists.
Markdowns as a strategy. Discounts in fashion are not occasional promotions — they are a planned phase of the product lifecycle. Knowing when a competitor starts marking down a category, and how deep, is often more useful than knowing the full price.
Marketing names instead of values. "Sage", "Moss", and "Olive Night" may all be green. "Relaxed", "Oversized", and "Boxy" may describe the same fit. Every brand speaks its own dialect.
Missing identifiers. Many fashion brands, especially direct-to-consumer labels, don't publish GTINs on product pages. That makes matching the same item across stores harder than in categories where every product carries a barcode.
The general process of filling gaps in a catalog — sources, matching, precedence rules — is covered in our guide to product data enrichment. This article focuses on what is specific to fashion: how to collect the data, and what it takes to make it comparable.
What Data You Can Collect from a Fashion Store
A fashion product page carries far more than a title and a price. Here are the fields worth extracting and what each one is used for.
Field | Level | What it's used for |
|---|---|---|
Product title | Style | Search, matching, attribute parsing |
Brand | Style | Assortment share, brand-level pricing |
Style code / model number | Style | Matching across stores when there's no GTIN |
Category / breadcrumb | Style | Taxonomy mapping, category analysis |
Regular price | Variant | Price positioning |
Sale price and discount % | Variant | Markdown tracking, promo depth |
Size | Variant | Size range, size-level availability |
Stock status per size | Variant | Sell-through signals, demand gaps |
Colour (as named by the store) | Variant | Display, search, colour trends |
Colour swatch / hex | Variant | Mapping to a base colour |
Material composition | Style | Filters, quality positioning, compliance |
Fit, rise, length, sleeve | Style | Filters, assortment comparison |
Care instructions | Style | Catalog completeness |
Images per colour | Variant | Catalog import, visual comparison |
Rating and review count | Style | Popularity, product performance |
Fit feedback ("runs small") | Style | Returns risk, sizing advice |
New arrival / bestseller flags | Style | Launch tracking, merchandising signals |
Two of these deserve special attention. Stock per size is the field most teams don't realise they can get, and it is one of the most valuable: a product that is "in stock" while only XXL remains is, in practice, sold out. Style code is the field that makes everything else comparable across stores when barcodes are missing.
Most of this is standard product data extraction. What changes in fashion is the need to collect it at variant level and keep the relationship between style, colour, and size intact. For the full list of supported fields, see what can be extracted.
Where to Collect It: Brand Sites, Retailers and Marketplaces
Different kinds of fashion stores answer different questions. Most projects combine several.
Brand and DTC sites. The most complete source for attributes: full composition, fit descriptions, care, every colourway, and the brand's own photography. Also the place where a brand's real pricing strategy shows — full price, its own sales, its own new drops. Many direct-to-consumer apparel brands run on Shopify, which makes their catalogs relatively regular in structure; see how to scrape a Shopify store for what that looks like in practice. Smaller labels often use WooCommerce, which has its own patterns for variations and full catalogs.
Multi-brand retailers and department stores. The best source for competitive pricing. The same brands appear across several retailers, so you can see who discounts first, who holds price, and which brands each retailer is pushing. Attribute data here is usually thinner and less consistent than on brand sites.
Marketplaces. Breadth rather than depth: thousands of sellers, wide assortment, offer-level pricing. Useful for spotting which styles and categories are crowded and where prices cluster. We cover this angle in more detail in marketplace intelligence for pricing and assortment.
Resale platforms. A secondary signal: which brands and styles hold value after the first sale. Relevant for premium and branded fashion more than for basics.
A practical rule: choose sources by the question, not by size. If you need attributes, start with brand sites. If you need price position, start with the retailers where your customers actually compare.
What Makes Fashion Stores Hard to Scrape
Fashion sites are some of the most demanding targets in e-commerce. Not because the data is hidden, but because of how it is presented.
Variants load on interaction. On many fashion sites, the price, images, and availability for a colour only appear after a shopper clicks its swatch. Size availability may arrive through a separate request when the size selector opens. A scraper that reads the page as it first loads will get one colour and miss the rest.
Stock is shown, not stated. Availability per size is often expressed visually — a crossed-out size, a greyed button, a "notify me" link — rather than as a clean field. It has to be interpreted correctly for every size on every variant.
Prices depend on location. Currency, regional pricing, VAT display, and country-specific promotions mean the same product page can show different prices to different visitors. Collection has to be pinned to a consistent market, or the comparison is meaningless.
Seasonal redesigns. Fashion stores change templates, campaign layouts, and listing structures more often than most retailers. A scraper tuned to last season's layout breaks quietly and starts returning gaps.
Heavy category pages. Infinite scroll, filters that rewrite the URL, and "load more" buttons make it easy to collect the first 48 products of a category and believe you have all of them.
Bot protection. Large fashion retailers are popular scraping targets and invest accordingly in protection.
None of this is unsolvable, but it is why fashion data collection tends to start as a quick script and end as an ongoing maintenance job. We describe the underlying engineering in why e-commerce web scraping became a real engineering problem, and the decision of whether to run it in-house in build vs buy. If you want the data without writing code, start with scraping product data without coding.
Normalizing Apparel Data: Sizes, Colours, Materials and Taxonomy
Collecting fashion data from five stores gives you five vocabularies. Before you can compare anything, the data needs to speak one language. This is the part of enrichment that is genuinely specific to apparel.
Sizes
Sizes arrive as letters (S, M, L), numbers (36, 38, 40), regional scales (EU 42, UK 8, US 10), waist and length combinations (32/34), and brand-specific systems. Normalization means mapping each value to a common scale per category — tops, bottoms, footwear, and children's wear each need their own — while recognising that a "M" from one brand is not the same garment as an "M" from another. For comparison purposes, a normalized size bucket is usually enough; for anything customer-facing, keep the brand's original size.
Colours
Map each marketing colour name to a base colour (black, white, grey, beige, blue, green, and so on) for filtering and analysis. Swatch images or hex values, where the store provides them, make this far more reliable than guessing from the name. Keep the original name as well: shoppers search for "sage", not "green".
Materials
Composition comes as text — "62% cotton, 35% polyester, 3% elastane" — sometimes split across shell, lining, and trim. Parse it into components and percentages, and you can filter by "100% cotton", compare natural-fibre share across a competitor's range, or flag missing composition before a marketplace rejects your listing.
Fit and style attributes
Fit, rise, length, neckline, and sleeve length are frequently buried in titles and descriptions: Women's High-Rise Straight Leg Jeans contains two attributes that belong in two fields. Product attribute extraction turns these phrases into structured columns using a controlled vocabulary, so that "relaxed" and "loose fit" end up as the same value.
Taxonomy
Every store organizes its catalog differently. One retailer's "Knitwear" is another's "Sweaters & Cardigans". Mapping each source's breadcrumbs to one fashion product taxonomy is what lets you compare category-level prices and assortment depth.
Matching without barcodes
With GTINs often missing, matching apparel across stores relies on brand plus style code, then colour, then size. Title similarity alone is risky: "Classic Crew Tee" exists at nearly every brand. The broader method, and its traps, are covered in what is product matching in e-commerce.
The rule that holds across all of these: store the original value and the normalized value side by side. Overwriting the source destroys information you will need for display, search, and debugging. For where missing attributes come from when a source simply doesn't have them, see where enrichment data actually comes from.
How Fashion Teams Use the Data
Price and markdown monitoring
In fashion, the interesting moment is not a price change but the start of a markdown cycle. Tracking regular and sale prices at variant level shows when competitors begin discounting a category, how deep the cuts go, whether they target specific sizes or colours, and how long full price holds after a launch. That turns end-of-season pricing from guesswork into a response to the market. Competitor price monitoring covers the setup; competitive pricing strategy covers what to do with the numbers.
Stock by size as a demand signal
Size-level availability is one of the few public signals of what is actually selling. When a competitor's core sizes sell out while the extremes remain, that style is performing. When the same style stays fully available for weeks, it probably isn't. And when a competitor runs out of your bestseller's size range, that is demand you can capture. The general approach is in how to track product stock and availability; in fashion, the key is tracking it per size, not per product.
Assortment and trend analysis
Regular snapshots of competitor catalogs show new arrivals by week, the share of each brand, colour stories for the season, price architecture by category, and which styles were removed. That is the input for range planning: where your assortment is thin, where it duplicates the market, and where there is room for a price point nobody covers. See assortment planning with competitor data for the method.
Catalog building for resellers and dropshipping
Resellers, multi-brand stores, and dropshipping businesses often need a supplier's full catalog — every style, every colour, every size, with images — loaded into their own store. Rebuilding that by hand for a fashion catalog is close to impossible because of the variant count. Scraped data structured as one row per variant can go straight into an import. The workflow is described in how to import supplier catalogs, and ShopScraping can deliver it as a ready-to-use Shopify import with variants already grouped.
Images, Descriptions and the Legal Line
Fashion has one complication that most categories don't: the product's photography and copy are a large part of its value, and they belong to the brand.
Factual data — prices, sizes, availability, composition, categories — is the normal material of competitive analysis and catalog work. Product photography and written descriptions are creative content protected by copyright. Using a brand's images in your own store is acceptable when you are an authorised reseller and your agreement allows it; otherwise it is not. Descriptions are best used as input for your own text, which is also better for SEO than the same paragraph repeated across dozens of retailers.
For competitive monitoring, images are usually collected only as reference — to confirm a match or track colourways — not for republishing. For the wider picture, see our guide on whether web scraping is legal.
How ShopScraping Collects Apparel Product Data
ShopScraping is built for exactly this kind of data: product pages with variants, availability, and media, from almost any online store.
For fashion sources, that means:
One row per variant, with style, colour, and size kept linked, so the dataset can be read at any level.
Availability per size, not just per product.
Regular and sale prices captured on every run, so markdowns are visible over time.
Images grouped by colour, ready for reference or for import where you have the rights.
Attributes parsed from titles and descriptions — fit, length, composition — into separate columns on request.
Normalization before delivery: consistent units, size and colour values mapped alongside the originals.
Delivery as CSV, Excel, or JSON on a schedule — daily during sale season, weekly or monthly for catalog snapshots — or as import-ready catalog files for Shopify and WooCommerce.
Setup and maintenance are handled on our side, including the redesigns that fashion stores go through every season.
Send us a list of the stores you watch and the fields you need, and we will prepare a sample from your actual competitors. Run a demo, check pricing, or get in touch.
FAQ
- What is apparel product data?
Apparel product data is the structured information that describes clothing products: brand, style code, category, price and sale price, sizes, colours, stock by size, material composition, fit, care instructions, images, and reviews. Unlike most categories, much of it exists at variant level — a combination of style, colour, and size.
- Can you scrape stock levels for each size?
Yes, where the store displays availability per size, which most fashion stores do. The result shows which sizes of each colour are in stock, out of stock, or low in stock. Exact unit counts are only available when the store itself shows them.
- How do you normalize clothing sizes across brands?
Each size is mapped to a common scale per category (tops, bottoms, footwear, kidswear), and regional systems such as EU, UK, and US are converted to that scale. The original brand size is kept in a separate field, because sizing differs between brands and the original is what customers see and search for.
- How often should fashion prices be scraped?
Daily during sale periods and around major launches, when markdowns change quickly. Outside those periods, two or three times a week is usually enough for pricing, and a weekly or monthly snapshot is enough for assortment and attribute data.
- Is it legal to scrape fashion websites?
Collecting publicly available factual data, such as prices, sizes, and availability, is common practice in competitive analysis. Product images and descriptions are protected content and shouldn't be republished without permission. The details depend on jurisdiction and use, so check our guide to web scraping legality and, for specific cases, a lawyer.
- Can scraped fashion products be imported into Shopify with variants?
Yes. When the data is collected at variant level, it can be shaped into a Shopify product import with options for size and colour, variant prices, SKUs, and images assigned to each colour.