Checkout Extension Translations: Build or Buy the Localization?
Checkout extension translation DEPENDS entirely on who owns the extension, because Shopify states merchants can't override or add translations. Locale files ship inside the extension bundle, and that bundle can't exceed 64 KB. BUY a vendor's extension for commodity checkout content and inherit its languages as they are. BUILD when the wording is yours, and own every locale file for every market forever.
Your profile — see how the verdict shifts
- Confidence
- High — Three verbatim sentences from Shopify's localized checkout UI extensions page settle this, all re-read on 2026-09-05. You supply translation data for your extension's strings in .json-formatted locale files, which are stored in the extension's locales folder. Merchants can't override or add translations. Localization is only supported for checkout UI extensions, and localization for post-purchase extensions isn't supported. The middle sentence is the one that decides the page, because it removes the option most teams assume they have. A merchant who dislikes a vendor's German string cannot fix it, and a merchant who needs a language the vendor never shipped cannot add it. Translation ownership therefore follows extension ownership exactly, with no third path. Two more facts set the cost of owning it. The compiled UI extension bundle can't exceed 64 KB and Shopify enforces this limit at deployment, so every locale file competes for the same budget as the code. Checkout UI extensions that render on the information and shipping and payment steps in checkout are available only to stores on a Shopify Plus plan. Verification also established what does not apply: the three translation apps read the same day are Shopify Translate & Adapt (4.5★, 1,440 reviews), Weglot (4.5★, 788 reviews) and langify (4.7★, 680 reviews), all healthy listings, and none of them reaches extension strings, because the override merchants would need does not exist. Naming that boundary plainly is the point of this page.
- Reference scenario
- $20M–$100M GMV · Shopify Plus · checkout UI extensions live across 4 or more market locales · agency or in-house dev bench
- As of
- September 2026
Decision at a Glance
| Your profile | Verdict | Why |
|---|---|---|
| One market, one language | WAIT | One locale file covers it and nothing is at stake yet. Revisit the day a second market opens, because adding a language later is a bundle change rather than a settings change. |
| Several markets · standard checkout content | BUY | A vendor's extension arrives with its languages already written and maintained. Check the language list before installing, since merchants can't override or add translations afterwards. |
| Several markets · wording that carries legal or brand weight | BUILD | A returns clause or a compliance line has to say what your counsel approved, in every language. Inheriting a vendor's phrasing with no override is not an option here. |
| Many locales · a mix of standard and proprietary blocks | DEPENDS | Split the surface. Buy the commodity blocks and accept their languages; build only the block whose wording you must control, and pay for its locale files every release. |
What Checkout Extension Localization Actually Drives
| Outcome | Impact | How it works |
|---|---|---|
| Customer experience | High | A shopper in a French checkout reading an English delivery clause loses confidence at the payment step, which is the least forgiving place on the site for a language gap. |
| Revenue — direct | Medium | Checkout copy in the shopper's own language reduces hesitation at the moment of payment, where abandonment is both most likely and most expensive. |
| Operational efficiency | Medium | Owning locale files puts every string change in one release pipeline instead of a support conversation with a vendor who may or may not agree to it. |
| Retention & LTV | Low | Consistent language across markets builds the sense of a brand that operates locally, which shows up over repeat purchases rather than in a single session. |
Spend ceiling: Spend on translation ownership only where the words matter enough to defend. Commodity blocks are worth a vendor's languages exactly as they come. Legal, returns and compliance wording is worth owning outright, because merchants can't override or add translations and there is no cheaper remedy once a wrong string is live in 4 markets.
What buying enables (top apps)
- + Checkout blocks that arrive already translated and maintained, with no locale files for your team to own
- + A vendor absorbing translation upkeep across every wording change it makes to its own extension
- + Storefront and theme translation solved separately and cheaply, from a free first-party app upward
What building additionally unlocks
- + Every string in every language under your control, with no vendor phrasing you are stuck with
- + Locale files as versioned .json that move between extensions, storefronts and future surfaces
- + Legal and compliance wording that reads as counsel approved it in each market you sell into
- + A new market's locale added on your schedule rather than on a vendor's roadmap
Find Your Verdict in 3 Questions
Do you sell into more than one language today or within the next year?
Yes: Go to question 2.
No: Your verdict: WAIT — one locale file covers a single market, and the decision reopens the day a second one does.
Does the checkout wording carry brand, legal or compliance weight you must control?
Yes: Your verdict: BUILD — merchants can't override or add translations, so owning the extension is the only way to own the words.
No: Go to question 3.
Does a vendor's extension already ship every locale your markets need?
Yes: Your verdict: BUY — inherit its languages and check the list again before you open a new market.
No: Your verdict: DEPENDS — split the checkout by block, buying the covered ones and building only where coverage runs out.
The TCC Scorecard — 12 Dimensions
TCC — Total Cost of Capability: what it actually costs to have this capability over three years, whichever way you get it. Each dimension is scored 0–5 for both paths. How we score →
| Dimension | Buy | Build | Why |
|---|---|---|---|
| Cost | |||
| Acquisition & implementation | A listed extension installs already translated; your own means a locale file per market plus a translation workflow before launch. | ||
| Recurring fees | Vendor extensions carry a subscription; an owned extension carries translation cost instead, which is per-string rather than per-month. | ||
| Maintenance & upgrades | The decisive cost row: every wording change you make has to be re-translated into every locale file and released, forever. | ||
| Switching & exit | A vendor's translations leave with its extension; your locale files are .json in your repository and move anywhere. | ||
| Risk | |||
| Vendor risk | A vendor that drops a language, or renders it badly, leaves no remedy at all, since merchants can't override or add translations. | ||
| Security & compliance surface | Compliance wording in a market you sell into is your legal exposure, and a vendor's string is one you cannot correct. | ||
| Platform-deprecation exposure | Localization is supported only for checkout UI extensions, and post-purchase extensions get none, which narrows where either lane applies. | ||
| Value | |||
| Fit to requirement | A vendor ships the languages and phrasing its roadmap chose; your locale files say what your brand and counsel actually approved. | ||
| Time to market | Live this week against 3–7 weeks for a custom extension plus translation rounds (Deploi estimate, illustrative). | ||
| Performance & scale | Locale files ship inside a compiled bundle capped at 64 KB, so each added language competes with the code for the same budget. | ||
| Data ownership & AI-readiness | Translations you own are .json in version control, reusable across surfaces; a vendor's strings are readable only inside its extension. | ||
| Focus & opportunity cost | Running a translation pipeline for checkout strings is real recurring work, and worth it only for wording that genuinely has to be yours. | ||
The App Landscape
| App | Status | Pricing | Best for |
|---|---|---|---|
| Category: checkout extension apps that ship their own translations | Category — The real buy lane for extension localization is buying the extension itself, because translation ships inside its bundle and merchants can't override or add translations. App Store checkout categories carry extensions in several languages, and the language list is a pre-install question rather than a setting you can change later. Ask which locales a listing ships and what happens when you open a market it doesn't cover. | Varies by listing; the language list is the thing to check before installing (verify) | Commodity checkout content where a vendor's language coverage is genuinely good enough |
| Shopify Translate & Adapt | Native — The post-Weglot default: machine translation plus manual edits, with translations stored portably in Shopify (July 2026 research) | Free — included with Shopify | Storefront and theme translation, which is a different surface from checkout extensions |
| Weglot: AI Translation & SEO | Live — 4.5★, 788 reviews; Built for Shopify. Priced by language count and translated word count, which is the shape of storefront translation rather than extension localization. Included to mark the boundary: no plan on this listing reaches an extension's locale files, since merchants can't override or add translations for checkout UI extensions. | Free (1 translated language, 2,000 translated words); Starter $17 / month (1 language, 10,000 words); Business $32 / month (3 languages, 50,000 words); Pro $87 / month (5 languages, 200,000 words); 14-day free trial (verified Sep 2026) | Storefront translation at scale, alongside a separately owned extension strategy |
| langify — translate your store | Live — 4.7★, 680 reviews; Built for Shopify. The free plan carries unlimited manual translations across up to 5 languages, and Basic lifts that to 20 languages with third-party app translation for storefront-rendered content. Same boundary as the others: checkout UI extension strings live in the extension bundle and stay outside any translation app's reach. | Free $0/month (unlimited manual translations, up to 5 languages); Basic $17.50/month (up to 20 languages, third-party app translation); Growth $29.95/month (bulk translations); Premium $59.95/month (priority support); free plan available in lieu of a trial (verified Sep 2026) | Manual, high-control storefront translation across many languages |
| Locale files in your own extension bundle (custom app) | Build lane — Translation data supplied as .json-formatted locale files in the extension's locales folder, shipped with the bundle and versioned with the code. Requires Shopify Plus for extensions on the information, shipping and payment steps. The compiled bundle can't exceed 64 KB, which every added language eats into, and each wording change is a re-translation plus a release. | $14,000–$36,000 one-time for the extension and its first locale set plus ongoing translation (Deploi estimate, illustrative) | Plus merchants whose checkout wording carries brand, legal or compliance weight |
The Build Path
- Decide ownership per block, not per checkout: A checkout usually holds several extension blocks, and they do not all need the same answer. A delivery-date picker is commodity and its vendor's Spanish is fine. A returns clause your counsel wrote is not, and its Spanish has to be the one counsel approved. Buy the first, build the second, and stop treating localization as one decision.
- Structure locale files for change, not for launch: Translation data lives in .json-formatted locale files in the extension's locales folder. Key every string once and reuse it, because the recurring cost is not the first translation round, it is the fourth time somebody rewords a sentence and it has to travel through every language you ship. Keep a source-of-truth locale and generate the rest from it.
- Budget the 64 KB bundle across code and languages together: Shopify enforces the compiled bundle ceiling at deployment, so a release fails rather than a review catching it. Locale files count. Ten locales of verbose legal copy is a real share of the budget, and the fix is shorter strings and fewer of them rather than a bigger bundle. Measure the bundle in CI with every language enabled.
- Put translation in the release checklist, permanently: No merchant can override or add a translation after the fact, which means there is no safety valve between a wrong string and a shopper reading it. Every copy change needs a translation pass and a release before it reaches a non-English market. Teams that treat this as a launch task ship English strings into French checkouts within a quarter.
- Effort band
- $14,000–$36,000 for one custom checkout extension with its first locale set — Deploi estimate (illustrative); lands in the $25–75K contact-form band, and translation is a recurring line beyond it
- Typical timeline
- 3–7 weeks for the extension, plus a translation round per market before launch (Deploi estimate, illustrative)
- Maintenance, honestly
- ~15–20% of build cost per year (Deploi estimate): roughly $2,100–$7,200/yr (Deploi estimate, illustrative) for checkout API version bumps and a translation pass on every wording change, across every locale you ship.
- What you own — and what you take on
- You own: every string in every language, the locale files as versioned .json, and the right to change any of them without asking a vendor. You take on: a translation pass on every copy change, the 64 KB bundle shared between code and languages, and Shopify Plus for extensions on the core checkout steps.
3-Year Total Cost of Capability
| Buy (app path) | Build (custom path) | |
|---|---|---|
| Year 0 (setup) | $0–$1,200 (illustrative) | $14,000–$36,000 (Deploi estimate, illustrative) |
| Years 1–3 (recurring) | $1,080–$3,600 (illustrative) | $6,300–$21,600 (maintenance and translation, Deploi estimate) |
| 3-year total | ≈$1,080–$4,800 (illustrative) | ≈$20,300–$57,600 (Deploi estimate) |
- † All figures illustrative samples for the reference scenario — not quotes, not verified pricing.
- † Left column is a vendor checkout extension at a mid subscription tier, with its languages included and unchangeable.
- † Right column is one custom extension plus a translation pass per market, over 4 locales; three-year horizon.
What the Sticker Price Hides
On the buy path
- — A vendor's language list is fixed at install, since merchants can't override or add translations for checkout UI extensions
- — Opening a market the vendor doesn't ship a locale for leaves shoppers reading another language at the payment step, with no admin remedy
- — Market overrides for checkout branding reach Advanced and Plus, but branding is styling rather than wording, and extension strings sit outside it
- — Translation apps priced from free to $87/month cover storefront content and do not reach extension strings (verified Sep 2026)
On the build path
- — Every wording change becomes a translation pass across every locale plus a release, with no way for a merchant to patch a string meanwhile
- — Locale files count against the 64 KB compiled bundle ceiling, which Shopify enforces at deployment rather than at review
- — Localization is supported only for checkout UI extensions, so a post-purchase extension gets none of this and needs a different plan
- — ~$2,100–$7,200/yr upkeep and translation (Deploi estimate, illustrative)
What Merchants Say
International managers describe finding the wrong phrasing in a live checkout and discovering there is no field to fix it, because the string belongs to the extension rather than to the store.
The recurring translation-app complaint is coverage boundaries: the app translates the storefront well and then stops exactly where the merchant most needs it, at surfaces it was never able to reach.
If You Change Your Mind Later
If you bought and outgrow it
Uninstalling a vendor's checkout extension removes its blocks and its languages together, and nothing of the translation work survives, since none of it ever lived in your store. Record which locales the extension covered before you leave, because that list is the requirement your replacement has to meet.
If you built and want out
Locale files are .json in your repository and go wherever you do, including into a different extension or a different storefront. Nothing is stranded. The dependency that stays behind is Shopify Plus, without which extensions on the information, shipping and payment steps stop being installable.
When This Answer Changes
We're watching for:
- ▸ Any Shopify change letting merchants override or add translations for checkout UI extensions, which would reopen the buy lane completely
- ▸ Localization support extending to post-purchase extensions, which Shopify's page currently rules out
- ▸ A change to the 64 KB compiled bundle ceiling, which today makes each added locale a budget decision
Verdict change log:
No changes since first publication (September 2026).
Common Questions
Can merchants translate a checkout UI extension themselves?
No. Shopify states plainly that merchants can't override or add translations for checkout UI extensions. Translation data is supplied in .json-formatted locale files stored in the extension's locales folder, which means every language ships with the bundle. Localization is supported only for checkout UI extensions as of September 2026, and post-purchase extensions get none at all.
Do translation apps cover checkout UI extensions?
No. Weglot, langify and Shopify Translate & Adapt translate storefront and theme content, and their pricing runs from free to $87/month (verified Sep 2026). None of them reaches a checkout UI extension's strings, because Shopify states merchants can't override or add translations for those extensions. The language list belongs to whoever built the extension.
What does adding a language to a custom checkout extension cost?
Each language is a locale file inside the extension bundle, and Shopify caps that compiled bundle at 64 KB. Adding a market means a new .json file, a pass over every string, and a release. Changing one sentence means changing it in every locale file you ship. Budget translation as an ongoing line rather than a launch task.
Your Next Steps
If you're going with BUILD
- List every checkout string and mark which ones carry brand, legal or compliance weight
- Structure locale files around reusable keys, with one source-of-truth locale others are generated from
- Measure the compiled bundle in CI with every language enabled, against the 64 KB deployment ceiling
- Put a translation pass into the release checklist so no wording change ships English into a non-English checkout
- Confirm Shopify Plus for any extension rendering on the information, shipping or payment steps
If you're going with BUY
- Ask the vendor for its exact locale list before installing, since you cannot add one later
- Read the extension's strings in each of your markets, not just in English
- Check what happens on a market whose locale the extension does not ship
- Diary a re-decision for the next market launch, when the language list becomes a live constraint again
Official Docs & Sources
- Localized checkout UI extensions — shopify.dev
- Checkout UI extensions API reference — shopify.dev
- Checkout extensibility technologies and plan gates — shopify.dev
Official documentation linked for verification — our verdicts and estimates are our own.
Related Decisions
Should You Build or Buy Bulk Channel Publishing on Plus?
No app bulk publishes products to your own channels and markets. On Plus, a small custom app on two exclusive GraphQL mutations does the job.
Per-Store App Fees or a Shared Hydrogen Front End on Plus?
Apps bill per store and theme licenses repeat per store on Plus. A shared Hydrogen front end removes the theme fee and little else. Go headless for other reasons.
Expansion Store vs. Shopify Markets: Which Fits a New Region?
Markets keeps a new region on the store you have. An expansion store fits a new brand or entity; nine are free on Plus, but apps and themes bill again per store.
Should You Plan Around Plus's 25-Hydrogen-Storefront Cap?
Plus documents up to 25 Hydrogen storefronts, and no app can lift that entitlement. The ceiling that arrives first is the number of codebases you can maintain.
Should You Build or Buy Multi-Currency & Market Pricing on Shopify?
Multi-currency is native on Shopify. The real decision is the market-pricing layer on top.
Shipping checkout content into more than one language?
We split the checkout surface block by block, buy the ones whose vendor languages are good enough, and own the locale files for the wording your brand and counsel need to control.
Contact us todayVerdict scored for the reference scenario above. Estimates are not quotes; app pricing carries its verification date and gets re-verified quarterly. Full scoring anchors: see the TCC methodology.
Read how we score these decisions (the TCC Framework). No affiliate links, no paid placement — no app vendor pays to appear here.