# Size Guide

OVERVIEW

What is this field?

The Size Guide field provides structured sizing information that helps customers select the correct size. This goes beyond simply listing available sizes — it includes measurement data, size system references, and fit guidance.

A size guide should not be stored as a single image. Structured size data enables filtering, comparison, AI-driven size recommendations, and accessibility.

Effective size guides reduce returns, increase conversion, and build customer confidence.

BUSINESS VALUE

Why this field matters

* Sizing issues account for the largest share of fashion returns in e-commerce
* Structured size data powers AI-based size recommendation tools
* International customers need size equivalents across different systems (US, UK, EU)
* Accessible size data supports screen readers and assistive technology
* Product comparison and filtering tools rely on structured sizing information
* Accurate size data reduces customer service inquiries about fit and sizing

TECHNICAL SETUP

Recommended setup

Field type: JSON / structured metafield or dedicated size chart metafield

Namespace: custom.product

Key: size\_guide

STEP-BY-STEP WALKTHROUGH

How to create the Size Guide field in Accentuate

Follow these steps to create and configure this metafield in your Accentuate dashboard.

Step 1: Navigate to metafield definitions

Open your Accentuate dashboard and go to the metafield definitions section. Select the "Product" resource type to add a new product-level metafield.

| Accentuate dashboard — navigate to Product metafield definitions |
| ---------------------------------------------------------------- |

Step 2: Create a new metafield

Click the "Add definition" or "Create metafield" button. Enter the namespace "custom.product" and the key "size\_guide". Set the display name to "Size Guide".

| Click “Add field” to create the “Size Guide” metafield |
| ------------------------------------------------------ |

Step 3: Select the field type

Set the field type to "JSON / structured metafield or dedicated size chart metafield". This field uses a single value.

| Select the data type for “Size Guide” |
| ------------------------------------- |

Step 4: Configure validation and description

Add a helpful description for merchants: "Structured sizing information including measurements, size equivalents, and fit notes for this product." This will appear as helper text when merchants edit the field on a product.

| Description and validation settings for “Size Guide” |
| ---------------------------------------------------- |

Step 5: Save and verify

Save the metafield definition. Then navigate to any product and confirm that the "Size Guide" field appears in the metafields section, ready to accept values.

| The “Size Guide” field visible on a product editing page, empty and ready |
| ------------------------------------------------------------------------- |

STRUCTURING GUIDANCE

How to structure the values

Store size data in a structured format (JSON or a dedicated size chart metafield), not as freeform text or an image-only reference.

Include body measurements (chest, waist, hip, inseam) in centimeters and/or inches, mapped to each size label.

Provide size equivalents across relevant systems: US, UK, EU.

Include garment-specific measurements when available: sleeve length, shoulder width, total length, and rise.

Note any size anomalies: “This style runs one size small; consider sizing up.”

USAGE CONTEXT

When to use this field

* Every apparel product should have size guide data
* Footwear with international size conversions
* Accessories where sizing applies (rings, hats, belts, gloves)
* Products with extended or non-standard sizing
* Any product where incorrect sizing commonly leads to returns

REFERENCE VALUES

Example values

The following values are recommended starting points. Adapt them to your product catalog as needed.

| Value                 | When to use                                                       |
| --------------------- | ----------------------------------------------------------------- |
| XS                    | Extra small; body measurements range e.g. chest 80–84 cm          |
| S                     | Small; body measurements range e.g. chest 84–88 cm                |
| M                     | Medium; body measurements range e.g. chest 88–92 cm               |
| L                     | Large; body measurements range e.g. chest 92–96 cm                |
| XL                    | Extra large; body measurements range e.g. chest 96–100 cm         |
| XXL                   | Double extra large; body measurements range e.g. chest 100–104 cm |
| EU 36 / US 4 / UK 8   | International size equivalents for a women’s garment              |
| EU 38 / US 6 / UK 10  | International size equivalents for a women’s garment              |
| EU 50 / US 40 / UK 40 | International size equivalents for a men’s garment                |
| Waist 28″ / 71 cm     | Trouser/jeans sizing by body measurement                          |
| Waist 32″ / 81 cm     | Trouser/jeans sizing by body measurement                          |
| Chest 92 cm / 36″     | Upper body measurement for jackets and shirts                     |
| Inseam 32″ / 81 cm    | Leg length measurement for trousers                               |
| Length 65 cm          | Total garment length from shoulder to hem                         |
| One size              | Accessory or garment designed to fit a range of bodies            |

<br>

| The “Size Guide” field populated with example values |
| ---------------------------------------------------- |

RECOMMENDATIONS

Best practices

* Store size data in a structured, machine-readable format — not only as an image
* Include both body measurements and garment measurements where available
* Map sizes across multiple international systems relevant to your customer base
* Add a fit note field for items that run notably large or small
* Keep size guides updated when patterns or suppliers change
* Link size guide data at the product level, not just at the category level

AVOID THESE

Common mistakes

* Uploading a size chart as an image without any underlying structured data
* Using generic category-level size charts instead of product-specific measurements
* Providing sizes in only one regional system
* Not including body measurements alongside size labels
* Storing size data as freeform text that cannot be parsed or filtered
* Ignoring that different garment types need different measurement points

IN CONTEXT

Example: How it appears on a product

| <p>Women’s High-Rise Straight Leg Jeans</p><p>Size guide: US 2–16 / EU 32–46 / UK 6–20</p><p>Measurements: Waist 24–34″, Hip 34–44″, Inseam 30″</p><p>Fit note: This style runs true to size</p><p>Fit: Straight fit</p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

| Size Guide data displayed on the storefront via Custom Liqui |
| ------------------------------------------------------------ |

<br>