OnlineDocTranslatorGuides

Answer

How Shopify Localization Works and What It Means for Your Agency

Shopify localization splits into Markets (currency, pricing, routing), the Translation API (strings), and Translate & Adapt (merchant UI) — here is how agencies

Shopify localization sits inside the broader Service Localization: What Translators and Agencies Actually Deliver program as a CMS-specific sub-lane of Website Localization: What Translators and Agencies Actually Do on the Project, and it inherits the same production patterns described in How App Localization Works and What Clients Are Buying. The reader here is the translator or agency producing the release, not the Shopify merchant setting up a store.

What is Shopify localization from the translator's and agency's side?

Shopify localization is the CMS-specific adaptation of a Shopify storefront's content, currency, pricing, routing, and theme strings for added markets and languages, delivered through Shopify Markets, the Translation API, and the Translate & Adapt app and consumed by translators via TMS connectors. The three surfaces are decoupled by design, and merging them into a single TMS job breaks hreflang at release. Agencies that treat these surfaces as one unified export regularly introduce routing defects that suppress organic traffic in the target market from the moment a locale goes live.

From the production side, Shopify localization splits into three clearly bounded lanes:

  • Shopify Markets — owns the country list, currency per market, market-specific pricing, locale routing, and the localization Liquid object. Every decision about which locale a shopper lands on and which price they see is controlled here.
  • Shopify Translation API — delivers per-string content through the translatableResources GraphQL query and the translationsRegister mutation, covering Product, Collection, OnlineStorePage, Article, Blog, EmailTemplate, ShopPolicy, Metafield, and Theme resource types. This is the layer TMS connectors call directly.
  • Translate & Adapt app — is the merchant-facing editor layered on top of the Translation API. Its free tier supports two languages with AI-assisted translation, but it has limited metafield coverage and no native agency TMS connector, making it a starting point for small merchants rather than a production tool for agency pipelines.

The business case for investing in this infrastructure is clear: ecommerce stores that localize currencies on product pages see substantially higher conversion rates, which is why market-specific pricing inside Shopify Markets is the first configuration item an agency should validate — before a single string reaches the TMS. Getting currency rendering, locale routing, and translated content aligned from the outset prevents rework that compounds across every subsequent release.

What ecommerce localization best practices apply specifically to Shopify agency work?

Beyond tool configuration, agencies must follow proven ecommerce localization principles — consistent terminology glossaries, locale-appropriate imagery, culturally adapted CTAs, and market-specific pricing copy — to deliver releases that convert in each target market. On Shopify specifically, five practices move the needle:

  1. Lock a per-market glossary before the first push, including currency names (USD, EUR, CAD) and payment-method labels, because these terms recur across product, checkout, and email surfaces.
  2. Translate product metafields on the same release cadence as the parent product, not as a deferred follow-up, since metafield content appears inline on product pages in most themes.
  3. Localize CTAs in the theme locale JSON rather than overriding them per product, so a single update propagates across every storefront surface that references that string.
  4. Review checkout and email strings in-context rather than in isolated bilingual files, because truncation defects — especially common in long German and Finnish strings — only surface at render time inside the actual template.
  5. Validate hreflang pairs after every market publish, since Shopify emits them automatically for every published locale within a Market and a missing or mismatched pair silently suppresses search visibility.

Which Shopify surfaces does an agency actually touch during localization?

Agencies touch three decoupled Shopify surfaces during localization: Shopify Markets handles country, currency, pricing, and locale routing; the Translation API exposes translatable strings via GraphQL translatableResources; and Translate & Adapt is the merchant-facing editor that reads and writes the same translation records. Each surface has a different export shape and a different sync cadence. This mirrors the i18n handoff pattern described in i18n: What Internationalization Means for Translators Producing Localized Builds.

SurfaceOwnsAgency consumes via
Shopify MarketsCountry, currency, pricing, routing, localization Liquid objectAdmin configuration + theme audit
Translation APIPer-string content on all translatable resourcesGraphQL translatableResources via TMS connector
Translate & AdaptMerchant UI editor + AI suggestionsCSV export or staging drafts for post-edit

What does Shopify Markets own?

Shopify Markets owns the country list, currency per market, market-specific pricing, domain or subfolder routing, and the localization Liquid object that themes read at render time to append currency codes such as CAD or EUR to prices. Agencies do not translate inside Markets. They configure it, then audit the theme to confirm the money Liquid filter renders the correct symbol and placement per market.

