Guides

How to Translate Shopify Store Customer Account Pages and Order History for International Buyers

A German buyer completes their purchase on your beautifully translated Shopify storefront—then logs into their account and finds every label, order status, and navigation link is in English. That jarring switch is one of the most common trust-killers in international ecommerce, and it's almost entirely fixable once you know where Shopify stores account-page strings and what its current architecture actually allows.

This guide gives you the concrete steps: which locale JSON keys control account pages, how Legacy and New Customer Accounts differ in where translations live, what to do about order history language, and how to audit your locale files properly.


Why Shopify Customer Account Translation Gets Skipped

Most translation checklists focus on product pages, collections, and store policies. Account pages get skipped because merchants assume Shopify handles them automatically. It doesn't—not completely. The UI text is pulled from your theme's locale files using Liquid's t filter, and unless those files are fully populated for each language, strings silently fall back to English.


Legacy vs. New Customer Accounts: Where Translations Actually Live

This distinction matters enormously for where you do your work.

Legacy Customer Accounts

Legacy accounts render inside your theme. Every label—"Order History," "Shipping Address," "Log out"—is output via Liquid like this:

{{ 'customer.orders.title' | t }}
{{ 'customer.account.title' | t }}

Those keys live in your theme's locale JSON files under /locales/, for example locales/de.json. The relevant top-level keys are:

  • customer.orders — order history table labels, order numbers, status strings
  • customer.account — account title, login prompts, address book labels
  • customer.addresses — address form field labels and actions
  • customer.login / customer.register — authentication screens

Because these pages are inside your theme, translations you add via Shopify's Translations API (resource type: ONLINE_STORE_THEME) are applied here. You can also manage them directly in Shopify Admin under Online Store → Themes → Edit default theme content, switching language with the locale selector.

New Customer Accounts

New Customer Accounts (enabled under Settings → Customer accounts → Use new customer accounts) are hosted by Shopify on a separate subdomain (account.myshopify.com or your custom domain equivalent). They do not render inside your theme, which means your theme's locale files have no effect on them.

For New Customer Accounts, Shopify exposes a dedicated translation resource. In the Translations API, the resource type is CUSTOMER_ACCOUNT (available via the GraphQL translationsRegister mutation). You target it like any other translatable resource, but the fields are specific to the new account UI: page titles, section headings, button labels, and status messages within the portal.

In Shopify Admin, navigate to Settings → Languages, select your target language, and look for the Customer accounts section within the translation editor. This is where you add or edit strings for the new portal—it is separate from your theme content.

Practical check: Go to Settings → Customer accounts and confirm which mode you're using before touching any locale files, or you'll edit the wrong place entirely.


Auditing Your Locale Files the Right Way

Weak advice tells you to compare character counts between locale files to spot missing translations. Don't do this—it's an unreliable proxy. Instead, use Shopify CLI to pull your theme and diff the JSON keys directly.

shopify theme pull --theme your-theme-id

Then compare the key sets between your base locale (usually en.json) and a target locale (e.g., de.json):

# Extract all keys from both files and diff
jq '[paths | join(".")]' locales/en.json | sort > en_keys.txt
jq '[paths | join(".")]' locales/de.json | sort > de_keys.txt
diff en_keys.txt de_keys.txt

Any key present in en_keys.txt but missing from de_keys.txt will fall back to English at render time. Focus your translation effort on the customer.* namespace first—those are the keys that govern everything a logged-in buyer sees. A missing customer.orders.fulfilled key means your German buyer sees "Fulfilled" in their order history even if every product title is in German.


The Order History Language Problem (And Its Real Limits)

This is the question merchants ask most often, and it deserves a direct answer rather than a footnote.

What You Can Translate

The structural labels around order history—column headings ("Order," "Date," "Total," "Status"), button text ("View order," "Reorder"), and empty-state messages ("You haven't placed any orders yet")—are all controlled by locale file keys under customer.orders. Translate these keys and every buyer sees the table chrome in their language.

What You Cannot Translate (Without Extra Work)

The order status strings that Shopify generates at fulfillment time—"Fulfilled," "Partially fulfilled," "Unfulfilled," "Pending"—are written into the order record in whatever language the admin was using when the fulfillment event occurred. They are stored as static text on the order object, not as keys that Shopify re-renders per locale.

This means a French buyer who places an order while your admin is in English will see "Fulfilled" in their account, not "Exécuté," even if your French locale file is perfect.

Workarounds merchants use:

  • Use Liquid conditionals in Legacy themes to intercept the raw status string and output a translated version:
    {% case order.financial_status %}
      {% when 'paid' %}{{ 'order.status.paid' | t }}
      {% when 'pending' %}{{ 'order.status.pending' | t }}
    {% endcase %}
    
  • For New Customer Accounts, this workaround is not available since you don't control the template—your only lever is the CUSTOMER_ACCOUNT translation resource for static UI strings.

Set buyer expectations in your transactional email translations by using translated status language there, where you do have full template control.


Translating Account-Adjacent Content That's Often Missed

Beyond the core account portal, several surfaces affect the logged-in buyer experience:

  • Login and registration pages — keys under customer.login and customer.register; these are high-visibility pages where an English error message like "Invalid email or password" breaks the experience for every market
  • Address forms — customer.addresses keys include field labels and validation messages; especially important for markets where address formats differ
  • Email notifications — order confirmations, shipping updates, and account welcome emails are separate from the account portal UI and need their own translation pass
  • Checkout and post-purchase pages — the bridge between a completed transaction and the account portal; gaps here make the language switch feel abrupt
  • Returns and support content — buyers often reach support from within their account; if your support content isn't translated, the portal translation work is only half done

Using StoreLingo for Account Page Translations

For Legacy Customer Accounts, StoreLingo translates theme content—including all customer.* locale keys—across 47 languages using Claude AI. Because it works through Shopify's Translations API, translations publish directly to your multilingual storefront without theme edits.

A concrete example of how the change-detection workflow operates: if you update the label text for customer.orders.title in your theme, StoreLingo compares the stored translation fingerprint against the new source string. Only strings whose source content has changed are queued for re-translation on the next run—unchanged keys are skipped. This means updating a single account page label doesn't trigger a full re-translation of your entire theme locale file.

For merchant review, StoreLingo surfaces each translated string alongside its source so you can spot-check critical UI text—like order status labels or error messages—before publishing to live buyers.

Add StoreLingo on the Shopify App Store →


FAQ

Does Shopify automatically translate customer account pages when I add a language? No. Adding a language in Shopify enables the multilingual storefront but does not populate translations. You must either manually add strings to your locale JSON files or use a translation app—Shopify only provides the framework, not the translated content.

Can I translate order status labels like "Fulfilled" or "Pending" for international buyers? In Legacy Customer Accounts, yes—you can intercept the raw status string in Liquid using a {% case %} block and output a key from your locale file instead. In New Customer Accounts, this template-level workaround is not available; you can only translate the static UI surrounding the order list, not the status values stored on the order record itself.

Which Shopify API resource type do I target to translate New Customer Account pages? Use the CUSTOMER_ACCOUNT resource type in the GraphQL translationsRegister mutation. This is separate from ONLINE_STORE_THEME and only affects the new account portal—editing your theme locale files will have no effect on New Customer Accounts since that portal is hosted outside your theme entirely.

Choose from 47 languages

StoreLingo translates products, collections, pages and articles with AI — review and approve by default. On paid plans from Starter, auto-translate is off by default and publishes new or updated products automatically. Keep your brand terms consistent.

Add to Shopify →