Running a multilingual WooCommerce store involves more than translating product names. Product variations, attribute terms, categories, tags, Cart content and Checkout interface text all need to be considered in the right order. WPML provides a documented workflow for these areas, but the result still depends on how the store is configured and which theme or extensions provide the visible text.
This guide explains how to translate WooCommerce with WPML using the documented setup: install the required components, configure WooCommerce Multilingual and Multicurrency, select the catalog data that should be translated, send products through the Translation Dashboard, and verify the translated Cart and Checkout pages. It also provides a troubleshooting path for strings that remain in the source language.
The process below follows official WPML documentation. It does not independently verify identical behavior with every third-party theme, checkout extension, payment gateway, custom block or WooCommerce configuration. Treat the final checks as part of the implementation rather than as an optional step.
What You Need Before Translating WooCommerce with WPML
Before beginning a WPML WooCommerce translation workflow, prepare the components identified in WPML’s official WooCommerce guide. The documented list includes WooCommerce, the WPML core plugin, WPML String Translation and WPML Multilingual & Multicurrency for WooCommerce. Each component has a place in the overall process: WooCommerce supplies the store structure, WPML manages languages, String Translation handles interface text, and the WooCommerce-specific component supports multilingual store configuration.
Required plugins and initial setup
After activation, the documented setup flow uses WPML → Setup and WooCommerce → WCML. Start by defining the active languages and then work through the WCML configuration rather than immediately translating individual products. This gives the store a language structure that later product, taxonomy, Cart and Checkout translations can follow.
The initial setup also affects which attributes are treated as translatable and whether translated store pages are created. For a practical overview of available store extensions that may be relevant when planning a WooCommerce project, you can explore WooCommerce plugins, but do not assume that any particular extension has WPML compatibility without checking that specific configuration.
It is important to separate the documented WPML workflow from a universal compatibility claim. The research does not establish that every theme, checkout extension, payment gateway or custom block works identically with WPML.
Configure WCML for Products, Attributes and Store Pages
The WCML setup wizard is the point at which several decisions affecting later translation work are made. WPML documents that the wizard can create store pages in all active languages, allow administrators to choose which product attributes are translatable, and optionally configure multiple currencies. These options should be reviewed against the actual catalog and localization requirements instead of being enabled without a clear purpose.
Store pages, attributes and currency choices
When store pages are created for active languages, check that the expected language versions exist before starting a large catalog translation. The wizard can also ask which attributes should be translated. This matters for multilingual WooCommerce products because an attribute may be customer-facing text, or it may be a number, code or measurement that does not require localization. WPML’s documentation notes that attributes based on numbers, codes or measurements may be left untranslated when localization is not needed.
There is no single correct attribute policy for every catalog. A clothing store, technical catalog and store with coded product data may require different choices. Decide based on how customers see and use each attribute in the translated store.
Multiple currencies are optional in the documented setup, so they should not be treated as a requirement for translating products. If language or currency handling is changed, review the documented options for synchronizing, clearing or notifying customers about existing Cart contents. Changing these settings can affect items already in the Cart, so test the behavior before deploying it on a live store.
Translate WooCommerce Products and Variations
Once the WCML configuration reflects the catalog, use WPML’s Translation Dashboard to begin the product workflow. In the Products section, select the products that need translation and send them through the chosen translation process. This is the central workflow for translating product content rather than editing isolated fields without considering the related catalog data.
Product translation workflow
The documented workflow can include the product variations associated with a product, linked attribute terms, categories, tags and image text such as captions, titles and descriptions. This is why product translation should be reviewed as a complete catalog task. A translated product title alone may not provide a complete customer-facing result if the visible variation or attribute terms remain in the original language.
For WPML product variations, check that the relevant variation information is included in the translation workflow and that the translated product displays the expected choices on the front end. The exact fields included depend on the product data and on the attributes selected as translatable during WCML setup. Do not assume that every custom field supplied by an extension is automatically covered by the documented product workflow.
Catalog data to review after translation
After sending products for translation, review the associated catalog elements rather than treating the product as an isolated page. Confirm the translated product, its variations, linked attribute terms, categories and tags. Also review image captions, titles and descriptions where those texts are part of the product presentation.
- Check the product in each active language.
- Review variation choices and related attribute terms.
- Confirm that categories and tags use the intended language.
- Inspect relevant image captions, titles and descriptions.
- Open the product on the front end and verify the customer-facing result.
This review helps distinguish catalog translation from interface translation. A product can be translated while a Cart label or Checkout message supplied by WooCommerce, a theme or an extension still requires separate string translation.
Translate WooCommerce Cart and Checkout Pages
During WCML setup, WPML can automatically create translated Cart and Checkout pages for the active languages when those pages use WooCommerce shortcodes or blocks. This answers the basic question of how to translate WooCommerce Cart and Checkout page structures: first configure WCML and then verify the generated language versions.
Shortcodes and blocks in Cart and Checkout
Check whether the Cart and Checkout pages use the WooCommerce shortcodes or blocks described in the WPML workflow. Then open each page in the relevant language and confirm that the page structure is available. The automatic creation of translated pages does not mean that every visible interface string has already been translated. The page itself and the text supplied by WooCommerce, a theme or an extension are related but separate parts of the multilingual store.
A useful verification path is to add a product, open the Cart, continue to Checkout and repeat the process in each active language. Review product names, variation information, labels and messages as they appear in the customer journey. This also gives you a practical way to identify whether an untranslated phrase belongs to the page, WooCommerce, the active theme or another plugin.
Do not treat automatic page creation as a guarantee for every custom checkout or block. The accepted research describes WPML’s supported workflow and does not verify every external configuration.
Troubleshoot Untranslated Cart and Checkout Strings
When a Cart or Checkout phrase remains in the source language, start by identifying which documented situation is closest to the problem. WPML identifies languages added after WCML setup, missing translations for shortcode-based pages and missing translations for Cart or Checkout blocks as causes of untranslated text. The exact source may still need to be identified by the relevant theme, plugin or text domain.
A diagnostic path for shortcode-based pages
First check whether the language was added after WCML was configured. If so, update the required translations for that language and review the relevant Cart and Checkout pages again. For missing strings on shortcode-based pages, WPML directs users to the Translation Dashboard’s Other texts (Strings) area.
Use the relevant theme or plugin text domain as a filter when searching for the phrase. This is especially useful when the text is supplied by WooCommerce, the active theme or an extension rather than by the page content itself. Once the source is identified, translate the registered string and revisit the affected page in the appropriate language.
JavaScript strings in Cart and Checkout blocks
Cart and Checkout blocks may contain frontend strings stored in JavaScript files. WPML documents that these strings may not be detected by default. In that situation, temporarily enable JavaScript string detection, visit the affected frontend page, and scan the relevant plugin or theme so that the strings can be registered for translation.
After the strings have been registered, translate them through the available String Translation workflow and test the page again. WPML’s documentation warns that JavaScript string detection may affect performance, so disable the detection option after the required strings have been registered and translated.
This sequence is a documented troubleshooting path, not a universal diagnosis for every untranslated phrase. If the text is still missing, identify whether it comes from the theme, WooCommerce, another plugin or a custom implementation before choosing the next action.
Pre-Launch Checks for a Multilingual WooCommerce Store
Before publishing multilingual changes, validate the complete purchase path rather than checking only the translated product editor. The purpose of this stage is to confirm that the selected configuration works for the actual catalog and the active languages.
A practical multilingual store checklist
- Open representative products in every active language.
- Check product variations and linked attribute terms.
- Review translated categories, tags and relevant image text.
- Move a product from the product page to Cart and then to Checkout.
- Repeat the path in each configured language.
- Review the accepted currency behavior and existing Cart handling.
- For untranslated interface text, identify the theme, plugin or text domain providing it.
- Confirm that JavaScript string detection is disabled after the required strings have been registered and translated.
Testing should reflect the specific store rather than an assumed standard setup. The research does not include an independent test on a live WooCommerce installation and does not establish identical compatibility with every theme, checkout extension, payment gateway or custom block. Those integrations require verification in the actual environment before deployment.
For the same reason, document which attributes were selected as translatable, which languages were active during WCML setup and how Cart contents behave when language or currency settings change. This creates a clear reference for future catalog updates and helps narrow down the source of later untranslated strings.
In summary: start with WooCommerce, WPML, WPML String Translation and WPML Multilingual & Multicurrency for WooCommerce. Configure WCML, select the attributes that genuinely require localization, and use the Translation Dashboard for products, variations, taxonomies and image text. Verify the translated Cart and Checkout pages, then diagnose missing strings according to whether they come from a later-added language, a shortcode page, a theme or plugin text domain, or JavaScript-based blocks. Finally, test the complete purchase path before going live. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.