> 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/manual-mode-for-legacy-products.md).
# Manual mode for legacy products
Display EU energy labels for older products not in the EPREL database by filling in Energy Class, label image, and product sheet metafields manually.
For older or discontinued products not listed in the EPREL database, you can manually display the energy class, energy label, and product information sheet.
First, enable Manual mode: go to **Apps → EU Energy Label → Settings** and turn on **Enable manual mode**. This creates three additional metafields at the **product level** in your Shopify admin:
* **Energy Class** (A+++ to G)
* **Energy Label** (image file)
* **Product Information Sheet** (PDF)
Fill in these metafields for the relevant products, and the app will display the values automatically.
{% hint style="warning" icon="triangle-exclamation" %}
**Important notes:**
1. The **EPREL Registration Number** metafield must be left empty — both at the product and variant level.
2. Manual data is set in the product-level metafields only.
3. Manual energy badges are displayed on the Product page, Collection pages, Search results, Cart page, and Cart drawer.
4. To stay compliant with EU law, use this method **only for legacy products** that do not have an EPREL registration. The energy class, label image, and product sheet you enter are provided by you — their correctness is your responsibility.
5. Turning Manual mode off stops displaying manual labels on the storefront, but the metafields and their values are kept — nothing is deleted. Turning it back on restores them.
{% 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/manual-mode-for-legacy-products.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.
