> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/how-to-translate-a-template.md). # How to Translate a template Add languages to a tenant, translate pass template fields one by one, and bulk-edit translations through Excel export and import. ## **Importance of multilingual cards** In the retail or the event worlds, it is crucial to offer cards in different languages to cater to an increasingly international clientele. Providing a multilingual pass also helps avoid any misinterpretation, which is particularly essential during events. ### **Steps to manage translations of a pass template** Go to "Settings" then to "General".

Settings menu with the General entry selected — Translations start from the General settings screen.

The internationalization section is where languages are added. For example, to add the Spanish language, simply enter the ISO code for the language, which is "es". Then, click on the small cross to confirm before saving. **The ISO code of a language can be found** [**right here**](https://en.wikipedia.org/wiki/List_of_ISO_639_language_codes)**{target="\_blank"}.**

Internationalization section with an ISO language code being entered — Check that the two-letter ISO code is the correct one for the language being added.

As many languages as needed can be added.

Internationalization section listing several configured languages — Verify that every language the programme needs appears in this list.

To set a default language, just click on the chosen language. Don't forget to click on "save" on the top of the screen.

Language list with the default language selected — Confirm the default language before saving.

In the template menu, the newly added languages now appear on the selected template. Click on one of them to preview the card.

Template editor showing the newly added languages above the card preview — Switch between languages here to preview the card in each one.

To translate a field, click on this small icon:

Only fields showing this icon can be translated.

Each language can then be translated in turn.

Field translation dialog with one input per configured language — Check that every configured language has a value before closing the dialog.

⚠️ **Only a field that has the translation icon can be translated.** ### **Steps for bulk translation** With many languages, translating fields one by one in the template editor is slow. Bulk editing is available instead, from the "Locales" section in the "Tools" menu.

Tools menu with the Locales section selected — Bulk translation lives under Tools → Locales.

Choose the pass template to translate, click on the three dots on the right and click on "bulk edit".

Locales list with the bulk edit action open in the three-dot menu — Confirm the selected template before opening bulk edit.

From this interface, all the fields can be translated.

Bulk edit grid listing template fields and their translations — The bulk edit grid shows every field and every language side by side.

Fields highlighted in orange indicate that they have not yet been translated. Simply translate the fields to the corresponding language before saving.

Bulk edit grid with untranslated fields highlighted in orange — Orange cells are the ones still missing a translation.

The file can be exported in Excel format for easier handling.

Export action in the bulk translation screen — Export produces the Excel file used for offline translation.

Once the Excel file has been modified, it can be imported back into The Wallet Crew.

Import action used to upload the translated Excel file — Import the translated file, then check the grid no longer shows orange cells.

--- # 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://docs.thewalletcrew.io/configure/advanced-configuration/wallet/template-configuration/how-to-translate-a-template.md?ask=&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.