Translations and languages
Translate steps, questions and answers side by side, use CSV, and adjust the builder's own text per store.
The builder shows the language the buyer browses your store in. Two kinds of text need translating: your own content (steps, questions, answers, help text) and the builder's interface (Next, Back, Add to cart, error messages).
Your content
Open the customizer in the editor and switch to Translations. Pick the language you are translating into: every buyer-facing string is listed with your primary language next to the translation, a count of what is still missing and a filter to show only the missing ones. Type straight into the list.
For a translator or a bulk change, export the table as CSV, fill in the columns and import it back. Rows are matched by their ids (such as question:q1), so the order of rows doesn't matter.
To get a first draft quickly, click Fill missing by machine. It fills only the empty cells for the language you picked, using machine translation, and leaves anything you already typed alone. Read the results through before publishing: machine translation doesn't know your product, so short option names in particular can come out wrong. One undo takes the whole fill back. Each store has a monthly allowance of 100,000 characters, enough to translate several customizers into a few languages.
Where a translation is missing, the builder falls back to your primary language. Order keys and order values are not translated, so your team always sees the same words on orders.
The builder's own text
The interface text comes built in for English, Spanish, German and French. In Settings, Storefront text you can override any of these strings for your store, for example to say "Add to bag" instead of "Add to cart", or to fill in a language that isn't built in.
Currencies
Prices are converted to the buyer's currency with the same rate and rounding as checkout. See Pricing and checkout.