What Every Shopify Translate and Adapt Store Runs Into

A merchant emailed me last month. She sells handmade linen bedding out of Ghent, primary market Belgium, primary language Dutch, secondary French. She had added German three weeks earlier and expected T&A to do what it had done for French: press "Auto translate", wait a few minutes, edit the awkward sentences, publish. Nothing happened. The app showed the target language, showed the source strings, and quietly refused to translate them.

She was not doing anything wrong. She had hit the two-language auto-translation ceiling, which is the first of six things Shopify Translate and Adapt will do to a store that grows past its comfort zone. Nobody warns you before you install it. The app looks fine at launch. That is the whole problem.

I've walked merchants through this setup enough times that I now open every one of those conversations the same way: which language you're on, how many products in your catalog, and whether you have a page builder or a review app that stores its own content. Depending on the answers, my recommendation is either "stay on T&A" or "skip it and go straight to a paid tool." What follows is what I check when it's already installed and something has broken.

The two-language ceiling is still the two-language ceiling

Shopify Translate and Adapt launched in August 2022. A Shopify Staff member acknowledged the two-language auto-translation cap in a community thread that same month, said an expansion was "being considered," and gave no timeline. Four years later the cap is still two. If you need auto-translation for a third language, the app will not do it. You can add the language, and you can manually enter every string, but the "Auto translate" button stays greyed out.

For a store with fewer than fifty products, manual entry is annoying but survivable. For a store with three hundred products, five hundred metafield values, and eight collection pages, it is a project. This is where I lose about half the merchants I talk to. They hit the third language, do the math on the manual work, and start pricing paid apps.

The reason this ceiling matters more than most feature gaps is that it hides. You install T&A, translate to French, feel good about it, and tell yourself the tool handles multilingual. Then a wholesale customer in Germany asks whether you ship to Berlin, and you're back on the App Store looking for a third-party translation app. The two-language cap does not stop you from adding the third language. It stops the automation you assumed came with it.

The "Auto translate all" button is a footgun

If you use the bulk auto-translation action on a resource that already has manually corrected translations, T&A overwrites those corrections with fresh machine output. No warning dialog. No confirmation step. No undo. I have seen at least three merchants lose hours of copy work this way, and one of them lost a full afternoon of German product descriptions she'd rewritten because Google Translate had been calling her cotton sheets "kotton" in Dutch-influenced German.

The App Store reviews are blunt about this. A Swedish jewellery merchant left a one-star review in May 2026 saying every manually edited translation had been overwritten without any warning. Community threads from 2023 document the same complaint. Whether the trigger is truly the bulk auto-translate button or a separate feature called Store Contextualization that Shopify Staff have implicated in some of the same-symptom cases, the practical outcome is identical. Your corrections vanish.

If you're staying on T&A, the workaround is to export your translations to a spreadsheet before you touch the bulk action. T&A has an export function tucked into the app's overflow menu. Export, then auto-translate, then re-enter your corrections by hand. This is a bad user experience masquerading as a feature. It is also the only path I trust.

Third-party app content is invisible to Shopify Translate and Adapt

Shopify Translate and Adapt can only translate content that lives inside Shopify's own Translations API. If a page builder, subscription app, review widget, or checkout extension stores its text in its own database and only injects it into the storefront at render time, T&A cannot see it. The strings never even appear in the app.

The apps most commonly missed:

Page builders like PageFly, Shogun, and Replo, whose section content is stored on the vendor's side
Subscription apps like Subify, and some Recharge configurations that inject cart language
Review widgets that render star badges and review text from their own CDN
Checkout extensions that use custom fields defined outside the standard checkout schema

The diagnostic I ask merchants to run before recommending T&A is small: pull up your live storefront, open the browser inspector, right-click a piece of text you care about being translated, and check whether it's rendered by Liquid or injected by a third-party script. If it's the script, T&A will not touch it. You'll need a front-end translation tool like Weglot or Langify, which do their translation by rewriting the DOM after the page loads and can see everything the browser sees.

