> 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/displaying-energy-labels/finding-eprel-numbers.md).

# Finding EPREL numbers

Three ways to locate the EPREL registration number for any covered product.

Every energy badge starts with the product's **EPREL registration number** — the ID under which your supplier registered the model in the European Product Registry for Energy Labelling. There are three ways to find it:

1. **Ask your supplier or manufacturer.** They are legally required to communicate the EPREL registration number to you, and to provide the energy label or product information sheet within five working days of your request.
2. **Scan the QR code** on the product's printed or digital energy label — it links straight to the model's page in EPREL, where the number appears as gray digits in the breadcrumb.
3. **Search the** [EPREL public database](https://eprel.ec.europa.eu/screen/home) by brand and model identifier. The number appears the same way — gray digits in the breadcrumbs on the model's page.

{% hint style="info" %}
If a covered product isn't registered in EPREL at all, contact the supplier — registering it is their legal obligation. For older products that predate EPREL, see [Manual mode for legacy products](/docs/energy-label/special-cases/manual-mode-for-legacy-products.md).
{% endhint %}

***

Got the numbers? Assign the first one in the [Setup guide](/docs/energy-label/getting-started/setup-guide.md), or fill your whole catalog at once with [Bulk assignment](/docs/energy-label/displaying-energy-labels/bulk-assignment.md).


---

# 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/displaying-energy-labels/finding-eprel-numbers.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.