Skip Navigation

In this release, we improved the usability of our multi-currency mode. After numerous rounds of testing, we’re so satisfied with the improvements that we even changed the name of the plugin to include the word multi-currency. However, we’re most interested in hearing from our users: what do you think about the WooCommerce Multilingual multi-currency mode?

Improved Multi-Currency Mode

WooCommerce Multilingual has always made it possible for WPML users to run a fully multilingual e-commerce site with multiple currencies, depending on the location or language of your customers.  

You can enable the multi-currency mode by going to WooCommerce → WooCommerce Multilingual and Multicurrency and entering the Multicurrency tab. From there, you can decide between showing currencies based on Site Language or Client Location. You can also choose which currencies you want to display for each language or country.

Watch this video for a quick, complete guide on adding multi-currency to your store:

Free Standalone Mode

Now, even users without a WPML license will be able to use WooCommerce Multilingual’s multi-currency features – for free. So, if you have friends who use WooCommerce but not WPML, tell them they will soon be able to grab a copy of WooCommerce Multilingual from the WordPress repository and start showing product prices in different currencies based on client location.

We are rolling this version of WooCommerce Multilingual to WPML clients first, in batches. Once it’s available to all clients, we’ll release it on the WordPress plugin repository as well.

Of course, to use other features besides multi-currency, it’s necessary to purchase WPML.

Showing currencies based on Client Location in the standalone multicurrency mode

Better Compatibility with WooCommerce Add-ons

With WooCommerce Multilingual 5.0.0, several WooCommerce add-ons are now integrated with WPML’s Advanced Translation Editor so it’s easier than ever to translate them. This also makes them fully compatible with WPML’s Translate Everything mode.

WooCommerce add-ons compatible with the Advanced Translation Editor:

Bug Fixes and Compatibility Improvements

This release also includes a number of bug fixes and compatibility improvements. For the full list of changes, please see the changelog.

Download and Update

We’ll be releasing this update gradually. You will receive this update on your registered sites automatically once it’s available for you. If you’d like to update to the new version now, go to Plugins → Add New and click over to the Commercial tab. From there, click the Check for updates button. 

Updating to the newest version of WooCommerce Multilingual & Multicurrency

We’d Love To Hear Your Opinion

We’re curious how you feel about WooCommerce Multilingual, so we’d like to pick your brain and see how we can make it even better. Do you use our multi-currency features? Do you have any feedback or suggestions for our plugin? Leave a comment here and we’ll get back to you!

5 of 5 stars

Are you enjoying your experience with WooCommerce Multilingual?

Please take a moment to give it your 5-star review on