What does the Shopify Translation API own?

The Shopify Translation API owns per-string translated content on translatable resources — Product, Collection, OnlineStorePage, Article, Blog, EmailTemplate, ShopPolicy, Metafield, and Theme locale JSON — exposed through the GraphQL translatableResources query and the translationsRegister mutation. This is the surface that TMS connectors read and write. The same framework-level pattern appears in React i18n: How Translators Fit Into a React Localization Pipeline for product apps.

Where does the Translate & Adapt app fit?

Translate & Adapt is the merchant-facing editor layered on top of the Translation API, offering free machine translation for 2 languages plus paid tiers. Agencies treat its AI suggestions as a staging draft to post-edit, not as the final deliverable. Treating raw Translate & Adapt output as finished copy skips the LQA gate and ships defects.

What export shapes does Shopify hand to the translator?

Shopify hands translators three export shapes: CSV exports from Translate & Adapt for merchant-driven handoff, JSON locale files for theme strings, and GraphQL translatableResources payloads for TMS connectors. Each shape has a different sync cadence and a different reimport path. Mixing them in one job breaks the TM leverage calculation.

Which Shopify resources map to which export shape?

Products, collections, pages, articles, policies, email templates, and metafields map to CSV or GraphQL; theme strings map to JSON locale files under the theme's /locales directory; checkout and notification strings map to the Translation API via the Shop and EmailTemplate resources. The table below is the resource-by-resource export map competitors do not publish.

Shopify resourceTranslate & AdaptCSV exportGraphQL translatableResourcesJSON locale file
ProductYesYesYesNo
CollectionYesYesYesNo
OnlineStorePageYesYesYesNo
Blog / ArticleYesYesYesNo
EmailTemplatePartialNoYesNo
ShopPolicyYesYesYesNo
MetafieldPartial (by definition type)PartialYesNo
Theme stringsNoNoNoYes (/locales)
Checkout / notificationNoNoYes (Shop, EmailTemplate)No

How does the agency wire Shopify into its TMS?

The agency wires Shopify into its TMS by connecting the store's Translation API through a connector such as Crowdin, Phrase, Smartling, or Lokalise, defining a pseudo-loc and staging checkpoint, and routing TM-leveraged segments to review rather than full translation. This is the same wiring diagram shared with React i18n, Webflow, and Pendo pipelines. See Localisation Strategy: How Agencies Plan, Price, and Deliver Multi-Locale Programs for the central diagram, and How Webflow Localization Works and What Translators Need to Know for the Webflow sibling pattern.

The 5 wiring steps for a Shopify program are:

  1. Install the TMS connector and authorize read/write on translatableResources.
  2. Pull the theme's /locales JSON separately — it lives in the theme file store, not the Translation API.
  3. Define pseudo-loc on a sandbox market before the first live push.
  4. Set TM leverage rules so 100% matches route to review, not re-translation.
  5. Add a staging checkpoint tied to a preview URL per market.

What sync cadence does each connector run?

Crowdin and Phrase run on push-on-publish webhooks for Products and Articles; Smartling and Lokalise typically run scheduled polling on translatableResources; theme JSON edits require a separate theme pull. The decision table below maps connector against cadence.

TMS connectorSync modeltranslatableResources coverageTheme JSON pull
CrowdinPush-on-publish webhookFullSeparate
PhrasePush-on-publish webhookFullSeparate
SmartlingScheduled pollingFullSeparate
LokaliseScheduled pollingFullSeparate

How are dynamic content and metafields handled differently from product data?

Dynamic content — blog Articles, metafields, and section group settings — is handled on a separate review track from product listings because the Translation API routes them through different resource types, and translation memory leverage runs consistently lower on marketing prose than on structured product descriptions. An agency that collapses all resource types into a single TMS job loses the ability to apply differentiated quality gates and risks shipping unreviewed marketing copy at the same time as catalog strings.

Metafield translation is routed via the Translation API, but coverage varies by metafield definition type. Not every metafield definition is translatable by default; agencies must audit which definitions are exposed as translatable resources before scoping a project. Metafields that store rich text or single-line text are typically covered, while those storing references, integers, or booleans are not, and attempting to register translations against non-translatable types returns silent failures in some TMS connector implementations.

