> For the complete documentation index, see [llms.txt](https://modutheme.gitbook.io/helix/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://modutheme.gitbook.io/helix/how-to-guides/how-to-set-up-indicator-fit.md).

# How to set up the Indicator/Fit bar

The **Indicator/Fit** block shows a segmented bar on the product page to indicate sizing or fit — from "Runs small" to "Runs large". It works on its own with one shared position, and you can optionally use a metafield to set a different position per product.

![The Indicator/Fit bar on the product page](https://3215967854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlyCMfKbEVTf3hu8uxjSZ%2Fuploads%2Fgit-blob-2bf4027a53543f94b265c4932ee6a3efa35241a9%2Fhow-to-indicator-fit-overview.png?alt=media)

***

## Add the Block

In the theme editor, go to the product page → **Product Information** section → **Details** block, and add an **Indicator/Fit** block. Set its number of **Segments**, the **Active segment** to highlight by default, and the **Title** and **Left / Middle / Right** labels (for example, `Runs small` / `True to size` / `Runs large`).

![Adding and configuring the Indicator/Fit block](https://3215967854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlyCMfKbEVTf3hu8uxjSZ%2Fuploads%2Fgit-blob-3bb87ee091ddbf266f2be21015fc3cf76ca88c99%2Fhow-to-indicator-fit-add-block.png?alt=media)

This is all you need for a single shared bar. To vary the position per product, continue below.

***

## How to Customize the Indicator per Product

By default, all products use the **Active segment** value set in the block. To set a different position per product, store the segment number in a metafield and connect it to the **Active segment** field with a dynamic source. The namespace and key are your choice — Helix reads whatever value is connected to the setting, not a fixed key.

**Step 1 — Create the metafield definition**

In Shopify admin, go to **Settings → Metafields and metaobjects → Products**, click **Add definition**, and set:

* **Name** — `Indicator fit`
* **Namespace and key** — `custom.indicator_fit` (or any name you prefer)
* **Type** — Integer, one value

Click **Save**.

![Creating the Indicator fit metafield definition](https://3215967854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlyCMfKbEVTf3hu8uxjSZ%2Fuploads%2Fgit-blob-7fcfd3ccb45c5e2be00783b193af1a465de2b7a5%2Fhow-to-indicator-fit-metafield.png?alt=media)

**Step 2 — Assign fit values to products**

Open a product, scroll to **Metafields → Indicator fit**, enter the segment number that best represents its fit, and save.

For a 5-segment bar:

| Value | Meaning         |
| ----- | --------------- |
| 1     | Runs very small |
| 2     | Runs small      |
| 3     | True to size    |
| 4     | Runs large      |
| 5     | Runs very large |

![Assigning a fit value to a product's Indicator fit metafield](https://3215967854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlyCMfKbEVTf3hu8uxjSZ%2Fuploads%2Fgit-blob-6fb711008e4272caca4fb66b528f31a83adf2eb9%2Fhow-to-indicator-fit-assign.png?alt=media)

**Step 3 — Connect the metafield to the block**

In the theme editor, open the **Indicator/Fit** block. On the **Active segment** field, click the **Connect dynamic source** icon next to the field, select your **Indicator fit** metafield, and save.

![Connecting the Indicator fit metafield to the block's Active segment](https://3215967854-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlyCMfKbEVTf3hu8uxjSZ%2Fuploads%2Fgit-blob-4007862fcbcc54b2149bb13a35fd10984f39c565%2Fhow-to-indicator-fit-connect.png?alt=media)

{% hint style="info" %}
Each product now highlights the segment stored in its own metafield. Products that leave it empty fall back to the default **Active segment** typed into the block.
{% endhint %}

***

{% hint style="info" icon="headset" %}
**Need help?**

Whether you have a question, run into an issue, or just need some guidance, our support team is here to help.

<a href="https://go.crisp.chat/chat/embed/?website_id=6c25581e-794a-41b4-8552-52f3de1dd1f7" class="button secondary" data-icon="comments">Chat with us</a> <a href="https://modutheme.ticksy.com" class="button primary" data-icon="ticket">Submit a ticket</a>
{% endhint %}
