How to Translate a Shopify Store?

Translating a Shopify store correctly is a 4-layer problem: storefront copy (Shopify Translate & Adapt or third-party app), checkout localisation (Shopify Markets), product imagery and metadata (manual per-language), and SEO infrastructure (hreflang, sitemap, theme.liquid edits). The fastest viable route ships in 10 working days and costs roughly £997 in managed migration spend at the Growth tier. The slowest free route takes 60-90 hours of internal work per language. For Amazon FBA EU sellers targeting DE/FR/IT/ES, the architectural choices made on day one determine whether the store ranks on Google.de or stays invisible.

---

The short answer: 4 layers, 10 working days

A complete Shopify multilingual launch covers four distinct layers, each with its own tooling. Skipping one breaks the entire deployment.

Here is the layer-by-layer breakdown for translating a Shopify store:

• Layer 1 — Storefront copy: Shopify Translate & Adapt (free for 2 languages, then £8/month per additional language) OR third-party apps like Weglot (€29-499/month) OR managed translation pipeline. Handles product titles, descriptions, navigation, blog posts.
• Layer 2 — Checkout localisation: Shopify Markets (free with most plans). Handles currency conversion, payment methods (SEPA/Bancontact in EU), tax calculation, shipping zones.
• Layer 3 — Product imagery and metadata: Manual per-language. Handles language-specific imagery, alt text, video subtitles, and locale-specific product specs.
• Layer 4 — SEO infrastructure: Hreflang tags (auto on Online Store 2.0 themes, manual on legacy), multi-locale sitemap, geo-targeting in Search Console, structured data.

Read on for how each layer actually deploys.

Layer 1: storefront copy

Shopify Translate & Adapt is the default first-party app and the cheapest entry point. It auto-translates storefront strings via Google Translate engine, free for up to 2 languages. For DTC brands serious about conversion, the free auto-translation needs native review or replacement.

The app installs from the Shopify App Store and exposes a translation panel under Settings → Languages. You add a target language, click "Auto-translate", and Google's API generates translations for product titles, descriptions, navigation, and most theme strings. The free tier ships unedited Google output directly to your live storefront — fine for prototype testing, problematic for production. For German and Italian markets specifically, DeepL outperforms Google Translate by 15-25% on benchmark tests, which is why most managed migrations replace the Google engine with DeepL plus native review. Read our is Shopify Translate and Adapt free deep-dive for the full breakdown of what the free tier covers and what it misses. Third-party alternatives like Weglot, ConveyThis, and Linguise extend the feature set but add £29-499/month in software cost. The cheapest production-quality path is managed translation that replaces the auto-engine entirely.

Layer 2: Shopify Markets for checkout

Shopify Markets handles everything Translate & Adapt does not: currency conversion, regional payment methods, tax calculation per country, and shipping zones. It is included with most Shopify plans and is mandatory for EU launches.

Markets configuration lives under Settings → Markets and lets you create regional storefronts that share product catalogues but localise checkout. You add Germany as a market, configure EUR currency display, enable SEPA payments and Klarna, set German VAT rates (19% standard, 7% reduced), define shipping zones from your fulfilment centre, and Markets routes German visitors to the correct flow automatically. Critically, Markets does NOT translate any storefront copy — that is Translate & Adapt's job. The two apps work together. For Amazon FBA EU sellers, Markets is non-negotiable: without it, a German visitor sees GBP pricing and UK payment methods, which kills conversion in the first 200ms of page load. The Shopify Help Centre documentation covers the full Markets setup. Total configuration time for a 4-market launch (DE/FR/IT/ES) is roughly 3-4 hours if you have your VAT registrations and EPR compliance in hand. Coordinate with EPR registration before launch — Germany requires LUCID number activation before you can ship.

Layer 3: product imagery and metadata

Shopify's translation apps handle text. They do not translate imagery, video subtitles, or locale-specific product specifications. For DTC brands competing in German and French markets, product imagery often needs language-specific assets.

The mechanism varies by product category. For fashion and lifestyle brands, model imagery is often kept consistent across markets — same hero shots work globally. For supplement and food brands, regulatory disclaimers must appear in-language on the packaging shots, which means locale-specific imagery sets. For technical products (electronics, beauty devices), product spec callouts on imagery need translation, which means duplicated image assets per language. Shopify's Files section supports unlimited file uploads, but linking the right asset to the right language version is manual work in the Translate & Adapt panel. Alt text translates automatically through Translate & Adapt; image filenames do not. Filename localisation is a small SEO factor (5-10% impact on image search) but matters for product discovery in German and French. We typically allocate 4-6 hours per language for imagery audit and asset upload during a managed migration. For Amazon FBA EU sellers, coordinate this with your A+ content imagery to maintain brand consistency across the website and Amazon listings. Read our Amazon FBA Germany website guide for the cross-channel imagery checklist.

Layer 4: hreflang and SEO infrastructure

Hreflang tags are mandatory for multilingual Shopify stores. Without them, Google flags translated pages as duplicate content of the source URL, drops them from index, and your German store stays invisible on Google.de.