Checkout and notification strings occupy a third sub-track. These are translated through the Shop and EmailTemplate resources on the Translation API and are among the highest-defect surfaces in Shopify localization work. Long target-language expansions — particularly in German and Finnish — regularly cause truncation inside fixed-width notification templates, and these defects are invisible in a standard bilingual file review. Agencies run a dedicated in-context LQA pass on EmailTemplate strings before every release that touches a notification-heavy locale.

The practical production model is therefore two review tracks per release: one for structured catalog content (Products, Collections, ShopPolicies) where TM leverage is high and reviewer throughput is fast, and one for dynamic marketing prose (Articles, Blogs, metafields, EmailTemplates) where leverage is low, expansion risk is higher, and an additional in-context rendering check is mandatory.

What locale rules apply beyond language on a Shopify build?

Locale rules beyond language on Shopify are numerous and interdependent. The surfaces that carry locale-sensitive data include currency symbol and placement via the money Liquid filter, date and address formats per market, payment method availability per Market, hreflang pairs expressed as ISO 639-1 plus optional ISO 3166-1 country code, and automatic geo-detection prompts. Each of these is a distinct QA checkpoint, not a by-product of translating strings.

The money Liquid filter is a particularly common LQA defect source. It renders prices in the active market's currency and controls symbol placement — whether the symbol precedes or follows the amount, whether a space sits between them, and how decimal separators are formatted. A translated storefront that renders € 49,00 in one context and €49.00 in another creates visible inconsistency that undermines purchase confidence. Agencies include explicit money-filter rendering checks in their Shopify LQA checklist, separate from string-level review.

Payment method localization is a related non-string consideration. Consumer payment preferences vary sharply by market: domestic payment schemes dominate transaction volumes in several European countries, and a checkout that fails to surface the locally preferred method loses conversions regardless of how well the surrounding copy is translated. Agencies flag payment method configuration as a Markets-layer deliverable that sits outside the TMS workflow but must be confirmed before a locale goes live.

How are hreflang and locale routing emitted on Shopify?

Shopify emits hreflang automatically for published locales within a Market, with each page referencing all its alternates — including itself — using the correct ISO 639-1 language code and optional ISO 3166-1 country code, for example hreflang="es-MX" for Spanish as spoken in Mexico. This automatic emission is reliable when Markets are configured correctly, but it is conditional on the locale being published rather than merely created. An unpublished locale produces no hreflang output, which means a staged locale that leaks into a crawl creates an incomplete alternate set and can trigger search-engine demotion of the primary locale. Agencies validate the full hreflang set — including the x-default tag — after every market publish, treating it as a binary release gate rather than a post-launch audit item.

How does the agency run LQA on a Shopify release?

The agency runs LQA on a Shopify release with an Xbench pre-pass on exported bilingual files, a screenshot-based in-context review of checkout, product, and notification screens in each target locale, and one in-market reviewer with block-release authority. The gate is under 2 errors per 1,000 words against a trimmed MQM rubric, priced at $40–$90 per 1,000 words in US agencies. The full rubric sits in Localization QA: How Translators and Agencies Run LQA Before Release.

What Shopify-specific defects does the LQA pass catch?

Shopify-specific defects the LQA pass catches are:

  • Money Liquid filter output showing wrong currency codes or symbol placement per market.
  • Theme locale JSON keys falling back to English because the /locales file was not pulled.
  • Metafield translations missing on PDP sections, especially rich-text definitions.
  • Checkout string truncation in long German or Finnish copy.
  • EmailTemplate variables rendering untranslated placeholders.

Should an agency building a Shopify app localize the app's name and listing?

An agency building a Shopify app localizes the listing description, screenshots, and all in-app strings but keeps the app name in English. This is a deliberate discoverability decision: non-English merchants search the Shopify App Store predominantly in English, so a translated app name reduces findability more than it increases trust or comprehension. The app name functions as a search term as much as a brand identifier, and altering it for each locale fragments the name's accumulated search authority across the listing.

