Multi-Module Translation Batches
Group any number of installed Odoo modules into a single translation batch tied to one target language. Source keys never bleed across modules.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 627 |
| Technical Name |
mrm_translation_studio |
| License | LGPL-3 |
Odoo · Translation & Localization App
Translation Studio
Translation Studio
Translate Odoo modules at native speed
The complete Odoo translation manager. Edit every translatable string
inline, fill the blanks with Google auto-translate in one click,
and write back the native .po files directly inside each
module — without ever leaving Odoo.
Overview
The complete Odoo translation workflow — inside Odoo
Translation Studio is a purpose-built Odoo translation
management app that replaces the painful round-trip of exporting .po
files, editing them in an external tool like Poedit, and importing them back. Pick the
installed modules you want to translate, pick a target language, and edit every
translatable string in a single searchable, filterable grid: code translations,
model field labels and model_terms all in one place.
When you are done, click one button to save a clean i18n/<lang>.po file
inside each module — perfectly compatible with Odoo's native translation loader and ready
to commit to git. Or push the translations live into the running Odoo database
to preview the result without restarting anything.
Translation Studio is built for module developers, localization teams, translation agencies, and anyone running Odoo in more than one language. It works with every language Odoo supports, including right-to-left (RTL) scripts such as Arabic and Hebrew, and complex East-Asian scripts such as Chinese, Japanese and Korean.
Core Features
Everything you need to translate Odoo modules
One app, one workflow, zero external tools.
Inline Translation Editor
Edit every translatable Odoo term in a clean editable list. Source keys are read-only, translation values are one click away — no popups, no modal forms.
Smart Filters & Full-Text Search
Filter by module, translation status (translated vs. untranslated), term type (code, model, model_terms), or search across source and translation text.
Google Auto-Translate (No API Key)
Fill every empty translation by calling Google Translate with one click. No API key, no billing setup. A built-in throttle keeps large batches safe.
Native .po File Generator
Write back a clean i18n/<lang>.po file per module on disk — perfectly compatible with Odoo's translation loader and friendly to git diffs.
Apply Translations Live
Push edited translations directly into the running Odoo database for instant preview. Model and model_terms strings apply immediately, no restart.
Idempotent Reload
Reload a batch at any time — previous lines are wiped and rebuilt from the modules' current state, so the batch never drifts out of sync with reality.
Stateful Workflow
Draft → Loaded → Done lifecycle keeps batches organized. Sequence-generated references (TR/00001, TR/00002…) make tracking effortless.
Import & Export Shortcuts
Direct shortcuts to Odoo's standard language import and export wizards sit right next to your batches — no menu hunting required.
Safe by Default
Read-only source keys, unique constraints per (batch, module, key), confirmation prompts on destructive actions. Hard to break, easy to use.
Zero External Dependencies
Pure Python plus polib and requests. No SaaS, no API keys, no Docker sidecar. Install and use immediately.
RTL & Multi-Script Ready
Built for Arabic, Hebrew, Persian, Urdu, Chinese, Japanese, Korean, Thai and every other language Odoo supports out of the box.
How it works
From zero to fully translated module in four steps
A workflow designed to be the shortest path between "untranslated module" and "shipped .po".
1 · Create a Batch
Pick one or more installed modules and a single target language. The batch reference (TR/00001…) is auto-generated by sequence.
2 · Load Translations
Pull every translatable term from each selected module — code strings, model fields, and model terms — into one searchable list.
3 · Edit or Auto-Translate
Type translations inline, filter what you need, or let Google fill in the blanks. Edits are saved as you go on each line.
4 · Save or Apply
Write back native .po files inside each module on disk — or apply the translations live to the running Odoo database.
Why teams choose it
Built for developers and localizers alike
✓
No external tools neededForget Poedit, gettext or third-party SaaS — everything happens inside Odoo's UI.
✓
Source-control friendlyGenerated
.po files use the exact format Odoo writes, so diffs stay clean in git.✓
True multi-module supportTranslate many modules in one pass while keeping each module's PO file isolated.
✓
Zero external dependenciesPure Python with
polib and requests — no setup, no API keys, no SaaS sign-up.✓
Safe by defaultRead-only source keys, unique constraints, and confirmation prompts on destructive actions.
✓
RTL & multi-script readyWorks with Arabic, Hebrew, Chinese, Japanese, Korean and every language Odoo supports.
✓
Open Source — LGPL-3Free to install, free to modify, free to redistribute under the LGPL-3 license.
✓
Built for Odoo 18Native compatibility with Odoo Community and Enterprise — no compatibility shims.
Use cases
Made for every translation workflow
Odoo Module Developers
Ship multi-language modules from day one. Generate clean .po files for every release without leaving your dev instance.
Localization Teams
Empower in-house translators to work directly in the Odoo UI without needing a developer to export and import files.
Multi-Country Rollouts
Standardize translations across regional deployments by managing every language from a single batch dashboard.
Custom Implementations
Translate client-specific custom modules at deployment time and commit clean PO files back into the client repository.
Translation Agencies
Auto-translate first drafts with Google, then have human reviewers refine inline — cuts initial-pass time by up to 80%.
Open-Source Contributors
Generate the official PO files community projects expect — no formatting drift, ready to commit to upstream repos.
SaaS & Multi-Tenant Hosts
Maintain one canonical translation set per language and push it to every tenant database with a single click.
Arabic / RTL Deployments
First-class Arabic, Hebrew and Persian support — including correctly mirrored fields, layouts and PO file encoding.
Language coverage
Translate Odoo into 100+ languages
Translation Studio works with every language Odoo supports. A few of the most-requested:
العربية (Arabic)
English
Français
Español
Deutsch
Italiano
Português (BR/PT)
Nederlands
中文 (简体/繁體)
日本語
한국어
עברית (Hebrew)
Русский
Türkçe
Polski
हिन्दी
ภาษาไทย
Tiếng Việt
Bahasa Indonesia
فارسی (Persian)
اردو (Urdu)
Svenska
Suomi
Ελληνικά
+ many more
Technical details
Compatibility & specifications
- Odoo Version
- 18.0 Community & Enterprise
- Module Version
- 18.0.1.0.0
- License
- LGPL-3
- Category
- Tools / Localization
- Dependencies
- base
- Python Libraries
- polib, requests
- Access Group
- Settings / Administration
- Author
- DevMRM
- Languages
- 100+ supported
- RTL Support
- Yes (Arabic, Hebrew, Persian, Urdu)
- External APIs
- Google Translate (free, no key)
- Database Impact
- Live model + model_terms apply
FAQ
Frequently asked questions
Everything you need to know before installing Translation Studio for Odoo 18.
Does Translation Studio require a Google Translate API key?
No. Translation Studio uses Google Translate's free endpoint — no API key, no billing setup, no third-party SaaS sign-up. A built-in throttle prevents rate-limit hits when translating large batches.
Where are the generated .po files written on disk?
Each Odoo module receives its own i18n/<lang>.po file under that module's own path. Source keys never cross module boundaries, so every module stays self-contained, version-control friendly, and ready to commit to git.
Does the "Apply to system" action update code-level translations too?
Model and model_terms translations apply immediately to the running Odoo database. Code translations live only inside PO files, so they take effect after clicking Create / Update PO file and reloading the module.
Can I translate multiple Odoo modules in the same batch?
Yes. You can add any number of installed modules to a single translation batch. Each translation line stays tied to its source module, so the resulting .po files are generated correctly per module.
What happens if I reload a batch that already has edits?
The "Load Translations" button rebuilds the batch from the modules' current state — any unsaved edits are discarded. A confirmation prompt protects you from accidental reloads.
Does it work with Arabic, Hebrew, Chinese and other non-Latin languages?
Yes. Translation Studio works with every language Odoo supports, including right-to-left scripts (Arabic, Hebrew, Urdu, Persian) and complex scripts (Chinese, Japanese, Korean, Thai).
Who can access the Translation Studio?
By default, only users in the Settings / Administration group. You can adjust this via Odoo's standard access rules and record rules.
Will Google auto-translate overwrite my existing translations?
Not unless you explicitly opt in. Auto-Translate (Google) fills only empty translations by default. A separate Re-translate All button overwrites existing values, with a confirmation prompt.
What Odoo are supported?
Translation Studio is built for Odoo Community and Enterprise. It depends only on the Python libraries.
Stop juggling .po files. Translate Odoo the right way.
Install Translation Studio for Odoo and ship multi-language modules with confidence.
Please log in to comment on this module