Translate WooCommerce Products: A Complete Multilingual Store Guide

To translate WooCommerce products properly you need more than product descriptions: variations, categories, cart and checkout pages, order emails and SEO fields all have to be complete in every language, and prices should appear in a currency that suits the target market. The most common mistake is translating the product pages but leaving checkout and emails in the original language, which costs trust at exactly the moment of purchase. This guide covers what to translate in a store, decisions on currency and tax, the SEO foundations and a step-by-step setup.

What needs translating in a store?

• Products: title, long and short descriptions, attributes such as colour or size, and variation names.
• Categories and tags: both their names and their URL slugs.
• Cart and checkout: buttons, form fields, error messages, shipping and payment method names. Much of this text comes from the theme and plugins and needs string translation.
• Order emails: order confirmation, shipping notifications and invoices should go out in the language the customer shopped in.
• Legal pages: returns policy, terms of sale and privacy policy; have an expert check them after translation.
• SEO fields and image alt text: titles, descriptions and alternative text for images.

Separate products or shared stock?

Localise product copy, don't just translate it

Translating product text word for word is rarely enough. Units (centimetres and inches, kilograms and pounds), size charts (EU, US and UK sizes differ), voltage and plug type for electrical goods, and ingredient information for food and cosmetics all need thinking about per market. These details are often what decides a purchase, and a wrong size chart drives returns straight up. Product and category names should also follow local search habits, since the same item can be searched under a different name in another country, so a quick keyword check for best-sellers in each language pays off.

Separate products or shared stock?

With plugins that use the separate-content model, each language version of a product is technically its own record. Keeping stock, price and SKU in sync across languages is then critical; otherwise a product that sells out in one language may still be on sale in another. When choosing a plugin, test how stock and prices are synchronised and how translations update when you add a new variation. We explain the plugins' content models in our WPML vs Polylang comparison.

Currency: display or charge?

There are two separate decisions here: showing prices in the customer's currency, and actually charging in that currency. Automatic conversion at live rates is the easy way to keep prices current in every language; the Pro plan of our own AYM Multilingual plugin converts WooCommerce prices automatically at live rates. To charge in a currency, though, your payment gateway has to support it. In markets with volatile exchange rates, prices that change every day can put customers off, so rounded fixed prices for best-selling products are another option.

Some businesses deliberately list prices in a single currency. The plans for our sports-venue software Multi Score Screen, for example, are offered worldwide in US dollars, a common and transparent approach in international B2B software. For consumer stores selling physical goods, a local currency usually converts better.

Tax, shipping and local payment habits

Adding a language often means entering a new market, which means revisiting tax and shipping. VAT rates, invoicing rules and customs procedures vary by country, so work with your accountant. Define shipping zones and delivery times per market and state the delivery time clearly on product pages. Payment methods differ too: cards dominate in one country, bank transfers or local wallets in another.

SEO foundations: hreflang for product pages

Each product page needs its own URL per language, a translated slug and hreflang tags pointing to its equivalents in the other languages. The price and currency in the product's structured data must match the price shown on the page. The same rules apply to category pages and filtered results; keep the large number of URLs created by filters from being indexed uncontrolled. After translation, check the source of a few product pages in each language to confirm hreflang and canonical tags.

Performance as languages grow

Every new language adds pages and database records. Make sure your caching plugin keeps a separate cache per language and that language selection works on cached pages; cart and checkout pages should never be cached. We cover the general ways to speed up a store in our WooCommerce speed and conversion guide.

Step-by-step setup

1. Decide target markets, languages and currencies.
2. Install the multilingual plugin and set the URL structure (for example /en/, /de/).
3. Translate products, attributes, categories and slugs; fix brand and product names in a glossary.
4. Translate theme and plugin strings, cart and checkout steps.
5. Test order emails in every language with test orders to confirm the customer receives them in the right language.
6. Configure currency, tax and shipping, and check that the payment gateway supports the currency.
7. Check hreflang, canonical tags and the sitemap, then submit it in Search Console.

Common mistakes

• Leaving checkout in the original language: the customer meets a foreign language at the moment of paying and may abandon the cart.
• Forgetting emails: an order confirmation in a different language undermines trust and creates support questions.
• Not checking currency conversion: without rounding and update-frequency settings, prices can show odd figures.
• Skipping text in images: banners and campaign images need a version per language too.

If you would like professional help opening your store to new markets, see our WooCommerce solutions, and compare plugin plans on our pricing page.

Share:XLinkedInWhatsApp