Shopify Translation API / Markets locales missing translations for products, themes, or checkout.

Several localization bugs look like “the market still shows English.” They do not share one engine. This page is only when Admin GraphQL Translation API / Markets locales leave product, theme, or checkout resource translations missing for a secondary locale — locale not registered on the market, translationsRegister never wrote the resourceId/key, outdatedLocale, primary fallback on PDP/theme/checkout copy. Hosted checkout UI language / Translate & Adapt checkout rows stuck in English are checkout language wrong. Markets Pro / managed markets duties vs landed cost is Markets Pro duties mismatch. Product metafield definitions not rendering on the theme are metafields not showing on storefront. Translate & Adapt storefront string UI without proving API registration is Translate & Adapt missing strings. This page is only: Shopify Translation API / Markets locales missing translations for products, themes, or checkout.

Six ordinary reasons translations stay missing: locale enabled in Languages but not assigned / published on the market; translationsRegister never called for PRODUCT title/body_html / SEO keys; ONLINE_STORE_THEME or CHECKOUT resource keys never registered; theme locale JSON missing for the secondary language while primary works; translation / ERP / PIM app that overwrites primary content and skips Translation API; or you are debugging checkout UI language, Markets Pro duties, or metafield display instead of locale registration + resource translations. Walk them in that order. You already pay for Shopify. You do not need another “locale SaaS” to prove shopLocales equals rendered secondary-locale content.

Open Settings → Languages and Markets → the market → Languages / domains / subfolders. Screenshot primary vs published secondary locales. If you use Admin API, query shopLocales / availableLocales and translatableResource for a known product GID, an ONLINE_STORE_THEME resource, and a CHECKOUT / EMAIL_TEMPLATE resource. Keep the last translationsRegister / translationsRemove response (including userErrors) and any translation-app sync log that claims “100% translated.”

Reproduce on the live market URL (not a stale tab or primary domain only): open the secondary-locale product URL — title/body/SEO should match registered translations. Hard-refresh theme chrome (nav, cart drawer, buttons) and start checkout on that market. If only the hosted checkout chrome language is English while product translations exist, leave this page and use checkout language wrong. If duties / import tax lines are wrong, open Markets Pro duties mismatch. If only metafield values are blank on the theme, open metafields not showing on storefront.

Enable and publish the locale on the market (language assignment + domain/subfolder live). Register translations for PRODUCT / PRODUCT_OPTION / PRODUCT_VARIANT title, body_html, meta_title, meta_description via Translation API or Translate & Adapt. Register ONLINE_STORE_THEME and CHECKOUT resource keys the buyer actually sees. Fill theme locale JSON for the secondary language and publish the theme — draft theme locale files never hit the live storefront.

Pause or reconfigure ERP / PIM / translation apps that write only primary product fields and never call translationsRegister, or that leave outdatedLocale after primary edits. After Save / register, hard-refresh the market URL logged out and retest PDP + theme chrome + checkout copy. If Translate & Adapt UI shows gaps but you have not proven API registration, also walk Translate & Adapt missing strings. If checkout chrome language alone stays English after product translations render, use checkout language wrong.

Checklist: (1) screenshot Languages + market language assignment, (2) confirm shopLocales includes the secondary locale published, (3) query translatableResource for product / theme / checkout GIDs, (4) register missing keys via translationsRegister or Translate & Adapt, (5) fill theme locale JSON and publish, (6) stop apps that skip Translation API or leave outdatedLocale, (7) prove market URL shows translated PDP + theme chrome + checkout resource copy, (8) if only checkout UI language / duties / metafields remain wrong, switch playbooks.

Prove it: on a live secondary-locale market URL, open a product whose translationsRegister payload includes title + body_html — storefront must show those strings, not primary English. Theme nav/cart labels must match theme locale JSON. Checkout resource strings you registered must appear. If product translations are correct but hosted checkout language is still English, open checkout language wrong.

Hosted checkout UI language stuck in English is checkout language wrong. Markets Pro duties / landed cost mismatch is Markets Pro duties mismatch. Product metafields not rendering are metafields not showing on storefront. Translate & Adapt storefront string UI without API proof is Translate & Adapt missing strings. None of those fix Translation API / Markets locales missing translations for products, themes, or checkout resource keys.

Finish prove shopLocales + translatableResource → register missing keys / publish locale / theme locale JSON → live market URL proof first. Only then open the related playbook that matches the remaining symptom.

Stay DIY if you can spend one afternoon on the list above: prove shopLocales vs translatableResource, register missing product / theme / checkout keys, publish the market locale, stop apps that skip Translation API, prove secondary-locale render, and stop treating checkout language / Markets Pro duties / metafields as the same bug. That is the whole playbook. No agency required. Short answers also live on the merchant FAQ. Related pages: Checkout language, Markets Pro duties, Metafields, Translate & Adapt strings.

Pay $997 when the gap is wiring — lead capture, ops alerts, and a checkout-ready workflow on the stack you already pay for, including Translation API / Markets locale translation exceptions landing in a channel you already check. Clock starts when collaborator access is in. 72 hours. One live store. Latch does not sell an earnings or ops-efficiency number. No invented case studies.

Buy the 72-hour install — $997Merchant FAQHome