Executive summary
- What: Translate and Adapt now refreshes machine translations weekly, and the automatic language ceiling rises from two to eight for stores based in twelve European markets.
- Why: translated storefronts drifted out of date between manual runs, so localized buyers read stale copy after every content edit.
- Who: Plus merchants with stores based in Austria, Belgium, Denmark, France, Germany, Ireland, Italy, the Netherlands, Spain, Sweden, Switzerland, or the UK.
What changed
Two things. First, Auto-sync: a per-language toggle that lets Shopify translate new and changed content once a week, on the same day and time, without anyone opening the app. Second, capacity. Stores in the listed countries can now machine translate up to eight languages beyond the store default, up from two. The old Auto-translate button is renamed Translate now and still performs one immediate pass, for launches that cannot wait for the next weekly window.
Manual work is unchanged: translations a person wrote or edited are never overwritten. Auto-sync is off by default, so nothing moves until someone enables it per language. One constraint deserves attention first. Using Auto-sync or Translate now on a language consumes one of your eight slots, and that assignment cannot be shifted elsewhere later. Removing a language does not release the slot. Auto-sync also does not run on activation: the first pass lands at the next weekly sync, up to seven days out.
Why it matters
Localization decay is an unglamorous and expensive failure mode. A team shipping weekly copy changes in its primary language will, within a quarter, serve a measurably worse experience in every secondary language, and nobody files a ticket because the pages still render. Weekly sync bounds that drift at seven days, a materially different risk profile for catalogues that change often.
The jump from two languages to eight is the bigger strategic change. Two slots forced most European merchants into paid vendors from market three onward. Eight covers the realistic European footprint for a mid-sized Plus brand, which changes the arithmetic on expansion sequencing. If you are mapping that sequence, our Shopify internationalization guide covers how language, market, and domain structure interact before you commit to slots you cannot reassign.
One exclusion to plan around: store legal policies are not machine translated. Those still need a human, and in most jurisdictions a professional.
Role-specific impact
- Marketers: translation coverage stops being a recurring chore and becomes a configuration decision. Keep a review step in localized launches, because machine output still needs a read before it fronts a campaign.
- Developers: no API surface changed. Translated content now mutates on a weekly cadence you do not control, so cached or externally synced localized copy, including headless builds and PIM round trips, should assume weekly deltas rather than deltas on publish.
- Store admins: you own the slot ledger. The app shows how many of the eight automatic languages are consumed and which. Record the intended allocation before enabling anything, because the decision is permanent in practice.
Use-case example
Real-world scenario
A UK-based Plus merchant sells into five European markets with roughly 4,000 active SKUs and revises copy most weeks. Under the two-language limit, German and French were automated while the other three markets ran on quarterly vendor exports. Spot checks found around 18 percent of product pages in those languages serving copy at least one revision behind, concentrated in the recently updated products paid traffic pointed at. Auto-sync across five languages caps worst-case staleness at seven days and retires the vendor cycle for everything but legal pages.
Implementation checklist
- Confirm eligibility: the app showing Translate now rather than Auto-translate is the reliable signal, regardless of listed country.
- Write down the eight-language allocation you want, including markets on the roadmap, since slots cannot be reassigned once used.
- Audit translation status per language to find manual work to preserve.
- Enable Auto-sync on one lower-risk language first, using Translate now if you need coverage before the first scheduled sync.
- Roll out the remaining languages, then publish any held unpublished so their syncs begin.
- Route legal and policy pages to human translators.
- Tell downstream consumers of localized content, such as a headless frontend or PIM sync, to expect weekly changes.
FAQ
Q: Will Auto-sync overwrite translations our team wrote by hand?
A: No. Automatic translation fills gaps and refreshes earlier machine output only. Manual translations are left alone, and for some theme content only missing strings are added.
Q: We are a US-based store selling into Europe. Do we get this?
A: Availability follows the country your store is based in, not where you sell. Stores outside the listed markets stay on two automatic languages with Auto-translate and no weekly sync, unless the app surfaces Translate now.
Resources
Shopify documentation: Translating content automatically using the Translate and Adapt app.
Need guidance? Talk to Makro.