19 Responses to “WooCommerce Multilingual 5.0 – Improved Multi-Currency Features and Better Compatibility with Popular Add-ons”

    • Hi, thanks for taking the time to let us know! We’ve fixed the issue and the link to the changelong should work as expected now.

  1. Hi. I would like to know if with this version we will be able for a same country have the possibility to present the same devise in french and in english but with $ position different et change the “.” by “,”.

    Thank you

    • Hello! Are you using the same currency for different languages, but looking to display it in different ways by changing the separator from “.” to “,”?
      At the moment, you can only change the separator settings by currency. If one currency is displayed for multiple languages, they will all share the same settings, including the separator settings.
      Thanks for sharing your feedback and thoughts with us. I understand how this could be a useful feature, so may I also suggest sharing it with our team using the form on the Suggest a New Feature for WPML page?

  2. Errr…. where can we download 5.0? I don’t see it at the page or in the dashboard.

    • Hi Kathy! We’re releasing this update gradually, but if you already have WPML installed on your site and would like this update right away, you can head to Plugins → Add New and click over to the Commercial tab. After clicking the Check for updates button, you should see the option of downloading version 5.0 of WooCommerce Multilingual.
      The standalone version of WooCommerce Multilingual will be available on the WordPress plugin repository once we finish rolling out the update to all WPML clients.

  3. Multi-currency update sounds awesome.

    How about the “edit original language” thingy I’ve been feature requesting for quite some time?

    Your translation editor is such a convenient way to let users edit the content of a website without the risk of them messing up the layout. It just misses the option to edit the original language, and you’ll save us tons of work that we do manually with Toolset(having to separate the website content into two different post types, then let users edit one of them which holds custom fields for each individual page. Then I have to call the contents of these custom fields and lay them in a layout inside the block editor. So if want to keep a client’s unexperienced hands away from the layout/design I have to go through a lot of procedures that require manual adjustments after each general layout update, and are prone to human error. You can fix all this by enabling the Translation editor work with original language. It can be a simple check box in the settings panel that enables a specific user type access to editing original text. Pleeaaasseee!

    • Hi Diyan, thanks for your feedback!
      At the moment, we don’t have any plans for creating a specific user role that would make it possible to edit the content in the original language using the translation editor.
      However, please feel free to share your suggestion here:
      Suggest a New Feature for WPML

      • Unfortunately my feature request will be ignored since your team already decided they will not develop such feature(I just got an email stating that!)… What a pity.

        Thanks anyway!


        • I’m sorry to hear that, Diyan. We get a lot of feature requests and it’s not always possible to implement them right away. However, please keep in mind that we’re always re-evaluating the requests and will definitely reconsider our decision if similar requests from other users come in.
          Have a great day!

          • Thanks Kathy!

            I was sorry to hear that answer from your team as well, and I know your job is to try to make things look great anyway… Unfortunately the only thing that matters to me is getting proper support for a product I would like to regularly pay for on the long term. And proper support for such kind of a product would actually mean implementing feature requests that we as clients make.

            Otherwise, since we already have a problem that needs solving, we have no choice but look elsewhere. Possibly make our own solution based on the experience and knowledge that teams like yours have gained on solving similar problems. In other words – if you fail to implement this in your product, we might take it and modify it ourselves and implement it ourselves, filling the void that your team refuses to fill.

            Basically all we need to do is create an Original Language translation and then copy existing original content into that Original Language translation using what you already have in the translation editor. When each original language translatable item gets 100% translated, the actual translated item on the source page gets replaced with a call that pulls the content from the Original Language translation.

            All this could be triggered by a simple function that does just that – Enable editing of original content in the translation editor. Most of the hard work is done anyway, so I doubt that part would be that hard to add..

            • Hi Diyan,

              Thanks again for your comments. I understand your point and feature request, but please understand that WPML powers more than one million sites. Implementing something that may seem simple on the surface could potentially have unwanted effects for some clients or could cause usability issues for thousands of other users.
              We have thousands of clients with hundreds of feature requests but like everyone else, we have limited resources. As much as we’d love for it to be possible, we simply can’t bring them all to life. At the moment, we’ve only received this particular feature request from you. And while we can’t implement it just yet, that doesn’t mean it won’t ever happen!

              Thanks for understanding.

  4. Hola!

    Nos gustaría saber si con esta opción podemos establecer diferentes tarifas de precios por país usando la misma moneda.

    Es decir, nosotros vendemos en diferentes países de Europa, todos con moneda €, pero queremos establecer tarifa diferente de precios para cada país.

    ¡Sería ideal poder hacerlo!


  5. Hi!

    As I said in a feature request, the rounding rules are useless when using the following settings together:
    – display price including VAT (most non-US stores use this setting)
    – different VAT rates per country (usable by most international stores which need to apply VAT according to the shipping country – at least in the EU this is the case)
    – user geolocation

    The rounded price is never be visible to the visitor geolocated in a country with a different VAT rate than the store base country because the geolocation features modifies the displayed price after the rounding rules are applied.

    In order for the rounding rules to actually be useful with these settings, they should be applied on the final displayed price (after geolocation happens) and the VAT should be recalculated.

    There are multicurrency plugins out there that have this feature: the base backend price is converted and the VAT amount is adjusted according to the user applicable VAT rate.

    I found no workaround for this issue so our prices are rounded for customers in 2/30 countries that we sell to.

    Maybe you could consider developing a feature that would allow rounding to work together with geolocation.

    Otherwise, the plugin works fine.


    • Hello! Thanks for your comment.
      We appreciate you taking the time to request a new feature. I don’t have an ETA for you just yet, but our team is looking into your suggestion.

      • Hi Kathy,

        That’s great news. This feature will also resolve issues with google / facebook feeds that check the website prices.


      • Hi Kathy!

        Please let me know what is the ETA for this feature as we really need it because of its impact on UX and we’re considering switching plugins.


        • Hi Tudor,

          Our team is aware of your feature request and looking into it, but it would be unfair of me to give you an ETA when we don’t have one. I understand that this is a feature you’re waiting for. We always do our best to meet client expectations but please understand that our development capacity is limited.

          Have a great day!