WooCommerce Regional Pricing vs Multi-Currency: Which One?

Stores selling into more than one country face a recurring decision, and the correct answer depends on which of two distinct problems they have.

The first is that customers are shown a currency they do not transact in. The second is that a single price does not suit every market being sold into. The two are frequently conflated, they require different tools, and selecting the wrong one is among the more common configuration errors raised in support.

What Regional Pricing Actually Means

Regional pricing means you set the price yourself, per country or per group of countries, and it stays exactly where you put it. A licence is 49.00 in the eurozone, 45.00 in Poland, 59.00 in Norway. Those are three decisions you made, not three outputs of a formula.

You would reach for it when:

• Local purchasing power differs enough that one number under-recovers in one market and prices you out of another
• Local competitors set a price point you need to sit near
• Landed cost differs by destination, which since the July 2026 removal of the EU’s €150 customs duty exemption now affects more stores than it used to
• You want round, credible numbers in every market rather than whatever the rate produces

What Multi-Currency Actually Does

Multi-currency takes your base price and presents it, and usually charges it, in the customer’s currency. The conversion runs off an exchange rate, normally refreshed automatically from a provider such as Open Exchange Rates or OFX.

The important consequence is that the number you show is derived, not chosen. If your base price is 50.00 USD and the rate moves, the euro figure moves with it. Today it is 46.20. Next month it might be 47.85.

Neither behaviour is wrong. An accurate conversion is exactly what you want on a store where price parity matters and you would rather not maintain a table of numbers. A chosen price is what you want when the number itself is part of your commercial strategy.

The Difference in One Example

Say you sell a plugin licence at 50.00 USD and you want to sell into Germany and Norway.

The multi-currency column is not worse. It is simply not a pricing decision. If the rate drops 8% and your Norwegian price drops with it, your margin in Norway drops too, and nobody chose that.

When You Need Multi-Currency Only

Most stores start here, and plenty should stay here. Multi-currency alone is the right answer when:

• You sell broadly and do not want to think about individual markets
• Your margins are wide enough to absorb rate movement
• Price parity across markets is a feature, not a problem, which is common for digital goods and licences
• You need customers to pay in their own currency to reduce card declines and cross-border fees, which is often the real reason people go looking in the first place

Our complete WooCommerce multi-currency guide covers the mechanics in detail, including the distinction between converting a price for display and actually taking payment in that currency, which is a bigger difference than it sounds.

When You Need Regional Pricing Only

Less common, but real. Regional pricing without a currency layer suits a store that sells into several countries which all use the same currency, and wants a different number in each.

Selling across the eurozone is the clearest case. Germany, Portugal, Ireland and Finland all pay in euros, and average willingness to pay is not the same in all four. A single euro price is one compromise applied to four different markets.

When You Need Both Layers

This is where most growing international stores land, and the order matters. The currency layer sits underneath, handling what the customer pays in and how the rate is stored against the order. The pricing layer sits on top, overriding the derived number with your chosen one wherever you have set it.

Practically, that means a product can have:

• A base price, used anywhere you have not made a specific decision
• Automatic conversion for the long tail of countries where a bespoke price is not worth the effort
• Explicit prices in the handful of markets that matter enough to price deliberately

You are not obliged to price all 195 countries. Most stores set explicit prices for five or ten markets and let conversion cover the rest, which is the sensible balance between control and maintenance.

Are You Allowed to Charge Different Prices per Country?

Generally yes. Differential pricing by market is standard commercial practice, and software, streaming services and consumer goods all do it openly.

The constraint worth knowing about is the EU’s geo-blocking regulation. In broad terms it stops you blocking or rerouting a customer because of where they are, and stops you applying different terms of access without justification. It does not force one price across the EU. What it does mean is that a customer who deliberately chooses to buy at your Portuguese price, from Sweden, on Portuguese terms, generally must be allowed to.

The practical read: differential pricing is fine, hard blocking is where the risk sits. If your reason for pricing differently is genuine and commercial rather than an attempt to trap customers in a market, the position is unremarkable. Confirm your own position if you are selling regulated goods or operating at scale.

How to Set Different Prices per Country in WooCommerce

Core WooCommerce has one price per product, plus tax rules. It has no concept of a price that varies by customer country, so this always needs an extension.

What a workable setup gives you:

That last point is the one most often overlooked. If the price only corrects at checkout, the customer encounters a discrepancy at the final step rather than a localised store. Our guide on how to change currency in WooCommerce based on customer location covers the IP-resolution side, and the walkthrough on how to offer different product prices per country in WooCommerce covers the setup itself.

Purchasing Power Parity: Pricing by What a Market Can Bear

The commercial argument for regional pricing is usually framed as purchasing power parity, and the idea is simple enough. The same nominal price represents a very different amount of effort depending on where the customer earns their income. A price that feels routine in Zurich can be prohibitive in Bucharest, and the conversion rate between the two currencies says nothing about that gap.

