Shopify's Translation Tool Adds Auto-sync: What Still Needs Review
Use Shopify Translate & Adapt Auto-sync with a two-product check that separates automatic updates from manual review, plus eligibility and correction steps.
Shopify's translation tool, Translate & Adapt, can now refresh machine-translated content weekly with Auto-sync on eligible stores. Enable it for routine updates, but keep a separate review process for manually edited translations and any product change that must be accurate before the next scheduled run.
The useful question is what happens after your English product description changes. A translated page can look finished while describing yesterday's product. This guide explains the new controls, then gives your content team a two-product exercise to verify what updates automatically and what still needs a person.
What changed, and which stores get it?
Shopify announced the update on October 9, 2026. Eligible stores gain weekly Auto-sync and an allowance of eight automatically translated languages. Translate & Adapt itself is an existing app; this announcement concerns its update workflow and expanded allowance.
For our readers, the key regional distinction is the store's location. Shopify lists the UK and Ireland among eligible countries. US, Canadian, Australian, and New Zealand stores ordinarily retain two automatic languages without Auto-sync. However, Shopify says the Translate now button confirms eight-language and Auto-sync access even outside its listed countries. Check your app rather than assuming eligibility from where your customers live.
The current automatic-translation documentation is the reference for that distinction. It also says removing a language does not recover its automatic-translation allowance. Choose a language you actually intend to support instead of spending a slot on an experiment.
Automatic-language allowances are separate from how many languages a store can publish. Shopify's multilingual requirements list up to 20 languages on Basic, Grow, Shopify, and Advanced, and up to 30 on Plus. They also require a compatible theme and a language selector. Do not buy a plan upgrade simply because a translation button is missing; establish which requirement is responsible first.
Set up the first update deliberately
Open Apps > Translate & Adapt and select the intended language. On an eligible store, use Translate now for a one-time update. Enable Auto-sync translations for ongoing weekly updates, confirming the dialog if shown. The toggle is per language and initially off.
Turning it on does not start the first translation immediately. For an unpublished language, the first scheduled run waits until the weekly time after publication. Keep automatic publication unchecked during your initial review if the confirmation offers it. Prepare the content before sending customers to it.
Before changing translations, export a reference copy through Settings > Languages > Export, selecting the language and All content. Shopify's CSV guide documents the export and its resource, field, locale, market, source-content, and translated-content columns. Save the dated file with your change record so reviewers can compare the actual wording.
Start with an existing language that already serves a working market. Assign one reviewer who can read it well enough to judge meaning. A content editor who cannot assess the translation can coordinate the work, but should not become its final language approver simply because they know the admin.
Run this two-product check before trusting the weekly routine
This is a proposed acceptance exercise, not a report from a client store. Use two representative products with legitimate copy updates pending. Choose low-risk descriptive changes, such as clarifying the location of an apron pocket. Do not introduce false specifications or change safety instructions merely to test automation.
For product A, choose a description whose translation has remained machine-generated. For product B, choose a description your team previously edited manually. Ask the previous editor to confirm that history; do not guess from how fluent the wording looks. If nobody can confirm it, select another example with known history. Record the source description and translated description for each before proceeding.
Write the expected result before changing anything
- Product A: after translation runs, the translated description should convey the newly clarified product detail.
- Product B: the existing manual translation should remain protected; a reviewer must incorporate the source change.
- Both products: the customer-facing descriptions must agree with the real product before you consider the work complete.
That second result follows Shopify's documented protection of manually added or edited translations. In this test, an unchanged manual description is an automation pass and a publishing task still open. Keeping those two judgments separate prevents a team from repeatedly rerunning translation when the correct next action is an editorial update.
Observe one update cycle
Make the approved source changes and record their time. If your store is eligible, let the planned weekly cycle run for this low-risk exercise. If the update has a deadline, use the one-time translation control instead and record that choice. A successful one-time run tests the content behavior; it does not prove that the weekly schedule has executed.
Compare the resulting descriptions with the saved versions. For A, ask whether the changed fact is present and accurate, not whether the wording merely looks different. For B, have the language reviewer add the corresponding correction manually. Shopify documents that editing path as Apps > Translate & Adapt > language > resource, then edit the appropriate field and save in its manual translation guide.
Finish on the storefront. Open each product in the intended language, check the changed passage, and save the URL and review time. Repeat on mobile, including any expandable description or care-information panel. Then ask a second team member to find the same product through the normal collection or search journey. This catches a narrower problem than “the translation failed”: the editor may be inspecting the right content while the shopper is reaching a different page or language.
Investigate a failed observation without widening the change
If A did not update, first verify its editing history, selected language, and whether the intended run occurred. If the admin contains the correct translation but the storefront does not, record both views and escalate that discrepancy. Avoid repeatedly translating the whole language without knowing which observation failed.
If B changed unexpectedly, pause further automated work while you investigate who or what wrote the translation. Check other translation apps and recent imports with the responsible team. Preserve the before-and-after wording. The exercise is useful because it gives support a specific product, field, language, time, and expected outcome instead of a general complaint that the store is mixed-language.
Give every source edit a translation owner
The practical deliverable is a small change record that follows the source edit. I would use these entries:
- Changed fact: the exact product detail or customer promise being corrected.
- Affected content: product description, related collection copy, imagery, and any other place the same claim appears.
- Languages and owners: who checks each version and who approves publication.
- Update method: scheduled machine update, one-time translation, or manual revision.
- Evidence: the reviewed storefront URL, review time, and unresolved exceptions.
Keep this with the merchandising task rather than in an unrelated translation spreadsheet nobody opens. When a reviewer improves machine wording manually, add that translation to future human review. Protection from overwriting is valuable only if somebody remembers to maintain the protected text.
For campaign launches, work backward from the time the customer promise must be correct. Assign translation and review as launch dependencies. If the reviewer is unavailable, choose a narrower launch scope or delay that language's campaign. A calendar reminder to “check translations later” is inadequate when ads already send shoppers to the changed claim.
Check the content Auto-sync cannot take over
Shopify's Translate & Adapt limitations include collection filters, Shopify Forms content, manual payment instructions, product images, tags, and third-party content not exposed through supported Shopify translation resources or locale files. Do not interpret a completed language update as verification of those surfaces.
Walk through one purchase task and write down every sentence that helps the buyer choose: the product specification, size advice, subscription explanation, delivery message, cart warning, and payment instruction. Assign each to the tool or person that actually controls it. Ask app vendors to demonstrate their own translation coverage using your installed widget.
For an image containing care instructions, put the graphic itself on the review list. Readable translated copy underneath does not establish that the image agrees. Shopify's manual translation documentation explains localization of supported files and theme imagery; confirm the specific image placement before promising an automatic replacement.
Language review also needs a commercial reference. Use your actual currency setup when checking price-related wording; our Shopify multi-currency guide explains the separate payment decision. For gift-card copy, include the restrictions and behavior covered in our multi-currency gift-card guide. Translators need those decisions in the brief, not after the wording is approved.
When to leave Auto-sync off, and how to correct a bad update
Leave it off when your publishing process requires approval before any translated wording changes and you have not established how scheduled updates fit that rule. It is also a poor sole solution when every product update requires immediate multilingual publication. In those situations, define the review and timing requirements before evaluating another app or a custom workflow.
If a translation is wrong, stop future scheduled updates with the language's Auto-sync toggle and correct the affected content. Treat stopping automation and repairing published wording as two separate tasks. Shopify says uninstalling Translate & Adapt does not delete its translations, so removing the app is not a content rollback.
For several corrections, use Shopify's documented CSV import process. Work from a fresh export, edit the intended Translated content entries, and deliberately choose whether to overwrite existing translations. Review the import confirmation for skipped or failed content. Do not restore an entire old export without checking for legitimate translations added since it was saved.
Repeat the customer-facing checks after correction, then decide whether to resume automation. Keep the two-product exercise as a regression check when your translation workflow changes. If responsibility is split across your theme, apps, and content team, our Shopify implementation services can help map those responsibilities and verify the resulting journey.