The Shopify documentation has no any word about translation of a settings field value for a Checkout UI extension. Since it’s managed by a merchant then it should be translatable within an admin panel but I wasn’t able to find the place where it is presented. Does anybody know how can this be done? Or maybe you have a workaround for that. Please share.
Topic summary
A developer is seeking guidance on translating settings field values for Checkout UI extensions, noting that Shopify’s documentation lacks clear instructions on this topic.
Proposed Solutions:
- Third-party apps like Langify may support extension translations but could require additional configuration
- Shopify’s Translate & Adapt app can handle translatable settings fields, but developers must explicitly enable translation support when creating these fields
- Alternative approaches include using metafields to store values or leveraging TranslatableResource queries, though these methods appear incomplete or unclear
Current Status:
- The developer contacted Shopify’s dev assistant for implementation guidance
- Translation appears technically possible but documentation remains insufficient
- Uncertainty exists about which approach is most effective or fully supported
Apps like Langify support translating various parts of a Shopify store, including extensions. However, their support for dynamic fields inside a Checkout UI extension may require additional configuration or integration.
Well, I asked the support and got the next answer:
Yes, app Checkout UI extension settings fields can be translatable. Shopify provides an interface for this through the Translate & Adapt app. However, it is important to note that app developers need to enable translation support for each settings field they create. If the settings fields are not designed to be translatable by the app developers, they will not show up in the Translate & Adapt app for translation.
I don’t know how much true in this answer so I just went to their .dev Assistant on the shopify.dev portal and asked about the way to implement this. The suggestion was to use metafields to store the value from settings which is weird to me and not fully achievable. Another way is to use translatableResource queries which is not clear enough.
Anyway it looks possible, it should be possible but there’s too little information on this.