Metafield.translatable on each owner resource to decide whether a metafield value supports translation. If registering translations, fetch the content digest with translatableResourcesByIds. Do not substitute Metafield.compareDigest; Shopify documents that the two digests are different.On this page
Why the old shop-wide approach is misleading
Shopify introduced Metafield.translatable: Boolean! on September 21, 2026. Translatability depends on both metafield type and the owner resource, so a shop-wide translatableResources(resourceType: METAFIELD) enumeration isn’t a good long-term classifier. The METAFIELD enum value is deprecated but still works for now; Shopify will announce its removal separately. This isn’t a requirement to migrate every app that merely reads metafield values.
Discover values through their owners
Query products, collections or other relevant owners and paginate their metafields. Inspect the new boolean on each metafield. You cannot filter Shopify’s metafield connection directly by translatable, so filter returned nodes in your app. If you previously scanned all metafields in a shop, enumerate the owner types you support and consider bulk operations for large datasets. A single product query is not a complete shop-wide replacement.
Example: inspect product metafields
query ProductMetafields($id: ID!) {
product(id: $id) {
metafields(first: 50) {
nodes { id namespace key type translatable }
pageInfo { hasNextPage endCursor }
}
}
}
Call this against Admin GraphQL 2026-10 or later with the appropriate owner read scope. Keep paginating until all relevant values are inspected. A false value means the app should not offer translation for that value.
Register translations with the correct digest
For each translatable metafield ID, request translatableResourcesByIds and read its translatableContent entry for key value, including the content digest. Pass that digest as translatableContentDigest to translationsRegister with the metafield resource ID, locale, key and translated value. The separate compareDigest is for metafield concurrency semantics and is not interchangeable. Handle mutation user errors and refresh digests when the source content changes.
Markets and storefront verification
Confirm the target locale is enabled and published for the intended market, and verify the translated metafield appears in the actual storefront context. A successful Admin API mutation alone doesn’t prove the theme renders that metafield or that the visitor’s locale selects the translation.
How to test this
- Create one translatable text metafield and one non-translatable metafield on a test product.
- Query both on API 2026-10; verify the boolean matches Shopify’s translation eligibility.
- Fetch
translatableResourcesByIdsfor the eligible metafield and register a test locale translation using its content digest. - Change the source value and verify stale-digest handling before retrying with a refreshed digest.
- Visit the published locale/market storefront and verify the translated value, not merely the API response.