The practical localization scope for a Shopify App Store listing covers three items in descending priority:

  1. Listing description — translated fully into each supported locale, with localized value propositions and feature language that matches how merchants in that market describe their problems. This is the highest-leverage item because it is indexed and influences conversion from search results.
  2. Screenshots and preview media — localized to show UI strings, currency symbols, and product examples relevant to the target market. A screenshot showing USD prices and English-only UI discourages a German merchant from installing, even if the description is translated.
  3. In-app strings — translated through the app's own i18n layer, covering all merchant-facing labels, error messages, onboarding flows, and help text. These strings sit entirely outside the Shopify Translation API and require the agency to manage a separate localization pipeline for the app's own codebase.

Agencies that build multiple Shopify apps apply this same name-in-English rule consistently across their portfolio. The in-app string surface is typically the largest by word count and the most maintenance-intensive, since product updates regenerate new strings with each feature release. Establishing a TMS integration for the app's own string files — separate from any storefront localization work — is therefore a worthwhile infrastructure investment from the first localized release onward.

The questions below cover the production-side Shopify localization decisions agencies and translators meet most often, from currency switching to Translate & Adapt limits to the Markets localization Liquid object.

Frequently asked questions

Which translation app is best for Shopify?

The best Shopify translation app for an agency depends on whether you need machine-draft output, human review workflows, or certified translation delivery. Popular options include Weglot (automatic translation with manual override), Langify, and Shopify's native Translate & Adapt app. For agencies producing certified translations, the priority is an app that supports importing professionally reviewed content — not one that publishes raw machine output. Evaluate each tool on its ability to accept XLIFF or CSV imports, preserve formatting, and handle product, metafield, and blog content simultaneously.

How can I translate my Shopify store?

You can translate a Shopify store by using the native Translate & Adapt app, a third-party app like Weglot or Langify, or by manually importing translated content via the Shopify Translations API. Shopify Markets lets you assign specific languages to specific markets, so each locale gets its own URL (e.g., /fr for French). For agencies, the professional workflow typically involves exporting content, producing or reviewing translations in a CAT tool, and re-importing the final strings — keeping certified or reviewed copy separate from raw machine output.

How should I handle localization/translation of products AND blog posts/marketing material on Shopify?

Shopify's Translations API covers products, collections, metafields, pages, and blog posts under a unified content model, so all resource types can be handled in one workflow. The practical challenge for agencies is that product copy, legal disclaimers, and marketing blog posts often require different levels of review: product titles may need only light post-editing, while promotional claims may need full certified review. A scalable approach is to segment content by risk level, use first-draft generation tools for volume, and route high-stakes content to senior translators or certifiers before import.

How does the Shopify localization object work with Shopify Markets?

The Shopify localization object is a Liquid object that exposes the active language and active market to storefront templates at render time, allowing themes to conditionally display locale-specific content, currency, and formatting. When combined with Shopify Markets, each market can be assigned one or more languages, and the localization object reflects whichever locale the visitor is browsing in. For translation agencies, this means translated strings imported via the Translations API are served automatically — no custom routing code required — as long as the market and language are correctly configured in the Markets settings.

What does localisation mean in marketing?

Localisation in marketing means adapting content — not just translating words — so it resonates with a specific regional audience's culture, expectations, and buying context. This includes adjusting idioms, imagery references, date and number formats, currency, legal disclaimers, and even product names. For translation agencies working on Shopify stores, localisation goes beyond the Translations API: it requires human judgment on tone, brand voice consistency, and market-specific compliance. A certified translator adds value precisely where automated tools fall short — in culturally sensitive copy, regulated product descriptions, and promotional claims.

How do I automatically change language and currency based on the visitor's location?

Shopify Markets handles automatic language and currency switching via geolocation combined with the localization object and market-specific URL structures (subfolders or subdomains). When a visitor lands on the store, Shopify detects their country and redirects to the correct market URL, serving the assigned language and currency. For this to work, translated content must already be published through the Translations API or a compatible app — geolocation only serves what has been pre-loaded. Agencies should ensure all target-locale strings are fully reviewed and imported before a market goes live.

What's the best app or method for translating a Shopify store?

For professional translation agencies, the most reliable method is using Shopify's native Translate & Adapt app or the Translations API combined with a CAT tool and a first-draft generation service, rather than relying solely on a consumer-facing translation plugin. This approach separates machine-draft production from human review, preserves translation memory, and produces an auditable workflow — essential when clients require certified translations. Third-party apps like Weglot work well for speed, but they publish machine output directly, which is unsuitable for regulated content or markets where certified accuracy is required.

Related