Your Size Guide Is Costing You Sales and Causing Returns — Here's the Fix

By Jonathan · Founder, PageGains

Most fashion brands treat their size guide like a legal disclaimer — something you slap on the page to cover yourself, not something you actually design to help a customer make a confident decision. That's a mistake that shows up in your return rate and your conversion rate simultaneously. The good news is that fixing it hits both problems at once.

Why Shoppers Abandon at the Size Step (And What the Data Says)

The moment a shopper thinks "I don't know if this will fit me," you've lost them — either to abandonment or to a return that eats your margin. Barclaycard research has found that roughly 30% of online clothing purchases get returned, with sizing being the number one reason. Meanwhile, a study by Fits.me showed that shoppers who interact with a sizing tool convert at rates two to three times higher than those who don't.

The problem isn't that customers are indecisive. It's that most size guides force them to do mental gymnastics: find a measuring tape, convert centimeters to inches, cross-reference a generic chart that says "medium = 38–40 inch chest" without accounting for the fact that your brand runs slim. That friction is enough to send someone to a competitor who makes it easier.

Fix the entry point first. Put a visible "Find my size" link directly on the product page — not buried in the footer, not hidden in a dropdown. Place it right next to the size selector, where the decision is actually being made.

Stop Using Generic Brand Size Charts and Build Product-Level Guidance Instead

A single sitewide size chart is almost always wrong for at least half your catalog. A tailored blazer and an oversized hoodie from the same brand don't share the same fit logic, so a single chart that tries to cover both ends up useful for neither.

Take ASOS as a benchmark. They publish individual garment measurements — actual bust, waist, and hip measurements for each specific product — alongside their standard size guide. The result: shoppers can compare their own measurements to the exact item they're buying, not to an average approximation of a "medium" across 400 SKUs.

