WPML, Polylang or TranslatePress for a Multilingual WooCommerce Shop
Short answer: WPML is the most complete option for a shop with many products, variations, multiple currencies and translated emails, because its free WooCommerce Multilingual add-on covers almost every store detail, though it is paid and the heaviest of the three. Polylang is lighter and its core is free, but proper WooCommerce support needs its paid WooCommerce add-on and there is no built-in currency switching. TranslatePress lets you translate visually on the live page and keeps one product per item instead of copies, which suits smaller catalogues and non-technical editors. Choose carefully, because moving between them later is painful.
Two different ways of storing translations
Understanding this one difference explains most of the trade-offs.
- Separate posts per language (WPML, Polylang). A French product is its own WordPress post, linked to the English original. Stock, SKU and price are kept in sync by the plugin, but there are two product records in the database.
- One post, translated strings (TranslatePress). The product exists once. The plugin stores translations of each piece of text in its own tables and swaps them in when a visitor views the French version.
Separate posts give fine control, such as a different image for one language, but double the content in the database. Translated strings keep things lean but make language-specific differences harder.
Comparison table
| Area | WPML | Polylang | TranslatePress |
|---|---|---|---|
| Data model | Separate posts | Separate posts | One post, string tables |
| WooCommerce support | Free WooCommerce Multilingual add-on with paid WPML | Paid Polylang for WooCommerce add-on | Included in free version |
| Products and variations | Full, synced stock | Full, synced stock with add-on | Translated on page; variations handled as strings |
| Theme and plugin strings | String Translation module | Built-in strings panel | Translated visually on the page |
| Transactional emails | Sent in customer's language | Supported with add-on | Supported, check settings |
| Multiple currencies | Built into WooCommerce Multilingual | Needs a separate plugin | Needs a separate plugin |
| Translated URL slugs | Yes | Yes | Paid add-on |
| Automatic translation | Credit-based service | Via paid add-on or integrations | Google or DeepL, some features paid |
| Licence model | Annual, paid | Core free, add-ons paid | Core free, add-ons paid |
Plugin features and pricing change, so confirm the current details on each vendor's page. The WPML WooCommerce Multilingual documentation is a good place to see the full list of store-specific settings it handles.
Editing workflow
Think about who updates products week to week.
WPML opens a translation editor for each product, with fields lined up side by side. You can assign translation jobs to translators with their own logins, which works well when an outside translator handles the second language.
Polylang uses the normal WordPress editor. You create the translation from a small language box in the sidebar, and the French product opens like any other product. Familiar, but you switch between editors a lot.
TranslatePress opens the live front end with a sidebar. You click a heading, button or product description and type the translation. Shop staff who are not comfortable in the admin area often find this the easiest. The catch is that content only visible in certain states, such as an error message on checkout, needs you to reach that state to translate it.
Performance
All three can run fast on good hosting with caching, but they load differently:
- WPML adds database queries and admin overhead, which is noticeable on cheap shared hosting with large catalogues.
- Polylang is generally lighter in the admin and on the front end.
- TranslatePress processes page output to swap in translations. With page caching, visitors rarely notice; uncached pages such as cart and checkout do a little more work.
For a store with a few hundred products, hosting quality and caching matter more than plugin choice. For thousands of products with many variations, test on a staging copy with real data before committing.
Currencies, taxes and payments
A second language often comes with a second market. WPML's WooCommerce add-on can show prices in multiple currencies and set prices per currency manually. With Polylang or TranslatePress you add a separate currency plugin. Whichever you choose, check that your payment gateway supports the currencies and that tax settings follow WooCommerce's rules for the countries you sell to. Tax treatment is not something a translation plugin decides; check with your accountant.
Migration risk if you switch later
Switching from one plugin to another is the most expensive mistake in this area:
- WPML to Polylang is possible because both use separate posts, and migration tools exist, but expect to check every product, variation and string afterwards.
- To or from TranslatePress means converting between data models. Translations stored as strings do not become separate posts automatically, and vice versa, so plan for substantial rework.
- URL changes during a switch can break search rankings unless every translated URL is redirected.
Pick the plugin that matches where the shop will be in three years, not only today.
A trial run before you commit
Set up a staging copy of the shop and install your preferred plugin there first. Translate five representative items: a simple product, a variable product with sizes and colours, a category page, the cart and the order confirmation email. Then place a test order in the second language and check that stock drops on the original product, the email arrives in the right language and the URLs look clean. An afternoon of testing like this reveals more than any feature list.
Which one to choose
- Larger catalogue, several currencies, external translators: WPML.
- Budget-conscious, comfortable in the WordPress editor, single currency: Polylang with its WooCommerce add-on.
- Smaller catalogue, staff who prefer visual editing, simple setup: TranslatePress.
FAQ
Can we use the free version of Polylang with WooCommerce?
Basic pages translate, but product sync, cart and checkout handling need the paid WooCommerce add-on.
Does TranslatePress translate product variations?
Variation names and attributes are translated as text on the page. Test variable products carefully after setup.
Which plugin is best for SEO?
All three create separate URLs per language and output hreflang tags. Translated slugs and proper metadata matter more than the plugin name.
Can we run two translation plugins together?
No. They conflict. Choose one and remove the other completely.
Tell us how many products, languages and currencies you have through our enquiry form, and we will recommend the plugin that fits.