---
title: "Ecommerce translation: what to translate first in a shop"
description: "What ecommerce translation covers, in order: the pages that sell, the checkout text shops forget, prices that must not change, and a routine for updates."
url: "https://www.langrelay.com/blog/ecommerce-translation"
---

1. [Home](https://www.langrelay.com/)
2. [Blog](https://www.langrelay.com/blog)
3. Ecommerce translation: what a shop needs translated, and in what order

Article

# Ecommerce translation: what a shop needs translated, and in what order

What ecommerce translation covers, in order: the pages that sell, the checkout text shops forget, prices that must not change, and a routine for updates.

[Chris Jayden](https://www.langrelay.com/about)

Founder

Published

10 November 2026

Updated

13 November 2026

Reading time

9 min read

![A small corner shop on a quiet harbour street at dawn, parcels stacked by its open door and a delivery drone resting above the striped awning.](https://www.langrelay.com/_emdash/api/media/file/01M72BK9Y772FDYZ6H0WJ4KT8W.webp)

On this page

1. What ecommerce translation covers
2. Start with the pages that sell: product, category, shipping and returns
3. The parts shops forget: cart, checkout, emails and notices
4. Check the translation in the shop, not in a spreadsheet
5. Prices, units and numbers that must not change in translation
6. Product search, structured data and translated pages in Google
7. How much does it cost to translate an ecommerce website?
8. Keeping a catalogue translated as it changes
9. Common questions
10. Should I translate the whole catalogue at once?
11. Can customer reviews stay in their original language?
12. Can shoppers just use their browser's translate button?
13. Do I need a separate shop for each country?
14. Which language should I add first?

Ecommerce translation means putting everything a shopper reads on the way to a purchase into their language: product and category pages, shipping and returns, the cart, checkout, emails and the product data you send to Google. Do it in that order, starting with what sells, and plan for how translations stay current as products and prices change.

Language affects whether people buy at all. In a 2020 survey of 8,709 online shoppers in 29 countries, [CSA Research](https://csa-research.com/l/media/Consumers-Prefer-their-Own-Language) found that 76 percent prefer to buy products with information in their own language, and 40 percent will never buy from websites in other languages.

## What ecommerce translation covers

A shop holds far more text than its pages show. Translate only the pages you wrote and a shopper meets their own language on the product page, then yours again in the cart.

| Layer | Examples | Where it usually comes from |
| --- | --- | --- |
| Pages | Home, about, shipping, returns, FAQ | You |
| Catalogue | Product titles, descriptions, attributes, variant names, category names | You, or a supplier feed |
| Shop interface | Add to cart, out of stock, coupon errors, checkout labels | The shop software or theme |
| Messages | Order confirmation, shipping notice, refund, password reset | The shop software, edited by you |
| Data around the page | Page titles, meta descriptions, image alt text, the product feed | You, or generated from the catalogue |

Ecommerce localization goes a step further and adapts currency, units, sizes and payment methods to the market. The [website localization guide](https://www.langrelay.com/guides/website-localization) covers that wider work; this article stays with the text.

## Start with the pages that sell: product, category, shipping and returns

You do not need the whole catalogue in a new language on day one. You need the path a buyer takes to your likeliest sales, in this order:

1. **Your best sellers and their categories.** Sort a sales report by revenue and translate the top products and the category pages that lead to them.
2. **Shipping, delivery and returns.** A buyer abroad wants the cost, the delivery time and the way to send something back before they add anything to the cart.
3. **Size guides, care instructions, safety notes and warranty text.** A mistake here leads to returns and complaints. Product safety and labelling rules in some markets also say which language this information must be in, so check the rules of each country you sell into.
4. **The home page and the main menu.** They come fourth because a shopper from search often lands on a product page first.
5. **The rest of the catalogue, then the blog and the about page.**

Before the first product goes out, write down how you translate the words that repeat on every page: product line names, materials, size names, and your brand terms. A short [translation glossary](https://www.langrelay.com/blog/translation-glossary) keeps "linen blend" from becoming three different phrases across a hundred product pages. Check the words buyers search for in that market too: a literal translation is not always what people type.

![A shop owner holds a sales report and lifts a folded shirt from a stocked shelf into a box of the first products to translate.](https://www.langrelay.com/_emdash/api/media/file/01M7AM303KQDKP40ARSMXYQBJK.webp)

## The parts shops forget: cart, checkout, emails and notices

Much of the text a shopper sees after "Add to cart" sits in the shop software, the theme or an extension, and much of it appears only after a click. A translator working from an export of your pages never sees it. Google's own Merchant Center help, as of November 2026, lists translating "landing pages and checkout flow" as part of fully localizing a shop for another country ([Supported languages and currencies](https://support.google.com/merchants/answer/160637)).

Go through this list in each language:

- **Cart:** the added to cart message, quantity and remove labels, the coupon field and its errors, the empty cart text, the shipping estimate.
- **Checkout:** field labels, address fields (the order of fields and the postcode format differ between countries), required field errors, payment method names, the terms checkbox, the order button.
- **Account:** sign in, password reset, order history, saved addresses.
- **Emails:** order confirmation, payment received, shipped, delivered, refund issued, and any reminder about a forgotten cart.
- **Notices:** the cookie banner, sale banners, a free shipping bar, low stock messages, newsletter pop ups.
- **Documents:** invoices, packing slips and return labels.

To find what is missing, place a test order in each language, from the product page to the last email, and note every line in the wrong language. Some interface text is built in the browser after the page loads, so check a live page. If your shop runs on WooCommerce, the [guide to translating a WooCommerce store](https://www.langrelay.com/guides/translate-woocommerce-store) goes through these parts screen by screen.

![At a packing table, a shop owner reads the packing slip from an opened test parcel and ticks items on a paper checklist beside a phone.](https://www.langrelay.com/_emdash/api/media/file/01M7AM312QC2XC17S22T1VBX3R.webp)

## Check the translation in the shop, not in a spreadsheet

A translation that reads well in a file can still break the page it goes into. Short labels grow the most: the W3C, citing IBM's design guidelines, gives an average expansion from English into European languages of 200 to 300 percent for text of up to 10 characters. "Add to cart" is 11 characters; the German "In den Warenkorb" is 16.

Open each kind of page in the new language, on a phone and on a computer, and look at:

- Buttons and badges: add to cart, buy now, sale and sold out labels that wrap, overlap or get cut off.
- Filters and variant pickers: size, colour and material names in drop downs and swatches, which often have little room.
- Product images and banners: words inside an image stay in the original language until you make a second version of the image.
- Size charts and spec tables: columns that no longer fit once the headings are translated.

When a label does not fit, widen the button or let it wrap onto a second line. A label cut short to fit usually reads worse in the shopper's language than a slightly larger button.

## Prices, units and numbers that must not change in translation

A translation may change how a number is written. It must never change its value. The same number is written differently from one language to the next: the [MDN reference for number formatting](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat) shows 123456.789 as `123.456,79 €` in German with euros and `￥123,457` in Japanese yen, which has no minor unit. In German notation, "1.299" reads as one thousand two hundred and ninety nine. In English it reads as just over one.

| Can change in translation | Must stay the same |
| --- | --- |
| Decimal and thousands separators | The price and the sale price |
| Where the currency symbol sits | Discount percentages and coupon values |
| Date order (day before month) | Sizes, weights and dimensions |
| Words around a number ("in 3 to 5 days") | Delivery times and return windows |
|  | Model numbers, SKUs, phone numbers |

Three habits keep numbers safe:

- **Let the shop print prices.** Store each price once as a number and let the shop format it per language. A price typed into a banner ("free shipping over 50") is text, and can be mistranslated or left behind when the offer changes.
- **Make unit and currency changes in the source data.** Centimetres instead of inches, or another currency, is a product decision, never a translation one.
- **Compare the numbers after every translation.** Pull the digits out of both texts. Any difference beyond formatting is a mistake to fix before the page goes live.

## Product search, structured data and translated pages in Google

As of November 2026, Google's guide to [multi-regional and multilingual sites](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites) recommends a different URL for each language version rather than cookies or browser settings, and advises against redirecting visitors automatically by the language their browser or location suggests. A subfolder per language is the simplest pattern:

```
https://example.com/products/linen-shirt/
https://example.com/de/produkte/leinenhemd/
```

Each product page then names its other language versions with hreflang. Google's [localized versions guide](https://developers.google.com/search/docs/specialty/international/localized-versions) says each version must list itself and all the others, and the tags are ignored when two pages do not point to each other.

```
<link rel="alternate" hreflang="en" href="https://example.com/products/linen-shirt/" />
<link rel="alternate" hreflang="de" href="https://example.com/de/produkte/leinenhemd/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/products/linen-shirt/" />
```

The same guide says Google does not use hreflang or the HTML lang attribute to detect a page's language. It reads the content. A product page with a translated menu and an untranslated description is, to Google, a page in the original language.

Two more places carry your product text:

- **Product structured data.** The markup on a translated page should carry the translated name and description. Google's [merchant listing documentation](https://developers.google.com/search/docs/appearance/structured-data/merchant-listing) asks for the currency as a three letter ISO 4217 code in `priceCurrency` (EUR, GBP, JPY), a distinct URL for each currency you sell in, and shipping costs in the same currency as the offer. Its [product snippet guide](https://developers.google.com/search/docs/appearance/structured-data/product) adds that sending both page markup and a Merchant Center feed helps Google understand and check your data.
- **The product feed.** Merchant Center expects your landing pages to be in the same language as the product data you submit, and warns that products may be disapproved when most of the data does not match the language you declared for it.

If you plan to use machine translation for the catalogue, read [what Google says about machine translation and SEO](https://www.langrelay.com/blog/does-machine-translation-hurt-seo) before you publish thousands of pages at once.

## How much does it cost to translate an ecommerce website?

The cost depends on how many words the shop holds, how many languages you add, how the words are translated, and how often the catalogue changes. Count the words in the layers from the table above; interface text and emails are small but easy to leave out of a quote.

You can mix methods: a professional translator for the best sellers, the checkout and the legal pages, and machine translation with a review for the rest of the catalogue. The guide to [machine versus human translation](https://www.langrelay.com/blog/machine-vs-human-translation) helps you decide which text goes where, and the article on [what website translation costs](https://www.langrelay.com/blog/website-translation-cost) explains the pricing models with worked examples. For a shop, the running cost matters as much as the launch, since every new product and sale banner is new text in every language.

## Keeping a catalogue translated as it changes

A shop fully translated in spring can be half translated by autumn. A new product goes live in one language only, or a returns window changes on the English page and stays the same on the Spanish one, and the shopper reads an old promise.

Build a routine around the changes a shop makes:

| When | What to translate or check |
| --- | --- |
| A product is added | Its title, description, attributes and images' alt text, before or on the day it goes live |
| A description or spec changes | The same fields in every language, then the numbers |
| A price changes | Any text that repeats the price, such as banners and descriptions |
| A sale or campaign starts | Banners, coupon text and emails, before the start date |
| A sale ends | Remove its text in every language, not only the original |
| A product is retired | Remove or redirect it in every language |
| Once a month | A test order per language, Merchant Center errors, a few pages read in full |

Keep one list of what changed and when, even a spreadsheet filled from your shop's last edited dates. Each week, ask which source pages changed after their translations did, and fix those first.

![In a shop with two identical shelves side by side, a worker updates a price tag on one shelf to match the same product on the other.](https://www.langrelay.com/_emdash/api/media/file/01M7AM320429TVFFQAB7X65AH3.webp)

## Common questions

### Should I translate the whole catalogue at once?

Not at the start. Translate the products that sell and the pages around them, then add the rest in batches, so the part you have translated is complete.

### Can customer reviews stay in their original language?

Yes. Showing reviews as they were written keeps them in the customer's own words. If you translate them, say so next to each review.

### Can shoppers just use their browser's translate button?

They can, but it does not replace a translated shop. The translation exists only in that visitor's browser, so there is no page in that language for search engines to find, and you cannot check what it says about prices, sizes or returns. Your emails and invoices stay untranslated too. The article on [how accurate Google Translate is](https://www.langrelay.com/blog/is-google-translate-accurate) shows where automatic translation goes wrong.

### Do I need a separate shop for each country?

Not for language alone. One shop with a version per language is easier to keep current. A separate setup starts to make sense when prices, stock, tax or legal terms differ by country.

### Which language should I add first?

Look at the orders and traffic you already get. Your analytics show visitors' languages, and your order history shows where people already buy despite the language barrier. The article on [building a localization strategy](https://www.langrelay.com/blog/localization-strategy) turns that evidence into a one page plan. If you add just one language, the guide to [setting up a bilingual website](https://www.langrelay.com/blog/bilingual-website) covers the URLs, the switcher and the routine for keeping both versions matching.

## Sources

The pages this one cites, with the day each was read.

1. 01[Consumers Prefer their Own Language (CSA Research, July 2020)](https://csa-research.com/l/media/Consumers-Prefer-their-Own-Language)csa-research.com, checked 13 November 2026
2. 02[Supported languages and currencies (Google Merchant Center Help)](https://support.google.com/merchants/answer/160637)support.google.com, checked 13 November 2026
3. 03[Managing multi-regional and multilingual sites (Google Search Central)](https://developers.google.com/search/docs/specialty/international/managing-multi-regional-sites)developers.google.com, checked 13 November 2026
4. 04[Tell Google about localized versions of your page (Google Search Central)](https://developers.google.com/search/docs/specialty/international/localized-versions)developers.google.com, checked 13 November 2026
5. 05[Merchant listing structured data (Google Search Central)](https://developers.google.com/search/docs/appearance/structured-data/merchant-listing)developers.google.com, checked 13 November 2026
6. 06[Product snippet structured data (Google Search Central)](https://developers.google.com/search/docs/appearance/structured-data/product)developers.google.com, checked 13 November 2026
7. 07[Intl.NumberFormat (MDN Web Docs)](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/NumberFormat)developer.mozilla.org, checked 13 November 2026
8. 08[Text size in translation (W3C Internationalization)](https://www.w3.org/International/articles/article-text-size)w3.org, checked 13 November 2026

[Chris Jayden](https://www.langrelay.com/about)

Founder, LangRelay

Chris Jayden is the founder of LangRelay. Chris has worked on websites of every size, from large e-commerce stores to small sites with a handful of pages, and started LangRelay after years of translating them the hard way.

On this page

1. What ecommerce translation covers
2. Start with the pages that sell: product, category, shipping and returns
3. The parts shops forget: cart, checkout, emails and notices
4. Check the translation in the shop, not in a spreadsheet
5. Prices, units and numbers that must not change in translation
6. Product search, structured data and translated pages in Google
7. How much does it cost to translate an ecommerce website?
8. Keeping a catalogue translated as it changes
9. Common questions
10. Should I translate the whole catalogue at once?
11. Can customer reviews stay in their original language?
12. Can shoppers just use their browser's translate button?
13. Do I need a separate shop for each country?
14. Which language should I add first?

Share

- [Share on LinkedIn (opens in a new tab)](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.langrelay.com%2Fblog%2Fecommerce-translation)
- [Share on X (opens in a new tab)](https://x.com/intent/post?url=https%3A%2F%2Fwww.langrelay.com%2Fblog%2Fecommerce-translation&amp;text=Ecommerce%20translation%3A%20what%20a%20shop%20needs%20translated%2C%20and%20in%20what%20order)

See it on your site

A 30-minute walkthrough on one of your pages.

[Book a demo](https://www.langrelay.com/book-a-demo)

## Keep reading

- Article
  ### [How much does it cost to translate a website in 2026?](https://www.langrelay.com/blog/website-translation-cost)
  Website translation cost is words times languages times rate, plus what changes each month. Worked prices for a 20,000-word site, by human and by software.
- Article
  ### [Machine vs human translation for websites: how to choose](https://www.langrelay.com/blog/machine-vs-human-translation)
  Choose machine or human translation per page, not per site. Content types, dated per-word rates, a cost model for a 20,000-word site, and where approval fits.
- Article
  ### [Does machine translation hurt SEO? What Google says](https://www.langrelay.com/blog/does-machine-translation-hurt-seo)
  Google's policies don't ban machine translation. They target pages made at scale with little value. What that means for your site, and where review fits.
- Article
  ### [Translation QA checklist for websites, stage by stage](https://www.langrelay.com/blog/website-translation-qa-checklist)
  A translation QA checklist for websites: what counts as an error, how severe it is, and what to check in the text, on the page and on the live site.
- Article
  ### [SEO localization: what to change on each translated page](https://www.langrelay.com/blog/seo-localization)
  SEO localization adapts what search engines read on a translated page: title, meta description, slug, alt text, structured data and social tags, field by field.

Book a demo

## See LangRelay on your own site

Book 30 minutes with the team. We translate one of your pages live and walk through review, publishing and multilingual SEO.

[Book a demo](https://www.langrelay.com/book-a-demo)[See pricing](https://www.langrelay.com/pricing)
