A translated product page can read beautifully and still be wrong. A changed model number or an invented warranty promise is enough to make it misleading.
We build Lumo AI Translation Addon for WPML. Here is a small, practical workflow for using it with more deliberate instructions. This is a product walkthrough, not a benchmark of model accuracy.
1. Separate language from identifiers
Before translating, list the terms that should remain unchanged: brand names, SKUs, model numbers and proprietary feature names. Then identify what should be localized, such as explanatory prose and customer-facing headings.
For example, a product called “Atlas Pro X200” can have a natural French description without changing “X200” into another identifier. Check units and warranty wording against the original, too.
2. Give the model a useful brief
The add-on supports Custom Instructions for tone, industry and protected terms, with rules that can apply to different content types. A starting brief might be:
Translate into natural French for an electronics store. Keep brand names, SKUs and model numbers unchanged. Preserve numerical specifications and the meaning of warranty conditions. Do not add claims missing from the source.
Instructions reduce ambiguity; they do not replace review. If the original is unclear, improve it before creating more language versions.
3. Start with one representative product
Connect your chosen provider, such as OpenAI, Claude or Gemini, using your own API key. Configure the WPML translator and language pairs, then send one representative item through the workflow. Include a product with a table, a technical term and a real call to action.
Review the saved target, not only the returned text. Check its title, description, identifiers, links and mobile layout. Choosing a model is not a substitute for these checks.
4. Fix the smallest part that is wrong
If only a title needs improvement, use title-only retranslation rather than regenerating the body. The add-on also provides Bulk Tools for selected posts, taxonomies, custom fields, WPML strings and Elementor templates. Choose the content owner deliberately: a global header is not the same document as a page body.
For Elementor content, verify that the intended fields were included and inspect the actual translated page. Do not assume every custom widget is covered just because the page contains it.
5. Expand after the pilot passes
Use the background queue for a larger batch after the small review succeeds. Long content is processed in chunks, with retry/resume support. Keep a backup and a record of the source, target language and instructions so the next review is reproducible.
WPML is required. Lumo is an independent third-party add-on, and AI provider usage is billed separately from the plugin licence. There is no universal model or prompt that guarantees a flawless translation.
Explore the add-on and tutorial.
What is the one term your translation workflow must never change?
Top comments (1)
The biggest thing is protecting product specifications and warranty terms. AI can make translations sound natural, but accuracy matters more than fluency when customers are making buying decisions. A small test batch and human review before scaling can prevent a lot of problems.