Expanding a WooCommerce store beyond a single language market is one of the more reliable ways to grow revenue without spending a cent on new customer acquisition ads. Shoppers browse and buy more comfortably in their own language, and when product pages, checkout fields, and confirmation emails all speak that language, cart abandonment tends to drop. That is the entire premise behind WPML Multilingual & Multicurrency for WooCommerce, an add-on built specifically to bridge WooCommerce’s default single-language architecture with WPML’s translation engine.
The plugin is not new. It has been maintained for years under the WPML umbrella, and as of this writing the current release is version 5.5.7, with more than 100,000 active installations and testing confirmed up through WordPress 7.1. That kind of install base and update cadence matters, because a translation layer sitting between your storefront and your checkout is not somewhere you want to run outdated code.
Why Store Owners Bother Translating WooCommerce at All
Running a store in only one language works fine until your analytics show visitors arriving from Germany, Brazil, or Japan and bouncing before they add anything to a cart. A large share of that bounce is not about price or product fit. It is about friction: an unfamiliar checkout form, a currency they have to convert in their head, a shipping policy written in a language they only half understand. None of that friction is necessary once WooCommerce is properly localized.
Translating a store also changes how it performs in search. Google indexes translated pages as separate, language-specific URLs when they are set up correctly, which means a French product description can rank for French search terms independently of the English original. That is organic traffic you simply do not get from a single-language catalog, no matter how well the English copy is written.
What You Need Installed Before You Start
The multilingual WooCommerce stack has a few moving parts, and it helps to know what each one does before you start clicking Activate on things:
- WPML Multilingual & Multicurrency for WooCommerce - the connector plugin that teaches WooCommerce how to handle multiple languages and currencies.
- WPML (the core WordPress Multilingual Plugin) - handles the actual page, post, and menu translation across your site.
- WPML String Translation - translates the smaller text fragments that live in theme files and plugin settings, things like button labels and system notices.
- WooCommerce - your store framework. WPML’s WooCommerce add-on is built to sit directly on top of it.
One detail that trips people up: if all you want is multi-currency pricing, without full translation into other languages, the plugin can run in a standalone currency-switching mode. You do not need to buy the full WPML translation license just to let shoppers view prices in their local currency. That is a meaningfully cheaper path for stores that serve English-speaking markets across different countries but still want localized pricing.
Getting Your Store Ready Before You Translate Anything
Before touching a single product description, take stock of what actually needs translation. Products and categories are the obvious candidates, but attributes, variations, custom fields, and even your permalink structure all factor in. Decide early whether you want language-specific URLs (like /fr/produit/) or a subdomain/domain-per-language setup, because switching that decision later means redoing a lot of configuration work.
It also pays to check your theme’s translation readiness before you commit. Most modern WordPress themes are built with proper text domains and gettext functions, but older or heavily customized themes sometimes hardcode strings directly into template files, which WPML cannot reach through its normal string translation tools. A quick audit here saves a lot of frustration three steps into the process.
Step-by-Step: Installing and Configuring the Plugin
Step 1: Install the Plugin
Download WPML Multilingual & Multicurrency for WooCommerce from the official WordPress.org plugin directory, or search for it directly from your dashboard under Plugins → Add New. If you are installing a downloaded ZIP manually, go to Plugins → Add New → Upload Plugin, select the file, click Install Now, then Activate. Activation alone will not do anything visible yet; it just registers the plugin’s hooks into WooCommerce.
Step 2: Configure Your Languages
Once activated, a new WooCommerce Multilingual section appears in your dashboard. Here you set your default store language (the one your original content is written in), then add every additional language you plan to support. For each additional language you can choose manual translation, where a human translates every field by hand, or automatic translation, which uses machine translation as a starting draft that you then review and correct. Automatic translation is faster but should never be treated as production-ready without a human pass over pricing-sensitive or legally relevant text like shipping and refund policies.
Step 3: Translate Products
Go to WooCommerce → WooCommerce Multilingual → Products, select the product you want to localize, and translate the title, short description, long description, attributes, and any variations. Save each translation individually. For stores with large catalogs, this is the step that takes the longest, and it is worth prioritizing your best-selling or highest-margin products first rather than trying to translate the entire catalog in one sitting.
Step 4: Translate Categories and Tags
Open WooCommerce Multilingual → Categories and add a translation for every category and tag a shopper might use to navigate or filter your catalog. Skipping this step is a common mistake: a store can have beautifully translated product pages that are still impossible to browse to, because the category menu is still showing English labels to a French-speaking visitor.
Step 5: Localize the Checkout Flow
Head to WooCommerce Multilingual → String Translation and translate every field a customer sees during checkout: billing and shipping labels, the Place Order button, cart notices, shipping method names, and payment gateway instructions. This is arguably the highest-stakes translation work on the whole site, since a confusing checkout page is where sales are lost even after a customer has already decided to buy.
Step 6: Add a Language Switcher
Enable the built-in language switcher in the plugin settings and place it somewhere visible: the main navigation menu, the footer, or a sidebar widget. Visitors should never have to guess whether a translated version of your store exists. A switcher that is buried or missing entirely defeats a lot of the translation work you just did.
Step 7: Test Before You Announce Anything
Switch between every language your store supports and walk through a full purchase: browse a category, open a product, add it to the cart, and complete checkout with a test order. Confirm that confirmation emails, order notes, and any automated messages also render correctly in the selected language. This step catches the small stuff, an untranslated button here, a currency symbol mismatch there, before real customers run into it.
Multi-Currency Without Full Translation
If your priority is currency rather than language, the plugin’s standalone multi-currency mode lets you display prices in a shopper’s local currency based on their location or their own manual selection, while keeping your store content in a single language. Exchange rates can be set to update automatically or be managed manually if you prefer to control margin on currency conversion yourself. This is a common setup for stores selling into Canada, the UK, Australia, and the US simultaneously, where language is not the barrier but currency display is.
Translating Emails and Order Notifications
It is easy to translate the storefront and forget that a customer’s relationship with your brand continues well past the checkout button. Order confirmations, shipping updates, and any promotional emails triggered by WooCommerce all pull from the same string tables that power your site, so use WPML String Translation to localize the email templates themselves along with the dynamic content that gets inserted into them, like order numbers, item names, and shipping carrier names. A customer who checked out in Spanish and then receives an English shipping notification will notice, and it undercuts the localized experience you just built.
Also Read: How to Create and Send PDF Invoices & Packing Slips in WooCommerce
Translating Reviews and Other Customer-Generated Content
Product reviews are one of the strongest trust signals on any commerce site, and that trust does not transfer automatically across a language barrier. If your reviews only display in the language they were originally written in, an international shopper reading nothing but foreign-language reviews gets little value from them. WPML Multilingual & Multicurrency for WooCommerce lets you manage this in a few ways:
- Automatic language display: when a translation of a given review exists, it is shown to visitors browsing in that language.
- Manual review translation: use WPML String Translation to translate high-value reviews, testimonials, or product Q&A entries by hand for accuracy.
- Native-language submission: allow customers to leave new reviews in their own language rather than forcing everyone into a single review form.
None of this needs to be exhaustive. Translating your ten most-referenced reviews on a bestselling product does more for conversion than machine-translating every three-word review on a product nobody buys.
A Practical Testing Checklist
After the translation work is done, resist the urge to call it finished without a real walkthrough. Switch languages, add a product to the cart, and go through checkout exactly as a customer would. Watch specifically for three things: text that is still showing in the default language, layout that breaks because a translated string is longer than the original (German and Finnish are notorious for this), and currency figures that do not match what the customer expects to pay.
Practical Tips That Save Time Later
- Use automatic translation as a first draft, not a final answer. It is genuinely useful for saving time on bulk product descriptions, but review anything customer-facing before it goes live, especially pricing and policy language.
- Test checkout in every supported language, not just the two most common ones. Buttons, labels, and payment instructions are the fields most likely to get missed.
- Use WPML’s Advanced Translation Editor for side-by-side context. Translating a string in isolation, without seeing the sentence around it, produces more awkward phrasing than translating with the full paragraph visible.
- Treat SEO per language as its own project. Meta titles and descriptions should be written for the target language’s search behavior, not machine-translated from the English version.
- Track analytics by language segment. This tells you which translated markets are actually converting, which should guide where you invest further translation effort.
Common Problems and How to Fix Them
- Untranslated checkout buttons: almost always a missed string in WPML String Translation rather than a plugin bug. Search for the exact button text and translate it there.
- Slow store performance after adding multiple languages: caching, image optimization, and reasonably fast hosting matter more here than with a single-language store, since you are now serving more page variations. A good caching plugin configured to respect language-specific URLs solves most of this.
- Duplicate content warnings in SEO tools: confirm that
hreflangtags are present on every translated page. WPML sets these automatically in most configurations, but it is worth spot-checking with a tool like Google Search Console after launch. - Mismatched currency symbols: double check your multi-currency settings against your payment gateway’s supported currencies. Not every gateway supports every currency WPML can display, and a mismatch here causes failed transactions at the worst possible moment.
Where This Fits Against Alternatives
WPML is not the only way to run a multilingual WordPress store. TranslatePress and Weglot both offer WooCommerce-compatible translation with a more visual, front-end editing experience, which some store owners find faster to work in day to day. WPML’s advantage is depth: its String Translation and Advanced Translation Editor tools reach further into theme and plugin text than most competitors, which matters more the more customized your store’s checkout and account pages are. If your store runs a heavily modified theme or several commerce-adjacent plugins, that reach is usually worth the steeper learning curve.
Budgeting for a Multilingual Rollout
Cost is usually the first question a store owner asks, and it splits into two buckets: the plugin licenses and the translation labor itself. The plugin side is comparatively predictable, WPML’s core plugin and the WooCommerce add-on are sold as annual licenses with tiers based on how many sites you run them on. The translation labor is the variable that catches people off guard. Machine translation through the plugin’s automatic mode is effectively free beyond the license cost, but it is not something you want powering your checkout copy or refund policy without review.
Human translation, whether done in-house by a bilingual team member or outsourced to a professional translator, is priced per word in most markets, and a mid-sized catalog of a few hundred products can run into real money once you multiply per-word rates across every product description, attribute, and category. A common middle path is to machine-translate the full catalog for baseline coverage, then pay for human review on your top-selling products, your checkout flow, and any legally binding text like terms of service and shipping policies. That gets you full-site coverage without human-translation costs on every single SKU.
How Long a Realistic Rollout Takes
For a catalog under 50 products, a single person working through the seven-step process above can typically get a second language fully live, tested, and polished within a week of part-time effort. Larger catalogs scale roughly linearly with product count once the initial configuration (languages, currency settings, theme compatibility) is sorted out, since that setup work is a fixed cost regardless of catalog size. Stores adding a third or fourth language after the first one is live tend to move faster, because the checkout, email, and string translation workflows are already familiar and mostly just need repeating for the new language.
Frequently Asked Questions
Do I need the paid version of WPML to use this plugin?
Not necessarily. If you only need multi-currency display without full site translation, the plugin can run in a standalone mode. Full product, category, and checkout translation requires the core WPML plugin and, for smaller UI strings, WPML String Translation.
Will translating my store hurt my existing SEO rankings?
Done correctly, with proper hreflang tags and language-specific URLs, translation adds new ranking opportunities rather than diluting existing ones. The risk comes from doing it incorrectly, duplicate URLs without hreflang markup, or machine-translated text that reads poorly enough to hurt engagement metrics.
Can I translate only part of my store, like just the top-selling products?
Yes. WPML does not require an all-or-nothing approach. Many stores start with their best-selling category and expand from there once they see how the new language segment performs.
What happens to a product if I add a new language after the store has been live for years?
Existing products remain untranslated in the new language until you translate them, and the plugin will typically show either the default-language version or a machine-translated fallback until you do, depending on your configuration. Nothing breaks automatically when you add a language, but nothing translates itself either.
Does this work with mobile checkout the same way it does on desktop?
Yes, because the translation happens at the content and string level rather than in a separate mobile-specific template. As long as your theme is responsive, translated labels, prices, and checkout fields render the same way on a phone as they do on a laptop. It is still worth running your full testing checklist on an actual mobile device rather than assuming desktop testing covers it, since longer translated strings sometimes wrap or truncate differently on smaller screens.
Building a Store That Actually Serves Global Customers
A multilingual WooCommerce store is not a weekend project, but it is also not the multi-month undertaking it can feel like at the outset. With WPML Multilingual & Multicurrency for WooCommerce, the pieces, products, categories, checkout, emails, and reviews, all connect through the same translation system, so once you understand the workflow for one content type, the rest follow the same pattern. Add multi-currency pricing on top and your store is genuinely ready to serve customers who were never going to convert while everything was written in a language that was not theirs.
Interesting Reads
How to Use Advanced Product Fields to Add Custom Product Options in WooCommerce
How to Automatically Convert Product Prices to Local Currency in WooCommerce