Polylang Multilingual Shop for WooCommerce — a multilingual store on free Polylang

Polylang Multilingual Shop for WooCommerce builds a multilingual store on the free Polylang. Polylang translates posts and pages; this module teaches it WooCommerce: products with variations, categories, tags and attributes, the shop, cart and checkout pages, the cart, the order and the e-mails. A shopper who reads the store in Ukrainian buys in Ukrainian and gets a Ukrainian e-mail, while the warehouse sees one product with one stock level.

A product is translated in one click: “+” in the language column creates a full copy — prices, stock, SKU, images, translated categories and attribute values, every variation. You only translate the texts. From then on everything that is not text stays the same in every language: change the price in any language and the others follow, sell the product in the German version and the stock drops everywhere.

What the shopper sees

• A shop page for every language. The Ukrainian shop page lists Ukrainian products; the language switcher leads from shop to shop, not to the home page.
• Product, categories, attributes in the shopper’s language. “Колір: Червоний” instead of “Color: Red”, navigation and breadcrumbs in Ukrainian.
• Same prices. The sale, the price range of variations and the stock are the same as in the English version.

The cart follows the shopper: switch the language and the lines move to the translations of the same product and variation, with the same quantity and coupon. The block cart, mini-cart and checkout get the page language (their Store API requests carry it), and so does the classic checkout — product names, shipping, field errors and the order itself are all in Ukrainian.

The order keeps the language it was placed in. “Order received”, then “Shipped” or “Completed” reach the customer in that language — whether the status is changed by an admin in an English dashboard or by a payment service at night.

What the admin gets

• Product translation with “+” in the product list or in the language box on the product screen — a full copy, status “Draft” or the same as the original (configurable).
• Shared data in sync from any language: prices and sale dates, stock and status, SKU and GTIN, weight and dimensions, shipping and tax classes, image and gallery, categories, tags, attributes, linked products. The product screen tells you what exactly is shared.
• WooCommerce → Polylang Shop: how many products each language has and how many are not translated yet, the shop, cart, checkout and account pages per language and a “Create the missing page translations” button — a copy with the block or shortcode, not an empty page.
• Languages → Translations: attribute names, your own WooCommerce e-mail subjects, headings and texts, and in Pro the payment and shipping texts.

The orders list has a Language column (HPOS and legacy storage), the order screen an “Order language” field. Admin notifications (“new order”, “low stock”) go out in the store’s default language, one per product rather than one per translation.

Pro: the whole catalogue at once, prices per language, payment texts and CSV

• Translate the whole catalogue. Pick a language and a status — the module gives products without a language the default one and creates the missing translations of categories, tags, attribute values and products with all their variations. Short steps, can be stopped and resumed, a rerun duplicates nothing.
• Separate data per language. Untick a group and each language keeps its own price, stock, images or SKU — for example a separate stock per market.
• Payment and shipping texts per language: payment method titles, descriptions and instructions (bank details on the thank-you page and in e-mails) and shipping method titles — on the classic and the block checkout; plus the store notice and the checkout consent texts.
• CSV with languages. WooCommerce export and import with “Language” and “Translation group” columns: products and variations come in already in their languages and linked.

How it works — step by step

1. You add languages in Polylang; the module makes products, categories, tags and attributes translatable and creates the shop, cart, checkout and account pages for every language.
2. “+” in the language column — a full copy of the product in that language; you translate the texts and publish.
3. You edit price, stock or variations in any language — the module carries the shared data to every translation; an order reduces the stock in all languages.
4. The shopper switches language — the cart moves to the translations; block and classic checkout run in the page language.
5. The order stores its language; every customer e-mail about it goes out in that language, admin e-mails in the store language.

Under the hood

• Public APIs only. Languages and translations through Polylang functions (pll_*), products and orders through the WooCommerce CRUD — so it works with HPOS and with legacy order storage.
• Data. Order language in the _catcode_plms_lang meta, the link between variations across languages in _catcode_plms_vgroup, settings in one option catcode_plms_settings. No custom tables.
• For developers. The catcode_plms_email_language filter sets the language of any WooCommerce e-mail.
• Removal. Products, translations and pages always stay; settings, variation links and the order language go only with “Delete data on uninstall” ticked.

How to install

1. Install and activate WooCommerce and the free Polylang, add your languages in Languages → Languages (“language from the directory name” is recommended).
2. Download the free version catcode-polylang-multilingual-shop-for-woocommerce-1.0.1.zip with the button at the top of this page (or the Pro zip from your account after purchase) and install it: Plugins → Add New → Upload Plugin.
3. WooCommerce → Polylang Shop → “Create the missing page translations” — the shop, cart, checkout and account pages get copies in every language.
4. In Products click “+” in a language column and translate the texts. In Pro — “Translate the whole catalogue”.
5. Translate attribute names and e-mail texts in Languages → Translations.