Why does my store show different prices to international visitors?

Two mechanisms produce this: automatic currency conversion applied at display time, and per-market pricing rules. They can both be on at once, and whichever applies last wins.

Why the numbers break

The 3 patterns below — the first is the most common.

Fix it in this order

Follow these 5 steps in order.

  1. Decide which mechanism owns the price: fixed per-market pricing, or automatic conversion. Running both is the source of most surprises.
  2. Write down the intended price for your top three markets, then load each market and compare. Any difference you cannot explain is a setting conflict.
  3. Check whether displayed prices are tax-inclusive per market, and make that visible on the page so the difference reads as compliance rather than error.
  4. Verify the checkout total, not just the product page. Display and checkout can use different conversions.
  5. Re-test after any currency or market settings change — these settings interact, so changing one can move the other.

Confirm the fix

The 3 checks below confirm the change stuck.

The packaged version

the price-display and tax-consistency checks behind this page are packaged as Pricing Page Builder. Local-only, standard-library Python; no API key, no telemetry. It builds 4 page blocks: tier structure, anchor pricing, objection handling and copy. One-time $27.55.

Quick answers

3 questions that follow this one.

Does this cost me sales?

It can. A price that looks inconsistent reads as untrustworthy, and trust is what a first purchase depends on.

Should I show tax-inclusive prices everywhere?

In most EU markets, yes — it is a legal requirement, not a preference. That is why the numbers differ from a US-facing price.

Is this the same as showing local currency?

No. Local currency display is about which currency symbol appears; this is about which price the number came from.

Not legal advice: 956231 Studio's rule-based checks and configuration behaviour. Updated 2026-10-23.