This is a deliberate API design, not a bug. richbrown, one of the Shopify Community moderators, has spelled it out repeatedly since 2023: apps that don't save content natively to Shopify's Translations API are untranslatable by T&A, full stop. Merchants who read that answer for the first time after building on T&A go quiet and then ask if there's a way to migrate. There isn't a clean one.

Transactional emails are their own multilingual problem

If you've been at the multilingual configuration for an afternoon and can't tell whether you need a new email app or a translation layer on top of your current one, the first fifteen minutes with a help1 expert is on us and that's usually enough time to draw the map.

T&A translates the storefront. It does not translate anything your email apps send. Order confirmations, shipping notifications, review request emails, abandoned-cart flows, loyalty updates, password resets - all of these go out in the store's default language unless the email app itself supports per-recipient language routing.

Most email apps do support this. Klaviyo, Judge.me, Omnisend, Loox - all of them will send in a customer's preferred language, and none of them do it by default. The support usually sits on a paid plan tier the merchant has not yet moved to. A Belgian merchant on r/shopify put it plainly in April 2026: her store operates in Dutch, German, and English, and her review request emails still shipped in English unless she upgraded her email app. The thread accumulated over a hundred comments. This is not an edge case, and merchants keep discovering it late.

Budget for it. The full multilingual stack for a small EU store is usually three separate things: the storefront translation layer (T&A, Weglot, or Langify), the email app's multilingual add-on for every email tool you use, and support chat translation if you're doing that live. The last two are line items the "free" framing on T&A obscures at decision time.

Weglot is the community default now, with one honest catch

When I tell a merchant Shopify Translate and Adapt is going to hit a wall on their setup, the next question is always the same: what should I use instead. Reddit threads through 2026 point to Weglot for stores expanding past two languages. Setup is faster, translation quality is closer to DeepL than to Google Translate, and hreflang and URL translation come without extra work. A merchant on r/shopify in May reported that roughly a third of their organic traffic came from German-language pages after moving off T&A. That's the SEO story I hear most.

The honest catch is billing. Weglot charges by word count. A large catalog on a small Weglot plan will exhaust its quota, and if you inadvertently translate archived or unpublished products first, you can leave your active inventory sitting untranslated on your live storefront. It is exactly the kind of thing a paid tool should surface as a warning and does not. Set your Weglot config to exclude archived and unpublished products before you press "Translate all" for the first time.

If you're a lower-catalog store and want the T&A pricing model with less Weglot polish, Langify is the community's other pick, usually described as sturdier for larger catalogs and closer to T&A architecturally. It uses Shopify's Translations API the same way T&A does, which means Langify can read T&A's existing translations on install - handy if you're migrating a live store and don't want to redo the work. Weglot's front-end architecture does not read from that store. If you're moving off T&A to Weglot, plan on retranslating everything.

If you want to see what a broken multilingual setup looks like from the storefront side once it's already live, my earlier post on where Shopify multilingual setup breaks walks through the same-day chase from a different angle.

Migrating off Shopify Translate and Adapt is worse than merchants expect

There isn't a clean export from T&A into Weglot. There is a workable path into Langify, because both apps read from the same Shopify translation data store. There is nothing clean from anywhere back to T&A either. Once you leave, the direction is one-way.

Two related traps I've seen this year:

Running two translation tools in parallel to get the best of both. A Shopify Community thread from 2024 documents a merchant who lost every existing T&A translation after adding a second tool alongside it. There is no recovery path. Do not install a second translation app while T&A is active, even if a support agent tells you the two can coexist.
Assuming API-level metafield updates re-trigger translations. If you're using Pipedream, Zapier, or a custom script to bulk-update product metafields, the default-language value updates and the translated value stays locked at the previous string. The fix is to write the translation update into the same automation using the translationsRegister GraphQL mutation, which is a developer-level change your automation partner has to make.

Take

The mistake merchants make with Shopify Translate and Adapt is treating it as the multilingual solution rather than the first ninety percent of one. It's a genuinely useful free tool for a narrow use case: one or two additional languages, a standard theme, no heavy metafield use, no page builder. Outside that window, it is a stepping stone that costs you time you cannot get back. Decide before you install it whether your store is going to grow past that window in the next year. If it is, skip the stepping stone.