| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1238 |
| Technical Name |
ai_ecom_translate |
| License | OPL-1 |
| Website | https://erpoxa.com/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
eCommerce (website_sale)
• Discuss (mail) • Website (website) • Invoicing (account) |
| Community Apps Dependencies | Show |
| Lines of code | 1238 |
| Technical Name |
ai_ecom_translate |
| License | OPL-1 |
| Website | https://erpoxa.com/ |
AI Bulk Translate Products
Multilingual Odoo stores have a translation problem: hundreds of products, dozens of languages, every "name in EN, body in EN" fallback chips away at conversion. One bulk action fixes it.
Translate the catalog in every language
Bulk-translate product names, descriptions and SEO — HTML tags preserved.
The whole module in 25 seconds
Two entry points · annotated wizard · timing estimate · skip vs overwrite · per-row result · settings — captured against a real catalog.
Each step is shown in detail with its own annotated screenshot further down the page.
Test this module instantly
You can explore all features using the demo account. No setup required.
6 fields per product
Name · short description · long website description · SEO title · meta description · meta keywords.
Quick-pick presets
"Names only", "Descriptions only", "SEO only", "All", "Clear" — one click instead of ticking six boxes.
Smart skip
Already-translated (product, language) pairs are skipped by default. Tick "overwrite" to force retranslation.
Nightly cron (optional)
Auto-translate any product edited in the source language since the last run. Off by default.
Per-product · bulk list · top menu
All three routes open the same wizard. The only thing that changes is what's pre-populated in the Products picker.
Per-product · the AI Translate stat-button
ONE PRODUCTOpen any product → click the AI Translate stat-button at the top. The wizard pre-fills that product. After every successful run, a "Last AI translation: <timestamp>" banner appears on the form so you always know which products have been processed.
Tip: the AI Translate button is the only one this module adds. Adjacent buttons (AI Suggestions, Generate Now…) come from other AI eCommerce modules and do different things — see their own descriptions.
Bulk · multi-select on the products list
N PRODUCTSOpen Sales → Products in list view → tick rows → click Actions → AI Translate. The wizard opens with every ticked product loaded. The cron-driven path commits per product, so a long run survives a worker timeout without losing earlier work.
Top menu · AI eCommerce → Bulk Translate
EMPTY PICKEROpens the wizard with no products preselected. You pick them inside via the autocomplete picker (start typing a name or paste a list). Useful when you've identified products from a report and want to run translation on that set without backtracking to the list view. Hard UserError with a friendly message if you click Translate without picking products — no silent failures.
One screen — five control regions
The Configure view shows a summary at the top, then five regions you can adjust in any order:
1. Products picker
Tag-style picker, editable at any time. Pre-populated when the wizard was opened from a product form or a list selection; empty when opened from the top menu. Click to add more, ✕ to remove. Hard error if you click Translate with zero products — no silent runs.
2. Source language
Which language the product copy is currently written in. Defaults to your company's main language (override in Settings → AI eCommerce → Bulk Translate · Defaults). The source is automatically excluded from the target list.
3. Target languages
Pre-filled with every installed language except the source. Add/remove tags directly, or click "Pick all installed languages" for the full sweep. Languages must be installed under Settings → Translations → Languages first.
4. Fields to translate
Six tickboxes with descriptive icons: name · short description · long HTML description · SEO title · meta description · meta keywords. HTML structure is preserved — only text content inside tags is translated.
5. Quick-pick presets
Five buttons: All · Names · Descriptions · SEO · Clear. One click instead of ticking individual boxes. Useful when you only want to refresh, e.g. the SEO meta across every product without retouching descriptions.
+ Overwrite toggle below the cards
Off by default — already-translated (product, language) pairs are skipped, so re-running is safe and idempotent. Tick this when source copy changed and you want all targets refreshed.
Per-product, per-language result — never silent
Every wizard run ends on a Done screen with a real result table. No "did it work?" guessing.
Written
Lists which exact fields landed ("Wrote: name, description_sale, website_meta_title, website_meta_description"). Empty source fields are silently skipped, so you only see what actually got translated.
Skipped
A (product, language) pair already has a translation and you didn't tick overwrite. Re-running with overwrite ON flips these to "Wrote: …".
Errors
Rate limit, API key issue, network blip. Other rows still complete — failures don't break the whole run. Detailed error message inline; the AI eCommerce Request Log has the full trace.
Four toggles in Settings → AI eCommerce → Bulk Translate
| Setting | Default | What it does |
|---|---|---|
| Source language | English (US) | Which language the AI assumes the product is currently written in. The wizard pre-fills this as the source on each new run. |
| Keep proper nouns verbatim | On | Brand names, SKUs, model numbers (e.g. "iPhone", "GTX-7000", "FURN_7777") are passed through unchanged. Important for tech / fashion catalogs. |
| Overwrite by default | Off | Pre-ticks the wizard's overwrite checkbox so every run retranslates everything. Useful if you frequently edit source copy. |
| Nightly auto-translate | Off | Enables a daily cron that finds products edited in the source language since its last run and translates them into all installed languages. Set-and-forget mode. |
Why "real translation" isn't the same as Google Translate
🏷️ Brand-aware
The system prompt explicitly tells the LLM "Brand names, model numbers, SKUs and product codes (e.g. 'iPhone', 'GTX-7000') must NOT be translated; keep them verbatim." No more "iPhone" rendered as "ai-fawn" in Arabic.
🧠 Selling tone preserved
Prompted as a "professional eCommerce translator": preserve meaning and selling tone — not a literal word-for-word output. Marketing copy stays marketing copy.
🧩 HTML-safe
Rich HTML descriptions keep every tag and attribute exactly as in the source. The LLM only translates the text content inside tags. No "<b>" magically becoming "<بأف>".
🔁 Idempotent & resumable
Re-running the wizard on the same selection is safe — it skips already-translated pairs. If a big run fails mid-way, just re-run; only the missing ones get processed.
📒 Audit-logged
Every LLM call lands in AI eCommerce → Request Log with tokens used, latency, source = translate. You see exactly what each translation cost.
🗓️ "Last translated at"
Each product gets a stamped ai_ecom_last_translated_at field — visible as a banner on the form and filterable in the list view, so you can find which products are out-of-date.
Three steps to a multilingual catalog
Install the module
Depends on ai_ecom_base — uses the shared OpenAI key, no extra config.
Install your target languages
Settings → Translations → Languages → Activate. Only installed languages appear in the wizard.
Tick products → Actions → Translate products
Or click the AI Translate stat-button on any single product. Done.
Plays well with the rest of Odoo
Ship a multilingual catalog this afternoon
AI Translate turns one English catalog into ten with a single bulk click.
Built & supported by Erpoxa
An Odoo consultancy focused on scalable AI-powered modules and bespoke integrations. We answer fast and ship clean code.
Website
All apps, docs & portfolio
erpoxa.comOdoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module