> For the complete documentation index, see [llms.txt](https://staylime.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staylime.com/docs/volume-themes/faq/products-and-variants/where-is-the-size-guide-and-why-does-it-show-on-products-without-sizes.md).

# Where is the size guide, and why does it show on products without sizes?

Where the Volume size guide lives, how it is matched to an option, and why it appears on products with no variants.

The size guide is not a section. It lives inside the **Variant picker** block of the **Product overview** section, under the **Size guide** header — which is why it is easy to miss.

{% stepper %}
{% step %}

### Open the block

In **Customize**, open a product template, expand the **Product overview** section and click the **Variant picker** block. Scroll to the **Size guide** header.
{% endstep %}

{% step %}

### Name the option it attaches to

**Size label** holds the option name the guide should sit next to — `Size` by default. The match is exact and case-insensitive, so an option called **Sizes** or **UK size** will not be found. List several names separated by commas if your catalogue is inconsistent, for example `Size, Legs size`.

If a product has more than one matching option, the link is rendered once, next to the first match.
{% endstep %}

{% step %}

### Give it content

Fill in **Content from rich text**, **Content from page**, or both — the rich text is rendered first, the page content below it. **Content from page** takes a normal Shopify page created under **Online Store → Pages**.

Nothing appears until at least one of these two is filled in, even if **Size label** matches.
{% endstep %}
{% endstepper %}

### Why it shows on products with no sizes

This is the one case where the **Size label** match is skipped. On a product with **no variants at all** (a single default variant), Volume renders the size guide link whenever **Content from rich text** or **Content from page** is filled in — there is no option to match against, so the theme shows it unconditionally.

Products that do have variants behave as expected: if none of their options matches **Size label**, no link appears.

The fix is to stop hard-coding the content in the block and feed it per product instead. Create a metafield, fill it in only on the products that need a chart, and connect it to **Content from rich text** or **Content from page** as a dynamic source. Products without the metafield then have nothing to show, so nothing is rendered — variants or not. Full walkthrough in [Size Guide](/docs/volume-themes/products/size-guide.md).

{% hint style="warning" %}
The pop-up renders the page's **content**, not the page's own theme template. Sections you added to the size chart page in the theme editor will not appear inside the pop-up — put the chart in the page's rich-text body.
{% endhint %}

{% hint style="success" icon="lightbulb" %}
Two more fields in the same group are worth knowing: **Show ruler** toggles the little ruler icon on the link, and **Style** switches the pop-up between **Popover** and **Drawer**.

The link text itself is the translation string `Size Guide`, editable under **Online Store → Themes → … → Edit default theme content**.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://staylime.com/docs/volume-themes/faq/products-and-variants/where-is-the-size-guide-and-why-does-it-show-on-products-without-sizes.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.