How to Translate Shopify Store Checkout Fields, Error Messages and Validation Text for International Customers
A customer in Germany adds your product to cart, reaches checkout — and then stalls on a field labeled "State/Province" with no German equivalent. They close the tab. That single untranslated label is enough to kill the sale, and it's one of the most overlooked gaps in Shopify internationalization.
This guide covers exactly how to translate Shopify checkout fields, validation messages, and error text — including where each string lives, which Shopify APIs and tools handle them, and what you need to know about the limits of each approach.
Why Checkout Copy Behaves Differently Than the Rest of Your Store
Product descriptions, navigation, and theme content all live in Shopify's standard translation layer and respond to the locale parameter (?locale=de) in the Storefront API. Checkout is different. It runs on Shopify's hosted checkout domain (checkout.shopify.com or your custom domain on Plus), which means:
- Shopify controls the rendering environment, not your theme
- Many system-level strings — field labels, error messages, CTA buttons — are managed by Shopify's own locale files, not your theme's JSON
- On non-Plus plans, your ability to override these strings is limited to what Shopify's native localization already supports
This distinction matters before you spend time searching for strings in the wrong place. It also explains why translating checkout buttons and system text in your theme files won't affect what appears at checkout.
What Shopify Does Automatically (And What It Doesn't)
What Shopify Handles Natively
Shopify's checkout is already localized into dozens of languages for standard elements. When a customer shops in a locale you've enabled — say, French (fr) — Shopify automatically renders:
- Country and region field labels ("Pays," "Province")
- Standard CTA buttons ("Continuer," "Passer la commande")
- Built-in validation error messages ("Ce champ est obligatoire")
- Dynamic address field labels that adjust by country — for example, the "State/Province" field renders as "Préfecture" for Japan, "Comté" for France, or "Land" for Germany
Important caveat: This dynamic label behavior only applies to Shopify's native hosted checkout. If your theme uses a custom cart drawer or a third-party cart page that mimics checkout fields, those labels are controlled by theme code and will not adjust dynamically. You'd need to handle that localization separately in your theme's locale files.
What You Still Need to Translate
Even with Shopify's native localization active, several categories of checkout copy are your responsibility:
- Custom field labels added via checkout extensions or apps
- Shipping method names and descriptions you've written yourself
- Order summary text pulled from your product titles and descriptions
- Policy link labels and consent checkboxes (if added)
- Post-purchase page content and upsell text
- Payment method instructions from third-party gateways
Where Checkout Translation Strings Actually Live
The checkout.en.json File (and Its Locale Variants)
If you're on Shopify Plus, you have access to the checkout liquid template and its associated locale files. The primary translation file is checkout.en.json, located in your theme's locales/ directory. This file contains keys for strings you can override at the checkout level.
To find a specific string, open your theme editor, navigate to locales/, and search for the relevant JSON key. For example:
checkout.general.or→ the "or" divider between payment optionscheckout.cart.title→ the order summary headingcheckout.shipping.title→ the shipping method section heading
For each additional language, you create (or populate) a corresponding file: checkout.fr.json, checkout.de.json, and so on, using the same key structure with translated values.
Non-Plus stores do not have direct access to checkout.liquid or these locale files. Shopify handles the rendering, and your translation options at the checkout step are limited to the content you supply — product names, descriptions, shipping rates — rather than the UI shell.
The Shopify Admin Translations API
For programmatic access, Shopify exposes locale data via the Admin API. The translations endpoint (POST /api/2024-01/graphql.json using the translationsRegister mutation) allows you to set translations for supported resource types — products, collections, metafields, pages. Checkout UI strings controlled by Shopify's system are not accessible through this endpoint; only the content you own (product data, custom fields) can be pushed via the API.
This is a meaningful limitation worth knowing before you build a custom integration expecting full checkout string access.
Checkout Extensions (Plus Only)
If you've built custom checkout extensions using Shopify's UI Extensions framework, those components are fully under your control. Any text rendered by your extension — custom field labels, consent copy, upsell messages — needs to be translated by you. Shopify's extension framework supports localization via a locales/ folder within the extension package, using the same JSON key pattern as theme locales. See our deeper guide on translating checkout extensions and post-purchase pages for specifics on that workflow.
A Shopify-Specific Translation Audit for Checkout
Generic "check your translations" advice isn't useful. Here's what to actually do:
Step 1: Enable a Test Locale and Walk the Checkout
In your Shopify Markets settings, enable a target language (e.g., German). Then visit your storefront with ?locale=de appended to the URL, add a product to cart, and proceed through checkout. Screenshot every step. Note every string that appears in English — those are your gaps.
Step 2: Check Your locales/ JSON Files Directly
Open your theme code and search for checkout keys across your locale JSON files. A missing key in checkout.de.json that exists in checkout.en.json means that string will fall back to English. Compare files side by side or use a diff tool to catch missing keys systematically.
Step 3: Audit Shipping Rate Names
Go to Settings → Shipping and delivery and check every shipping rate name and description. These strings are entirely yours to write — Shopify does not translate them. If your rate is called "Standard Shipping (3-5 business days)," that text will appear verbatim in every language. Create market-specific shipping profiles with localized rate names, or keep rate names short and language-neutral (e.g., "Standard / Express").
Step 4: Review Custom Field Labels from Apps
Any app that adds fields to checkout — address validators, delivery date pickers, gift message inputs — controls its own label text. Check each app's settings for a localization or translation option. If none exists, contact the developer or consider whether the app supports Shopify's extension localization framework.
Step 5: Verify Error Messages Trigger in the Target Language
Change your browser's Accept-Language header (or use a locale-specific URL) and deliberately trigger validation errors: submit an empty required field, enter a malformed email, use an invalid postal code. Confirm the error messages appear in the expected language. Shopify's built-in validation errors will localize automatically if your locale is correctly configured — but custom validation from apps will not.
Keeping Checkout Copy Consistent With the Rest of Your Store
Checkout copy doesn't exist in isolation. If your product page calls a product a "Handtasche" but your order summary calls it something different because the product title wasn't translated, customers notice. This is where having all your product translations — titles, variants, options — accurately maintained becomes critical for checkout coherence.
For stores managing large catalogs, tools like StoreLingo can translate product titles, descriptions, and SEO fields at scale across 47 languages, keeping that content consistent through to the order summary. The translations publish into Shopify's native multilingual layer, which means no custom checkout integration is needed — Shopify pulls the localized product data automatically. That said, StoreLingo (like any translation app) handles the content layer, not Shopify's system UI strings, which remain under Shopify's control as described above.
If your checkout also involves transactional follow-up, the localization work doesn't stop at purchase confirmation — translating email notifications and transactional messages is the logical next step to keep the post-purchase experience consistent.
For stores running promotions, discount banners shown during checkout also need localization — a topic covered in detail in our guide on translating discount codes, banners and promotional content.
The Checkout Branding API: What It Does and Doesn't Do
Shopify Plus merchants can use the Checkout Branding API to customize visual elements — colors, typography, corner radius, logo placement. This API controls appearance, not string content. You cannot use the Checkout Branding API to override field label text or error message copy. Those strings are still controlled by Shopify's locale files or your checkout.en.json overrides.
This is a common point of confusion: the Checkout Editor in the Plus admin lets you rearrange and style checkout UI, but field label overrides via code remain limited even on Plus. The text you can change is what's in your locale JSON files — not the underlying Shopify system strings.
Add StoreLingo on the Shopify App Store →
FAQ
Can I translate checkout field labels on a non-Plus Shopify plan? On non-Plus plans, Shopify controls the checkout rendering and applies its own localization for standard field labels and error messages based on the active locale. You cannot directly edit these system strings — your translation work at this level is limited to the content you own, such as product titles, shipping rate names, and app-added fields.
Does the Shopify Translate & Adapt app cover checkout fields? Translate & Adapt handles translatable resources exposed through Shopify's Translations API — products, collections, pages, metafields, and theme content. It does not provide access to Shopify's core checkout UI strings (field labels, built-in validation errors), which are managed by Shopify's own locale system. Custom content you've added to checkout via extensions is a separate matter handled within the extension's own locale files.
Why does the "State/Province" field label change automatically by country, but my custom fields don't? Shopify's native address field labels are dynamic: they pull from Shopify's internal country-specific address schemas, which define the correct administrative division label per country. This behavior is built into Shopify's checkout infrastructure and only applies to standard address fields in the native hosted checkout. Any field you add — through a checkout extension, an app, or custom code — uses static labels that you define, so localization is entirely your responsibility.
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 →