> 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/getting-started/faq.md). # FAQ ### Can the app use GTIN to fetch energy labels and product sheets? Not yet. The app uses the **EPREL Registration Number** — the one identifier every registered model is guaranteed to have. EPREL has added GTIN search, but only a small share of registered models include a GTIN so far: it's an optional field that many suppliers haven't filled in. We plan to add GTIN lookup once its coverage makes it reliable. *** ### Can the app use EPREL numbers from another metafield? No — the app reads only its own **EPREL Registration Number** metafield. You can migrate existing values into it in one pass, whether they live in another metafield or in an external file such as a supplier's CSV — see [Migrating from another source](https://staylime.com/docs/energy-label/displaying-energy-labels/bulk-assignment#migrating-from-another-metafield). *** ### Can I manually set the energy class, label, and product sheet without using EPREL? Yes. Go to **Apps → EU Energy Label → Settings** and turn on **Enable manual mode** — this creates three metafields on the product level: * **Energy Class** (A+++ to G) * **Energy Label** (image file) * **Product Information Sheet** (PDF) Enter the data, and the app will display it automatically. See [Manual mode for legacy products](/docs/energy-label/special-cases/manual-mode-for-legacy-products.md) for details. *** ### Does the app work with native Shopify variants? Yes. Set the **EPREL Registration Number** metafield at the variant level, and the badge, label, and product sheet update with the selected option. Collection and search pages show the product-level badge, so we recommend filling the product-level metafield as well — see [Variants support](/docs/energy-label/special-cases/variants-support.md). *** ### Why did a customer get the product sheet in a language my store isn't translated to? Because the document follows the customer's country, not the storefront language: EU rules require the product information sheet in the official language of the country where the product is sold. The PDFs are generated by the EPREL database in all official EU languages, so no storefront translations are needed. See [Product sheet language](/docs/energy-label/localization/product-sheet-language.md) for how the language is chosen. *** ### 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 can include the required certification attribute yourself. 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/getting-started/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.