Amazon Size Charts and Fit Content: Cutting Returns Before They Happen

What a size chart actually is on Amazon

A size chart isn't a photo you upload — it's structured data, built from required attributes that every US apparel and footwear listing has to carry: target gender, age range, size class, and size value at minimum, with category-specific fields layered on top. A shirt listing needs neck and sleeve measurements; pants need waist and inseam; shapewear needs cup and band. Amazon uses these fields to build the standardised size chart a shopper sees on the product page, and to power comparisons across sizes and across products in the same category.

Brand-specific size charts — where you supply your own measurements rather than relying on Amazon's category default — are only available to Brand Registered sellers, accessed through Catalog → Add Size Charts in Seller Central. An unregistered seller's apparel listings still carry the required size attributes, but they inherit Amazon's generic category chart rather than a chart built from the actual garment in front of you.

Why this is a returns problem before it's a conversion problem

Apparel and footwear carry the highest return rates of any Amazon category, and fit — not damage, not wrong item, not change of mind — is the largest single reason inside that number. A shopper who can't see how a garment's actual measurements compare to their own body has exactly two options: guess, or leave. Guessing wrong produces a return; leaving produces a lost sale that shows up nowhere in your conversion data as a fit problem, because it never became an order at all.

A size chart doesn't eliminate either outcome, but it moves the decision earlier, onto information the shopper controls, rather than leaving it to a size label that varies by brand, by country, and sometimes by production run within the same brand. "Medium" on a size chart with actual chest and length measurements is a fundamentally different piece of information than "Medium" on a size label alone.

A worked example: reading a chart against a real return pattern

Take a t-shirt line selling in sizes S through XL with no size chart attached, and assume a category-typical return rate where fit-related returns run meaningfully above the account's average. If the listing does 400 orders a month, and even a modest slice of those returns trace to a shopper choosing between two labelled sizes with no measurements to compare, the fix isn't a discount or a better photo — it's the four required attributes plus a chest and length measurement in inches, attached once, that keeps paying down that specific return cause on every order after it's live.

The arithmetic that makes this worth doing: a size chart is a one-time setup cost per size class, not a per-order cost. Once the chest, length, and sleeve measurements are entered for the regular-fit size class, every ASIN sharing that size class inherits the same chart. A five-colour t-shirt line variation only needs the work done once, not five times — which is the opposite of most conversion fixes on a listing, where the cost scales with catalogue size.

What Fit Insights adds on top of the chart

Amazon has been building AI-driven fit tooling on top of the standard size chart — a Fit Insights capability aimed at surfacing what the size and fit data already on file suggests about how a specific shopper's stated size compares to a listing's chart, rather than leaving every shopper to do that comparison by eye. This sits on top of the size chart, not instead of it — the underlying required attributes and measurements are still the raw material any fit tool, Amazon's or otherwise, is working from.

The practical implication is that a listing with incomplete or missing size attributes doesn't just show a worse chart to a human shopper — it gives less to work with to whatever automated fit-matching Amazon layers on top going forward. Getting the base attributes right now is not a one-off task with a fixed payoff; it's infrastructure that new fit features build on without you doing anything further.

When it goes wrong: the chart is live and nobody's reading it

The first failure is treating the chart as decoration rather than checking it against real return data. If a size class's return rate hasn't moved after a chart goes live, the likely cause isn't that shoppers don't read charts — it's that the chart itself is wrong: measurements taken from a sample garment that doesn't match production, a size class applied to the wrong product type, or units left ambiguous between inches and centimetres on a listing selling into both US and international marketplaces.

The second failure is a chart that answers a question the shopper isn't asking. A chest measurement is the wrong lead metric for a garment where length or sleeve is actually driving the fit complaints in the reviews — check what shoppers are asking about and returning for before assuming the standard fields are the ones worth getting exactly right first. Reading the return reason codes and the questions in existing reviews before rebuilding a chart is cheap diligence that a generic chart skips.

The third is leaving the underlying attributes blank while still trying to use Fit Insights or any newer Amazon fit feature — those tools are only as good as the size data feeding them, and an incomplete attribute set silently limits what any fit-matching layer built on top of it can do, with no error message telling you why the feature isn't helping.

Where fit sits inside the bigger conversion picture

72.4% of the sessions across the 46 brands we manage arrive from the Amazon mobile app, where a shopper is even less likely to zoom into a size chart buried below the fold than on desktop — which makes the chart's clarity, not just its presence, part of the job. A size chart that requires pinching and scrolling to read on a phone is functionally similar to no chart at all for most of a listing's actual traffic.

Dr. CRO's listing work treats size and fit attributes as part of the same versioned record as the rest of a listing's copy — tracked, checked before a change goes live, and built to be legible on the traffic a listing actually gets rather than the desktop view a spreadsheet review happens on.