> For the complete documentation index, see [llms.txt](https://docs.yaycommerce.com/yaymail/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yaycommerce.com/yaymail/integrations/loco-translate.md). # Loco Translate

Upon checkout, customers who select English as their language will receive emails in English, while those who choose Deutsch will receive emails in Deutsch. {% hint style="info" %} Note: If you need to change the order status manually in the backend, ensure that the administrator's language setting matches the language of the client's order to make sure the email is sent in the correct language. {% endhint %} 1. You must change the current user language to the same as the customer's order language in the language setting.

2. After that, you can change the order status to deliver an email to your customers as desired.

With these steps, the email will be received in the correct language. --- # 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://docs.yaycommerce.com/yaymail/integrations/loco-translate.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.