Supra Size Chart
How Accurate Size Charts Cut Apparel and Footwear Returns
Returns are the quiet tax on every apparel store. A customer buys a jacket, it arrives a size too tight, and now you're paying for return shipping, restocking, and a lost sale — plus a shopper who may never come back. Industry surveys consistently put apparel return rates between 20% and 40%, and the single most common reason is the same every year: "it didn't fit."
The good news is that fit-related returns are the most preventable category of returns you have. A shopper who knows their exact measurements and can compare them against a clear, garment-specific chart makes a better decision before checkout. This post walks through why size charts move the needle, what a genuinely useful chart looks like, and how to keep yours accurate as your catalog grows.
Why "It Didn't Fit" Happens
Most fit returns trace back to one of three gaps:
- No chart at all. The shopper guesses based on their "usual" size, which varies wildly between brands.
- A generic chart. One S/M/L table applied to every product, even when a slim-fit shirt and a relaxed hoodie clearly run differently.
- A chart nobody can find. The measurements exist, but they're buried in a tab three scrolls down or hidden in a low-contrast link.
Each gap pushes the fit decision into guesswork, and guesswork is what your returns team pays for later.
What a Good Size Chart Actually Contains
A useful chart gives shoppers real measurements, not just letter sizes, and tells them how to measure. Body measurements let a customer compare against clothes they already own. Here's a sample women's tops chart in both metric and imperial:
| Size | Bust (in) | Waist (in) | Hip (in) | Bust (cm) | Waist (cm) | Hip (cm) |
|---|---|---|---|---|---|---|
| XS | 31–32 | 24–25 | 34–35 | 79–81 | 61–64 | 86–89 |
| S | 33–34 | 26–27 | 36–37 | 84–86 | 66–69 | 91–94 |
| M | 35–36 | 28–29 | 38–39 | 89–91 | 71–74 | 97–99 |
| L | 37–39 | 30–32 | 40–42 | 94–99 | 76–81 | 102–107 |
| XL | 40–42 | 33–35 | 43–45 | 102–107 | 84–89 | 109–114 |
Pair the numbers with a short "how to measure" note:
- Bust: measure around the fullest part, keeping the tape level.
- Waist: measure around the narrowest part of your torso.
- Hip: measure around the fullest part, feet together.
Footwear Needs Its Own Approach
Shoe returns are especially costly because half-sizes and regional systems collide. A cross-reference table prevents most of it:
| US (M) | US (W) | EU | UK | Foot length (cm) |
|---|---|---|---|---|
| 7 | 8.5 | 40 | 6 | 25.0 |
| 8 | 9.5 | 41 | 7 | 25.7 |
| 9 | 10.5 | 42 | 8 | 26.7 |
| 10 | 11.5 | 43 | 9 | 27.3 |
| 11 | 12.5 | 44 | 10 | 28.3 |
Always include the foot length in centimeters — it's the one measurement a shopper can take at home with a ruler and trust completely.
Match the Chart to the Garment
The biggest accuracy win is stopping the "one chart for everything" habit. A slim-fit tee, an oversized fleece, and high-rise jeans all size differently, and a shopper can feel misled when a single generic table applies to all three.
The practical fix is to build a small library of charts — slim tops, relaxed tops, denim, footwear — and assign the right one to each product. This is exactly the workflow Supra Size Chart is built around: you create each chart once in the app admin, then assign it to products by collection, product type, vendor, or tag. Your denim chart lands on every pair of jeans automatically, and your footwear chart on every shoe, without editing products one at a time.
Make It Impossible to Miss
An accurate chart that shoppers don't see may as well not exist. A few placement rules that consistently help:
- Put the size-guide trigger right next to the size selector, where the decision happens.
- On mobile, prefer a tappable link that opens the chart in place rather than sending shoppers to a separate page.
- Keep the table readable — real numbers, adequate contrast, and horizontal scrolling instead of squished columns.
Because Supra Size Chart renders tables server-side with Liquid, the chart appears instantly on load rather than flashing in after the page settles, which matters most on the mobile connections where a lot of apparel shopping happens.
Measure the Impact
Treat size charts as an experiment you can verify, not a set-and-forget task:
- Baseline your fit-related return rate for a category over 4–8 weeks.
- Deploy garment-specific charts across that category.
- Compare the return rate over an equivalent window.
- Read your return reasons. If "too small" dominates a specific product, your chart for that item likely runs optimistic — adjust the numbers.
Return-reason data is a feedback loop. A chart that produces steady "too small" complaints is telling you something concrete, and updating a central chart fixes it everywhere that chart is assigned at once.
The Takeaway
Fit returns aren't inevitable — they're a symptom of missing or mismatched information at the moment of choice. Give shoppers real measurements, match each chart to the actual garment, place it where the sizing decision happens, and keep it updated using your own return data. The stores that do this consistently turn one of retail's most expensive problems into a quiet competitive edge.