The action here is straightforward: for your top 20% of products by revenue, add a measurements table at the product level. List the actual garment dimensions (not the body measurements it's designed for — the garment itself, laid flat). Include at least chest or bust, waist, hip where relevant, and length. This alone can reduce size-related returns on those SKUs by a meaningful margin — some brands report 15–25% drops after implementing it.

If you're on Shopify, this can live in a metafield and render as a tab or accordion on the product page without any custom development.

Add a "How to Measure Yourself" Section That Actually Works

Most "how to measure" instructions assume the customer already owns a fabric measuring tape and knows to measure over light clothing. Neither assumption is safe. If your instructions are a text-only list, you're leaving conversions on the table.

The fix is visual. A simple line drawing or photograph showing exactly where to place the tape — around the fullest part of the chest, at the natural waist, around the hips at the widest point — removes ambiguity instantly. Anthropologie does this well. Their size guide includes illustrated measurement guides that take about 10 seconds to interpret.

Add one more thing that most guides skip entirely: a tip on what to wear while measuring. "Measure over your underwear or thin base layer, not over bulky clothing" sounds obvious, but not including it creates measurement errors that lead directly to returns.

Keep this section short and scannable. Two or three illustrations with one-sentence captions will outperform three paragraphs of text every time. If video is in your budget, a 60-second measurement tutorial embedded on the size guide page reduces uncertainty even further — Zappos saw meaningful drop in size-related contacts after adding instructional video content.

Use Fit Language, Not Just Numbers

Numbers tell shoppers what size they are. Fit language tells them what the item will feel like on their body. Both matter, and most brands only include one.

Here's the difference: "Medium: 38–40 inch chest" is a number. "This jacket fits close to the body through the shoulders and chest. If you prefer room to layer, size up." That's fit language — and it's what helps a 39-inch chest customer decide whether to order a medium or a large.

Nudie Jeans does this well. Every denim style on their site includes a written fit description that explains the silhouette, the rise, and how the leg opening sits. A customer can read "slim through the thigh, small leg opening" and immediately know whether that matches their preference, regardless of their exact measurements.

For each of your products, write two to three sentences that describe how it actually fits a human body. Is it boxy or tailored? Does it run long in the torso? Is the waistband forgiving or structured? This content costs almost nothing to produce and directly addresses the mental gap between "I know my measurements" and "I know this will work on me."

Make Size Recommendations Specific, Not Hedged

"When in doubt, size up" is not a recommendation. It's a hedge that protects the brand while doing nothing for the customer. Specific recommendations, on the other hand, convert.

The best implementations do one of two things. Option one: a brief quiz or tool that asks two or three questions (height, weight or measurements, preferred fit) and outputs a single recommended size. Brands using tools like Kiwi Sizing or True Fit have reported conversion rate lifts of 10–20% among users who complete the recommendation flow.

Option two: model call-outs on the product page. "Our model is 5'10" and wearing a size 8" is useful because it gives shoppers a real reference point. Make it more useful by adding the model's measurements: "Our model is 5'10", 145 lbs, with a 35" bust, and is wearing a size 8." Now shoppers with similar proportions have actual data to work with.

What doesn't work: "Sizing varies by style — please consult the size guide." That sends the customer on a scavenger hunt and loses them. The recommendation needs to meet them where they are, which is on the product page, mid-decision.

Design the Size Guide for Mobile First

More than 60% of e-commerce traffic comes from mobile, and most size guides are clearly designed for desktop — multi-column comparison tables that collapse into unreadable messes on a phone screen, PDFs that open in a new tab and require pinch-zooming to read.

If your size guide isn't mobile-native, it's functionally broken for the majority of your visitors. A shopper on their phone who can't read the chart doesn't call customer service — they leave.

The mobile fix: switch from multi-column tables to vertical cards. Instead of a row showing XS | S | M | L | XL across the top, stack each size vertically with its corresponding measurements listed beneath it. The customer scrolls to their size, reads the numbers, done. No horizontal scrolling, no squinting.

Also reconsider where the size guide opens. A slide-in panel or modal that stays within the product page keeps the shopper in context. Sending them to a separate size guide page — especially if it opens in the same tab — kills the momentum and increases the chance they lose their place and don't come back.

Test this specifically: on mobile, move the "Find my size" link to above the size selector rather than below it. In multiple implementations, this single positional change has lifted size guide engagement by 15–30%.

Turn Return Reason Data Into Size Guide Improvements

Your return reason data is one of the most underused inputs in CRO. If customers are marking "too small in the shoulders" or "runs large in the waist" on their return forms, that's direct signal that your size guide or product fit descriptions aren't setting the right expectations.

Pull your return reasons by SKU monthly. Look for patterns — if three different customers in a single month return the same jacket because the sleeves are short, that's not bad luck, it's a communication failure. Add a note to the product page: "Note: This style runs slightly short in the sleeve. If you're over 6'1", consider sizing up for sleeve length."

This kind of specific, product-level callout does two things. It prevents the next round of returns from customers with the same proportions. And it builds trust — shoppers respond well to brands that are honest about fit quirks rather than pretending every item fits everyone perfectly.

Patagonia does this systematically. Their product pages frequently include fit notes like "slightly shorter torso than our standard cut" or "roomy in the hips for layering." The message it sends is: we know this product, we're being straight with you.

Set up a monthly review loop: return reasons → product page updates → size guide refinements. It takes about two hours a month and compounds over time.

The Bottom Line

A size guide that actually works isn't a static chart you build once and forget. It's a live asset that reflects what you know about your products, your customers, and the gap between the two. The brands with the lowest return rates and the highest conversion rates on sizing decisions have one thing in common: they treat fit communication as a core part of the product experience, not a compliance checkbox.

Start with the highest-return SKUs in your catalog. Add product-level measurements, write real fit language, make the "find my size" entry point impossible to miss on mobile, and run a monthly return-reason review. None of this requires a six-figure tech investment — most of it is copy and layout decisions.

The payoff is real on both ends of the funnel. Fewer returns means better margins and fewer customer service contacts. Better size guidance means fewer hesitations at the point of decision, which means more completions. Those two outcomes usually feel like they're in tension. With the right size guide, they're the same fix.