Apps › Website

AI Translation: Auto-translate Odoo Content

Translate your products, website pages and any other translatable field in batches, with your own key at an OpenAI-compatible API or at DeepL, a glossary that answers first and a review queue.

Open the live demo Read the manual

Odoo 16Odoo 17Odoo 18Odoo 19Odoo 20

A batch in review: its two languages and engine, the counters, and each term with its source, its proposed translation, its status and its note
A batch in review: its two languages and engine, the counters, and each term with its source, its proposed translation, its status and its note
Runs onOdoo 16 to 20Community or Enterprise, self-hosted or Odoo.sh
NeedsOdoo onlyno Enterprise module
Price129 EURone-time, per series, on the Odoo Apps Store
Demodemo20.bambooforge.devlogin page already filled in
Supportsupport@bambooforge.devfirst reply within one business day
Version20.0.1.2.2bambooforge_translate_ai

28 automated checks run before every release of this app, the same suite on every series it ships for. The complete list is in the source you receive; run it yourself with --test-enable.

For the people who decide

What your managers see

AI Translate > Reporting is the manager's menu. Its one analysis, Translations, opens on a chart, with the pivot one click away.

Translations

every term a scan listed, counted and with the characters of its source, by target language, engine, content, batch, status and month, with filters for the applied, failed, rejected and waiting ones.

The e-commerce or marketing manager sees what each language took in characters, which engine fails, and what still waits for a reviewer.

Batch counters

each batch card shows its terms, its applied lines and its failed lines, and the batch form adds the lines waiting for review.

The reviewer sees which batch still needs a decision.

The app prints no document. One file leaves it:

How you use it

From a list of missing texts to translations you approved

Flow 01

Scan, translate, review, apply

A batch goes from one language to another, with one engine, over the content rules picked on it.

  1. AI Translate > Batches > New: choose the languages under From and To, and the engine. Every content rule is on a new batch.
  2. Scan Content lists each text that has no translation in the target language, one line per term.
  3. Translate answers from the glossary first and sends the rest to the engine, 40 to a request. Each line comes back Proposed, or Failed with the reason under Note.
  4. Type over a translation to correct it, approve or reject each line or press Approve All, then Apply Approved writes the approved lines.
Batches as cards: the name, the status, the two languages and counters for terms, applied lines and failed lines
Flow 02

The glossary answers first

For one target language, a term and the translation it must get.

  1. AI Translate > Glossary: type the term, pick the target language, type the translation.
  2. A text that is exactly the term gets that translation, with the note glossary, and is not sent to the provider.
  3. An OpenAI-compatible provider also gets the glossary of the target language in its prompt. To keep a word as it is, a brand name for example, repeat it as its own translation.
The glossary list: a term, its target language and its translation on each line
Flow 03

Connect the provider you already pay

One line per service, kept by a manager. The line at the top is the engine a new batch starts with.

  1. AI Translate > AI Providers > New: name the line and choose an OpenAI-compatible API, DeepL or the Demo engine.
  2. Type the address under Base URL, and your key. A new line starts with OpenAI's address: for DeepL type DeepL's, a DeepL line without it sends nothing.
  3. For an OpenAI-compatible API, choose the model and add extra instructions if you want: tone of voice, formality, audience.
  4. The key is masked on screen and only managers can read it. Users run batches with it all the same.
The AI Providers list: one line per service with its name, provider type, model, address and masked key

Price and where to buy

129 EUR, one payment per Odoo series, on the Odoo Apps Store. Pick your series:

Twelve months of support by the people who wrote the code; bug fixes and improvements within the series free for as long as it is published. Report a bug within two months of purchase and, if it is not resolved within fifteen days, you get a full refund. Full source under OPL-1, no licence key, no phone-home. The whole promise.