Storefront languages
A MyShopie storefront can sell in 18 languages. You pick a default language and as many additional ones as you want, and the storefront UI, your product content, your pages and your theme copy all follow the shopper’s choice. Auto-translation fills the gaps so adding a language does not mean rewriting your catalog.
Plans: All plans
Prerequisites
Section titled “Prerequisites”- Permission to manage settings.
- A decision about which languages you will actually support. A half-translated language is worse for trust than one language done well.
The 18 supported languages
Section titled “The 18 supported languages”| Code | Language | Code | Language |
|---|---|---|---|
en |
English | fi |
Finnish |
de |
German | no |
Norwegian |
fr |
French | cs |
Czech |
es |
Spanish | ro |
Romanian |
it |
Italian | hu |
Hungarian |
nl |
Dutch | el |
Greek |
pl |
Polish | tr |
Turkish |
pt |
Portuguese | ar |
Arabic (right-to-left) |
sv |
Swedish | da |
Danish |
English is the universal fallback. Any string with no translation in the shopper’s language falls back to English rather than showing a blank or a raw key.
Choose your languages
Section titled “Choose your languages”-
Go to Settings → General and find the Languages & storefront section.
-
Pick your default language. This is what a shopper sees before they choose anything, and it is the language you author original content in.
-
Tick every supported language you want available. Your default language is always included and cannot be unticked.
-
Decide on auto-translate. On by default: new product names and descriptions are translated into your supported languages by a background job, so you create a product once.
-
Save. The language switcher in your storefront header reflects the change.
What is translatable
Section titled “What is translatable”| Content | Where you translate it |
|---|---|
| Storefront UI — buttons, labels, cart, checkout | Built in; nothing to do |
| Product names, descriptions, slugs | Per-language on the product, auto-translated when enabled |
| Category and attribute names | Per-language in the catalog |
| Theme copy — headings, button labels, empty states | Per-language in the customizer |
| Section content — hero text, rich text, CTAs | Per-language in the customizer |
| Announcement bar, newsletter block, footer copy | Per-language on those screens |
| CMS and legal pages | One page per language |
| FAQs | One FAQ per language |
| Email and invoice templates | Per-language templates |
Editing per language
Section titled “Editing per language”Every translatable field in the customizer is a per-language field. The editor has a language picker, and switching it switches every field on the panel to that language — the field itself does not change, only which language’s value you are editing. Your store’s default language is always offered first.
Locking a translation
Section titled “Locking a translation”Auto-translation is useful and occasionally wrong. Each per-language field can be locked, which pins the value you wrote and makes auto-translation skip it.
Lock a translation when:
- It is a product or brand name that should not be translated at all.
- It is legal text that a native speaker reviewed.
- It is copy a translator wrote and you do not want a machine improving on it.
- It is a technical term your industry uses in its original form.
Everything else is better left unlocked, so adding a language keeps filling it in automatically.
Arabic and right-to-left
Section titled “Arabic and right-to-left”Arabic switches the storefront to right-to-left. The layout mirrors — navigation, product grids, buttons, form fields — rather than simply reversing the text. If you support Arabic, look at your own storefront in it once, particularly any section with an image on one side and text on the other, because mirrored asymmetric layouts are where a design most often shows its seams.
Languages and currency are separate
Section titled “Languages and currency are separate”Your store currency is set independently under Settings → General, with its own display format. A shopper reading your storefront in French is not necessarily paying in euros, and choosing a language does not change the price they pay. Set the currency to match your actual bank account and tax position, not the language.
Common problems
Section titled “Common problems”A language is missing from the switcher. It is not ticked as supported, or your theme’s header has the switcher hidden.
Some text is English in another language. That string has no translation yet, so it falls back. Fill it in, or leave auto-translate on and let the job catch up.
A product never got translated. Auto-translate was off when it was created, or the translation job has not run yet. Re-save the product, or translate the field by hand.
Auto-translation replaced wording you wrote. Lock the field. Unlocked fields are fair game for the job.
Your default language cannot be unticked. That is intentional — it is the language the storefront falls back to before English.
Arabic looks broken in one section. A hard-coded left or right alignment in custom HTML does not mirror. Use the section’s own alignment setting instead.
How many languages does a MyShopie storefront support? Eighteen: English, German, French, Spanish, Italian, Dutch, Polish, Portuguese, Swedish, Danish, Finnish, Norwegian, Czech, Romanian, Hungarian, Greek, Turkish and Arabic.
How does a shopper’s language get chosen? From their own choice in the storefront language switcher, falling back to your store’s default language. Anything with no translation falls back to English.
Will auto-translation overwrite a translation I wrote myself? Not if you lock that field. A locked translation is pinned and auto-translation leaves it alone, which is how you protect product names, brand terms and legal text.
Is Arabic right-to-left? Yes. Arabic renders the whole storefront right-to-left, so the layout mirrors rather than just swapping the words.
