Skip to content Skip to sidebar

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 -
- 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 12:00 – 16:00 -

Supporter timezone: Europe/Zagreb (GMT+02:00)

This topic contains 11 replies, has 0 voices.

Last updated by Dražen 1 day, 14 hours ago.

Assisted by: Dražen.

Author Posts
December 8, 2025 at 7:52 pm #17645268

mathiasB-21

We are trying to fix an issue where secondary-currency prices become incorrect after VAT is added. WPML currently converts prices before tax, and because we cannot enable rounding with VAT included, our NOK and EUR prices become non-rounded amounts (e.g., 23.2121 after tax), which causes incorrect totals.

According to your documentation, WooCommerce Multilingual should provide options such as:

“Calculate prices in each currency based on the store default including taxes”

Currency rounding rules

The modern multicurrency configuration UI

However, our installation only shows the old basic currency list and none of the advanced settings. It appears our site may still be using a legacy “independent” multicurrency mode.

We need guidance on:

Why the new multicurrency UI does not appear even though all plugins are up to date.

How to migrate or enable the correct multicurrency mode so that tax-inclusive conversions and rounding work.

We can provide screenshots or the full icl_sitepress_settings record if needed.

Thank you.

December 10, 2025 at 10:27 am #17651423

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

Thank you for contacting us. Let me address your questions and help move things forward.

1) Missing modern UI for multicurrency - At the moment, there haven’t been significant updates to the multicurrency UI.

Could you please share how it appears on your end and compare it with the UI shown in our documentation here: https://wpml.org/documentation/related-projects/woocommerce-multilingual/multi-currency-support-woocommerce/

If there are differences, please let me know.

2) Tax prices and rounding issue - To better understand the problem, I’ve created a new test site. Please open the link below, configure your tax rules and multicurrency settings, and then let me know the exact steps you took and what result is incorrect. For example: “price is 1.3444 but should be 1.35.”

Test site:
hidden link

Let me know how it goes and if any troubles.

Regards,
Drazen

December 10, 2025 at 1:15 pm #17652378

mathiasB-21

Hi.
I have now updated the test site with our configuration. As you see the test product get a wierd price ( because tax )

However admin gui looks the same on the testsite as on mine. So my guess is that it was AI that just got lost. 🙂

Kind regards

December 10, 2025 at 1:45 pm #17652479

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

Thank you for getting back to us and for taking the time to reproduce the issue.

I’ve checked the calculations, and as I understand it, in the default language you have: 159.2 + 25% = 199 kr

In USD, the calculation is:
159.2 × 1.1 = 175.12 USD,
175.12 + 25% = 218.9 USD

From what I can see, this is working correctly.

What may be causing confusion is the multicurrency rounding settings for USD.

In the USD currency configuration, you can choose how prices should be rounded—or disable rounding completely. For example, I temporarily set it to round to the nearest integer and disabled any subtract, which results in a final price of 220 USD.

You can either disable rounding if you want the exact calculated value, or adjust the rounding rules to match your preference.

Video
- hidden link

Let me know if this helps and makes things clear or you have any other doubts.

Regards,
Drazen

December 10, 2025 at 2:33 pm #17652719

mathiasB-21

Hi. The problem is that the rounding is dome before tax. So the function works as expected, but prices are still looking bad.

It should manage or atleast have an option to apply the rules after tax?

December 11, 2025 at 7:38 am #17654508

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thank you for getting back to me.

I believe I understand it now—could you please confirm that this is the correct outcome you expect?

The price is 175.12 + 25% = 218.9 USD, which should be rounded to 219 USD, not 220, correct?

Regards,
Drazen

December 11, 2025 at 1:09 pm #17655991

mathiasB-21

Hi.
The price for the product i base currency
159,2 + tax 25% = 199

With WCML i would like to keep a nice looking price without getting a decimal.

Its not that important how it rounds as long as i understand how it does it. And make it after tax.

So my thought price 159,2 x 1.1 = 175.12 = 218,9 ( this is the ammount we think should be adjusted and the rounding should be based on ) Makes no sense to do that before tax since that will end up getting "bad looking pricing".

Kind regards

December 11, 2025 at 1:54 pm #17656292

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

thanks for getting back to me.

I understand that rounding is applied after tax, and why this matters — it can result in a slightly higher and incorrect price in the secondary currency.

You mentioned: "With WCML I would like to keep a nice-looking price without getting a decimal."

Just to clarify: rounding and decimal behavior can still be controlled from the WCML settings. You can choose to display prices without decimals and rounding them, and they will appear clean and rounded.

Here’s a video demonstrating this:

- hidden link

Please let me know if this makes sense and helps clarify the situation and if you have any further questions. If so, I will proceed with escalating the request regarding rounding after tax and not before the tax.

Regards,
Drazen

December 11, 2025 at 2:25 pm #17656415

mathiasB-21

Hi.
Displaying without decimals does not cut it if there is a decimal value ( tax will be incorrect )

And a nice looking price would be 220NOK for example not 218nok

Kind regards

December 11, 2025 at 2:33 pm #17656482

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

I believe you meant USD, not NOK, correct?

Regarding the other point: you mentioned that you expect the price not to be 218 USD, but instead 220 USD. However, this is actually what is happening now — the price is being rounded to 220 USD.

Example:
hidden link

Calculation:
159.2 × 1.1 = 175.12 USD
Rounded to 176 + 25% = 220 USD

I apologize for asking so many questions — I just want to fully understand your expectations so that I can escalate this properly. I understand the part about rounding after tax, and that makes sense, but the expected rounding behavior itself is still not completely clear to me.

For example, if rounding happens after tax:

What would you expect the final price to round to from 218.9 USD?
Based on the current rounding method (“round to nearest up”), this should result in 219 USD.

Could you please clarify what you expect in that scenario?

Regards,
Drazen

December 12, 2025 at 7:26 am #17657969

mathiasB-21

Hi.
No worries, we also want to get hit solved. So happy to answer 🙂
And yes on the demo site i seems like i am now looking at a price without any decimals.
However on my live site when i apply the same rules i get a price that is 218,75.

Also on the demo site with a product that cost 160 without vat = 200 inc VAT.
Now with USD set to 1.1 = product 220USD with the rounding function set to 10. If i autosubtract ammount it does not work as expected 223,75$ now?

I cant figure out this function or how to set it up.

Would it be possible to have a live chat that i can send you some printscreens etc?

December 12, 2025 at 8:14 am #17658176

Dražen
Supporter

Languages: English (English )

Timezone: Europe/Zagreb (GMT+02:00)

Hello,

Thank you for getting back to us.

This example clearly illustrates the issue you’re experiencing and what behavior you expect in this scenario.I understand it much better now.

I’ve escalated this to our second-tier support team for further review and guidance.

I will update you soon.

Kind regards,
Dražen