How to create a multilingual WooCommerce store

Choose the languages, default language and URL structure before you create translations. Decide whether every language will sell the same catalogue, and whether prices, currencies, tax rules or shipping methods differ by market. A language switcher does not automatically translate product copy or convert currencies.

Translate your key pages first: the shop, cart, checkout, my account, contact, returns and privacy pages. Keep a glossary for product names, attributes and recurring checkout terms so translations stay consistent.

Create a database and file backup, then do the setup on staging if the shop already receives orders. Multilingual plugins add translated records and relationships to your content, so testing on the live shop can leave partial translations or broken links if an installation fails.

Check that your theme and important WooCommerce extensions are translation-ready. Test product pages, variation selectors, cart fragments, checkout and transactional emails after each major change.

WooCommerce alone cannot maintain a connected set of translated products, categories, menus, checkout fields and customer emails. The manual alternative is to run separate WordPress stores or a multisite setup, duplicate the catalogue, translate each copy and maintain stock, prices, links and orders yourself.

This can work for a very small catalogue or genuinely separate regional stores, but it has no simple shared translation relationship and creates more opportunities for mismatched stock, outdated prices and incomplete checkout text. For one store with several languages, a multilingual WooCommerce plugin is the practical route.

Install a multilingual WordPress plugin and its WooCommerce integration. Add every language, set the default language and choose whether language codes appear in the URL, subdomain or domain. Complete the setup before translating products, because changing the default language or URL format later can create redirects and indexing problems.

Assign a language to existing products, categories, tags and attributes. Unassigned catalogue items may not appear correctly on the front end. Translate global attributes and their terms before building translated variable products, otherwise variation selectors can point to the wrong terms.

Open each product and create its translation from the language controls in the product editor. Translate the product name, description, short description, categories, tags, attributes and variation labels. Translate product categories, tags and global attribute terms separately, then check that each translated product is connected to the correct original.

Do not assume that every field should be translated. Prices, SKUs, stock, dimensions and shipping data may be shared or synchronised by the integration, while product copy and taxonomy names need language-specific versions. Confirm how your chosen plugin handles these fields before bulk editing.

Translate pages, menus, widgets and the language switcher. Create a menu for each language, assign it to the correct theme location and add the switcher so visitors can move between translated versions. If a translated page does not exist, the switcher may send visitors to the language home page instead of the equivalent page.

Translate WooCommerce settings such as shipping method names, payment instructions, tax labels, checkout text and customer emails. Some checkout strings are stored in WooCommerce settings rather than normal page content, so changing the WordPress site language will not automatically translate them.

Test the shop in every language using a private browser window. Check category archives, search, filters, product variations, add to cart, cart, checkout, account pages, order confirmation and customer emails. Place a test order in each language and verify that the order and email use the language selected at checkout.

Clear page, object and browser caches before retesting. A cached page can show the wrong language or preserve a previous language selection. Also check translated URLs, canonical links, language switcher links and any product feeds before sending traffic to the new versions.

For an online store, Polylang for WooCommerce is the focused shortcut. It adds WooCommerce-aware translation for products, categories, tags, attributes, emails and store settings, while working with Polylang’s language and menu controls. You still need to provide or review the translations, but you avoid maintaining disconnected product copies by hand.

Use it when one WooCommerce store needs several languages and shared catalogue data. Before installing it on a live shop, confirm the supported WordPress, WooCommerce and Polylang versions, back up the site and check compatibility with payment, shipping, product-bundle and page-builder extensions.