Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

To translate a WooCommerce store, first decide whether you need to localize the WordPress/WooCommerce interface in one language or let customers shop in several languages. Changing WordPress’s Site Language handles available interface translations; a multilingual store also needs translated products, categories, checkout, account pages, shipping and payment labels, and order emails.

Choose the translation scope

Your goal Approach What to keep in mind
Display WooCommerce’s standard interface in one language Set WordPress’s Site Language and update translation files. This does not translate product content or the complete shopping journey. WooCommerce localization guide
Change a few custom labels Use Loco Translate or Poedit for strings, or edit labels saved in WooCommerce settings. Custom translations may need maintenance after updates. WooCommerce localization guide
Offer a catalog and purchase flow in multiple languages Use a multilingual WooCommerce workflow, such as the one documented by WPML. Translate the full customer-facing experience and check theme and extension compatibility. WPML WooCommerce translation guide

Set WooCommerce’s interface to one language

  1. In WordPress, open Settings > General > Site Language, choose the language, and save.
  2. Go to Dashboard > Updates and choose Update Translations.

WooCommerce’s available locale files determine which interface translations are installed. If the language you need is not available, you will need a custom translation. The WooCommerce localization guide describes Loco Translate and Poedit for translating custom phrases; it recommends Loco Translate’s Custom location as the upgrade-safer option. After a WooCommerce update, sync translation files if needed to pick up new strings.

If some labels remain in the original language, check whether they were entered as settings rather than supplied interface strings. Shipping method names, payment instructions, and privacy-policy text may be saved in the database and need to be edited directly in the relevant settings.

Translate the whole store with a multilingual workflow

A multilingual setup needs to cover the store’s data as well as its interface. WPML’s WooCommerce translation guide describes managing products through its Translations dashboard, including simple, grouped, external or affiliate, variable, bookings, and subscription products.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Translate products and catalog structure

  • Translate product titles, descriptions, and other customer-facing product information.
  • For variable products, translate variations as well as the parent product; also translate relevant attribute terms.
  • Translate product categories, tags, attributes, and shipping classes as taxonomies. Preserve category hierarchy and localize relevant slugs.

Translate every purchase-flow touchpoint

  • Cart and checkout text, including checkout fields.
  • Account pages and customer-facing messages.
  • Shipping and payment method names and descriptions.
  • Coupon messages and transactional order emails.

Text added by a theme, extension, custom checkout field, or email template may not appear among the strings available for translation at first. WPML’s guide explains that such strings may need to be scanned or registered before you can translate them.

Choose language URLs and a language switcher

Configure the languages your store supports, choose how each language appears in its URL, and add a visible language switcher so shoppers can change languages. WPML documents three URL formats: language directories, a separate domain or subdomain for each language, or a language parameter. The choice depends on your site and SEO requirements; see WPML’s Language Setup guide.

Decide what happens to untranslated products

For each language, decide whether to hide products that have not been translated or display the default-language version as a fallback. Hiding them keeps the visible catalog translated but can leave fewer items available. Showing the fallback gives shoppers access to more products during a gradual rollout, while some content remains in the source language. WPML documents both behaviors in its WooCommerce translation guide.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Test the purchase journey in every language

After translating content, check that the storefront works as a shopper would use it. Include the following in your review:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Open important product types and verify variations, attributes, and translated product information.
  • Browse category pages and switch between languages.
  • Add products to the cart and follow the checkout flow, checking field labels, shipping and payment text, and coupon messages.
  • Review account pages and the customer emails generated by an order.
  • Look for untranslated text supplied by the theme, extensions, custom fields, or email templates.

If you use Google for WooCommerce product feeds, treat feed setup as a separate integration step. The product feed documentation says the feature uses language and currency configurations from supported plugins; it does not translate products or configure currencies. Products must be translated into the relevant market language to be included in that language’s feed.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.