> 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/multiple-eprel-numbers-and-titles.md).
# Multiple EPREL numbers and titles
Show multiple energy class badges on one product page for bundles or appliance sets by entering comma-separated EPREL numbers with custom titles.
For complex products like kitchens or appliance bundles, the app supports displaying **multiple energy class badges** on the product page — each with its own **custom title**.
To enable this feature, enter all EPREL numbers into the **EPREL Registration Number** metafield at the **product level**, using the following format:
```
1576181 [Dishwasher Siemens SN65YX00CE], 160567 [Oven Bosch HVA331BS0], 1776798 [Refrigerator Liebherr IRBPbsci 5170 BioFresh]
```
* The **number** is the EPREL registration number for the product.
* The **title** in **square brackets** is a custom label that will be displayed alongside the corresponding energy badge.
* Use a **comma** to separate each EPREL number and title pair.
{% hint style="warning" icon="triangle-exclamation" %}
**Important notes:**
1. Works only with the product-level **EPREL Registration Number** metafield. Shopify variants are not supported.
2. Multiple energy badges are only displayed on the Product page.
{% 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/multiple-eprel-numbers-and-titles.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.
