Shopify just made a subtle but powerful change to the GraphQL Admin API. Starting in API version 2026-10, every Metafield object now includes a non‑null translatable boolean field. This means apps can instantly see whether a metafield’s value can be translated, without relying on deprecated enums or hard‑coded rules. In this post we break down the change, who needs to act, and the exact steps to bring your integration up to speed.
What Changed: A New Boolean on Metafield
The Metafield type in the GraphQL Admin API now exposes a new field: translatable: Boolean!. When you query a metafield, the platform returns true if the value can be translated and false otherwise. For example:
{
product(id: "gid://shopify/Product/1") {
metafield(namespace: "custom", key: "care_guide") {
type # "single_line_text_field"
translatable # true
}
}
}
Before this release, apps had to query translatable metafields via the now‑deprecated TranslatableResourceType.METAFIELD enum in the translatableResources query. That approach required keeping a local copy of Shopify’s translatability rules, which could become stale as the platform evolves. The new boolean collapses all that logic into a single, always‑accurate field.
Who Is Affected
The change only impacts apps that:
• Use the GraphQL Admin API version 2026-10 or later, and• Explicitly fetch translatable metafields (for example, to surface translation UI in a custom app).
If your integration runs on API version 2026-07 or earlier, or if you never query translatable metafields, you can keep your existing code unchanged. The new field simply isn’t available on older versions, and the old enum continues to exist there as a deprecated fallback.
Why It Matters
Relying on the platform’s native boolean eliminates a common source of bugs. When Shopify updates which metafield types are translatable, your app no longer needs a manual sync. This reduces maintenance overhead and guarantees that merchants always see the correct translation options in your UI.
How to Update Your App
translatableResources(resourceType: METAFIELD) { ... }
remove that top‑level call and request the new field directly on the Metafield object instead.
if (metafield.translatable) { /* show translate button */ }
Testing and Validation
Create a test store, upgrade the app’s API version to 2026-10, and run a query against a known translatable metafield (e.g., a single_line_text_field). Verify that the translatable flag returns true. Then test a non‑translatable type (e.g., an integer) and confirm it returns false. Finally, confirm that any UI element that depends on this flag behaves as expected.
Conclusion & Next Steps
Shopify’s new translatable boolean on the Metafield object streamlines translation workflows and future‑proofes your code. By moving to API version 2026-10 and swapping out the deprecated enum, you’ll deliver a more reliable experience for merchants who sell in multiple languages. Need help with the migration or want a deeper dive? Reach out in the Shopify Community forums or contact our support team—we’re here to make the transition painless.
