Translate a Shopify draft theme before you hit Publish

The winter drop sits in an unpublished theme. Sections, announcement, buttons: still English. German product titles are done. In two weeks you click Publish. Shoppers then get a German catalogue with an English Add to cart and a footer that never left the source locale. Translate Shopify draft theme is the job you run *before* that click — not a polish pass on the live storefront.

The OO - Ultimate AI Translations listing pitches scheduled runs for products, pages, theme content and metaobjects, including draft themes. A live-theme job does not fill those unpublished keys. Draft/development theme is its own content type.

Yesterday: your own LLM. That is the provider. This article is which theme the job targets. Live theme strings were theme content. Here: the unpublished shell only.

Unpublished copy is invisible until Publish

Shopify serves the active theme. Editor preview is not the storefront. FAQ: the language switcher is missing unless the embed or block sits on the live theme. Draft translations can be ready; shoppers see them after that theme is live and the locale is published.

Manage languages: unpublished locales can still be selected for jobs so you can prepare copy. Switcher preview waits until you publish the language.

Jobs skip empty source, locked fields, handles, URLs, IDs, SKUs, size codes (S/M/L), JSON. Translating theme-file handles belongs in skipped. The string “Add to cart” in the draft theme does not. A live “theme” job does not fill those unpublished keys either: they are two types. Pick the type that matches the unpublished theme. Do not tick every content type “to be safe” without reading the history.

Save in the editor = lock. Automatic and scheduled jobs leave locked fields alone. Unlock if AI should touch them again.

How shops ship an English winter by accident

Products + live theme only. Dashboard looks green. Draft sections stay source language. Publish becomes a second launch night.

Locale-by-locale paste in the theme editor on the draft. Survives until someone duplicates a section. No Missing/Outdated. No lock against the next job.

ChatGPT into `locales/de.json`. Until the next theme update. Handles come along if you are not careful. Listing jobs skip those technical values on purpose.

None of that is: content type draft/development theme, Missing or Outdated, unlocked, AI connected.

What the app actually runs on a draft

OO - Ultimate AI Translations — 0 reviews, launched 14 Oct 2026. Live listing, USD. Do not invent stars.

• Free $0 — own AI (OpenAI-compatible), unlimited languages/markets/translations, language switcher. No backups, no scheduled jobs, App AI not included. A manual draft-theme job is allowed.

• Professional $10/month + usage — 1 manual + 1 automatic backup, monthly schedule, glossary, App AI at translation cost (~$0.01/unit) or own AI

• Plus $20/month + usage — 5 + 5 backups, daily schedule, App AI at cost or own AI

Pitch: free app with your own AI; App AI without markup (~$0.01/unit); jobs including draft themes; locks; glossary/brand voice; backups; a language (+ country) switcher you can style.

What is OO Translations?: editor, missing/outdated jobs, locks, glossary, backups, switcher, metaobjects. The listing puts draft themes in those runs. Quick start: one language, a small type, daily later. Daily = Plus. Monthly = Professional. Free = you press Run.

Same job as products when winter SKUs and winter sections must land together. Separate job if you do not want live storefront strings in that run.

Switcher styling belongs on the theme that will go live. Add embed or block on the draft in the editor, then check again on the now-active theme after Publish. FAQ: missing switcher means live embed/block forgotten.

Walkthrough: DE winter, live stays EN/NL

Store “Noordlicht”. Live theme EN/NL. Winter in a development theme. DE market in two weeks.

1. Install the app. Free: own AI, Connect AI. Or App AI on Professional/Plus.

2. Languages: enable DE, even unpublished. The job can already fill it.

3. Mini-job: content type draft/development theme, Missing, unlocked, one locale. History: translated / skipped / failed. Handles in skipped is correct.

4. Button copy you wrote yourself: editor, save, lock. Everything else Outdated when the English source in the draft changes.

5. Professional: monthly job on that type, backup before the first large run. Plus: daily. Free stays Run.

6. Publish day: theme live, publish DE, switcher on the now-live theme, hard refresh. Do not expect the live storefront to have shown draft copy in the weeks before.

Glossary (Professional+): do not “translate” the brand name in the announcement. Brand voice rides with the AI request. Backups: Free has none — no restore claim at $0.

Setup

1. Open the listing. Draft themes are in the pitch. Do not promise schedule on Free.

2. Connect AI. Mini-job on the draft theme, one unpublished locale.

3. Read skipped. JSON and handles stay skipped.

4. Lock copy you approved. Prepare the switcher on the draft; re-check on live after Publish.

5. Only then fold products/pages into the same cadence if those winter SKUs are still Missing.

Wrap-up

Translate Shopify draft theme is a content type, not an extra locale. You fill unpublished keys before Publish. Live jobs do not touch those keys. The switcher lives on the active theme. Locks keep your sentences. Jobs skip handles.

Queue the run in OO - Ultimate AI Translations. Publish the theme only when German Add to cart is actually German.