Polylang for WooCommerce

Overview

Polylang for WooCommerce is an add-on rather than a standalone multilingual system, so a working Polylang or Polylang Pro installation is part of the setup. Its practical appeal is the way it keeps related shop data connected across language versions: product translations can share synchronized inventory and selected catalog data, while customers can receive WooCommerce emails in the language used during checkout. This can reduce duplicated store administration, but it does not remove the need for translation review or compatibility testing. DeepL-based translation requires Polylang Pro and is not compatible with Elementor according to the supplied product documentation. The changelog also records changing minimum requirements over time; version 2.2 requires WordPress 6.5 or later, WooCommerce 9.2 or later, and Polylang 3.7 or later. Before deploying, test checkout, cart blocks, payment gateways, email previews, product variations, taxonomies, and every major WooCommerce extension on a staging copy.

Compatibility and setup context

• Requires Polylang or Polylang Pro; the product is an add-on and not intended to operate alone.
• For version 2.2, the documented minimums are WordPress 6.5+, WooCommerce 9.2+, and Polylang 3.7+. Check these requirements against the installed release.
• DeepL translation requires Polylang Pro and is currently not compatible with Elementor; test other page builders before committing to an automated workflow.
• The documentation lists compatibility with HPOS and several WooCommerce extensions, but individual payment gateways, themes, builders, and third-party plugins still warrant staging tests.
• A license key is used for automatic updates and helpdesk access; the supplied documentation states that the plugin continues operating after expiry, without those services.

Product Details