Where this matters most is digital goods, because the marginal cost of one more sale is close to nothing. A plugin licence sold at a lower price in a lower-income market is not a discount taken out of your margin, it is revenue you would not otherwise have had. The same logic does not hold for physical goods, where a lower price in a distant market has to absorb shipping and, since 1 July 2026, customs duty on EU consignments that previously entered duty free.

Three cautions worth holding onto:

• Do not go too granular. Three or four tiers covering groups of countries is manageable and defensible. Twenty-seven individual prices is a maintenance burden that will drift out of date within a year
• Expect arbitrage on digital goods. If your Polish price is half your Swiss price and there is nothing tying the purchase to a location, some customers will find the cheaper one. Set the differential at a level where that outcome remains acceptable
• Review on a schedule. Regional prices are a snapshot of a moment. Put a calendar reminder against them, because unlike converted prices they will never update themselves

How Regional Pricing Interacts With Tax and Shipping

A price is rarely the last number the customer sees, and the two things that land on top of it behave differently by market.

Tax. If you set a regional price of 49.00 EUR for Germany, decide explicitly whether that is inclusive or exclusive of the 19% VAT. EU consumers expect inclusive pricing, and in most member states showing them ex-VAT figures is not permitted. So a chosen consumer-facing price should almost always be the inclusive one, which means the number you set and the number your accounting sees are different. Getting that ordering wrong is the most common configuration error we see, and it is why Tax Display by Country exists as a separate layer rather than being folded into pricing.

Shipping. Regional pricing does not change shipping cost, and for physical goods the delivered total is what the customer actually judges. A carefully chosen product price undone by an unexplained shipping charge at the final step has not achieved anything. If you are pricing by market, price the delivered position by market.

There is a reporting consequence too. Once prices differ by country, your revenue reporting needs the country dimension or your average order value becomes a blended figure that describes no real market. Any tool worth buying stores the country and the applied price against the order so this stays reconstructable.

International Pricing Strategy: Rounding and Credibility

Once you control the number, you have to choose it well, and conversion output is almost never a good price.

46.20 EUR reads as a conversion. 49.00 EUR reads as a price. Customers cannot articulate why, but a number that looks calculated invites the question of what it was calculated from, and that question ends with them checking your other regional prices.

Two rules that hold up across markets:

• Round to a local convention. Norwegian prices tend to land on 9 or 0 at the tens; Japanese prices avoid awkward yen fractions entirely. Match the market’s habit
• Keep tier relationships intact. If your middle tier is twice the entry tier at home, it should stay roughly twice in every market. Conversion breaks these ratios silently

Aelia’s own pricing follows the same discipline. Prices are quoted at £69.00 ex. VAT rather than £69.99, in every currency, because a 9 at the end lands unfairly between markets once converted.

Which One Should You Buy?

The honest decision tree is short.

That last row matters. Neither of these plugins files a tax return, and we would rather say so than let you find out later. Our guide to WooCommerce EU VAT compliance covers what actually handles filing, including where we recommend a competitor.

• Prices by Country, £69.00 ex. VAT. Deliberate per-country prices, per-variation support, availability control.
• Currency Switcher, £89.00 ex. VAT. Multi-currency pricing and payment, automatic rates, rate stored against each order.

If you are still weighing vendors rather than approaches, our comparison of the best WooCommerce multi-currency plugins scores the field on capability, including four store types that should buy elsewhere.

Frequently Asked Questions

Does WooCommerce Show Prices in Local Currency Automatically?

No. Core WooCommerce has a single store currency and displays every price in it, regardless of where the visitor is. Showing local currency requires a multi-currency extension, and detecting the visitor’s country requires geolocation on top of that.

Can I Set Different Prices for Different Countries in WooCommerce?

Not with core WooCommerce, which holds one price per product. A regional pricing extension adds per-country or per-country-group prices, ideally with per-variation support and CSV import so you are not entering them by hand.

Is It Legal to Charge Different Prices in Different Countries?

In most markets yes, and it is common practice. Within the EU, geo-blocking rules restrict blocking or rerouting customers by location and applying different access terms without justification, rather than prohibiting differential pricing itself. Confirm your position if you sell regulated goods.

Should I Use Exchange Rates or Fixed Regional Prices?

Use exchange rates when accuracy and low maintenance matter more than control, which suits wide catalogues and healthy margins. Use fixed regional prices when the number itself is a commercial decision. Many stores use rates for most countries and fixed prices for their top few markets.

What Happens to My Margin if Exchange Rates Move?

Under pure multi-currency, it moves with them. A 6% adverse shift takes roughly 6% off your margin in that market until the rate recovers, and nobody made that decision. Fixed regional prices hold margin where you set it, at the cost of reviewing prices periodically.

Do I Need Both Plugins or Just One?

Just one, if you only have one of the two problems. Both, if you want customers paying in their own currency and deliberately chosen prices in your key markets. When you run both, the currency layer sits underneath and the pricing layer overrides it where you have set a specific price.

Try Prices by Country on Your Own Catalogue