# Fit

What is this field?

The Fit field describes how a garment is designed to sit on the body. It is distinct from size — fit describes the intended silhouette and shape, while size refers to the measurement dimensions.

Fit is one of the most important attributes for reducing returns in fashion e-commerce. When customers understand whether a jacket is tailored or oversized before purchasing, they can make more informed decisions.

This field should use controlled, consistent terms rather than subjective descriptions. “Slim fit” communicates a specific silhouette; “fits nicely” does not.

BUSINESS VALUE

Why this field matters

* Fit is the number one reason customers return clothing purchased online
* Search and filter systems rely on standardized fit values to surface relevant results
* AI recommendation engines use fit preferences to suggest products customers are more likely to keep
* Clear fit descriptions reduce the volume of pre-purchase support questions
* Fit data combined with size guides dramatically improves conversion rates
* Comparison shopping tools use fit data to help customers choose between similar products

TECHNICAL SETUP

Recommended setup

Field type: Single-line text or dropdown (controlled list)

Namespace: custom.product

Key: fit

STEP-BY-STEP WALKTHROUGH

How to create the Fit 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 "fit". Set the display name to "Fit".

| Click “Add field” to create the “Fit” metafield |
| ----------------------------------------------- |

Step 3: Select the field type

Set the field type to "Single-line text or dropdown (controlled list)". This field uses a single value.

| Select the data type for “Fit” |
| ------------------------------ |

Step 4: Configure validation and description

Add a helpful description for merchants: "How the garment is designed to sit on the body (e.g., Slim fit, Relaxed fit, Oversized)." This will appear as helper text when merchants edit the field on a product.

| Description and validation settings for “Fit” |
| --------------------------------------------- |

Step 5: Save and verify

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

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

STRUCTURING GUIDANCE

How to structure the values

Use a controlled vocabulary of fit terms that your catalog uses consistently. Avoid freeform descriptions.

Fit should describe the intended silhouette, not the customer’s experience of wearing it. “Relaxed fit” is correct; “comfortable” is not a fit value.

For products that span categories (e.g., a dress that could be slim or A-line), choose the dominant silhouette.

Consider whether your fit terms need to be garment-specific. “Wide-leg” applies to trousers but not to tops.

If a product intentionally runs large or small relative to its fit category, note that separately (e.g., in a size note), not in the fit field itself.

USAGE CONTEXT

When to use this field

* All tops, shirts, blouses, and t-shirts
* All trousers, jeans, shorts, and skirts
* Dresses and jumpsuits
* Outerwear including jackets, coats, and blazers
* Knitwear and sweaters
* Any garment where the silhouette is a meaningful differentiator

REFERENCE VALUES

Example values

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

| Value         | When to use                                                        |
| ------------- | ------------------------------------------------------------------ |
| Slim fit      | Cut close to the body with minimal excess fabric                   |
| Regular fit   | Standard proportions; not tight, not loose                         |
| Relaxed fit   | Slightly looser than regular; comfortable ease through body        |
| Oversized fit | Intentionally larger than body measurements for a loose silhouette |
| Tailored fit  | Structured, precise cut often with darts or seams for shaping      |
| Straight fit  | Uniform width from hip to hem; no tapering                         |
| Tapered fit   | Gradually narrows toward the ankle or cuff                         |
| Boxy fit      | Wide through the torso with a squared-off silhouette               |
| Cropped fit   | Shortened length, ending above the natural waistline or ankle      |
| Wide-leg fit  | Generous width from hip to hem; trousers and palazzo styles        |
| Skinny fit    | Very close to the body throughout; fitted through leg or sleeve    |
| Loose fit     | Generous room through the body without structured shaping          |
| A-line fit    | Fitted at top, flaring gradually outward; dresses and skirts       |
| Bodycon fit   | Body-conscious; stretchy fabric that hugs the figure closely       |
| Longline fit  | Extended length beyond the standard hem point for the garment type |

| The “Fit” field populated with example values |
| --------------------------------------------- |

RECOMMENDATIONS

Best practices

* Maintain a fixed list of fit values and apply them consistently across your catalog
* Use fit in combination with a size guide for the most complete picture
* Show fit visually where possible (e.g., a fit comparison diagram on the product page)
* If your brand uses unique fit names (e.g., “Athletic fit”), map them to standard terms in the data
* Test fit terms with customers to ensure they understand what each means
* Review fit assignments seasonally as design teams may shift silhouettes

AVOID THESE

Common mistakes

* Confusing fit with size: “Large” is a size, not a fit
* Using subjective language: “comfy,” “flattering,” or “great fit” are not structured values
* Applying the same fit term to every product by default instead of evaluating each one
* Using different fit terms for the same silhouette across different product categories
* Leaving fit blank on outerwear or knitwear where it significantly affects the look
* Using fit to describe fabric stretch rather than garment construction

IN CONTEXT

Example: How it appears on a product

| <p>Men’s Slim Fit Chino Trousers</p><p>Fit: Slim fit</p><p>Material: 98% Cotton, 2% Elastane</p><p>Size guide: Waist 28–38, Inseam 30/32/34</p><p>Occasion: Business, Casual, Everyday</p> |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |

| Fit data displayed on the storefront via Custom Liquid |
| ------------------------------------------------------ |

<br>
