You rebuilt the theme. It looks better, it converts better, and you publish it on a Tuesday morning. Then a customer in Germany opens the site, and the announcement bar, the cart drawer and the footer are all in English again.
This is one of the most common surprises in a multilingual Shopify store, and it is not a bug. It happens because of where Shopify keeps theme translations. Once you know that, the fix is simple, and you can do it before launch day rather than after.
Why a new theme starts untranslated
Shopify stores translations in different places depending on what is being translated.
Product titles, descriptions, collection text, page bodies, blog articles and metafields are attached to those records. They belong to the product, not to whatever theme is drawing it. Change the theme and they stay exactly as they were.
Theme content is different. The strings you edit in the theme customizer, plus the theme’s own locale files, are attached to that specific theme. A new theme is a new record, so it arrives with an empty translation set.
That is why a redesign feels like it deletes half your work. The catalogue is fine. The storefront chrome around it is not.
The short version
Your products keep their translations. Your theme does not. A new theme is a new record, and it starts empty.
What usually goes wrong
The common sequence looks like this.
- The agency or the in-house developer duplicates the live theme and starts rebuilding.
- Everyone tests the new theme in the source language, usually English, because that is what the preview shows first.
- The theme is published on a quiet morning.
- The translated markets suddenly show English navigation, English buttons and English announcement bars.
- Someone re-runs the translation, and the store sits half translated while the job works through the strings.
Nothing here is careless. The translated markets are simply not part of the normal theme review. The translations lived on the old theme, so nobody had a reason to look.
The fix: translate the theme before it goes live
LocaleFlow lists every theme in your store, not only the published one. On the Online Store tab you get a “Themes to translate” list, with each theme labelled by its role.
- Live is the theme shoppers currently see.
- Unpublished is a theme sitting in your theme library, including a duplicate you are rebuilding.
- Development is a theme pushed from a developer’s machine with the Shopify CLI.
You tick whichever ones you want translated. The live theme can stay unticked, so the translation run touches only the new theme.
Then you click Restart translation. The card confirms with “Job queued. Translation will start shortly.” A green banner then reports that the job is active. New content will be translated automatically, and a Check status link sits next to it.
When it finishes, preview the unpublished theme with one of your languages selected. If the navigation, the buttons and the announcement bar read correctly, the theme is ready. Publish it, and the storefront is translated from the first minute.
What the translation run actually does
Each theme you tick is translated from your source language. LocaleFlow does not lift the strings out of your old theme and drop them into the new one.
That distinction matters more than it sounds. A rebuilt theme rarely uses the same strings as the old one, because sections get renamed, copy gets rewritten and new blocks appear. Translating from source covers the new strings, including the ones that never existed before.
Your controls still apply to the run:
- Custom term translations keep your fixed wording, so a term you decided on last year is used again.
- Blacklisted keys stay in the source language, which is what you want for brand names and product codes.
- Custom prompt and per-language prompts hold the brand voice, so the new theme sounds like the old one.
The result is a new theme in the same voice as the theme it replaces, without anyone re-typing a glossary.
A checklist for a theme relaunch
Use this in the week before you publish.
- Duplicate the live theme, or push your development theme, so it appears in the theme library.
- Finish the copy in your source language first. Translating a theme that is still changing wastes a run.
- Open LocaleFlow, go to the Online Store tab and tick the new theme. Leave the live theme unticked.
- Click Restart translation and wait for the job to complete.
- Preview the unpublished theme with each target language and read the chrome, not the products.
- Fix anything that reads wrong using custom terms, then re-run.
- Publish the theme.
- Tick the newly published theme so ongoing edits keep syncing, and untick the retired one.
Step 8 is the one people forget. After the switch, the theme you are actively editing should be the one LocaleFlow keeps in sync.
What else is theme-specific, and what is not
It helps to know which parts of a store follow the theme and which do not, because it tells you what to check after a redesign.
Theme-specific, so it needs the run above:
- Theme customizer content, including announcement bars, hero text and section headings
- Theme locale file strings, including button labels, cart text and form labels
Not theme-specific, so it survives untouched:
- Products, collections, pages, blogs and blog articles
- Metafields and metaobjects
- Menus, shop policies, storefront filter labels and delivery method names
- Image alt text and product option names
LocaleFlow covers all fifteen resource types, so the same setup handles both groups. The only thing a redesign changes is which theme record the theme content belongs to.
Do this once
Add the translation run to your theme launch checklist, right next to the speed test. It takes one click and it removes the worst launch-day surprise in a multilingual store.
Related reading
- Shopify translation not working? The full fix guide
- How to translate the Dawn theme on Shopify
- Translate custom Liquid sections in Shopify
- Translate your Shopify announcement bar
Try LocaleFlow with a free demo - see your actual store content translated.
