Shopify Merchants: Publish Fit Notes on PDP and Test in 30–45 Days

Shopify Merchants: Publish Fit Notes on PDP and Test in 30–45 Days

A fit note is a short, comparative line on the product detail page that tells a shopper how a specific garment fits against a standard size, backed by garment measurements and model data. Get the wording and placement right and you reduce fit-related returns, which account for the majority of apparel returns, while giving shoppers the confidence to buy without a second tab open for reviews.

TL;DR:

• Clear, evidence-backed fit notes significantly reduce apparel returns when they include a verified fit verdict, basis, and size guidance.
• Garment measurements should be clearly presented in an HTML table next to size selection, with model data and return policy visible for shopper confidence.
• Publishing accurate, updated fit information supported by real garment measurements and model details increases conversions and decreases costly returns.
• Automating fit note creation through virtual try-on tools enables large-scale catalog updates, saving time and ensuring consistency across SKUs.
• Regularly reviewing and versioning fit notes based on return data and manufacturing changes maintains credibility and keeps shoppers well-informed.

Table of Contents

• What must a fit note include on a PDP?
• Body measurements vs garment measurements: what to publish and how
• How do you write a fit note that shoppers trust?
• Where should fit notes live on the page for SEO and accessibility?
• How do you test whether a fit note is actually working?
• What actually moves the needle, from someone who audits PDPs
• Why most fit-note advice stops one step too early
• Scale fit notes across your catalogue without the manual audit
• Key research and internal resources
• Sources

What must a fit note include on a PDP?

Most fit notes fail because they say something vague (“true to size, we think!”) instead of something checkable. A working fit note on a PDP needs six components, and none of them are optional if you want it to actually change buyer behaviour.

• A clear fit verdict — “Runs small”, “True to size”, or “Relaxed fit” stated in the first line, not buried in a description paragraph.
• The basis for that verdict — one sentence explaining why (return data, reviewer consensus, or a model fit check).
• Between-sizes guidance — a direct instruction: “Between sizes? Size down for a fitted look.”
• Garment measurements in an HTML table , positioned next to or directly below the size selector, not linked away to a separate page.
• Model height, measurements, and the size worn in the photograph, stated plainly rather than left to guesswork.
• A visible return-policy summary , since fit uncertainty and return friction are linked decisions for the shopper.

Miss the measurement table and the verdict becomes an opinion. Miss the return summary and even a confident shopper hesitates at checkout.

Body measurements vs garment measurements: what to publish and how

Body measurements describe the customer; garment measurements describe the product as sewn. Confusing the two on a PDP is the single most common labelling error, and it is why shoppers land on the wrong size despite reading the chart carefully.

Garment (finished) measurements are the ones that actually predict fit: chest width laid flat, garment length, inseam, sleeve length. Body measurements (bust, waist, hip) belong in a separate “how to measure yourself” reference, ideally linked rather than mixed into the same table. Shopify’s own guidance recommends exactly this separation, alongside a clear how-to-measure guide and international unit conversions embedded on the product page itself rather than in a downloadable PDF.

Key measurement points differ by category:

• Tops and dresses: bust/chest, garment length, shoulder width, sleeve length.
• Trousers: waist, inseam, rise, hem width.
• Shoes: internal length in millimetres, plus a note on width fit (narrow, standard, wide).

Show both metric and imperial units in the same row, not toggled between tabs, and keep the unit order consistent across every product in the catalogue. HTML tables also outperform screenshot-style size chart images for one practical reason: search engines and AI shopping agents can read the actual numbers , which an image cannot offer no matter how sharp the graphic looks.

Pro Tip: If you do not have a factory tech pack, measure three to five finished garments from the actual production run instead of estimating from a body-measurement chart. Finished measurements from real stock are far more reliable than projected numbers.

How do you write a fit note that shoppers trust?

A good fit note reads like a quick, honest comparison, not marketing copy. Three rules keep it useful: state the comparison first, name the basis for the claim, and avoid adjectives that don’t describe a measurable outcome (“flattering”, “gorgeous drape”) in the fit line itself, saving those for the product description.

Three templates cover most categories:

• Runs small: “This style runs small. We recommend sizing up one for a true-to-size fit, based on return data and customer feedback.”
• True to size: “True to size. The model is 175cm and wears a size 10 (UK). Order your usual size.”
• Relaxed or oversized: “Cut oversized by design. Size down if you prefer a fitted silhouette; keep your usual size for the intended relaxed look.”

Back every claim with evidence you can point to, rather than a hunch. Pull return reasons tagged “too small” or “too big” from your returns system, scan review text for repeated fit comments, and cross-check against a model fit session before publishing the line. Date each fit note and version it, because fabric and cut can shift between production runs even under the same SKU, and a note written for last season’s batch may no longer be accurate.

Where should fit notes live on the page for SEO and accessibility?

Placement decides whether a fit note gets read at all. Inline text next to the “Add to Basket” button outperforms a collapsed accordion every time, because accordions hide the exact information a hesitant buyer needs before they commit, and most shoppers never click to expand them.

