Shopify translation glossary: keep brand names consistent

German is published. “Online Origins” becomes a calque. The line name “Peak” becomes a mountain. SKUs survive — jobs skip handles, URLs, IDs, SKUs, and size codes like S/M/L — but a brand token inside a title is just a word. The model did what models do. You never pinned the term.

A Shopify translation glossary brand names list is that pin, per language, sent with the AI request. What is OO Translations?: glossary and brand voice so AI stays on-brand. The listing puts Glossary on Professional ($10/month + usage). Not on Free. Plus ($20) inherits it.

App: OO - Ultimate AI Translations. Free $0: your own OpenAI-compatible model, unlimited languages/markets/translations, language switcher; no backups, no scheduled jobs, no App AI, no glossary checkbox. Professional: monthly schedule, 1+1 backup, glossary, App AI at ~$0.01/unit (pass-through) or own AI. Plus: daily, 5+5 backups. 0 reviews, launched 14 October 2026. Do not invent a rating.

Translate with ChatGPT as your own model was 21 October. Job history was 22 October. This piece is why “Peak” stays Peak.

Glossary is not a lock

Locks: a field you save in the editor stays locked. Scheduled and automatic jobs will not overwrite it until you unlock. A glossary term rides in the request so the model prefers your form. It does not freeze a sentence you rewrite afterwards.

Brand voice (tone, formality, prefer/avoid) is the same family: on the request, not a field lock. Quick start lists brand voice + glossary after Connect AI. The listing still puts Glossary on Professional. Do not sell a glossary checkbox on $0.

Jobs already skip technical values. You do not glossary “SKU”. You do glossary brand names, line names, and claims that must stay identical in DE — or must use one prescribed DE wording.

How names drift without a list

A ChatGPT tab and a catalogue CSV. No glossary on the request. Peak → a synonym. Next chat, another synonym.

Translate & Adapt only. Fields fill. No per-language term list that a scheduled job will send.

Treating skipped handles as enough. Handles are skipped. “Peak” in the title is not, unless it is in the glossary or you locked the field after editing it.

None of that is: Professional, terms per language, jobs and the editor sharing the list, names stable.

What to pin, in which language

Positioning and listing: glossary terms (brand names, preferred wording per language). In practice:

• Brand: the same string in FR, DE, EN.

• A product line you refuse to translate.

• Words you *do* want steered: one French form for “collection”, not synonym roulette.

Not: S/M/L, barcodes, JSON, empty source. Jobs skip those already.

Own AI on Free translates without that list. The same model on Professional with a glossary: the difference is the request, not a suddenly dearer model. App AI on Professional/Plus is ~$0.01 per unit, billed at translation cost; you can keep your own key on $10. Glossary is then schedule + backup + terms, not a forced App AI.

Side-by-side editor after a job: spot-check brand tokens. Wrong = tighten the term or lock the sentence. History will not show a “glossary hit”. It shows translated / skipped / failed.

Example: brand + one line, DE and FR

You sell in Dutch, you open German and French. Twenty SKUs with “Peak” in the title. Theme header with the brand.

1. Professional (that is where glossary lives). Own AI can stay; App AI is optional.

2. Publish languages in Shopify. Connect AI if you still bring your own model.

3. Glossary: `Peak` → `Peak` in DE and FR. Brand name likewise. No mountain synonyms.

4. Small job: products, Missing, one language. Job history: failed is key/model/credits; skipped handles are healthy.

5. Sample titles. Header is theme content — include that content type if the header should follow the same list.

6. Then a monthly schedule. Locks on sentences you care more about than the model does.

Backup before a large first run: 1+1 on Professional, not on Free.

Get the terms into the next job

1. Install OO - Ultimate AI Translations. Free for own AI only. Professional once brand names must ride along on jobs.

2. Connect AI or App AI on $10/$20.

3. Glossary terms per language. Brand voice separately if the tone is sloppy — that is not a brand name.

4. Job on Missing. Read history. Locks for exceptions.

5. The storefront switcher is on Free; it does not translate names. Do not confuse chrome with the term list.

Scheduled jobs (Professional monthly, Plus daily) send the same glossary as a manual Missing run. A term you add after the schedule does not rewrite old DE titles by itself: those fields are filled, so they are not Missing. Outdated means the source changed, not “the glossary arrived late”. Then: unlock and retranslate, or write the sentence yourself and lock it.

Metaobjects and draft themes are on the listing. Same AI request, same term list, if those content types are on the job. A brand token in a metaobject title is as exposed as a product title. A theme header with theme content left off the job stays Dutch while products show DE-Peak.

CSV/Excel on the listing is “works with”, not a second glossary. Do not import a synonym sheet the app never documents. Terms belong in the glossary UI, not in a sidecar spreadsheet next to the job.

Wrap-up

Shopify translation glossary brand names is the Professional term list, per language, on the AI request. Not a Free toggle. Not a lock. Handles are already safe; “Peak” in a title is not until you pin it.

Own AI on every plan. App AI ~$0.01/unit, pass-through. Schedule and backups from Professional up. Put the names in the glossary before the next job, from the listing.