> 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/energy-label/special-cases/variants-support.md).
# Variants support
Display variant-specific EU energy labels, badges, and product sheets that update when the customer selects a different product option.
The app fully supports Shopify variants, allowing you to display a **variant-specific** energy class badge, full energy label, and product information sheet based on the selected option.
To enable this, simply add the **EPREL Registration Number** to the relevant **variant metafield** in your Shopify admin:
1. In your Shopify admin, go to **Products**.
2. Create variants or open an existing variant.
3. For each variant, locate the **EPREL Registration Number** metafield.
4. Enter the correct EPREL number and click **Save**.
{% hint style="warning" icon="triangle-exclamation" %}
**Important notes:**
1. Variant-based energy badges appear only on:
* Product pages
* Cart drawer
* Cart page
Variant-specific badges **do** **not** appear on:
* Collection pages
* Search results
These templates typically use 'Color' as a swatch option and don’t reflect variant-level energy efficiency.
If you want energy badges to show in **Collection** and **Search**, we recommend also setting the **EPREL Registration Number** at the **product level**. This way:
* **Product-level badge** → visible in Collection and Search
* **Variant-level badge** → shown on the Product page, in the Cart drawer, and in the Cart after a variant is selected
2\. [Manual mode for legacy products](/docs/energy-label/special-cases/manual-mode-for-legacy-products.md) **is not** supported for variants.
{% 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/energy-label/special-cases/variants-support.md?ask=&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.
