Shopify Multilingual Mayhem: When Your English Translations Vanish & Your Store's Default Language Goes Rogue

Running a multilingual Shopify store is a fantastic way to reach a global audience, but sometimes, things can go sideways in the most unexpected ways. We recently followed a really eye-opening discussion in the Shopify Community that highlighted a complex issue where a store’s English translations seemingly vanished, and its default language configuration went completely haywire. It’s a story that every merchant with a multilingual setup needs to hear, because it reveals a crucial distinction between theme files and backend store settings.

The Mystery of the Missing English Translations

Our community member, rcnir, a Japan-based merchant with a live production store supporting 11 languages, encountered a nightmare scenario. After performing a seemingly innocuous drag-and-drop replacement of theme locale JSON files (including en.default.json) on July 8th, all their English translations disappeared. But it got weirder.

• Shopify started treating en (English) as the default language.
• However, when exporting translation CSVs, there was no en column.
• The “Default language” column in the CSV still contained Japanese content.
• A ja (Japanese) column appeared in the export, implying Japanese was a translated language, not the original source.

This bizarre inconsistency meant overseas customers couldn’t view the site in English, order notifications were acting up, and the entire multilingual display was broken. Sales and customer experience were taking a hit, and rcnir was rightly stressed, having halted all store operations.

Unpacking the Core Problem: Theme vs. Store Locale

This is where the community really shone, with experts like Khadar and HamidEjaz providing crucial insights. The “aha!” moment came from understanding that there are two separate systems at play:

1. Theme Locale Files: Files like locales/en.default.json are part of your theme. They handle UI strings, button labels, and other theme-specific text. Replacing these files can indeed “delete and recreate” theme locale resources.
2. Store’s Primary Language & Translation Resources: This is a deeper, store-level setting found under Settings > Languages. It dictates your store’s canonical default language and manages all your product, collection, notification, and other content translations.

The key takeaway from the discussion? Replacing theme locale JSON files should not ordinarily flip your store’s primary language on its own. Yet, in rcnir’s case, Shopify Support later confirmed that the store’s default language had indeed changed from Japanese to English, without any manual admin action or external app/API interference.

Why the CSV Export Was So Confusing

HamidEjaz clarified a point that initially seemed like another bug: the missing en column in the translation export. As he explained, “The translation export never includes the default or source language as a translatable column, only the languages you translate into.” So, if the system was mistakenly treating English as the source, it would naturally drop the en column from the export and show ja (Japanese) as a target language, even though Japanese was the original content. This “mismatch is the core symptom” of the underlying store-level inconsistency.

Immediate Action: The “Stop Everything” Rule

Given the severity and complexity of the issue, the unanimous advice from the community (and confirmed by rcnir himself) was to immediately halt all operations that could further complicate the situation. This means:

• NO importing translation CSVs.
• NO changing Markets language settings.
• NO switching default languages.
• NO running translation apps.
• NO bulk API translation updates.
• NO product or theme edits that might affect language.

As Khadar emphasized, “until engineering confirms the underlying state.”

A Safe Step: Rolling Back Your Theme

While the store-level issue required Shopify’s backend team, HamidEjaz offered a safe, reversible step for the theme files themselves: using theme version history. You can go to Online Store > Themes, open your theme’s menu, select Older versions, and roll back to a point just before the incident. rcnir successfully did this to isolate the theme aspect, confirming that the core problem remained at the store level.

The Backend Battle and Support Escalation

This entire saga underscored that some issues simply require Shopify’s internal technical team to investigate and restore. rcnir was advised to ask Shopify Support for specific confirmations:

• The current canonical default locale.
• Whether original translation resources still exist in the backend.
• If locale identifiers changed during the delete/recreate operation.
• Whether a backend restoration from before the incident is possible.

However, rcnir also shared a common frustration: the lack of clear communication and timelines from support, especially when a live production store is affected. Template-like replies of “we are checking” or “we have shared this with the relevant team” without specific updates or estimated completion times can be incredibly stressful for merchants.

Key Takeaways for Multilingual Merchants

This incident serves as a powerful reminder, especially for stores whose default/source language isn’t English:

• Understand the Distinction: Theme locale files and your store’s primary language are distinct. Changes to one shouldn't automatically break the other, but clearly, edge cases exist.
• Document Everything: If you encounter a similar issue, immediately take screenshots of all language settings, domain settings, and translation export behaviors.
• Stop, Don’t Touch: Resist the urge to “fix” things yourself with CSV imports, API writes, or manual language setting changes. You could inadvertently make the problem worse.
• Push for Backend Investigation: If something feels “off” at a fundamental level (like your store’s default language changing unexpectedly), it likely requires Shopify’s backend team. Clearly articulate that you believe it’s a store-level issue, not just a theme or translation app problem.
• Insist on Clear Communication: For live stores, emphasize the urgency and politely but firmly request specific updates, timelines, and which team owns the resolution.

While the exact cause of rcnir’s default language flip remains a backend mystery, the community discussion provided a clear path for diagnosis and safe action. It’s a testament to the power of shared knowledge and a stark reminder that sometimes, what looks like a simple theme file issue can be a much deeper, store-level language resource inconsistency that only Shopify’s technical team can truly resolve.