Polylang > Pricing > Polylang for WooCommerce

Polylang for WooCommerce

Make WooCommerce multilingual and sell your products internationally!

The more you get, the less you pay:

Polylang for WooCommerce is subject to a yearly license with a 50% renewal discount due to continuous improvements, updates, and professional support.

Polylang for WooCommerce

Rating

4.7/5 (2 827votes)

Current version

Last update

January 13, 2025

Active installations

+800.000

Polylang for WooCommerce allows you to create a multilingual shop directly from the WooCommerce interface—nothing less, nothing more—to ensure

fast-blazing performance. 

Effortlessly translate WooCommerce pages and products. Stock and cart are synchronized across languages. Emails are sent to customers in the language chosen during the checkout!

fits perfectly for:

Online store owners who want to sell across borders and WordPress agencies that are looking for an easy and reliable way to translate their clients’ WooCommerce sites. 

Hint: To save extra money, consider the Business Pack, which bundles Polylang for WooCommerce and Polylang Pro

Easy and Quick Setup

Full WooCommerce Integration

Machine Translation

Built-in Performance

HPOS

Ready

Translate WooCommerce Products

Ensure global reach by translating your products manually or with machine translation:

  • The content of simple, variable, and grouped products.
  • Categories, tags, and global attributes.
  • Automatically loads static WooCommerce product strings if the language pack is available.

Translate WooCommerce Pages

Polylang for WooCommerce seamlessly integrates with WooCommerce language packs, automatically loading translations for:

  • Cart and Checkout pages.
  • Shop and My Account pages.

Send WooCommerce Emails in receiver’s language

Foster client relationships by providing localized WooCommerce emails:

  • Default WooCommerce emails (e.g., order confirmation).
  • If your WordPress user’s language is in the Polylang Language table, the email (e.g., new sale notifications) will be sent in that language.
  • Automatically loads existing WooCommerce email translations (if the matching language pack is available).
  • Customize and translate “Subject” and “Heading” from the Translations table.

Synchronize content Across Languages

Streamline your multilingual store management by synchronizing content across languages:

  • Synchronization of categories, tags, attributes, images, and galleries.
  • Synchronization of stock levels across product translations.

Sell your products everywhere with the

Polylang WooCommerce Addon

Key Features*

* Polylang for WooCommerce is an add-on that must be used in combination with Polylang Pro or Polylang.

Machine Translation (Polylang Pro)

Automatically translate products, categories, tags, pages and posts using our powerful DeepL integration.

Manual Translation

Translate your products, categories, tags, posts, and pages manually. Use Polylang Pro to duplicate a product and its content.

Translate WooCommerce Products

Translate simple, variable, and grouped products.

Translate Products Categories and Tags

Ensure seamless translation of products categories and tags.

Translate Global Attributes

Extend translation capabilities to global attributes.

Translate WooCommerce Pages

The shop, account, cart, and checkout pages are automatically translated by loading translations from the WooCommerce language Packs.

Send WooCommerce Emails in the Receiver’s Language

Send emails in the customer’s language, including default WooCommerce emails like order confirmations. If your WordPress user’s language is in the Polylang Language table, you will receive emails, such as new sale notifications, in your own language.

Stock Synchronization Across Product Translations

Ensure consistency in stock levels across translated products.

Other Content Synchronization

Synchronize prices, categories, tags, shipping classes, attributes, images, and galleries.

Built-in Performance + HPOS Ready

Full compatibility with the High-Performance Order Storage feature. Enjoy a fast online store experience with a bloat-free plugin that doesn’t add any extra tables.

Compatibility with WooCommerce add-ons

Polylang for WooCommerce is fully compatible with WooCommerce add-ons like Bookings, Subscriptions, Product Bundle, Composite products, Mix and Match products, and Dynamic Pricing.

SEO-Ready

Hreflang tags implementation, keyword, and meta description translation to improve the ranking of your WooCommerce store.

Compare Polylang fo WooCommerce with other versions

Logo

Compare with

addon Polylang for WooCommerce

From

99€

/ yr

