Running a WooCommerce store in several languages involves more than translating product names. The store owner must decide which languages are active, how language versions are represented in URLs, which product data requires translation, and how customers will move through the Cart and Checkout pages. A multilingual setup also needs testing across products, variations, shipping, taxes, payments, account pages, emails, and language switching.
WPML documents a structured workflow for these tasks. It begins with the required WooCommerce and WPML components, continues through the setup wizards and catalog translation, and ends with verification of the purchasing process. The documented workflow provides a practical foundation, but compatibility with a specific theme, extension, payment gateway, cache layer, or customized checkout requires separate verification before production launch.
What You Need Before Starting a WPML WooCommerce Setup
Baseline Components and Setup Wizards
The documented baseline for a WPML WooCommerce setup consists of WooCommerce, WPML, WPML String Translation, and WPML Multilingual & Multicurrency for WooCommerce. After activating these components, continue through the WPML and WooCommerce Multilingual setup wizards rather than configuring isolated options without an overall plan.
The WooCommerce Multilingual wizard can help create store pages in the available languages. It also lets the site owner decide which product attributes should be translatable and can optionally be used to configure multiple currencies. These decisions should be made before translating a large catalog, because they affect how product data is organized and reviewed later.
Prepare the work on a test copy or after creating a backup. Record the active theme, WooCommerce extensions, payment gateways, shipping methods, cache configuration, and checkout customizations. This inventory gives the implementation team a defined list of integrations to verify instead of assuming that the baseline components cover every store-specific feature.
Pre-Launch Compatibility Planning
WPML documentation describes the intended general workflow, not a complete compatibility matrix for every WooCommerce extension, theme, payment provider, cache layer, or checkout customization. Treat compatibility as a project task. Check whether product fields, checkout elements, payment labels, shipping methods, tax displays, customer account pages, and order emails behave correctly in every active language.
Do not assume that additional integrations will work without testing. A controlled test order on a staging site can reveal whether translated content is displayed correctly and whether the language selected by the customer remains consistent through cart and checkout. Keep customer, order, payment, and translation-service data out of screenshots and examples used during the project.
Configure Site Languages and Language URLs
The Three URL Structures WPML Documents
WPML documents three ways to represent language versions in URLs. The first uses language directories, such as a language-specific path within one domain. The second uses a separate domain or subdomain for each language. The third adds a language parameter to the URL.
There is no single universally correct format in the documented options. Language directories may be a straightforward starting point for a store operating within one domain. Separate domains or subdomains may fit an organization with distinct regional domain arrangements. URL parameters may be considered when the site’s SEO, analytics, caching, hosting, and operational requirements have been reviewed carefully.
The choice should therefore follow the store’s localization strategy and domain-management capabilities. It should not be based on an unsupported promise about rankings, conversions, performance, or international sales. Before translating the whole catalog, select the structure and verify representative product, store, Cart, Checkout, and account URLs in each active language.
Permalinks and Implementation Checks
If you choose language directories, WPML states that the permalink structure must differ from WordPress’s default structure. Its documentation recommends a Year/Month/Name or post-name structure for this configuration. Check the permalink setting before enabling the directory-based format and review the resulting addresses after the language configuration is saved.
Test direct access to translated product pages and navigation between language versions. Check whether links from category pages, product pages, the cart, checkout, and account areas preserve the intended language. Also verify that the language switcher leads to the corresponding translated page rather than sending the visitor to a generic destination.
Translate WooCommerce Products, Variations, and Attributes
Product Translation Workflow
Use WPML’s Translation Dashboard to select WooCommerce products and send them through the chosen translation workflow. When a product is sent for translation, WPML states that the job can also include product variations, linked attribute terms, categories, tags, and image text such as captions, titles, and descriptions.
This broader scope is important because a translated product page is not complete if its category, tag, variation option, or relevant image text remains in the original language without a deliberate reason. Create a review checklist for product names, descriptions, attributes, variation choices, categories, tags, and image captions, titles, and descriptions. Review each language version on the front end, not only in the administration area.
The workflow does not mean that every field supplied by every extension is automatically translated. Product templates, custom fields, add-on labels, emails, payment gateway text, and checkout customizations may require separate verification. Keep the translation review aligned with the actual data model and extensions used by the store.
Variable Products and Attribute Decisions
During WooCommerce Multilingual setup, mark the product attributes that should be translatable. The correct choice depends on the store’s content model. Descriptive attributes intended for local-language customers may need translation, while attributes based on numbers, codes, or measurements may not need translation when their meaning and presentation do not change between languages.
For variable products, check that translated attribute terms correspond to the correct options and that customers can select the intended variation. Test combinations on the front end after translation. Confirm that the product remains available, that the selected option is visible in the active language, and that switching language does not create an unexpected mismatch between the displayed product and its variation data.
Review categories and tags alongside attributes. These elements often form the navigation and filtering structure of the catalog, so untranslated or inconsistently translated terms can make the store difficult to use even when the main product description is complete.
Set Up and Verify Cart and Checkout Translations
What the Setup Wizard Handles
For WooCommerce Cart and Checkout pages built with supported shortcodes or blocks, the WooCommerce Multilingual setup wizard automatically creates translated versions for each active language in typical setups. This means that the owner does not always need to create every translated store page manually at the beginning of the process.
Automatic page creation should still be followed by inspection. Open the Cart and Checkout pages in each active language and verify their content, links, fields, and layout. Check the complete customer path: select a product, choose a variation when applicable, add it to the cart, review the cart, proceed to checkout, and inspect the available shipping, tax, and payment information.
The documented behavior applies to typical setups using supported shortcodes or blocks. It should not be treated as a guarantee for every checkout block, shortcode combination, extension, payment provider, or custom modification.
Troubleshooting Untranslated Checkout Text
Untranslated Cart or Checkout text can have several documented causes. The language may have been added after the initial WooCommerce Multilingual setup, or a shortcode-based or block-based page may still contain missing translations. Begin by checking when the language was added and whether the relevant translation files are current.
WPML documents updating translations, scanning the relevant plugin strings, and translating missing strings as troubleshooting steps. Use that sequence to identify text that is not part of the page content itself but is supplied by WooCommerce or another plugin. Then repeat the front-end test in the affected language.
Inspect checkout fields, shipping methods, taxes, payment processing, gateway labels, and order emails. Do not assume that a translated heading proves that the complete purchasing process is translated. Each active language must be tested from product selection through order completion, using the integrations enabled on the specific store.
Configure the WPML Language Switcher
Switcher Placement and Appearance
WPML adds a footer language switcher by default and also supports switchers in menus, widgets, templates, page or post content, and custom placements. Choose a location that is visible where customers need it, then verify that the switcher remains accessible on product pages, Cart, and Checkout rather than only on the home page.
The switcher can display flags and language names, and the language order can be configured. Select a presentation that makes the active language and available alternatives understandable to the store’s audience. Review the result on desktop and mobile layouts used by the site, while keeping the placement consistent with the active theme and templates.
Test the switcher on translated and untranslated content. Confirm that it changes the language as expected and that the visitor is directed to the corresponding page where a translation exists. If a product or store page is incomplete, the switcher should not hide that limitation from the implementation team.
Pre-Launch Multilingual Store Checklist
Functional Store Tests
Before launch, test every active language separately. Start with direct URLs for the home page, product pages, category pages, Cart, Checkout, and account pages. Include both simple and variable products, and review names, descriptions, categories, tags, attributes, variation options, and image text.
Run the complete purchase path in each language. Add products to the cart, change quantities where applicable, remove items, and confirm that cart contents persist as expected when moving to checkout. Review checkout fields, shipping methods, taxes, payment processing, gateway labels, order confirmation, and order emails. Also test the language switcher during browsing and shopping.
Test the active theme, extensions, payment gateway, cache layer, and custom checkout elements in the same environment planned for production. A configuration that works for a product page may still behave differently during checkout or payment processing, so the test should cover the entire customer journey.
Translation and Integration Review
Review missing strings after functional testing, especially if a language was added after the original setup. Update translations, scan the relevant plugin strings, and translate the missing elements documented by WPML. Check whether the translated Cart and Checkout pages are present for every active language and whether their content matches the current store configuration.
If WPML SEO options are used, inspect the page source for alternative-language information provided through hreflang links. Theme or plugin conflicts can affect the placement or completeness of these links. Treat this as a verification point, not as a complete SEO strategy or a promise of improved visibility.
Finally, review the current WPML and WooCommerce documentation before publication because administration labels, supported blocks, and integration workflows can change. Do not publish until the store-specific integrations and customized elements have been checked in the target environment.
A reliable multilingual WooCommerce implementation follows a clear sequence: install the documented components, run the WPML and WooCommerce Multilingual wizards, activate languages, select a URL structure, and translate the catalog with its variations and related taxonomies. Then verify Cart and Checkout pages, configure a visible language switcher, and test every purchasing path in every active language. The documentation provides the foundation, but each store’s theme, extensions, payment gateway, cache layer, and checkout customizations require their own review. This approach helps the team identify missing strings and functional issues before launch without assuming that any single URL format or automatic workflow suits every site. Explore our WordPress plugins, WooCommerce extensions, themes and membership plans to find the right tools for your website.