Translating a WooCommerce store involves more than preparing product names and descriptions. A multilingual purchase journey also includes product variations, attribute terms, categories, cart contents, checkout fields, validation messages, payment screens, order confirmations and customer emails. If any of these elements remains in the original language, the store may provide an inconsistent experience even when the catalogue appears translated.
This checklist follows the documented WPML and WooCommerce Multilingual workflow, while separating expected setup behavior from elements that require verification. The exact result can depend on the active theme, checkout method, payment and shipping extensions, custom fields and other implementation details. Prepare a staging copy, translate in a controlled sequence and test the complete purchase path before enabling a new language for customers.
What WPML and WooCommerce Components Are Required
The documented WPML/WCML stack
The documented setup for a multilingual WooCommerce store uses WooCommerce together with WPML, WPML String Translation, and WPML Multilingual & Multicurrency for WooCommerce. These components address different parts of the implementation: WooCommerce provides the store, WPML manages languages, String Translation handles text supplied by themes and plugins, and WooCommerce Multilingual & Multicurrency supports WooCommerce-specific translation and configuration.
Begin with the WPML setup wizard available through WPML → Setup. Then review the WooCommerce Multilingual configuration under WooCommerce → WCML. Before sending products for translation, confirm the active languages, store pages and product attribute settings. This sequence helps prevent bulk translation work from being performed against an incomplete store configuration. It is a documented workflow, not a guarantee of compatibility with every theme, payment gateway or WooCommerce extension.
Pre-Translation Preparation Checklist
Environment and implementation inventory
Create a complete backup before making bulk translation changes or using WPML troubleshooting tools. Preferably perform language and checkout changes on a staging copy first. Record the active theme, the checkout method, payment gateways, shipping extensions and custom checkout fields. This inventory gives the team a defined list of elements to test after the new language is enabled.
The inventory is especially important when the store uses custom product options, a modified checkout or extension-specific order data. The reviewed documentation does not establish a universal compatibility matrix for every WooCommerce extension, so behavior should be verified on the actual store rather than inferred from the basic setup.
Language, page and attribute decisions
Use the WCML setup wizard to configure available languages and create or assign translated store pages. When supported WooCommerce Cart and Checkout shortcodes or blocks are used, the wizard can create Cart and Checkout pages for active languages. Confirm that those pages exist and are assigned correctly before starting catalogue translation.
The wizard also lets administrators choose which product attributes should be translatable. Language-dependent labels normally belong in the translation scope. Values such as codes, measurements or other numeric information may intentionally remain unchanged, depending on the store’s content plan. Make this decision consistently so that translated products do not mix translated labels with accidental or unnecessary changes to technical values.
Translating WooCommerce Products, Variations and Attributes
Parent products, variations and attribute terms
Send products for translation through the WPML Translation Dashboard. In the documented workflow, a translation job can include product variations and related attribute terms. This means translating a parent product is not the end of the task for a variable product. Review the translated variation labels and confirm that the available combinations remain understandable to customers.
For every relevant variation, check the translated product page on the front end. Verify the variation name, attribute term, price, stock display, image and purchasability. Also test selecting a variation, adding it to the cart and changing the selection. The workflow supports the documented product structure, but the exact behavior of custom product types, complex options and third-party extensions must be checked separately.
Catalogue and image-content review
The translation scope can extend beyond the product title and description. The documented workflow may include product categories, tags and image text such as captions, titles and descriptions. Include these elements in the review so that customers do not encounter a translated product page surrounded by untranslated catalogue or media content.
Review the complete product presentation in each active language. Check that the translated name describes the same product, that attribute labels are clear and that images remain associated with the correct content. Do not treat automatic translation as final without reviewing product names, variation labels and other customer-facing information.
Translating the WooCommerce Cart and Checkout
Shortcodes, blocks and translated store pages
Cart and Checkout page creation is separate from translating the text displayed inside those pages. When the store uses supported WooCommerce shortcodes or blocks, WCML can automatically create Cart and Checkout pages for each active language during setup. That provides a starting point, but it does not prove that every notice, field, validation message or payment-related screen is translated.
First identify how the store implements the Cart and Checkout pages. Then test adding a product, changing a variation, viewing cart contents and completing checkout in every active language. Pay attention to shipping and tax information, coupon messages, required-field notices, payment instructions, payment return pages and order-related text. Customized checkout implementations require separate verification because automatic page creation does not establish that every custom element will behave as expected.
Also test language or currency changes while products are already in the cart. WCML provides options for keeping and synchronizing cart items, clearing the cart or showing a notice. Complex product options and extension-specific cart data may not always synchronize correctly, so this scenario belongs in the practical checkout test plan.
Troubleshooting Untranslated WooCommerce Strings
A diagnostic path for missing text
When cart or checkout text remains untranslated, start with the timing of the language configuration. If the language was added after WCML setup, go to Dashboard → Updates and update translations. Missing WordPress, theme or plugin translations can explain why some standard WooCommerce text has not changed.
Next, identify the source of the text. For shortcode-based pages, look for the missing string in WPML String Translation and filter by the relevant theme or plugin domain. A string supplied by the active theme or another extension may need to be translated under that source rather than under WooCommerce. This distinction prevents searching only one domain and incorrectly concluding that the text is unavailable.
If the string is still missing, follow WPML’s string-registration guidance or use its troubleshooting tools. Create a complete backup before running troubleshooting commands or changing translation data in bulk. These tools address situations such as missing language information, products not appearing for translation, translation-table problems and string-related errors, but they should be used cautiously on the specific site.
JavaScript strings in Cart and Checkout blocks
WooCommerce Cart and Checkout blocks can display text generated from JavaScript. Such strings may not appear in ordinary string searches. The documented process is to enable detection of strings in JavaScript files, visit the affected front-end page and scan the relevant WooCommerce component under theme and plugin localization.
After the scan, register and translate the strings that were found, then revisit the affected page. When the translations are complete, disable JavaScript string detection because WPML states that leaving this option enabled may affect performance. Do not leave the detection setting active as a general permanent solution.
Post-Language Launch Test Plan
Purchase-path checklist
After adding a language, update WordPress and plugin translations and confirm that translated Cart and Checkout pages are available. Then test the complete journey in the new language: select a product, choose each relevant variation, review categories and attributes, check stock display and prices, add and remove items, apply a coupon and continue through shipping and tax steps.
Continue through checkout fields, required-field validation, payment, the gateway return page, order confirmation, order status changes and customer emails. Review legal checkout text, shipping terms, payment instructions and customer-facing errors. A translated page title or product description is not evidence that the entire purchase flow is ready.
Run these checks on a staging copy before publishing the language on the live store. Document any issue by theme, payment gateway, shipping tool, checkout field or WooCommerce extension. This makes it possible to distinguish a missing translation from an implementation or compatibility issue.
Language and currency switching
Test switching language or currency with an existing cart. Check the behavior configured for the store: items may be kept and synchronized, the cart may be cleared or the customer may see a notice. Test both simple products and products with complex options where those are used.
Verify the resulting cart contents, selected variations, prices and checkout data. If an extension stores additional product or cart information, confirm that this data remains correct after the change. The documented behavior does not guarantee synchronization for every product type or extension-specific data structure, so record failures before launch and investigate them on the actual configuration.
WPML WooCommerce translation is best approached as a sequence rather than a single translation action. Configure WooCommerce, WPML, WPML String Translation and WPML Multilingual & Multicurrency for WooCommerce; complete the setup wizards; decide which attributes require translation; and then translate products with their variations and related catalogue content. For missing cart or checkout text, identify whether the source is a page, theme, plugin or JavaScript block before choosing a fix. Finally, test products, variations, cart behavior, checkout, payment, emails and language or currency switching on the store’s real theme and extensions. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.