WooCommerce Checkout Optimisation and Localisation Checklist

An international customer arriving at checkout assesses four things, largely without articulating them: whether the price is denominated in their currency, whether the total matches what the catalogue displayed, whether the address fields match the format they expect, and whether their usual payment method is available.

Any one of these failing is sufficient to lose the order. None of them are trust problems in the conventional sense. They are configuration problems, and each one is fixable. This checklist covers them in the order the customer encounters them.

What Checkout Localisation Covers

Localisation is often reduced to translation. Translation is one layer of it, and on a store it is rarely the layer costing you the most money.

The full set, in the order a customer encounters it:

• Country detection. Which market are we in
• Currency. What the prices are denominated in, and what the card is actually charged in
• Tax display. Whether prices show inclusive or exclusive of VAT
• Language. Interface strings, product copy, emails
• Checkout fields. Address format, postcode rules, state or province requirements
• Payment methods. What is on offer at the final step

A store can get language perfect and still lose the customer at a price shown in the wrong currency. The reverse is also true, and both are common.

The Foundation: Detecting the Customer’s Country

Everything above depends on resolving the country, and resolving it before the catalogue renders, not at checkout. If a visitor browses in one currency and reaches checkout in another, you have created the exact surprise localisation is meant to prevent.

In practice detection means IP geolocation, with two refinements that matter:

• An explicit override. Always let the customer choose. Expats, travellers and VPN users will get detected wrongly, and a visible selector turns a bug into a preference
• A defined default. Decide what happens when detection fails, because it will. Falling back to your home market is fine as long as it is deliberate

Our walkthrough on how to set a default country for WooCommerce checkout covers both the no-code settings route and the IP-detection route.

Layer One: Currency

Two things get conflated here, and the difference decides which tool you need.

Display conversion shows a converted figure but charges the base currency. The customer sees roughly what they will pay, then their bank applies its own rate and often a cross-border fee. The final statement does not match the checkout total.

Charging in currency means the transaction is denominated in the customer’s currency. The amount on the statement matches the amount at checkout.

The second reduces both abandonment and card declines, and it is what most merchants think they are buying when they install a currency plugin. Our complete WooCommerce multi-currency guide covers the distinction and how gateway support constrains it.

Layer Two: Language

Language is the layer most people start with, and the one with the most mature tooling. WPML and Polylang both handle it, and both integrate with the currency layer rather than replacing it.

The parts that get missed are rarely the product pages:

• Transactional emails. Order confirmations often ship in the store’s default language even when the site is translated
• Checkout field labels and validation messages. A translated page with an English “invalid postcode” error is worse than no translation
• Currency and number formatting. Decimal commas versus points, and where the symbol sits, vary by locale and are a separate setting from language
• Legal pages. Refund and terms pages carry the most weight for a hesitant international buyer

One decision worth making early: language and country are not the same axis. A Belgian customer might want French or Dutch. Treating language as a function of country will eventually produce the wrong result for some customers.

Layer Three: Tax Display

This is the layer stores skip, and it is where the price a customer sees stops matching what they expect.

EU consumers expect VAT-inclusive pricing, and in most member states showing consumers ex-VAT prices is not permitted. A German shopper seeing a figure that grows 19% at checkout will usually leave. A VAT-registered business buyer expects the opposite, because ex-VAT is their real cost.

The same catalogue therefore has to render two ways depending on who is looking, decided before checkout.

Tax display is a presentation job, not a compliance one. Getting VAT filed correctly is separate work, and our guide to WooCommerce EU VAT compliance covers the thresholds, OSS, reverse charge and VIES validation side, including which tools actually handle filing.

Checkout Fields That Change by Country

WooCommerce already localises address formats for many countries, but the defaults do not fit every market and the gaps present as friction at the final step.

The country codes underneath all of this are worth getting right at the data level. Our guide to WooCommerce country codes covers the ISO 3166-1 alpha-2 codes plus the US and Canadian state codes that cause errors for stores selling both sides of the Atlantic.

Payment Methods by Market

Card coverage is not payment coverage. In several large European markets the dominant method is not a card at all, and its absence reads as the store not being meant for that customer.

• Netherlands: iDEAL carries the majority of consumer e-commerce
• Germany: bank transfer and invoice-based methods remain heavily used
• Poland: BLIK and local bank transfer
• Nordics: Klarna and local mobile schemes

Two practical points. First, filtering methods by currency or country keeps the checkout clean rather than showing everyone everything. Second, verify each gateway settles the currency you are charging in, because a method that appears and then declines is worse than one that never appeared.

