QA a Shopify translation by testing the full order path, not just product pages. Add the language, assign it to a market, then place a test order and check the checkout, order confirmation, shipping update, and refund emails in that language. Also verify what appears when a translation is missing, because Shopify falls back to your primary language.
Most translation QA stops at the product page. That is the easy part. The expensive failures happen later: a checkout button in the wrong language, an order confirmation that switches back to English, or a refund email a customer cannot read. This guide gives you a repeatable test sequence for Shopify checkout and email translations, plus a decision table for the gaps that are easy to miss.
What does Shopify translate automatically, and what do you still own?
Shopify's localization and translation documentation explains that adding a language adds translations to supported themes and checkouts, but other store content needs imported translations or an app. You must supply the translations yourself, or install a translation app and assign the language to a market. See the official guidance on Localization and translation.
That single sentence sets your QA scope. You own the product titles, descriptions, collection copy, policy pages, navigation labels, and any custom theme strings. Shopify owns the default checkout and notification strings for languages that have professional translations available. Apps own their own strings, which is where most surprises live.
A useful mental model is three layers:
- Theme layer — product pages, collections, cart, footer, menus.
- Checkout layer — the checkout flow, payment step, and order status page.
- Notification layer — order confirmation, shipping confirmation, refund, and account emails.
Test all three. A translation that passes layer one can still fail layer two.
How do you set up a language so checkout and emails can be tested?
Before testing, confirm the language is published and assigned to the market you are selling into. Shopify's documentation notes that when customers land on a regional URL, the store automatically displays the translated version if translations exist. If translations do not exist, the store displays your primary language.
A practical setup sequence:
- Add the language in your Shopify admin.
- Assign that language to the relevant market.
- Import or create translations for theme content.
- Confirm the language is published, not just added.
- Open the storefront in that language and check the URL structure.
Shopify's documentation also notes that URL slugs can be translated, but the word "products" in the path cannot. So /en-ca/products/shoes might become /es-mx/products/zapatos. Check that your translated slugs resolve and do not create duplicate or broken paths.
Which checkout and email steps should you test?
Test the order path in the same order a customer experiences it. Use a real test order, not a preview.
| Step | What to check | Common failure |
|---|---|---|
| Cart | Line item names, prices, currency | Product title stays in primary language |
| Checkout | Field labels, buttons, error messages | Mixed languages on one screen |
| Payment step | Payment method names, tax labels | Untranslated app strings |
| Order confirmation | Subject line and body | Email arrives in primary language |
| Shipping confirmation | Tracking text, delivery wording | Tracking link label untranslated |
| Refund email | Refund reason and amount wording | Customer cannot understand the refund |
| Account pages | Order history, addresses | Account area not translated |
Shopify's documentation states that after you add and publish a language, translated content is displayed in the checkout and in email notifications sent to the customer. The checkout displays in the same language the customer used to browse. If translations are available for an email notification, the customer is automatically sent that notification in the language they placed the order in.
That is the behavior you are verifying. Do not assume it. Place the order and read the actual email.
What happens when a translation is missing?
This is the most important QA question, and the one most teams skip. Shopify's documentation is explicit: whenever translations do not exist, your online store displays content in your primary language.
So a missing translation does not break the page. It silently shows English (or your primary language) to a customer who chose another language. That is a quality problem, not a technical error, which makes it easy to miss in a quick visual check.
Build a missing-translation test into your routine:
- Pick one product with a complete translation.
- Pick one product with no translation.
- View both in the target language.
- Note exactly what the customer sees in each case.
- Decide whether the fallback is acceptable for launch.
If the fallback is not acceptable, the fix is to complete the translation before launch, not to hide the product. Hiding products to avoid a language gap usually costs more sales than the gap itself.
How do you test email notifications specifically?
Email notifications are the step teams most often forget, because they arrive after the test is "done." Shopify's documentation notes that you can customize translated checkout content using a compatible third-party translation app or by importing your own translations using CSV files, and that you can edit a customer profile to change the language of the notifications that a customer receives.
A practical email test:
- Place a test order in the target language.
- Open the order confirmation email and read the subject line and body.
- Trigger a shipping confirmation if your setup allows it.
- Trigger a refund and read that email.
- Check the account area for order history wording.
If an email arrives in the wrong language, check two things: whether the customer profile language matches the order language, and whether a translation exists for that specific notification. Shopify's documentation treats these as separate from theme translations, so a translated theme does not guarantee a translated email.
A worked example (hypothetical)
Imagine a UK retailer selling into France and French-speaking Belgium. They add French, assign it to the EU market, and translate product pages. A test order reveals:
- Product pages: French. Pass.
- Checkout: French labels, but one payment app shows English. Fail.
- Order confirmation: French subject, English footer. Partial.
- Refund email: English. Fail.
This is a hypothetical illustration, not a real result. The point is that three of four checks failed even though the product pages looked perfect. If the team had only checked product pages, they would have launched with three visible gaps.
What should you do before you call the translation ready?
Use this short pre-launch checklist:
- Language is added, published, and assigned to a market.
- Product pages, collections, and navigation are translated.
- A test order was placed in the target language.
- Checkout, payment step, and order status page were read end to end.
- Order confirmation, shipping, and refund emails were read.
- Missing-translation fallback was tested on at least one untranslated product.
- URL slugs resolve and do not duplicate.
If you are also preparing a campaign around a translated product, connect the landing page to a single buying decision rather than sending traffic to a generic catalog. That is covered in Product Landing Pages: Connect a Campaign to a Buying Decision.
Follow-up questions
Does Shopify translate checkout automatically when I add a language?
Shopify's documentation states that adding a language adds translations to supported themes and checkouts. The checkout has default translations for some languages, and you can customize translated content with a compatible third-party app or by importing your own translations using CSV files. So the checkout is partly automatic, but not fully yours to assume.
How do I know which email notifications are translated?
Place a test order in the target language and read each notification that arrives. Shopify's documentation notes that if translations are available for an email notification, the customer is automatically sent that notification in the language they placed the order in. You can add or edit email notification translations using the Translate & Adapt app. If a notification arrives in the wrong language, check the customer profile language and whether a translation exists for that specific notification.
