> 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/localization/product-sheet-language.md). # Product sheet language How the app picks the language of the product information sheet for each customer — and what the Product sheet fallback language setting does. The language of the product information sheet isn't a style choice: EU regulations require the document in the official language of the country where the product is sold. The app handles this automatically — there's nothing to configure per country. ### How the language is chosen The sheet opens in the official language of the **customer's country**, as Shopify determines it for each visitor. A customer browsing from Germany gets the German document, a customer from France the French one — regardless of the languages your storefront is published in. The documents are generated by the official EPREL database in all official EU languages, so you don't need to translate anything or add storefront languages. Two situations are handled automatically as well: * **Countries with several official languages** — Belgium, Finland, Luxembourg, Malta, Ireland: the customer's browser language picks among the country's official options — any of them is an official language of the customer's country. * **Visitors outside the EU/EEA**, where no language requirement applies: the app follows the customer's browser language and, if that isn't an official EU language, the fallback language from the settings. ### The Product sheet fallback language setting The only language setting in the app is **Product sheet fallback language** (**Apps → EU Energy Label → Settings → Localization**). It applies only in the last case above — when neither the customer's country nor their browser points to an official EU language. It's prefilled from your store's address on installation, so most merchants never need to touch it. Inside the EU it never overrides the country-based choice: a customer in Germany gets the German sheet no matter what's selected here. ### Link text vs. document language The "Product information sheet" link next to the badge is part of your storefront, so its text follows the **storefront language** the customer is browsing in — the app ships the official name of the document in every EU language. The document behind the link follows the **customer's country**. The two can differ by design: a customer in Germany browsing your English storefront sees the English link text and gets the German PDF. That's the intended behavior, not a bug: the document follows the country the regulation points to, the link text follows the language your customer is reading in. The link text itself can't be changed. The regulations require the link to be titled exactly "Product information sheet" (or "Product fiche" for product groups still on the older labels) — shorter or custom names such as "Specifications" or "PIS" are non-compliant, so the app doesn't offer a setting for it. See [Energy labeling requirements](/docs/energy-label/getting-started/energy-labeling-requirements.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 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/localization/product-sheet-language.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.