> 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/faq.md). # FAQ {% hint style="info" %} European Commission services in charge of the Energy labelling product registry, (EPREL), hold all rights, titles and interests in and to the API and/or data, including any copyrights. The energy labels, energy class badges, product information sheets and associated data are provided on an “as is” basis with no guarantees of completeness, accuracy, usefulness or timeliness. {% endhint %} ### How do I find the EPREL number for my products? There are three ways to locate it: 1. Ask your supplier or manufacturer — they are required to provide the EPREL number. 2. Scan the QR code on the product’s printed or digital energy label — it links to the EPREL page, where the number appears in the breadcrumb as gray digits. 3. Find the EPREL numbers online in the [EPREL database](https://eprel.ec.europa.eu/screen/home). The EPREL number appears as **gray digits in the breadcrumbs** on the product page. *** ### Can the app use GTIN to fetch energy labels and product sheets? Not yet. The app currently relies on the EPREL registration number. GTIN support is planned for 2025, once EPREL enables it through their updated API. *** ### Can the app use EPREL numbers from another metafield? At this time, the app does not support connecting to custom metafields for EPREL numbers. However, there’s a simple workaround: you can **migrate the data from your existing metafield to the app’s required metafield** using third-party tools such as [Matrixify](https://apps.shopify.com/excel-export-import). This allows you to reuse existing EPREL values without manually re-entering them for every product or variant. *** ### Can I manually set the energy class, label, and product sheet without using EPREL? Yes, if a product isn’t listed in the EPREL database, you can simply **fill out three metafields** on the product level: * **Energy Class** (A+++ to G) * **Energy Label** (image file) * **Product Information Sheet** (PDF) There’s no special setting to activate — just enter the data, and the app will display it automatically. *** ### Does the app work with native Shopify variants? Yes, it fully supports Shopify variants. To show energy labels per variant, simply use the EPREL Registration Number metafield at the variant level. The app will automatically display the correct badge and product sheet for each one. *** ### Can the app automatically send EPREL data to Google Shopping? No — it’s not handled by our app automatically, since merchants use different feed generators. Google requires that the feed includes a special attribute `[certification]`, as outlined here: [Google Merchant Center Certification Attribute Requirements](https://support.google.com/merchants/answer/13528839). You can extract the EPREL number directly from the EPREL Registration Number metafield provided by our app. In short, for each product, the feed should include a certification attribute. If your current product feed solution supports custom attributes, you should be able to include this data yourself and stay fully compliant with EU regulations. If not — or if you’re unsure — we’d be happy to explore a custom integration for you. *** ### What themes does the app support? The app supports most themes available at [Shopify Theme Store](https://themes.shopify.com/). However, we cannot guarantee compatibility with custom themes developed by third-party providers or highly customized ones. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://staylime.com/docs/energy-label/faq.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.