Locale: Supported content & limitations
- Bartosz Lewandowski
- Damian Rozmiarkowski
Introduction
At the time of publication, January 2024, these are the current resource types and status which can be accessed and processed for translation by Locale. As we continue to modify and update this connector, as well as work with updates that may come from Shopify in the future, this list is likely to change.
Supported content
The following is a list of content which can be accessed for translation by Locale, and will appear (if it exists) within your Locale instance during / after the analysis phase of your project.
Resource Type | Definition | Translatable Fields | Status |
Collections | A product collection. | title, body_html, handle, meta_title, and meta_description | All (published, unpublished, draft, archived) |
Delivery method definitions | The delivery method definition. For example, "Standard", or "Expedited”. | name | All (published, unpublished, draft, archived) |
Email templates | An email template. | title, body_html | All (published, unpublished, draft, archived) |
Links | A link to direct users. | title (also see limitations below) | All (published, unpublished, draft, archived) |
Online store articles | An online store article. | title, body_html, summary_html, handle, meta_title, meta_description. | All (published, unpublished, draft, archived) |
Online store blogs | An online store blog. | title, handle, meta_title, meta_description. | All (published, unpublished, draft, archived) |
Online store menus | An online store menu. | title. | All (published, unpublished, draft, archived) |
Online store pages | An online store page. | title, body_html, handle, meta_title, meta_description. | All (published, unpublished, draft, archived) |
Online store themes | An online store theme. | dynamic keys based on theme data. | All (published, unpublished, draft, archived) |
Packaging slip templates | A packing slip template. | body. | All (published, unpublished, draft, archived) |
Payment gateways | A payment gateway. | name. | All (published, unpublished, draft, archived) |
Products | An online store product. | title, body_html, handle, product_type, meta_title, meta_description. | All (published, unpublished, draft, archived) |
Product options | An online store custom product property name. For example, "Size", "Color", or "Material". | name. | All (published, unpublished, draft, archived) |
Product variants | An online store product variant. | option1, option2, option3. | All (published, unpublished, draft, archived) |
Shops | A shop. | meta_title, meta_description. | All (published, unpublished, draft, archived) |
Shop policies | A shop policy. | body. | All (published, unpublished, draft, archived) |
Product status definitions
Active → The product is ready to sell and can be published to sales channels and apps. Products with an active status aren't automatically published to sales channels, such as the online store, or apps. By default, existing products are set to active.
Archived → The product is no longer being sold and is not available to customers on sales channels and apps.
Draft → The product is not ready to sell and is unavailable to customers on sales channels and apps. By default, duplicated and unarchived products are set to draft.
Limitations
Live theme update: When a live theme is changed, the translation content is not always included as it is store specific, not theme specific. Shopify is aware of this and have recommended users leave feedback on this here. This may also have an inflammatory impact on the analysis of suggested content for translation in Locale, if themes and templates are chosen.
Meta field data: This information is not automatically processed for translation. If this is a necessary field for translation, as it can vary from use case to use case, please contact us and we will be able to advise a solution.
Initial synchronization time: The first time Locale connects to a Shopify instance, it may take some time for the analysis to be properly reflected. This is partly to do with the way Locale accesses all of the possible store content to be translated, as well as API call limitations, which may extend the time it takes to accurately analyze the size and translation requirements for your Shopify instance. If your analysis information does not reach an equilibrium within 2 hours of the first connection, contact us for help and we will be glad to advise.
Links: Only select content found in links is translatable. For example, hard-coded URLs in theme or email templates are not accessible by Locale. However, collection or product URLs are accessible for translation by Locale.
Example: https://locale-store.com/collections/sacs-a-dos/products/sac-champetre.
Locale will only translate sacs-a-dos and sac-champetre. These translations can then be seen in the Shopify app Translate and Adapt under the corresponding URL section (in our example, Product and Collection).