Going Global: A Practical Multi-Currency and Multi-Language Guide
Selling across borders is one of the most reliable ways to grow an online shop that has already found its footing at home. The instinct is right: your best-selling product in Manchester is very often a best-seller in Munich or Melbourne too. But the moment a visitor lands on a page priced in a currency they have to mentally convert, written in a language they only half-read, the friction shows up in your conversion rate long before it shows up in your reports.
The good news is that going global is now a configuration exercise rather than a re-platforming project. Dirora ships with multi-currency pricing, a multi-language commerce UI and one-click AI translation built in, so you can serve international shoppers properly without bolting on a stack of third-party apps. This guide walks through how to set it all up, and — just as importantly — the judgement calls that separate a store that merely displays other currencies from one that actually sells well abroad.
Currency versus language: two different jobs
The first thing to get straight is that currency and language are separate decisions that people constantly conflate. Currency is about trust and clarity at the point of purchase — a shopper who sees £24.99 has no idea whether that is expensive until they convert it, and most simply won't. Language is about comprehension and confidence across the whole journey — product descriptions, delivery information, returns policy and checkout.
They also don't map neatly onto each other. A customer in Switzerland might want German-language content but prefer to pay in euros. A shopper in Ireland reads English but pays in euros, not pounds. Because of that, Dirora treats them as independent settings a visitor can control separately, and you should plan your rollout the same way: decide which currencies you'll settle in first, then decide which languages are worth translating properly.
Setting up multiple currencies
Head to Settings → Localisation → Currencies to enable additional currencies alongside your base currency. A few things worth understanding before you switch them all on:
Automatic exchange rates. Rates refresh automatically, so displayed prices track the market without you editing anything by hand. This keeps you competitive, but it also means a product priced at a clean £20 can show up as an awkward €23.47 abroad. For flagship products it's often worth setting deliberate, rounded prices per currency rather than letting a raw conversion produce odd numbers.
Consistent display throughout the journey. Once a shopper picks a currency, they see it everywhere — listings, product pages, cart and checkout — not just on the first page and then a surprise at the till. That consistency is what actually reduces abandonment.
Settlement is handled by your payment provider. Payments run through Stripe, which captures the customer's currency and settles funds to you in your settlement currency. Cards are charged at standard rates with no platform markup, and you can offer Apple Pay, Google Pay and BNPL options such as Klarna and Clearpay from day one. PayPal is available too. Do check your provider's cross-border and currency-conversion charges, as those are separate from anything Dirora takes.
A storefront currency selector. A selector in the header lets customers switch currency at any time, and their choice is remembered for return visits so they don't have to reset it every time.
One honest caveat: multi-currency display is not the same as multi-currency tax compliance. Charging the right VAT or sales tax to an overseas customer is a distinct task — our guide to setting up tax for international sales covers registration thresholds and inclusive-versus-exclusive pricing, and it's essential reading before you start taking orders from a new region.
Adding languages to your store
In Settings → Localisation → Languages, enable the storefront languages you want to support. Every translatable field in the admin — product titles, descriptions, collection names, page content — then gains a per-locale tab:
Default language first. Your primary-market content lives in the first tab and acts as the source of truth.
Additional locales. Switch tabs to add each translation, field by field.
Completeness indicators. Green dots show locales where every required field is filled; grey dots flag gaps, so you can see at a glance which products are genuinely ready for a market.
A sensible fallback chain. If a translation is missing, the storefront falls back to your default language rather than rendering an empty field. That prevents broken pages, but it's a safety net, not a strategy — a product page that's half in German and half in English erodes trust. Use the completeness dots to reach 100% before you promote a locale.
One-click AI translation
Translating a large catalogue by hand is the single biggest reason international projects stall. Dirora's AI translation feature removes that bottleneck. A translate button appears next to every translatable field, and a Translate All action in the locale tab header fills every empty field for that locale in one go.
A few practical notes on how it works and how to use it well:
Credit-based billing. Translation is billed per character through a credit system; you activate the feature and buy credit packs from the Billing section. Because completed translations are cached server-side, repeat phrases resolve quickly and cheaply.
Treat AI output as a strong first draft. Machine translation in 2026 is genuinely good, but it doesn't know your brand voice, your product's nuance, or that a phrase is a pun. Auto-translate the whole catalogue to get to full coverage fast, then have a native speaker review your homepage, best-sellers and checkout copy — the pages that carry the most weight.
Watch units and idioms. Sizes, materials, care instructions and anything measured tend to need a human eye. A description that reads naturally but quotes the wrong units will generate returns.
URL structure and international SEO
Localised URLs follow the BCP 47 locale pattern — /en-GB/products/..., /de-DE/products/..., /fr-FR/products/.... This isn't cosmetic; it's what makes your translated content discoverable:
Each locale lives at a distinct, crawlable URL, so search engines can index every language version separately.
hreflang tags are generated automatically, telling Google which version to serve to which audience and preventing your translations from competing against each other as duplicate content.
Server-side rendering means the localised content is in the initial HTML, so crawlers see the real, translated page rather than an empty shell.
If you want the rest of the on-page fundamentals — titles, metadata, structured data and internal linking — our SEO best practices for e-commerce guide pairs directly with this one. And if you plan to trade under a local domain to build regional trust, the custom domains and SSL guide explains how custom domains with automatic SSL work in practice.
Storefront selectors and theme content
The storefront shows language and currency selectors in the header automatically, positioned before the theme's right-zone blocks so they're easy to find without cluttering navigation. Selectors use native language names — "Türkçe" rather than "Turkish", "Deutsch" rather than "German" — which shoppers recognise instantly in their own language.
Translation reaches beyond your catalogue, too. Theme content — hero banner text, button labels, newsletter headings and other section copy — is translatable directly in the Visual Theme Editor, which shows locale tabs on any section or block with text fields. That means a French visitor doesn't hit an English "Add to basket" button on an otherwise translated page, which is exactly the kind of small inconsistency that quietly costs conversions.
A sensible rollout order
Rather than switching on ten currencies and five languages at once, expand deliberately:
Pick one target market with real demand — often somewhere your analytics already show overseas traffic or orders.
Enable its currency and set clean, rounded prices for your key products.
Sort tax and shipping for that region before you promote it — see our notes on selling to the EU from the UK post-Brexit and on international shipping, customs and duties, which are where cross-border orders most often go wrong.
Translate the storefront, then have a native speaker review the high-traffic pages.
Measure, then repeat for the next market once the first is converting.
Handled this way, going international stops being a leap and becomes a series of small, reversible steps — each one paying for the next.
Ofte stillede spørgsmål
What's the difference between multi-currency and multi-language?
Multi-currency changes the currency prices are displayed and charged in; multi-language changes the words on the page. They're independent — a shopper might read German but pay in euros — so you configure and roll them out separately.
Do I need to translate my whole store before launching a new language?
No, but you should reach full coverage on the pages that matter — homepage, best-sellers, checkout, delivery and returns — before promoting a locale. Missing fields fall back to your default language, which prevents broken pages but looks inconsistent if it's widespread.
How accurate is AI translation?
Modern AI translation produces a strong first draft that's usually publishable for descriptive product copy. It's weaker on brand voice, idioms and units, so it's best practice to auto-translate for full coverage, then have a native speaker review your highest-traffic pages.
Does selling in another currency handle overseas tax for me?
No. Currency display and tax compliance are separate. You still need to configure the correct VAT, GST or sales tax rules for each market you sell into.
Will translated pages help my international SEO?
Yes. Each locale gets its own crawlable URL and automatic hreflang tags, so search engines can index every language version and serve the right one to each audience, rather than treating your translations as duplicate content.