Currency and Regional Pricing Without Confusion
A price in the wrong assumed currency is a late surprise at full scale. This guide covers naming currencies unambiguously, handling regional price differences with stated reasons, and keeping the checkout and the pricing page in agreement.
The short answer
Name the currency in words wherever a symbol could be shared or misread, state whether displayed prices convert or charge in the buyer's local currency, and explain regional differences briefly and honestly where they exist. The buyer's question is elementary - what will actually leave my account, in my money - and any ambiguity in the answer becomes a checkout surprise or a support dispute. If your platform shows localised display prices, label them as display or estimate wherever the charge itself is made in another currency. Clarity here is mostly labelling discipline, applied consistently on every figure.
Symbols are not currency names
Several major currencies share the dollar sign, and symbols in general assume the reader's location in a way the web does not guarantee. Use the currency code or name beside prices on pages that serve more than one market, at least at the first and most prominent statement of each price, and in every total. This costs a few characters and prevents the most extreme version of price surprise: the buyer who discovers at the statement that the figure was in a different currency altogether, worth materially more or less than they believed. Domestic only businesses can relax the rule only when they genuinely serve one currency area.
Display currency versus charge currency
Where your store detects location and displays converted prices, the page must make clear whether those figures are the charge or an estimate of it, what rate basis converts them, and which currency the payment will actually be taken in. An unlabelled estimate that drifts from the final charge by even a small amount reads, at checkout, exactly like the late fee problem: a number that changed when the buyer could least re-decide. Keep the final charge's currency stated again at checkout so the chain from pricing page to payment contains no silent handover between currencies.
Regional differences, explained once and plainly
Prices that differ by region have legitimate causes - taxes, delivery economics, local operating costs, regulatory requirements - and buyers accept differences they can understand far more readily than differences they discover. State that regional pricing applies where it does, name the main reason in a line, and make sure a buyer always sees the price for their region before any commitment step. Never let a buyer research on one region's prices and check out at another's without the change being flagged and explained at the point it happens. The explanation does not need to apologise; it needs to exist, briefly and factually.
Tax treatment across borders
Regional clarity includes the tax story: whether the price shown includes the taxes of the buyer's location, is calculated at checkout for their jurisdiction, or will involve charges on delivery for cross border orders. State the treatment in the same line of sight as the price for the markets you serve, and keep the statement accurate per market rather than gesturing at a global footnote. This is the regional face of the total cost discipline in showing total cost and fees. Buyers who import regularly are connoisseurs of this clarity and choose stores that practise it.
One region's story, told identically everywhere
The buyer's region specific facts - currency, price, tax treatment, delivery terms - should be identical across the pricing page, product pages, cart, checkout and confirmation for that buyer. Most regional confusion is born in templates: a footer in the home currency, a banner announcing a threshold in another, an email quoting the pre conversion figure. Audit the journey with your location set to each market you serve, or with the tools your platform provides, and fix the templates that leak the wrong region's facts. Assign the audit to the pricing review rhythm, because regional settings decay as templates and campaigns change.
Working with platform localisation
Hosted platforms offer varying localisation machinery: markets, currency conversion, duties calculation, translated price display. Use what yours provides, but verify the buyer's actual view rather than trusting the settings panel, and read the platform documentation in this guide's sources for what each setting truly controls. Where the platform cannot charge in a buyer's currency, say so and make the charged currency unmissable. A small store serving two or three markets well, with every figure honest, is in a stronger position than one displaying thirty currencies over a single silent charging currency.
Sources and evidence on the record
- Shopify, Shopify Help Center - platform documentation for themes, cart, checkout and Shop Pay.
- WooCommerce, WooCommerce documentation - store, product, cart and checkout mechanics.
Evidence basis: Platform guide. Behaviour described is as documented by the platform in the sources listed below, checked on 24 October 2026; platform behaviour changes, so re-check before a rebuild. Applies when: Any business whose buyers span currencies, tax regions or priced regions