Setting up a multilingual WooCommerce store involves more than translating product descriptions. Customers also interact with Cart and Checkout pages, variation fields, reviews, emails, interface strings, currencies and language-specific URLs. If these elements are configured separately or tested incompletely, shoppers may encounter mixed-language messages or unexpected cart behavior.
A practical workflow is therefore staged: prepare the WPML components, define languages and URLs, translate the catalog, configure the purchase journey and currencies, then diagnose untranslated strings by their source. The exact component names and interface labels may depend on the current WPML version, account and licensing configuration. Before changing live settings, use a tested backup and, preferably, a staging environment.
What You Need Before Starting
The documented WPML model for multilingual WooCommerce combines WooCommerce with WPML core, WPML String Translation, WPML Media Translation and WPML Multilingual & Multicurrency for WooCommerce. These components address different parts of the store, so identify what your site actually uses before beginning.
Component checklist
- WooCommerce and WPML core: provide the foundation for the store and its language configuration.
- WPML String Translation: handles interface text generated by WooCommerce, the theme or extensions when those strings are available for translation.
- WPML Media Translation: supports the documented media-related translation workflow.
- WPML Multilingual & Multicurrency for WooCommerce: supports WooCommerce-specific translation and currency features.
These are the components identified in WPML’s documented setup model, not a statement that every store needs every feature in every configuration. Verify availability and current labels in your WPML dashboard.
Pre-configuration risk check
Create an inventory of active languages, products, variations, categories, tags, attributes, emails and reviews. Also list the theme, checkout customization, payment gateway and WooCommerce extensions in use. The reviewed documentation does not verify identical behavior for every integration.
Plan tests for shipping, taxes, payment, caching, analytics and third-party integrations. Keep credentials, payment keys and customer data out of screenshots and troubleshooting examples.
Choose Languages, URL Formats and the Language Switcher
Configure the active languages and default language before reviewing translated store pages. WPML documentation describes several URL approaches: language directories, separate domains or subdomains, and language parameters in URLs.
URL structure options
- Language directories: the language indication appears in the site path.
- Separate domains or subdomains: language routing uses a domain-based structure.
- Language parameters: the language indication is added as a parameter to the URL.
Choose according to the store’s domain setup, maintenance process and possible migration impact. The available formats should be treated as configuration options, not as a universal ranking or conversion solution. Review the current WPML dashboard before making a production decision.
Switcher and navigation checks
Configure the WooCommerce language switcher together with the selected URL format. Test it on product pages, Cart and Checkout pages, and confirm that each link leads to the corresponding translated page.
Repeat these checks with the active theme and custom templates. A switcher can appear correctly while a customized page still points to an untranslated or incorrect destination, so verify the complete navigation path rather than only the menu label.
Translate Products, Attributes and Variations
Use WPML’s WooCommerce translation workflow for product titles, full descriptions and short descriptions. Continue with categories, tags and attributes, then review product-specific media and the storefront presentation in each active language.
Catalog translation workflow
- Start with the product title, full description and short description.
- Translate the relevant categories, tags and attributes.
- Review product media and confirm that the translated product page presents the intended content.
- Open the product from the customer’s language and test the add-to-cart path.
WPML documentation describes translated WooCommerce products as separate products linked to their translations, with language-specific text fields and shared images described in the compatibility documentation. This model means translation work should be performed through the provided workflow rather than by manually managing database relationships.
Variation and product-page verification
Check attribute selection and variation-related content for every important variable product. Verify images, prices and stock for the relevant product, and make sure a customer can select the intended variation in each language.
Do not assume that translating a product also translates theme labels, extension messages or checkout strings. These belong to separate translation or configuration checks. Test the product page, selection process and add-to-cart action from the storefront instead of relying only on the editing interface.
Translate Cart, Checkout, Emails and Reviews
The documented setup process can create translated Cart and Checkout pages for each active language. Include these pages in the translation inventory together with WooCommerce emails and product reviews.
Purchase-flow content
Separate product content from interface text generated by WooCommerce, the theme or an extension. Review Cart and Checkout pages in every language, then test product selection, variation selection, cart contents and the checkout form.
Do not assume that a customized checkout uses the same translation fields as a standard WooCommerce page. Payment, shipping, tax display and legal text also require store-specific review, because the reviewed sources do not establish identical behavior for every integration.
Email and confirmation checks
Run a test order in each active language and review the confirmation page, order-related messages and transactional email delivery. Include product reviews in the translation inventory and inspect how they appear on translated product pages.
Testing should cover the complete path from product selection through payment and confirmation. Do not use real credentials, payment keys or customer data in screenshots or examples.
Set Up Multiple Currencies
WPML Multilingual & Multicurrency for WooCommerce documents options for multiple currencies, including currency selection based on language or customer location. The configuration can also include a currency switcher, currency formatting, exchange-rate settings and rounding rules.
Currency rules and switcher
Decide whether currency should follow the selected language, the customer’s location or another configured store rule supported by the current setup. Review formatting and exchange-rate settings, then check the payment-gateway configuration for each currency used.
These are settings to evaluate, not universal requirements. Tax, payment and legal-display behavior may depend on the business location, customer location, payment provider and local regulations. Seek professional review where tax or legal compliance is involved.
Cart behavior after a change
Changing language or currency can affect existing cart contents. WPML allows the administrator to choose how the cart is handled, including synchronization or clearing or resetting the cart.
Deliberately choose and test the intended behavior. Add a product to the cart, change language, inspect the contents, then repeat the test with a currency change and the configured payment gateway. Confirm that the resulting customer experience is clear before publishing the configuration.
Fix Untranslated Cart and Checkout Text
Untranslated Cart or Checkout text does not always indicate a failed product translation. The remedy depends on how the text was generated and when the language was added.
Identify the string source
First determine whether the text comes from WooCommerce, the theme, a plugin, a shortcode or a block-based Cart or Checkout component. Also check whether the language was added after the WooCommerce Multilingual setup. Shortcode-based page strings and block-based strings can require different procedures.
Keep product-content translation separate from interface-string translation. A translated product title will not automatically provide a translation for a theme label or an extension message.
Apply the matching WPML workflow
- Update WordPress or WooCommerce translations where applicable, especially if a language was added after the initial setup.
- Inspect the WPML Translation Dashboard and String Translation for text that is not part of product content.
- Scan the relevant WooCommerce plugin, theme or extension if the string has not been detected or registered.
- For applicable block-based text, enable JavaScript string detection and verify the result in the storefront.
Test the affected page after each change. One step will not necessarily fix every untranslated string, because the source of the text determines the appropriate workflow.
Pre-Launch Testing Checklist
Before production, test the translated store as a customer would use it. The purpose is not only to confirm visible language changes, but also to separate WPML configuration issues from behavior introduced by a theme, gateway, checkout customization or extension.
Language and currency test matrix
- Review product pages, attributes, variations, images, prices and stock in every active language.
- Run product selection, variation selection, Cart, Checkout, payment, confirmation and transactional email tests.
- Repeat relevant checks for every configured currency.
- Change language and currency with an existing cart to confirm the selected synchronization or clearing behavior.
- Record untranslated strings and integration-specific failures separately.
Also review taxes, shipping, payment gateways, caching, analytics, redirects and third-party integrations in the actual store environment.
Production handoff
Confirm the selected URL format and language switcher behavior across catalog and checkout pages. Verify the full order and email flow before publishing changes. Document exceptions involving the theme, gateways or extensions so future updates can be tested against the same cases.
Prefer staging for final verification and keep a tested backup. The documented WPML procedure is a starting point, not proof of compatibility with every third-party integration. Remove credentials, payment keys and customer data from all test material.
A reliable multilingual WooCommerce store is built in stages: prepare the documented WPML components, inventory the translation work, configure languages and URLs, translate products and purchase-flow content, then set up currencies and test cart behavior. When text remains untranslated, identify whether it comes from product content, WooCommerce, a theme, an extension, a shortcode or a block before choosing a remedy. Finally, test every active language and currency through the complete order path, including emails and payment. This store-specific verification is essential because themes, gateways, checkout customizations, taxes and extensions may not behave identically. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.