Online Store 2.0 themes (Dawn and forks) generate hreflang automatically when Shopify Markets is configured per language. Legacy themes (Debut, Brooklyn, anything pre-2021) do not — and roughly 40% of mid-tier Shopify stores still run legacy themes. The fix on legacy themes is manual hreflang injection via theme.liquid edits, which is engineering work most brands cannot do in-house. The other SEO requirement is multi-locale sitemap.xml generation: Shopify auto-generates one if Markets is configured correctly on Online Store 2.0, but you still need to submit it to Search Console manually for each region. Geo-targeting per language gets set in Search Console under International Targeting. Search engine guidance from searchengineland.com and Google's own Search Central documentation treat this as the canonical setup pattern. Skipping any of these steps degrades ranking signal across non-English locales. Read our duplicate content multilingual guide for the full audit checklist.

How Eldris Website handles Shopify multilingual

Our managed Shopify migration replaces the auto-translate layer with DeepL plus native human review, configures Markets correctly across all target locales, ships hreflang on day one, and delivers in 10 working days at the Growth tier.

The full process at Eldris Website covers all four layers in a single 10-day sprint. We keep your existing Shopify plan and theme (or upgrade to Dawn 14+ if you are running a legacy theme — included in the activation), then layer in DeepL-grade translation with native review across all product pages, collection pages, navigation, and the top 25 blog posts. Markets gets configured for DE/FR/IT/ES with correct VAT, currency, and payment routing. Hreflang ships across every translated URL with reciprocal tags. The multi-locale sitemap.xml gets submitted to Search Console with geo-targeting per language. The Growth tier lands at £997 activation plus £149/month, with the 4-language bundle adding 15% activation discount — total year-one investment of roughly £4,425 all-in for a 25-page Shopify migration with 4 languages. For Amazon FBA EU sellers we coordinate with EU EPR registration so packaging compliance and German VAT activation hit the same week as the website launch. Book a Shopify migration call for a category-specific quote.

Frequently asked questions

How do I translate a Shopify store?

The complete process covers four layers: storefront copy via Shopify Translate & Adapt or a managed translation pipeline, checkout localisation via Shopify Markets, product imagery and metadata via manual asset management, and SEO infrastructure (hreflang, sitemap, geo-targeting) via theme configuration. Skipping any layer breaks the deployment. The fastest viable route is a managed migration that handles all four layers in 10 working days. The cheapest free route uses Shopify Translate & Adapt for 2 languages plus manual hreflang verification — works for prototype launches, struggles in production for serious DTC brands.

Is Shopify Translate and Adapt enough for a DTC brand?

For prototype launches and brands testing demand in a new market, yes. For production launches in competitive German, French, or Italian markets, no. The free tier ships unedited Google Translate output, which conversion benchmarks consistently show underperforms native-reviewed copy by 20-30%. The paid tier improves on this with manual override controls and DeepL engine access, but still lacks glossary management. Most serious DTC brands replace the auto-translation layer with managed pipelines that include native human review on every page. Read our Shopify Translate Adapt analysis for the full breakdown.

How much does it cost to translate a Shopify store?

Costs range from £0 to £15,000 depending on route. The free DIY path uses Shopify Translate & Adapt for 2 languages plus 60-90 hours of internal native review per language. The mid-tier path uses Weglot or similar third-party apps at £29-499/month with optional human review services at £0.05-0.15 per word. The managed path runs £997 activation plus £149/month at our Growth tier for 4 languages with full native review, hreflang infrastructure, and 10-day delivery. For Amazon FBA EU launches, the managed path typically pays back in 6-9 months on conversion uplift alone.

What about Shopify Markets vs Shopify Markets Pro?

Shopify Markets is included free with most Shopify plans and handles standard cross-border ecommerce: currency conversion, regional payment methods, tax calculation, shipping zones. Markets Pro is a paid upgrade ($59/month minimum) that adds Merchant of Record functionality, automated VAT and duties calculation, fraud protection, and chargeback handling for cross-border sales. Most DTC brands selling on Amazon FBA EU use standard Markets because they handle their own VAT registration. Markets Pro makes sense for brands wanting Shopify to act as the legal seller of record across markets.

Do I need separate Shopify accounts for each country?

No. One Shopify store with Markets configured for multiple regions handles 90% of international ecommerce scenarios. Each region gets its own URL slug (e.g., /de/, /fr/), local currency display, regional payment methods, and tax calculation, all from the same Shopify backend. Separate Shopify accounts only make sense if you have legally distinct entities operating in each country with different VAT registrations, banking, and inventory systems — which is rare for DTC brands. The single-store-with-Markets approach is meaningfully cheaper to operate and easier to maintain. Read our separate domains translated websites guide for the URL architecture decision.

How long does a Shopify multilingual launch actually take?

Managed migration timeline: 10 working days from kickoff to live across all 4 target languages, including DeepL engine setup, native review of every product page and collection page, Markets configuration for DE/FR/IT/ES, hreflang implementation, sitemap submission, and Search Console geo-targeting. DIY timeline using Shopify Translate & Adapt with internal native review: 60-90 hours per language plus 4-6 weeks of project management and QA. For Amazon FBA EU launches, coordinate the website timeline with EPR registration and German VAT activation — both can run concurrently in 4-6 weeks. Read our ecommerce website translation guide for the full project plan template.