Back to Intelligence
Platform UpdatesGlobal

Shopify adds a direct translatability flag to Metafield queries in API version 2026-10

The change mainly affects apps that fetch translatable metafields and move to 2026-10; merchants whose apps only read metafield values may not need to do anything.

Ecomwith EditorialEcommerce intelligence desk

Published
Updated
Risk
low

Reported details

What happened

The official Shopify Developer Changelog says API version 2026-10 adds a non-null translatable Boolean field to the Metafield object in the GraphQL Admin API.

Apps on 2026-10 or later that fetch translatable metafields can read that status directly from each metafield instead of using the deprecated TranslatableResourceType.METAFIELD value on translatableResources.

Apps on API version 2026-07 or earlier are unaffected by the new field; the deprecated enum continues to exist on those versions.

Shopify says the change adds no feature preview or access scope, and apps that do not query for translatable metafields do not need to change anything.

Business relevance

Why it matters

For app teams supporting translated product content, a field on the metafield itself may reduce the need to maintain separate logic for identifying translatable metafields.

The practical impact is version-dependent: the new field appears only when a request uses API version 2026-10 or later, so changing an app's API version and changing its query path are related but separate decisions.

Editorial perspective

Analysis & judgment

  1. This is primarily an app-maintenance update rather than a new merchant-facing feature. Its relevance rises for stores using custom or third-party apps that inspect metafield translatability as part of localization workflows.

  2. If an app supports several Shopify API versions, its owner should verify the version-specific query behavior before replacing the deprecated enum. A store does not need to force an API-version change solely because this field exists.

Applicability

Seller impact

Merchants using an app that fetches translatable metafields may need to confirm that the app handles the 2026-10 query path before the app migrates.

Merchants whose apps only read metafield values, or whose apps remain on 2026-07 or earlier, have no stated change to make based on this update.

Action plan

What to do now

  1. 1

    Identify whether any connected app queries translatable metafields

    now

    If your store uses a custom integration or localization app that checks metafield translatability, ask its owner which Shopify API version it uses and whether it relies on TranslatableResourceType.METAFIELD.

  2. 2

    Coordinate any planned move to API version 2026-10

    this-week

    For an app scheduled to use 2026-10 or later, have the developer test reading translatable from the Metafield object before retiring the older query path.

  3. 3

    Leave unaffected integrations unchanged

    monitor

    If no connected app queries translatable metafields, or if the relevant app remains on 2026-07 or earlier, monitor the app vendor's version plan rather than changing store configuration.

What not to do yet

  • Do not change API versions or add access scopes solely because this field was introduced; the supplied Shopify notice says availability depends on the API version and that no new scope is required.

Sources & context

Evidence and sources

A source may provide only a headline or summary. Read the evidence scope below. Links and workflow checks are not independent fact verification. Internal confidence values are workflow signals, not probabilities of factual correctness.

  1. 01

    API version 2026-10 adds a non-null translatable field to the Metafield object in the GraphQL Admin API. Apps that fetch translatable metafields and migrate to 2026-10 can now see whether a metafield’s value is translatable directly on the metafield itself. If your app doesn’t query for translatable metafields by shop, you don’t need to change anything. What changed The Metafield object in the GraphQL Admin API exposes a new non-null field, translatable: Boolean!, in API version 2026-10: { product(id: "gid://shopify/Product/1") { metafield(namespace: "custom", key: "care_guide") { type # "single_line_text_field" translatable # true } } } translatable returns the result that the platform already enforces when it decides whether a metafield’s value can be translated. Before this change, apps had to use the deprecated TranslatableResourceType.METAFIELD enum on translatableResources to query for translatable metafields. On API version 2026-10 and later, you should read translatable on the Metafield object instead of querying metafields through translatableResources. Who's affected This applies to apps that: Call the GraphQL Admin API on version 2026-10 or later, and Fetch translatable

    Shopify Developer Changelog · Workflow status: single-source

    Source link

    Retrieved: September 21, 2026 at 04:07 p.m. UTC

    Claim is bounded to the ingested title or summary; no source body or quotation is retained.

Related tutorials and tools

Ecomwith tutorials
Shopify adds a direct translatability flag to Metafield queries in API version 2026-10 - Ecomwith Intelligence