Running Odoo in more than one language quickly exposes a gap that the core translation engine was never designed to close. Odoo ships with ir.translation (now folded into the JSONB per-field translation storage in 17.0/18.0/19.0) and the built-in translation UI, but every string still has to be typed by a human, one language at a time, one record at a time. Product names, website pages, quotation terms, knowledge articles, and email templates pile up untranslated, and the "Translate" pencil next to a field is a manual, one-off action. For teams pushing thousands of products or a multilingual website through Odoo, that manual bottleneck becomes the single biggest reason localized content ships late or ships in only one language. There is no native automated machine-translation pipeline in Odoo core — it stops at giving you the empty translation slots.

This is a build-to-order module that ECOSIRE designs and builds to close that gap by wiring a neural machine-translation API directly into your Odoo translation workflow. Technically, we add a configurable connector (API key, endpoint, formality and glossary options stored on res.config.settings and encrypted in ir.config_parameter) plus a translation service layer that calls the provider over authenticated HTTPS. On any translatable field we expose a "Translate automatically" action — implemented as a server action / @api.model method plus a small OWL widget — that reads the source-language value, sends it to the translation API, and writes the returned text straight into the target-language translation for that record. We batch requests to respect provider rate limits and character quotas, cache results to avoid re-billing identical strings, and log every call (source, target, character count, status) in a dedicated model with ir.model.access.csv and record rules so usage is auditable. Bulk translation runs as a queued/automated action so translating an entire product catalog or website menu tree does not block the UI, and re-translation is idempotent — untouched source strings are skipped.

Because it is built to your scope, we ground it in the models you actually run: product.template/product.product names and descriptions, website.page and QWeb content, mail.template bodies, CRM and Sales terms, or any custom model with translatable fields you nominate. Field-level, record-level, and full-model bulk modes are all options; you decide which languages are in scope from the ones already installed in res.lang. The connector honors Odoo's own active-language set, supports formality and glossary/termbase controls where the provider offers them so brand and product terminology stays consistent, and degrades gracefully — an API failure leaves the existing translation untouched and surfaces a clear message rather than corrupting data. We target Odoo 17.0, 18.0, or 19.0 and work with both Community and Enterprise (Enterprise's website and knowledge apps simply give the connector more surfaces to translate).

Delivery is build-to-order: it does not exist as a finished download today. After a short scoping call we confirm the exact models, fields, languages, and bulk-vs-on-demand behavior, then build against your Odoo version, test on a staging clone, run UAT with you, and install to production with a rollback plan. Typical delivery is one working week from confirmed scope. Pricing starts from $999 (indicative, single-company base scope); wider language coverage, additional models and custom fields, glossary/termbase setup, multi-company deployment, and back-translation of large existing catalogs increase the quoted scope. You receive a fixed quote after the scoping call — the from-price is a starting point, not a firm total.