A size run is the complete, ordered set of sizes for one womenswear style. When womenswear size runs for upload teams arrive as a spreadsheet or line sheet, they often include label names only. A team building Shopify variants needs more: the labeling system, the intended display order, and which sizes belong to which product types. This guide covers exactly what to include.
Key takeaways
- A size run is the ordered set of sizes for one style; your upload team needs the labels, the sort order, and the sizing system (alpha, UK numeric, EU numeric).
- Shopify displays variant options in the order they are entered; without an explicit sort order, a team may sort alphabetically, which puts "L" before "M" and "S" in the picker.
- Different womenswear product types often use different sizing systems; a reference table prevents inconsistent option values across the catalog.
- For size-sensitive categories such as dresses and trousers, a measurement chart lets the team fill in description copy accurately.
- A style that genuinely skips a size (no XS in an outerwear style, for example) needs a confirmation note, not a correction from the team.
What a size run is in womenswear
A size run is the full, ordered set of sizes available for one style. For a womenswear top sold in XS, S, M, L, and XL, that five-value run is what creates five variants in Shopify, one per size.
Most womenswear ranges use more than one run at a time, because different product categories follow different sizing conventions. A dress might run in numeric sizes 6 to 16, the same brand's tops might run XS to XL, and a swimwear line might use 8 to 20. Sending all three systems as one undifferentiated list leads to mismatched option values across the catalog.
Our fashion product upload service handles the variant and option setup for womenswear ranges; what follows is the data we ask for at the start of each job.
What womenswear size run data your upload team needs
The table below covers what a team needs before it can build the Size option for a womenswear product in Shopify. Sending all of it with each new range avoids queries during the upload.
| Data item | What the team uses it for | Example |
|---|---|---|
| Size label names (exact) | These become the option values shoppers see in the variant picker | XS, S, M, L, XL; or 6, 8, 10, 12, 14, 16 |
| Sort order | Shopify displays variants in the order they are uploaded; the team follows your order, not alphabetical | XS first, XL last (not L before S) |
| Sizing system | Helps the team standardize labels consistently across styles from different suppliers | UK numeric, alpha, EU/international, Australian, US |
| Which product types use which run | Not every style in a range shares the same run; the team assigns the right options per product | Dresses: 6 to 16; tops: XS to XL; swimwear: 8 to 20 |
| Gaps in the run | A style that skips a size needs explicit confirmation; the team won't correct gaps without approval | Coat available in S, M, L, XL only (no XS) |
| Measurement chart (recommended) | Lets the team fill accurate description copy; most useful for dresses, trousers, and fitted knitwear | S = 85 cm (33.5 in) bust, 67 cm (26.4 in) waist |
Sizing systems and mixed conventions
Womenswear brands commonly use more than one labeling system across a range, particularly when sourcing from suppliers in different markets. The four systems most common in womenswear are alpha (XS through XL, sometimes XXS and XXL), UK numeric (6 to 26), European numeric (32 to 52), and Australian numeric (6 to 26, aligned with UK sizing).
When different styles in the same upload use different systems, the Shopify admin ends up with inconsistent option names unless the team has a mapping reference. For example, say a range includes tops in alpha sizes and dresses in UK numeric: without guidance, some products end up with an "S" variant and others with a "10" variant for the same body measurement.
A one-line mapping covers this: "our alpha XS = EU 32 = UK 6 = AU 6." You can choose to display one system consistently site-wide, or maintain separate systems per product type; either works as long as the upload team knows which approach applies.
For womenswear articles and resources organized by product type, the women's clothing upload hub covers the full range of womenswear catalog topics.
Sort order: the detail most merchants miss
Shopify displays variant option values in the order they are entered into the product record. A team that receives no sort instruction makes a default choice, and for alpha size labels, alphabetical order is almost never correct (as of October 2026, per Shopify's product options documentation).
Alphabetical sorting puts sizes in this order: L, M, S, XL, XS. For a shopper selecting a size from a dropdown or button grid, that ordering is disorienting. The expected order is XS, S, M, L, XL, from smallest to largest.
Numeric sizes (6, 8, 10, 12, 14) sort correctly in ascending numeric order without extra instruction. Alpha sizes require an explicit sort note every time.
The most useful handover format is a labeled list per product type:
- Tops and knitwear: XS, S, M, L, XL
- Dresses: 6, 8, 10, 12, 14, 16
- Outerwear: S, M, L, XL (no XS in this range)
- Swimwear: 8, 10, 12, 14, 16, 18
What happens when size run data is incomplete
A team uploading womenswear without clear size run data has to make decisions that should belong to the merchant. Here are the most common gaps and what they lead to:
No sort order. Variants appear alphabetically in the picker. L shows before S, and XL before M. Shoppers can navigate a disordered size selector, but it looks like an error and can trigger support questions.
Unlabeled sizing system. If a supplier file lists "10" and the team does not know whether it is UK 10 or EU 10, description copy will be empty or incorrect. A UK 10 corresponds to roughly EU 38 and AU 10; they are not interchangeable.
Unconfirmed gaps. A style that genuinely runs S to XL with no XS may look like an oversight to a team used to seeing XS in the same range. The team will flag it and wait for confirmation rather than upload it as-is.
Mixed conventions, undisclosed. A range using XS to XL for tops and 6 to 16 for dresses creates inconsistent option names across the catalog unless the team has been told this is intentional.
Our Shopify product data entry service is built to handle these gaps when you brief us upfront: a size run reference sheet at the start of a job removes the back-and-forth that slows large ranges.
How to prepare a size run handover
A one-page size run reference covers most upload jobs. It does not need to be a formatted spreadsheet. The information your team needs is:
- The product type groups and which sizing system each uses. One row per group is enough: dresses, tops, bottoms, outerwear, swimwear.
- The full, ordered size list for each group. Listed in the order you want sizes to appear in the picker.
- Any exceptions. Individual styles or colorways that deviate from the standard run for their group.
- A measurement chart, if available. Body measurements in both metric and imperial, per size, for the groups where sizing guidance matters most.
When you send this reference alongside your supplier files, the team can set up every product's Size option consistently without pausing to query common details.
For more on how to brief a team on each stage of a womenswear catalog job, see our guides on what photo sets an upload team needs and how to brief a team on womenswear collections.
Frequently asked questions
How many size variants can a Shopify product have?
A Shopify product can have up to 100 variants in total across up to 3 options (as of October 2026, per Shopify's variant documentation). A womenswear product with 7 alpha sizes and 4 colorways creates 28 variants, which is well within the limit. Styles that would exceed 100 size-and-color combinations need to be split into separate Shopify products.
Can we use the same size labels across all product types?
You can, but most womenswear brands do not, because sizing conventions differ by category. Tops often run in alpha sizes; dresses and trousers often run in numeric sizes. Consistency within a category matters more than consistency across all categories. Document which system each product type uses and send that reference to your upload team at the start of each job.
What if a colorway is not available in all sizes?
If a specific colorway only comes in S, M, and L while other colorways cover XS to XL, you have two options: create a separate Shopify product for that colorway, or include all sizes as variants and mark the unavailable ones with zero inventory and no availability. Either approach works; the team needs explicit guidance on which one to use. Do not leave size-availability gaps unresolved in the handover file.
Does an upload team need a measurement chart to set up size variants?
No. Size variant setup only requires label names and sort order. A measurement chart is useful for writing description copy, particularly for dresses, trousers, swimwear, and fitted knitwear, where shoppers need sizing guidance to make a purchase decision. If you have one, include it in the handover. If not, the team describes the size option in label-only terms.
What if different suppliers use different size label names for the same size?
This is a common problem in womenswear. One supplier lists "Small" and another lists "S" for the same size; a third uses "SM". Without a standardization note, the catalog ends up with mixed option values. Send a preferred label for each size in each category, and the team will apply it consistently across all supplier files. The conversion is straightforward once the rule is documented.
