Guide

Why your translated Shopify store drifts back to English — and how to keep it current

By Lexibond · Updated August 2026 · A practical guide for merchants selling in French

You did the work. You translated the products, the collections, the policies. For a few weeks your store was genuinely bilingual, and it felt finished.

Then, months later, someone mentions that a page came up in English. You look, and they're right — and so are three other pages you hadn't thought about. Nothing broke. Nobody made a mistake. Translation isn't a project you finish; it's a state your store leaves the moment you change anything. This guide is about why that happens, why you can't see it from the admin, and what to do — starting with the parts that cost nothing.

Keep your Shopify store’s French up to date Watch · 1 min 46 s

Plays from YouTube only once you press play — nothing is loaded from Google before that.

The five ways a store drifts

1. New content is born English

Every product, collection, page and blog post you add after translation day starts life in one language. Nothing marks it as missing a translation — it just quietly publishes, complete-looking, in English. This is the biggest source of drift by volume, and the least visible, because new content is exactly the content you're most excited about and least inclined to audit.

2. Editing the English leaves the French frozen

This is the dangerous one. Most translation flows — including Shopify's own Translate & Adapt — do not re-translate when you edit the source. The old translation simply stays. So you rewrite your refund policy in English, feel done, and your French policy keeps promising last year's terms.

A missing translation is obvious to a customer. A stale one is invisible — it reads as perfectly good French, and it's wrong. On policies and order emails, where the words are effectively a contract, that's not a cosmetic problem.

3. The theme changes underneath you

Theme text is a translation surface that doesn't feel like content: buttons, menu labels, announcement bars, cookie notices, empty-cart messages, section headings. Add a section, install a theme update, or switch themes, and new English strings arrive with it. Theme updates in particular can reintroduce default English into text you'd previously fixed.

4. Other apps write to your storefront

Reviews widgets, shipping-rate bars, subscription selectors, upsell blocks, popups — each brings its own text, and each translates (or doesn't) on its own terms. This is also the surface where translation tools collide: two apps writing the same field, the later one winning, silently. If a translation you're sure you fixed has reverted more than once, this is usually why.

5. Campaigns and seasonal content skip the process

Sale banners, holiday collections, "back in stock" copy, the urgent homepage change made at 9pm — the content created under time pressure is precisely the content that skips the translation step. And because campaigns are front-and-centre, drift here is the most visible to customers even though it's the shortest-lived.

Why you can't see it

Three structural reasons, and they compound:

• You don't browse your own store in French. You work in the admin, in English. The French storefront is a place you visited once, during setup.
• Nothing reports it. Your analytics show sessions and conversion, not language coverage. An untranslated page isn't an error — it returns HTTP 200 and looks completely fine.
• Customers don't tell you. This is the part merchants underestimate. A shopper who hits an English page on a French storefront doesn't email you; they form a quiet impression and leave. Drift's cost shows up as slightly worse conversion, which looks like everything else that slightly worsens conversion.

The compounding part

Do the arithmetic for your own store — it's more sobering than it sounds. Suppose you carry 300 products, add 10 a month, and revise your policies twice a year. Twelve months after translation day: 120 products — 29% of your catalog — arrived after you translated, and both policy revisions left French text that no longer matches the English. Add a theme update and a seasonal campaign or two, and a store that was fully translated a year ago is now meaningfully English again, without a single mistake having been made.

(Those are illustrative numbers, not a statistic — run them with yours. The shape of the answer rarely changes.)

If you sell to Quebec, drift is a compliance problem too

Under Quebec's Bill 96, commercial communications to Quebec consumers have to be available in French. Compliance isn't a certificate you earn once — it describes your store today. The uncomfortable overlap: the surfaces that drift most quietly (policies, order emails) are exactly the highest-risk ones, because they're formal, unambiguously commercial, and nobody re-reads them after an edit.

How to stay current — free methods first

You don't need to buy anything to fix most of this. You need a habit and a checklist:

1. Put translation in the publish checklist. New product isn't "done" at publish; it's done when both languages exist. Same for anyone else with admin access — this is the single highest-leverage change, and it's free.
2. Pair every English edit with its French twin. Especially policies and emails. If you edit one, open the other in the same sitting or it won't happen.
3. Read your own storefront in French, cold, once a month. Not the admin — the actual storefront, as a shopper, ideally on your phone. Fresh eyes on your own work catch things no checklist does; it takes ten minutes and it's the technique that surfaces the embarrassing stuff first.
4. Audit after every theme change. Treat a theme update or new section as a translation event, because it is one.
5. Keep a surface list. Products, collections, pages, blogs, policies, emails, theme, navigation, and each app that writes customer-facing text. You can't check what you haven't enumerated — and most merchants have never written the list down.
6. Quarterly, run a real audit. Our free 2-minute self-check is built for exactly this: a structured pass over the surfaces people forget.

If your store is small and changes rarely, the habit alone genuinely solves this. Be honest with yourself about whether it will hold for a year, though — most merchants find the checklist survives about two busy weeks.

Where software helps

The habit's weakness is that it depends on remembering, forever, across everyone with admin access. Software is good at exactly the part humans are bad at: noticing. Whatever tool you use, the three capabilities worth having are:

• Change detection — something that knows a field's source text changed since it was translated, and tells you, instead of waiting for you to look.
• New-content coverage — new products and pages get picked up automatically rather than joining a backlog nobody maintains.
• Provenance — a record of which translations you wrote by hand, so automation can update the machine-written ones without ever steamrolling your work.

Whatever you choose, the mental shift is the valuable part: "translated" is not a finish line, it's a setting you leave on. The stores that stay genuinely bilingual aren't the ones that translated hardest once — they're the ones that made staying translated cheap.

Lexibond helps you reduce Bill 96 compliance risk and effort. It is a positioning and monitoring tool, not legal advice or a certification. For a binding assessment of your obligations, consult a qualified legal professional.