Outerwear Size Guide Template

Outerwear is where a generic S–XL chart becomes especially unreliable. A customer may wear a T-shirt under a lightweight shell, a thick knit under a wool coat, or protective layers under a technical jacket. The size chart must explain whether it describes the body, the finished garment, or the amount of room intentionally built in for layers. Without that context, a shopper can read a correct number and still make the wrong decision.

Choose body or finished-garment measurements

Start by naming what the numbers describe. A body chart gives the range of chest, waist, or hip measurements the product is designed to fit. A finished-garment chart gives the dimensions of the actual jacket or coat. Both can be useful, but they answer different questions. “Fits chest 100–104 cm” is not interchangeable with “garment chest 118 cm.”

For an outerwear product, finished-garment chest, sleeve, back length, shoulder, and hem can help a shopper compare a jacket they already own. If the garment is measured flat, say so and explain whether the value is half circumference. If you publish body ranges, add the product’s intended ease and layering use. Never make the customer guess whether the extra room is an error or a design choice.

Make layering allowance visible

Layering is a functional requirement, not a footnote. A waterproof shell intended for use over a mid-layer needs different room from a cropped fashion jacket or a fitted down vest. State the expected base layer in plain language: “Designed over a T-shirt,” “allows a midweight knit,” or “close-fitting insulation layer.” If the product has an adjustable waist, hem, cuff, or drawcord, explain what that adjustment can and cannot solve.

The controlling measurement also changes by silhouette. In a structured coat, chest and shoulder may control the fit. In a parka, hip and hem can control sitting comfort and movement. In a ski jacket, sleeve length and room across the upper back matter because the garment is used with arms raised. A specific decision note gives customers a method; “size up for layers” is too broad to be reliable.

Create a chart for the exact product family

Do not reuse one outerwear table for trench coats, puffers, tailored blazers, rain shells, and insulated parkas solely because they have the same size labels. Group products only when their block, ease, and construction are genuinely shared. Give each approved table a stable name, a source-document version, and a scope note listing the SKUs or collection it serves. This lets the catalog team change one record while keeping the storefront and support references consistent.

The editor above provides a compact finished-garment layout for chest, sleeve, and back length. Add or rename columns to match the product, then replace sample numbers with approved measurements. The Shopify Custom Liquid export can be placed in a product template; the general HTML export works in a custom-code block on other platforms. Both remain readable text rather than a static image.

Design the storefront experience

Place a short decision note near the size selector and give the full chart a predictable label such as “Size and layering guide.” On mobile, the table should scroll horizontally inside its own frame, not shrink until measurement labels become illegible. Keep fit notes next to the relevant chart rather than hiding them in product photography or a general FAQ.

If a product has a model measurement, make the information verifiable: identify the displayed size, the model’s relevant measurement, and the intended silhouette. Do not use one model photo as a substitute for a chart. Photography can show proportion; the table and note explain the decision.

A practical publishing example

Imagine a brand selling a lightweight rain shell, an insulated ski jacket, and an oversized wool coat. The rain shell can say it is designed over a base layer and ask customers between sizes to choose by chest and sleeve. The ski jacket can state that its finished-garment chest includes room for a mid-layer and identify upper-back mobility as part of the fit. The wool coat can name its intentionally relaxed silhouette and use shoulder, chest, and length to explain proportion. The product pages can share a design system without sharing one misleading table.

Before publishing, ask a second editor to compare the chart with the product specification, selectable variants, and live fit note. Check desktop and mobile, then make sure customer support can locate the same source. Revisit the chart whenever the pattern, insulation, lining, or manufacturing source changes.

Outerwear chart QA checklist

• State clearly whether the table uses body or finished-garment measurements.
• Name the intended layer and amount of ease in plain language.
• Use columns that reflect the product: chest, shoulder, sleeve, length, hem, or hip.
• Define flat measurements and units rather than assuming the customer understands them.
• Keep the chart beside the size selector and readable on a phone.
• Reapprove the source whenever construction or pattern grading changes.