Multi Currency for WooCommerce

Multi Currency for WooCommerce shows your shop’s prices in the buyer’s own currency at the National Bank of Ukraine rate, while the order and the payment always run in a single currency: swapping the amount or the currency at the payment step is structurally impossible.

The order and the payment are always one currency

The most common way multi-currency plugins break: the page shows a price in one currency while the payment gateway charges the amount in another, or the payment signature is computed from the wrong currency. This module pins the currency at the exact moment the order is placed — the rate at that moment is stored on the order, and the WooCommerce order and the payment gateway then take the amount and the currency from the order itself. A mismatch between what the buyer saw and what went to the gateway cannot happen here.

The switcher and currency detection

The [catcode_currency_switcher] shortcode goes into a menu, the header or the footer and renders as a list or a dropdown. The buyer’s currency is remembered for a month. The Pro version can also suggest a currency based on the visitor’s country — the buyer’s own choice always wins over auto-detection.

WooCommerce reports stay correct

Orders in a foreign currency are converted to the shop’s base currency for WooCommerce Analytics and reports at the rate that applied at the time of the order itself — not at today’s rate, which may well have moved since.

Why a shop needs this

A Ukrainian shop selling abroad runs into something simple: a buyer in Poland or Germany sees a price in hryvnia and has no idea whether that is expensive or not. They will not go and work out the exchange rate — they will leave. Showing the price in a currency they know removes that step.

The second half of the job is harder than the switcher: the order and the payment must be in the same currency. If the storefront showed euro and the gateway charged hryvnia at a different rate, the shop ends up with a reconciliation gap and a complaint from the buyer.

Where the rate comes from

The rate is pulled from the National Bank of Ukraine and refreshes automatically twice a day. It is the official rate, not an exchange one — the same rate accounting uses, so the reports add up.

In Pro the rate can be set manually, or a markup can be added on top of the NBU rate — which is what shops usually do, to cover the acquiring fee and a day’s fluctuation.

What the admin gets

The shop’s base currency does not change — it stays hryvnia. Additional currencies are only layered on top as a storefront, so there is nothing to migrate and rolling back is painless.

Rounding is configurable: how many decimal places (0 to 4) to show for each currency.

Cache compatibility

The second classic failure of currency modules is caching. A page generated for a buyer in euro gets served to the next visitor, who sees somebody else’s currency.

The module adds the currency to the cache vary key, so each currency is cached separately. Caching stays switched on — you do not have to disable it for the sake of multi-currency.

What it costs

A Pro licence is 990 UAH for two sites (your store and a staging copy). The licence is annual: once it ends the module keeps working, only updates and support stop. We do not promise “forever” — the NBU changes its API format, and a module without updates will one day stop pulling the rate.

What is under the hood

The order’s currency and rate are stored in the order’s own meta fields. That is exactly why the payment and the reporting agree: any module that later reads the order sees the same “amount + currency” pair the buyer saw at checkout.

The rate is cached, so the NBU is queried twice a day rather than on every page load. If the API does not answer, the module runs on the last known rate instead of showing the buyer an empty price.

How to install it

1. Upload the archive in “Plugins → Add New → Upload Plugin” and activate it.

2. In the settings, switch on the currencies you need and hit the rate refresh.

3. Place the switcher with the shortcode wherever you need it — usually in the header.

4. Place a test order in a non-base currency and check that the gateway received the same amount and currency.

5. If you run a cache, warm the pages in both currencies and make sure they have not got mixed up.