Skip to main content
Every option set has a Translation tab in its editor. This is where you see every customer-facing string side-by-side with its translation in every target locale, and where you run the AI auto-translator.

​
Open the Translation tab

1

Open the option set in edit mode

From the sidebar go to Option Sets, pick one, and click Edit.
2

Save any pending changes

Translations work on the saved state of the option set. If you have unsaved edits, Customei asks you to save before switching to the Translation tab.
3

Click the Translation tab

The editor switches to a virtualized grid showing one row per translatable string.

​
The translation grid

The grid has one column for the source (your default locale) and one column for each target locale configured in Settings → Languages. Each row is one translatable string:
  • A field label (e.g. the “Your name” label above a text input).
  • A help text (the description under a field).
  • A value label (e.g. “Gold” in a swatch).
  • A button or message that the widget renders.
The source column is read-only — to change the source, go back to the option set editor and edit the underlying field. Target columns are editable; click any cell to type a translation.

​
Edit by hand

For short, high-visibility strings (field labels, primary CTAs) hand-editing is the right call. Click a cell, type, press Tab to commit and move to the next cell, Escape to cancel. Empty cells render as the source text on the storefront — so leaving a cell blank is the same as saying “don’t translate this one”.

​
Auto-translate with AI

For longer strings and bulk translations, use one of the three built-in providers:

Google Translate

Fast and cheap. Best for common language pairs and short strings.

Gemini

Context-aware, respects brand tone. Best for longer strings and marketing copy.

OpenAI

Strong quality across languages. Use when Gemini isn’t available or for specialty content.

​
Run auto-translation

1

Pick the provider

At the top of the Translation tab, pick a provider from the dropdown.
2

Pick a scope

  • Fill empty cells only — only translate strings that don’t have a translation yet. Safe default.
  • Overwrite all — retranslate everything. Use when you’ve edited the source copy and want fresh translations everywhere.
3

Pick target locales

By default, Customei runs for every configured target locale. Uncheck any you want to skip.
4

Start

Click Translate. Customei streams results into the grid as each string comes back — you’ll see cells fill in live.
The streaming is powered by Server-Sent Events, so you can watch progress in real time and cancel mid-run if something looks off. Canceling stops the stream; anything already streamed is kept.

​
Credits

AI translation runs cost credits — one credit per translated string per target locale (rough guideline). Running the translator on an option set with 40 strings into 3 locales costs roughly 120 credits. See Credits for the live pricing.

​
Review and save

After a run, scan the grid for anything that looks wrong and hand-fix it. Obvious gotchas to watch for:
  • Proper nouns. Product names, brand names, place names should usually stay in the source language.
  • Units. “5 oz” translated to “150 g” can surprise customers — either let Customei translate it (if you want local units) or hand-correct every row.
  • Tone. Gemini and OpenAI pick up tone from context; Google Translate can read more literally. If your copy is playful, one provider may fit better than another.
Once you’re happy, click Save. Customei persists the translations and rebuilds the storefront bundle so customers see the new strings on the next page load.

​
Glossary

A glossary is a list of locked phrases — “Customei”, your brand name, specific product terms — that the AI translator will never change. If you find yourself correcting the same term every run, add it to the glossary and it stops happening. See Translation glossary.

​
Save-before-translate

If you’ve made unsaved edits to the option set and try to run auto-translation, Customei prompts you to save first. This is because the translator operates on the saved state on the server, not the live in-browser state — saving ensures the AI is working from the version your team has approved.

​
Next