> ## Documentation Index
> Fetch the complete documentation index at: https://www.twicecommerce.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Sell in more than one language
> Step 6. Add a language, translate your catalog and checkout, and override TWICE's own wording with your vocabulary.
Part of step 6 of the [launch path](/docs/guides/launch/overview), [Design your storefront](/docs/guides/launch/shape-the-storefront). Skip this page if you sell in one language only.
**Settings → Translations & Languages** is where all of this happens: add a language, set the source language, translate your content, and override TWICE's own wording.
## Add a language
Open **Settings → Translations & Languages**. In the **All languages** card, click **Add**, then pick a language.
Two checkboxes decide what the language does, and neither is on by default:
| Checkbox | What it turns on |
| ---------------- | ----------------------------------------------------------------- |
| **TWICE Admin** | The admin interface, for your team |
| **Translations** | Customer-facing content, on the sales channels you check below it |
Check **Translations**, then check every sales channel, storefront and each checkout, that a customer in this language actually uses. A language added for one checkout but left unchecked on the storefront never reaches a storefront customer.
## Set the source language
Your content is written in a **source language**, and every other language's coverage is measured against it. It defaults to English. Change it from the **Source language** card on the same page.
Changing the source language recalculates every coverage percentage. Settle it before you start translating, not partway through.
## Translate the catalog and checkout
**Settings → Translations & Languages** covers content two ways:
* Open a language's group (Listings, Collections, Locations, Attributes, Variants, Booking prices, Subscription plans, Checkout fields, and more) to work through every entity of one type at once.
* Click the translate icon next to a field in the listing editor itself: Name, Description, a fixed booking price's duration label, a subscription plan's title.
A fixed booking price's or a subscription plan's label carries a second job: two rows with matching terms and a matching label count as one storefront offering. Translating the label never changes that grouping.
Editing the *source* label after translating does, and can split or merge a storefront option. See the note in [Multi-language content](/docs/concepts/admin/translations) before you touch one.
Three things never show up as translatable, on purpose: a rate-based booking price (it has no customer-facing duration label), a checkout field of type Customer attribute (translate its name from the Attributes group instead), and select-field options (every customer reads them in the source language).
## Override TWICE's own wording
Rename a built-in label, button, or message TWICE ships, for example "Rental" to "Hire". Open the **Theme Editor**, switch to its **Translations** mode, and pick a scope: **System strings** for the storefront, **Commerce** for labels shared across every channel. A checkout carries the same two scopes on its own **Translations** tab under **Settings → Checkouts**.
Overrides work on your source language too. Reword a label without touching your primary language setting.
## Track coverage
**Settings → Translations & Languages** carries a coverage card too: a percentage per enabled language, translated fields over translatable fields, counting only fields that hold a value in the source language. Watch it move as you translate, and expect it to reset when you change the source language.
A language does not need 100% to go live. Missing fields fall back to the source language, so customers always read something.
## Done when
* Every language you sell in is added, with the sales channels it should reach checked.
* The source language matches what your original content is actually written in.
* Coverage on each enabled language accounts for everything a customer in that language reads: listings, collections, and any custom checkout fields you use.
* Every system-wording override you made in the Theme Editor exists in every language you made it for.
## Related articles
The launch step this guide belongs to.
The translations settings UI in full reference detail.
Every translatable entity type, and the booking-price label note in full.
System string overrides and the storefront language selector.
The rest of this launch step.