Ecommerce Translation: Building a Multilingual Store

A multilingual online store lives or dies on the pages nobody thinks to translate first. Product titles get done; shipping policies, checkout error messages and tax disclosures often don't, and those are exactly the pages that make a shopper abandon a cart in an unfamiliar language. Here's what ecommerce translation actually needs to cover.

Product data: more than the description

Product listings have more moving parts than a single paragraph:

• Titles: keep them keyword-appropriate for the target market's search behavior, not a literal translation of the English title.
• Descriptions: accurate and persuasive, matching the tone of your brand rather than a stiff word-for-word rendering.
• Attributes and variants: size, color, material fields often live in structured data (CSV, XML feeds, PIM exports); translate the values, not just the visible page.
• Reviews and Q&A: optional, but stores that translate top reviews for new markets see better trust signals than an empty review section.

Feed-based catalogs (Shopify, Magento, PIM systems) should be exported as structured files so nothing gets missed or duplicated on import, the same principle as translating app string files rather than screenshots.

A practical detail that gets missed on large catalogs: keep a running glossary of product-line and brand names that should stay untranslated across every SKU. Without it, the same product line can end up rendered two or three different ways across a few thousand listings, which looks inconsistent even when each individual translation is accurate.

Currency and pricing are not the same decision

Displaying a price in the shopper's local currency is table stakes, but it raises two separate questions worth deciding upfront rather than leaving to whoever builds the checkout. First, do you charge a fixed local price per market, or convert your base price at the live exchange rate? Fixed local pricing is more predictable for the shopper and avoids prices that shift week to week, but it means someone owns updating those prices as exchange rates move. Second, how are taxes shown? Tax-inclusive pricing is the norm in the EU and UK, tax-exclusive is the norm in the US, and showing the wrong convention makes a price look wrong even when the math is correct. Neither of these is a translation decision by itself, but the checkout copy explaining the price needs to match whichever choice you make.

Checkout: where the money is actually made or lost

Checkout is the highest-stakes page on the entire site, and it needs full localization, not just translation:

• Currency displayed natively: a price shown in USD to a shopper paying in EUR creates hesitation at the worst possible moment.
• Payment methods labeled correctly: if you support iDEAL, SEPA, Alipay or Klarna, the checkout copy referencing them needs to be accurate in-language, not just the button.
• Form field labels and validation errors: "Invalid postal code" needs to reflect the actual postal format of the country selected, and every error message needs translation, not just the happy path.
• Shipping and returns policy: this is often the deciding factor for a first-time buyer in a new market, and it's frequently one of the last pages anyone thinks to translate.

Legal and tax pages

Terms of service, privacy policy, and any tax or customs disclosure need to be both linguistically accurate and aligned with what the receiving market actually requires. VAT display rules in the EU differ from sales tax display in the US, for instance. For anything with regulatory weight, confirm the exact requirement with your legal counsel or the relevant authority; a translator can render the text accurately, but shouldn't be your only compliance check.

Entering a new market: sequencing the work

Translating everything at once is expensive and usually unnecessary. A more practical sequence:

1. Checkout and legal pages first, since these carry the most risk and the most conversion impact per word.
2. Best-selling and category-page products next, covering the 20% of SKUs driving 80% of traffic before the long tail.
3. Full catalog and reviews last, extending once the market shows traction.

This lets you launch in a new language within weeks rather than waiting for a full-catalog translation to finish.

Customer service and post-purchase content

Once an order is placed, the shopper still interacts with your store through order confirmation emails, shipping notifications, and return-request forms. These get overlooked constantly because they're not on the storefront, but they're exactly the messages a customer reads most carefully, since they usually relate to money already spent. An order confirmation in English after a checkout completed entirely in French reads as a mistake, not a minor inconsistency, and it's one of the fastest ways to make a new market feel like an afterthought rather than a real launch.

If you run customer support in the new market, translating your top canned responses and help-center articles ahead of launch saves a support team from translating on the fly under time pressure once tickets start coming in.

Currency isn't localization by itself

Swapping a currency symbol without adjusting copy, tax display, and payment methods is a common half-measure. It looks localized at a glance but doesn't hold up at checkout, because shoppers notice when the price format, delivery estimate, or payment options don't match their market's norms.

We work with structured product feeds and can prioritize checkout and legal pages first if you're on a launch deadline. Check available language pairs for your target markets, and send us your product feed or CMS export through our localization service to get a fixed quote scoped to exactly what you need translated first.