Introducing One-Click AI Translation for Your Store

Selling across borders has always come with a translation tax. Every product title, description, collection name and policy page has to be rewritten in each language you want to support — and then maintained every time you change a price, add a variant or launch a new range. For most small merchants that work never gets done, which is why so many otherwise-brilliant stores quietly cap themselves at one language and one market.

We built One-Click AI Translation to remove that tax. Combined with Dirora's multi-language commerce UI, it lets you translate your storefront into the languages your customers actually shop in — without hiring an agency, wrangling spreadsheets, or copy-pasting into a translation site tab by tab. This post explains what it does, how to use it well, and where its limits are, because being honest about the limits is the only way you'll get good results.

What One-Click AI Translation actually does

The feature does two connected things. First, it gives you a translate action next to your translatable content in the admin — product fields, collection descriptions, page copy and the storefront strings your customers read. Instead of writing a German or French version by hand, you take your existing default-language content and generate a first-pass translation with a click.

Second, and just as important, the translated content is served through Dirora's multi-language commerce UI. That means the storefront itself — the buttons, the cart, the checkout labels, the account pages — presents in the shopper's chosen language, and your translated product content slots in alongside it. A customer browsing in French sees a French store, not an English store with a few French product titles bolted on. The two halves have to work together, and that's the point: translation is only useful if the whole buying experience follows the language, right through to the point of payment.

You stay in control of the result. A generated translation is a starting draft, not a locked-in fact. You can edit any string, keep the bits that read naturally, and rewrite anything that doesn't — which matters most for brand names, product names and the marketing lines where tone carries the sale.

Why this belongs on the platform, not in a plugin

Plenty of stores bolt translation on with a third-party widget that machine-translates the page in the browser. It looks fine in a demo and causes problems in production: the translated text usually isn't indexable, so you get none of the SEO benefit; it can flicker or mistranslate dynamic content like prices and variant names; and it rarely reaches the checkout, which is exactly where a confused shopper abandons.

Because translation is a first-class part of Dirora rather than an overlay, the translated content is real content. It lives in your store, it can be edited, and it's rendered server-side so search engines can read it. That last part is the difference between "my store technically supports French" and "my French product pages actually rank and convert." If you care about organic traffic from other markets — and on thin margins you should — that distinction is everything. Our SEO guide for online stores goes deeper on why indexable, server-rendered content beats client-side tricks.

Pairing translation with currency and tax

Language is one leg of selling internationally; money and compliance are the other two. A French-language store that still prices in pounds and can't handle EU VAT correctly will convert badly, however good the translation is. Dirora's multi-currency support lets shoppers see prices in their own currency, and its tax and shipping tools let you get the boring-but-critical parts right.

If you're expanding into Europe specifically, it's worth reading our notes on selling to the EU from the UK after Brexit and setting up tax for international sales before you flip the switch. Translation gets a customer to want the product; correct currency, tax and delivery estimates get them to actually buy it. Do all three together and a new-language store feels native rather than improvised.

How to roll it out without making a mess

The temptation is to translate everything into six languages on day one. Don't. A store that's 90% translated with awkward gaps looks less trustworthy than a clean single-language store. Here's a sequence that works:

1. Pick one target language first. Choose the market you already get traffic or orders from — check your analytics before you guess. One well-finished language beats five half-finished ones.

2. Translate the customer path, not just products. Prioritise the pages a buyer must pass through: home, key collections, your best-selling products, delivery and returns policy, and the checkout flow. These carry the sale.

3. Review the marketing-critical strings by hand. AI is excellent on descriptive, factual copy and weaker on idiom, humour and puns. Read your hero headlines, calls to action and brand taglines in the target language, ideally with a native speaker, and adjust anything that lands flat.

4. Leave product names and brand terms alone where appropriate. Not everything should be translated. Model names, brand words and certain technical terms are often better left in the original.

5. Test the whole journey in the new language. Add to cart, reach checkout, and read every label as a customer would. Fix anything that reads oddly, then move to the next language.

Treat the first translation as a draft you refine, and you'll get a store that reads like it was written for that market — because, after the edit pass, it effectively was.

Where AI translation is genuinely good — and where it isn't

Being honest about this is what separates a store that benefits from one that embarrasses itself. Modern machine translation is very strong on straightforward, descriptive text: specifications, materials, dimensions, care instructions, factual product detail. For the bulk of an average catalogue, a generated translation with a quick proofread is more than good enough, and it's produced in seconds rather than days.

It's weaker where language stops being literal. Wordplay, cultural references, humour and emotionally-loaded marketing copy can translate technically-correctly but tonally wrong. Regulated or safety-critical wording — ingredients, allergens, legal notices — should always be checked by someone who knows the target market's rules, not trusted blind. The right mental model is "AI does the heavy lifting, a human does the finishing," not "AI replaces a translator entirely." Used that way, it turns a job that was previously too big to attempt into an afternoon's work per language.

What it costs: a simple credit system

One-Click AI Translation is billed on a credit basis, so you only pay for the translation you actually generate. You activate the feature in the Billing section of your admin, then buy a credit pack; from that point the translate button appears automatically next to every translatable field. Translation is metered per character, which means a short product title costs a fraction of a long policy page — you're never paying a flat fee for content you didn't translate.

Two things make this cheaper than it first sounds. First, every completed translation is cached server-side: once a piece of content has been translated, Dirora stores the result and serves it instantly on every subsequent page load, so you're not re-billed each time a shopper views the page. Second, because you translate incrementally — priority pages first, then expand — your credit spend tracks the value you're getting rather than arriving as one big upfront bill. Top up a pack when you need more, and keep a small buffer if you edit product copy often, since regenerating a changed string draws on credits again.

This credit model is separate from your subscription and from payment processing. To be clear on the wider economics: Dirora charges 0% transaction fees on every plan, and the platform fee scales down as you grow — 1.5% on Starter, 0.75% on Pro, 0.25% on Business and 0% on Enterprise. Translation credits are simply the pass-through cost of the AI doing the work, priced by the characters you translate.

Getting started

One-Click AI Translation and the multi-language commerce UI are part of the Dirora platform — you can see them alongside multi-currency and the rest of the internationalisation toolkit on the features page. If you're still choosing a plan, the pricing page lays out what's included at each tier, with no transaction fees on any plan.

To begin, activate the AI Translation feature in Billing and buy a credit pack, enable your additional languages in the admin, then generate translations for your priority pages and do a review pass on the marketing-critical strings. If you're setting up a store for the first time, our getting started guide walks through the basics, and mastering the Theme Editor helps you make sure the translated storefront still looks the way you want in every language. Once you're happy, a language switcher lets your customers shop in whichever language feels like home.

International selling used to be a project you kept meaning to get round to. With translation built into the platform, it becomes a setting you turn on — and then refine, market by market, as the orders start coming in.