Contents
In briefWhat shippedWhat an agent is givenTheme and catalogueHong Kong and the GulfThe checkOur takeRelated service
Shopify Agentic Commerce →What Shopify shipped
On 2 October 2026 Shopify released improved support for three right-to-left languages, Arabic, Urdu and Hebrew, in the admin and on storefronts. It names checkout, customer accounts and the Horizon family of themes. Where a shopper's device settings are available, Shopify says those settings determine the display language.
Shopify's Fall ’26 Edition says you can launch your online store in Arabic, Hebrew or Urdu to reach over 600 million people who read these right-to-left languages.
Product pages, and the other content you own, stay in the languages you have enabled. Shopify says you add a product-page translation with Translate & Adapt in the admin, and you start by adding the language there. Checkout, customer accounts and a Horizon theme can carry the new support while the product title is still the language you wrote it in.
The changelog does not mention shopping agents. The link is ours. An agent shopping in Arabic still reads the product record, and a title you have not translated is not there to read. That split is what we check first on a Shopify Agentic Commerce store.
What an agent is given
A shopping agent reads the catalogue. On a Shopify store that read is a search_catalog call on Storefront Catalog, and the buyer context on the call can include a language, along with country and currency, as a signal for localisation. The response carries the product record: title, description, options, variants and tags. Shopify documents the language field. It does not say that passing Arabic back fills in a translation you never wrote.
Whether that record exists in the buyer's language is decided in Markets. Publish a language and Shopify creates a URL with the language code, such as example.com/fr or example.com/de, and adds hreflang for the languages you have published. On that URL the store shows a translation where you have one. Where you don't, it shows your primary language, and the page still loads. The language left in the field is the one an agent can match, which is our reading of that fallback, not a line in the 2 October changelog.
The theme can be finished while the catalogue is not
Shopify splits the two jobs. Adding a language adds translations, in the languages it supports, to a compatible theme and to checkout. Products, collections and pages wait until you import the translations, or write them in Translate & Adapt or another app. Publish a language and add none of your own copy, and the store shows the translations Shopify already provides for the theme and the checkout.
Those are different records in the admin. A product title is a product field. A menu link is a menu. A section heading is theme content. A French header and an English product title can sit on the same URL, and search_catalog returns that title in whatever language the field is in.
The 2 October release names the Horizon family of themes, not every custom theme. A custom theme still has to be compatible with more than one language, and its own strings are yours to translate. Product titles are yours either way. That is the changelog's line: content you own stays in the languages you have enabled.
Tags cannot be translated. That includes product tags, article tags and blog tags, and the catalogue response includes the tags on the variant as they were written. You can translate the title and the tags still go out in the language they were written in.
The translation status names the miss. Outdated means the primary-language copy changed and the translation didn't. Untranslated means that field has no translation. On the storefront both are filled from the primary language, so the page has no empty box to show you. A meta title left on the default setting follows the translated product title and description. Customise the meta title and it needs its own translation, or it stays in the primary language with the other untranslated fields.
Hong Kong and the Gulf feel it first
A store selling from Hong Kong is already asked in English, Traditional Chinese and Simplified Chinese. The storefront can look finished in a language while the product titles are not, which is the split the 2 October changelog states for Arabic, Urdu and Hebrew, and it was already the split on a Chinese store. The two scripts still need their own vocabulary and their own reader. Converting one script into the other misses the words buyers type, and both languages go on one store through Markets. We treat that hand review as the translation audit: automatic translation is a first pass, and someone who shops in that script signs off the product names, the page titles and the policy lines.
Dubai and the Gulf are where an Arabic-speaking shopper meets this. Arabic is one of the three right-to-left languages, with the improved support in the admin, on the storefront, in checkout, in customer accounts and on Horizon themes. Where that shopper's device settings are available, Shopify uses them for the display language. The product page is in Arabic only once you have enabled the language and translated the product in Translate & Adapt. Whether a Dubai store adds Arabic is the commercial decision that comes before that writing. On our reading, an agent arriving in Arabic can know the product only as far as that translation went. The changelog does not say that.
Brands trading the Hong Kong and Gulf routes carry both of those on one catalogue, often across more than one store. The jewellery work across France, the Middle East and Asia is that shape of setup: regional stores, with the French store's files passing a native language check before they go live. That check is the same job as the Chinese hand review.
Check one product in one language
Pick a product you sell and one language you have published. In the admin, go to Settings, then Languages, then Export. Choose that language, and choose Untranslated content. Shopify emails a CSV. The Type and Field columns name each row: a product title, a description, a menu link, a theme section. Find a product title whose Translated content cell is empty, then open that product on the locale URL Shopify created for the language.
Read the menu, then the title and the description. A menu in the market language and a title still in your primary language is the fallback, on the page a customer sees and in the product record an agent reads. The empty cell in the export is that title.
If the primary-language copy has changed since the translations were written, export again and choose Outdated. Those rows no longer match the source. A careful first pass goes stale without anyone publishing a new language. Where a market has its own language list, confirm the language is added under Markets, then Languages and domains. That screen needs an international domain, a subfolder or a subdomain. Without one, every market shares the store's languages, and the export above is the file that covers them.
A developer can call search_catalog with the language set in the buyer context and read the title that comes back. Shopify documents that field as a localisation signal. The check you can run without a developer is the export and the locale URL. The call itself is covered in what a shopping agent sees on your store.
Our take
Readiness is language-agnostic. Agents act for users in the user's language, so a store in English, French, German or Chinese must be knowable to an agent arriving in any of them.
Sources & references
- Shopify Changelog, Admin now supports 3 new languages(changelog.shopify.com)
- Shopify Editions, Fall ’26(shopify.com)
- Shopify Help Center, Localization and translation(help.shopify.com)
- Shopify developer documentation, Storefront Catalog MCP(shopify.dev)



