← All posts // international

Multi-Language Product Listings: Should You Translate or Localise?

Published 2026-04-19 · scrb by vøiddo

The answer sellers want is 'just translate and I'll be fine.' The answer the data gives is 'translation is the minimum; localisation is where the money is.' Here's what each means, where the gap shows up in conversion, and how to decide what's worth the extra effort.

Try scrb free → Plans from $9.99/mo

Translation vs. localisation — the actual difference

When translation is enough

Low-consideration categories: cheap accessories, impulse buys, commodities where the buyer compares on price. Here, 'good enough' translation outcompetes 'no listing at all', and the marginal gain from full localisation is small.

When localisation wins

Practical workflow

For a multi-market catalogue: translate first, localise the winners. Start every listing with a quality translation. Monitor conversion per market. Localise the top 20% of products that account for 80% of revenue — that's where the extra effort pays off. Use generic translation for the long tail.

Common localisation mistakes

FAQ

Can I use Google Translate for product listings?

For a first draft, sure. For production, no — GT misses platform-specific trust signals, regulatory nuance, and tone. Use it to bootstrap, then either hire a native speaker or use a platform-aware AI tool.

How many languages should my Shopify store support?

Start with the top 3 markets that account for your traffic. Adding languages you don't have demand in just bloats SEO without adding revenue.

Does Amazon penalise translated listings?

No, but it reward listings written natively for each marketplace. An AU-specific listing often outranks a US-listing 'available in AU' even with the same translation.

Generate free →

Related reading