• Keep the measurement table visible on load on desktop; on mobile, a single tap to expand is acceptable, but the fit verdict sentence itself should never be hidden.
• Use real <table> markup with <th> headers, not a styled <div> grid, so screen readers and crawlers parse rows and columns correctly.
• Add descriptive alt text to any fit diagram image, since the table carries the data but shoppers using assistive tech still need context for the illustration.
• Where your platform supports it, expose size and returns data through structured data properties such as SizeSpecification , additionalProperty , and merchantReturnDays so merchant feeds and AI shopping tools can read fit and return terms directly.
• If you publish more than one model card per SKU (different heights or body shapes), keep each labelled clearly rather than stacking them without captions.

Field experiments on virtual fit information found it increases conversion and order value while cutting fulfilment costs tied to multi-size ordering, precisely the pattern you’d expect once fit information is easy to find rather than buried three clicks deep.

How do you test whether a fit note is actually working?

Publishing a fit note is a hypothesis, not a fact. Track it like one.

• Pick your primary metrics before launch: SKU-level return rate, PDP-to-purchase conversion, rate of multi-size orders (a proxy for “bracketing,” where shoppers buy two sizes to try at home), average order value, and, if your reporting allows it, customer lifetime value.
• Run an A/B test or a staggered rollout across a matched set of SKUs for at least one full return-window cycle, typically 30 to 45 days depending on your return policy, so returns from the test period have time to actually process.
• Log at SKU and order-item level , not just order level, so a return on one item in a multi-item order doesn’t get misattributed to the whole basket.
• Feed qualitative signals back in: if reviews or return-reason tags shift after a fit note change, update the wording again rather than treating the first version as final.
• Read the return-rate number in context. A large-scale study found that each unit quarterly increase in size-finder usage predicted a 7.51% rise in customer lifetime value the following quarter, even where short-term returns moved slightly. Fit tools can occasionally increase returns briefly, as more confident shoppers try items they’d otherwise have skipped, so judge success on CLV and repeat purchase, not the first month’s return line alone.

Pro Tip: Set a decision date before you launch the test, not after. Deciding “we’ll call it in six weeks” up front stops a noisy early result from getting killed too soon or a genuinely bad idea from limping on for a quarter.

What actually moves the needle, from someone who audits PDPs

The two most common failures are a size chart hidden behind a link and a fit label so vague it says nothing (“fits true to size, mostly”). The fastest fix is not a redesign. Add one model card with height and size worn, and one comparative sentence above the size selector. That alone resolves most of the ambiguity a shopper faces in the ten seconds before they either buy or bounce.

Where this gets slow for merchants is populating fit data across a large catalogue by hand. Automated virtual try-on tools can generate model imagery and size recommendations at scale, giving you a starting draft of the fit verdict for dozens of SKUs at once instead of writing each one manually from a spreadsheet.

Why most fit-note advice stops one step too early

Most guidance on fit notes tells you to be clear and specific, then stops there. That advice is correct but incomplete. Clarity without evidence is just a confident-sounding guess, and shoppers can tell the difference between a fit note grounded in return data and one written to sound reassuring.

The bigger gap is treating fit notes as a one-time copywriting task rather than a maintained system. Fabric batches shift, factories change, and a note written for last season’s cut quietly goes stale while still sitting on the page as gospel. The merchants who get real value from fit notes are the ones who revisit them the same way they’d revisit a pricing page: dated, versioned, and tied to a metric.

If you do one thing after reading this, make it the measurement table. A vague verdict sentence without a garment measurement table underneath is a claim with no evidence behind it, and shoppers increasingly know it.

— Jack

Scale fit notes across your catalogue without the manual audit

Writing one fit note is straightforward. Writing, verifying, and updating fit notes for a catalogue of hundreds of SKUs by hand is where most merchants stall, and where fit-related returns quietly keep costing money every month. Garmcheck is built to close that gap directly on Shopify: shoppers upload a single photo, and the app generates a photorealistic image of how that specific garment fits their body in under ten seconds, using size recommendations built from eight body measurements .

That same data can populate the fit verdict, the model card, and the measurement notes across a whole catalogue far faster than a manual review sheet, without the need for extensive engineering resources. For merchants weighing the cost of fit-driven returns against the price of getting sizing right the first time, the virtual try-on tool is worth testing on a handful of SKUs first. Start a trial and check how it performs against your current return rate before rolling it out further.

Key research and internal resources

The core evidence behind this guide comes from a Harvard Business School field experiment on virtual fit information, a large-scale study on size-finder usage and customer lifetime value, and Chalmers research on digital fitting and return costs . Shopify’s own guidance on building a sizing guide covers the practical formatting side.

For deeper implementation reading, see Garmcheck’s notes on structuring customer reviews with fit data and auditing ecommerce returns costs at SKU level.

Sources

• Fits like a glove? Knowledge and use of size finders and high-end fashion retail returns
• The value of fit information in online retail: evidence from a randomized field experiment (Harvard Business School)
• Digital product fitting reduces fit uncertainty and return costs (Chalmers research)
• Why your retail store needs a sizing guide and how to create one (Shopify blog)

Recommended

• Fabric stretch guide for Shopify size recommendations
• Size curve optimization: the Shopify fit playbook
• Denim fit guide for UK Shopify merchants
• Plus size try-on for Shopify merchants: a practical guide