Subscriptions and Recurring Orders Across Currencies

Subscriptions are where a localised checkout most often breaks quietly, because the failure happens months after the sale and nobody connects it back to configuration.

The rule to hold to is that a subscription created in a currency should keep renewing in that currency, at the terms the customer agreed to. If a renewal re-converts at the current rate, the amount taken drifts from the amount signed up for. Some customers will not notice. Others will treat an unexpected charge as an unauthorised one, and a chargeback costs considerably more than the difference.

What to verify before you offer subscriptions internationally:

• The currency is stored on the subscription itself, not read from the current store setting at renewal time
• The gateway supports recurring payments in that currency, not just one-off payments
• Renewal emails show the same currency and formatting as the original order
• Switching a customer’s display currency does not silently alter an active subscription

The same applies to any deferred transaction: pre-orders, deposits, instalments and partial refunds all depend on the original rate being retrievable rather than recalculated.

Shipping and Delivery Expectations by Market

For physical goods the delivered total and the delivery date are judged together, and both are local questions.

• Quote shipping to their country before checkout. A generic shipping page is not the same as a figure for their address. Cost revealed late is the most cited abandonment reason in every survey that asks
• State whether duty and tax are included. Since the EU removed the €150 customs duty exemption on 1 July 2026, low-value consignments now attract duty as well as VAT. A customer receiving an unexpected courier invoice will remember it as your error
• Give a delivery window, not a dispatch time. Cross-border buyers are estimating a date, and “ships in 2 days” leaves them doing arithmetic they will get wrong
• Say what happens with returns. Who pays return postage across a border is the top unspoken hesitation on a first international order

Testing a Localised Checkout Before You Trust It

Localisation fails silently, because everything looks right from your own IP. A short test pass catches most of it.

The last item is the one to insist on. If the order does not record what the customer was shown, you cannot investigate a dispute, process a fair refund, or reconcile revenue by market later.

Checkout Optimisation: The Conversion Layer

With localisation handled, ordinary checkout optimisation applies, and international traffic is less forgiving of friction than domestic traffic.

• Show the total early, including tax and shipping. Surprise costs at the last step are the most cited abandonment reason in every survey
• Do not force account creation. Guest checkout matters more for a first-time buyer from an unfamiliar country
• Cut optional fields. Every field is a chance to reconsider
• State shipping cost and time to their country before checkout, not on a generic policy page
• Show the refund position plainly. Cross-border returns are the top unspoken hesitation

The Full Localisation Checklist

The Three Plugins That Cover the Layers

Language aside, which WPML or Polylang handle, the three layers map to three tools:

• Currency Switcher, £89.00 ex. VAT. Pricing and payment in multiple currencies, automatic rates, rate stored against each order, gateway filtering by currency.
• Tax Display by Country, £69.00 ex. VAT. Inclusive or exclusive price display resolved by visitor country via geolocation.
• Prices by Country, £69.00 ex. VAT. Deliberate per-country prices rather than exchange-rate output, plus per-country availability.

If you are unsure whether you need the third one, our comparison of regional pricing versus multi-currency sets out which problem each solves.

Frequently Asked Questions

What Is Checkout Localisation?

Adapting the buying experience to the customer’s market: currency, language, tax display, address fields and payment methods, all driven by their detected country. It is broader than translation, and the non-language layers usually cost more in lost conversion.

Does WooCommerce Support Multiple Currencies by Default?

No. Core WooCommerce has one store currency and shows every price in it. Multiple currencies, and charging in them rather than just displaying them, require an extension.

How Do I Detect a Customer’s Country in WooCommerce?

Through IP geolocation, which WooCommerce supports natively for tax and shipping estimates. For it to drive currency and tax display it has to resolve before the catalogue renders, and you should always pair it with a manual override for travellers and VPN users.

Should Prices Include VAT for International Customers?

For EU consumers, yes, and in most member states showing them ex-VAT prices is not permitted. For VAT-registered business buyers the ex-VAT figure is the useful one. That means the same catalogue needs to render both ways depending on the visitor.

Do I Need Local Payment Methods to Sell Internationally?

Not to start, but they matter more than most merchants expect in specific markets. iDEAL in the Netherlands, BLIK in Poland and Klarna across the Nordics carry large shares of consumer e-commerce, and their absence reads as the store not being intended for that customer.

Does Localisation Handle My VAT Returns?

No. Currency, tax display and pricing tools change what the customer sees and pays. Filing returns, OSS reporting and VAT number validation are a separate category of tool. The two are easy to conflate and are worth budgeting for separately.

Start With the Currency Layer