> For the complete documentation index, see [llms.txt](https://subscriptions-docs.tech-arms.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://subscriptions-docs.tech-arms.io/features/translation.md).

# Translation

Show the subscription widget, the customer portal, and Build-A-Box pages in your customers' language.

Customers see the app's text in three places. Each place is translated in a different way:

| What customers see                                                                            | Where you translate it                                                                  | Guide                                                                                                              |
| --------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| The **subscription widget** on product pages: plan names, purchase options, and widget labels | **Shopify Translate & Adapt**, opened with **Localize** from a selling plan or a widget | [Multilingual widget](https://subscriptions-docs.tech-arms.io/features/translation/multilingual-widget.md)         |
| The **customer portal** and **Build-A-Box** pages                                             | **Settings > Translation** in the app                                                   | [Multilingual pages](https://subscriptions-docs.tech-arms.io/features/translation/translation.md)                  |
| **Emails** sent by the app                                                                    | Each email template, in one language for all customers                                  | [Email Notifications](https://subscriptions-docs.tech-arms.io/features/email-notifications/email-notifications.md) |

Translate both the widget and the pages, so customers don't see a mix of languages between the product page and the portal.

## Before you start

1. In Shopify admin, go to **Settings > Languages**. Add the languages you want and **publish** them. The app only shows published languages of your store.
2. Install **Shopify Translate & Adapt** from the Shopify App Store. You need it to translate the widget.

## Good to know

* Customers see the language they choose on your store. Text you haven't translated is shown in English.
* When you change a selling plan or a widget, update its translation too. New or changed text is not translated automatically.
* Emails are not translated per customer. See [Email Notifications](https://subscriptions-docs.tech-arms.io/features/email-notifications/email-notifications.md).

*If you need help, feel free to reach out to us via in-app* [***Live chat***](https://go.crisp.chat/chat/embed/?website_id=c4ae10a3-f762-4968-b35a-c931caf62a96)***,*** [***Book a call***](https://calendly.com/ta-subscription-app-support/30min) *or at* [***support@tech-arms.io***](mailto:support@tech-arms.io)***.***


---

# 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://subscriptions-docs.tech-arms.io/features/translation.md?ask=<question>&goal=<user_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.