User-friendliness
Easy start with our installation wizard Logo
Loading…
Logo
Benefit from our intuitive interface Logo
Loading…
Logo
Specific WooCommerce features
Translate products, categories, tags, global attributes Logo
Loading…
Logo
Translate WooCommerce pages (Shop, Cart, Checkout, My Account) Logo
Loading…
Logo
Translate WooCommerce emails Logo
Loading…
Logo
Duplicate a product and its translations in 1 click Logo
Loading…
Logo
Synchronization of taxonomies, attributes, metadata across product translations Logo
Loading…
Logo
HPOS ready Logo
Loading…
Logo
Synchronisation of the cart across languages Logo
Loading…
Logo
Help and support
Standard support on wordpress.org Logo
Loading…
Logo
Access to the documentation and guides Logo
Loading…
Logo
Premium professional support Logo
Loading…
Logo
DeepL Machine Translation integration (Doesn't Work with Elementor and some builders)
Translate your content automatically in the post or page interface (in edition mode) Logo
Loading…
30 languages available with DeepL. Check your language’s availability Logo
Loading…
Translate your content
Translate menus and widgets Logo
Loading…
Translate slugs in URLs (custom post types, taxonomies and more) Logo
Loading…
Duplicate the content when creating a translation Logo
Loading…
Translate custom post types and custom taxonomies Logo
Loading…
Translate posts, pages, media, categories, tags Logo
Loading…
Translations can share the same slug in the URL Logo
Loading…
Synchronized posts to get the same content across translated posts, pages Logo
Loading…
Setup a multilingual website
Enable or disable languages Logo
Loading…
Use subdirectories, subdomains or separate domains Logo
Loading…
Import/Export of strings translations in PO or XLIFF format Logo
Loading…
XLIFF Import/Export for pages, posts, media Logo
Loading…
Add a language switcher Logo
Loading…
Other features and compatibilities
Additional integration with ACF Pro Logo
Loading…
REST API Support Logo
Loading…
Site Editing support Logo
Loading…
WPML API compatibility Logo
Loading…

Do you have any questions?

  • Is Polylang GDPR compliant?

    Arrow

    Since the version 4.9.6, WordPress allows to export personal data. This includes the biographical info. As Polylang and Polylang Pro allow the users to translate their biographical info, the translations are added to the exported data since the version 2.3.6.

    None of our plugins collect other personal data.

  • Arrow

    Polylang uses a cookie to remember the language selected by the user when he comes back to visit again the website. This cookie is also used to get the language information when not available in another way. Examples are ajax requests or the login page.

    According to the section 3.6 of the  Opinion 04/2012 on Cookie Consent Exemption, this cookie is part of the user interface customization and may be considered as requested by the user. Whether it requires the explicit consent of the user seems to depend on the expiration time or the information provided on your website. Moreover European countries have all their own law and do not apply the European directive the same way. Please check if this cookie requires an explicit user consent in your own country.

    Here are the information about the cookie used by Polylang:

    • Default name: pll_language, can be changed by setting the constant PLL_COOKIE
    • Value: the language code of the last browsed page
    • Default expiration time: 1 year, can be changed with the filter pll_cookie_expiration

    It is possible not to use the cookie (be aware however that in this case and as stated above, not everything will work correctly)  by putting the code below for example in your wp-config.php file:

    define( 'PLL_COOKIE', false);

  • Is Polylang compatible with multisite?

    Arrow
    Yes it is. Polylang is fully tested in a multisite environment, activated at site level. It should also work when network activated but is not so well tested in this configuration. In most cases, it shouldn’t be useful to network activate Polylang.
  • Do I need another license key for staging sites and localhost?

    Arrow

    No. You can buy only one license key per public site and use it for localhost and your staging site. Your test site url has however to match:

    • localhost
    • localhost.localdomain
    • 10.0.0.0/8
    • 172.16.0.0/12
    • 192.168.0.0/16
    • *.dev
    • *.local
    • *.test
    • dev.*
    • staging.*
    • sandbox.*
    • *.wpserveur.net
    • *.wpengine.com
    • *.wptiger.fr
    • *.myraidbox.de
    • *.lndo.site
    • *.go-vip.net
    • *.kinsta.cloud

    All URLs matching the rules above will not be counted against your limit of sites. If you have any problem, please contact our support.

  • What is the duration of a license key?

    Arrow

    A license key is necessary to obtain the automatic updates and to access to the helpdesk support.

    A license key is valid for one year as from the date of purchase. It may be renewed after one year at a preferential rate (currently 50% of the new license price). If a key is not renewed prior to its expiration, the plugin will continue to operate but you will no longer have access to automatic updates and helpdesk support.

    It is recommended to run the latest version of WordPress, your theme and your plugins.

     

  • What is covered by the support?

    Arrow

    Per our general terms and conditions of sale, the support includes the assistance with the installation and use of our plugins. It of course includes the correction of bugs. It does not include the resolution of conflicts with theme or third party plugins. It does not include writing personalized code to fix a problem. It does not include reviewing or fixing personalized code written by the client. No support will be due in the event of a modification of the plugin by the client.