$ 57.07
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 1906 |
| Technical Name |
odoo_deepl_translation |
| License | OPL-1 |
| Website | https://www.atharvasystem.com/odoo-development |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 1906 |
| Technical Name |
odoo_deepl_translation |
| License | OPL-1 |
| Website | https://www.atharvasystem.com/odoo-development |
Odoo DeepL
Translation
Automatically translate your Odoo records into multiple languages using the DeepL API with support for bulk, real-time, and glossary-based translations.
Key
Features
DeepL API Integration
Powered by DeepL's world-class neural machine translation for highly accurate, natural-sounding translations.
Model & Field Configuration
Configure any Odoo model and select specific translatable fields (char, text, html) for translation.
Real-Time Auto Translation
Automatically translate records on create or update with the Auto Translation feature.
Bulk Translation
Translate all records at once with chunked processing, or select specific records from the list view using Server Actions.
Translation History
Track every translation with detailed history records showing source, target, field-level data and timestamps.
Glossary Support
Create and sync DeepL glossaries to ensure consistent domain-specific terminology across all translations.
HTML/XML Field Support
Intelligent term-based translation for HTML and XML fields, preserving markup structure while translating content.
Multi-Language Support
Translate into multiple target languages simultaneously from a single source language.
Usage Tracking
Monitor DeepL API character usage and expected token counts directly from the settings page.
How It
Works
Enable DeepL Integration
Step 1Navigate to Settings > DeepL Configuration and enable the Enable DeepL Integration checkbox to activate the translation service.
Enter DeepL API Key
Step 2Enter your valid DeepL Translation API key. The key can be obtained from your DeepL account (Free or Pro plan supported).
Validate API Key & View Usage
Step 3Click the Validate button to verify your API key. Once validated, the Usage Status section displays your character consumption and remaining quota.
Configure Translation Models
Step 4Click Configure Translation Models or navigate to Settings > Translations > Translation Model Configuration to set up which models and fields should be translated.
Translation Model Configuration
ConfigurationSelect the Model to translate, set Source and Target Languages, configure settings like Override Existing Translation, Auto Translation, and Translation History. Choose specific fields from the Model Fields tab.
Calculate Expected Tokens
Token EstimationUse the Calculate Expected Tokens action from the gear menu to estimate how many DeepL API characters will be consumed when translating all records.
Bulk Translate All Records
Bulk TranslationClick the Translate button on the configuration form to start translating all records for the configured model in optimized chunks.
Create Server Action
Server ActionClick the Create Action button to create a server action that allows translating selected records directly from any view of the configured model.
Translate Individual Record
Record TranslationOpen any record, click the action menu, and select Translate Record to translate that specific record into all configured target languages.
Translation Results
ResultsAfter translation, open the field's translation dialog to see the translated values in each target language (e.g., German: "Buch", Slovenian: "Knjiga" for "Book").
Bulk Translate from List View
Bulk ActionSelect multiple records from the list view, click Actions, and choose Translate Record to translate all selected records at once.
Auto Translation on Create
Auto TranslationEnable Auto Translation in the config to automatically translate fields whenever a new record is created. Translations are applied instantly.
Auto Translation on Update
Auto TranslationWhen a record is updated (e.g., adding a description), the translation is automatically triggered for the modified fields, including HTML content.
Manage Actions & History
ManagementUse the Unlink Action button to remove the server action. Click the Translation History smart button to view all past translations. Toggle Translation History on or off as needed.
Translation History List
HistoryView all translation history records with details including model name, record ID, source & target languages, and the translation timestamp.
Translation History Detail
History DetailEach history record shows field-level translation data with Source and Target values. Click Open Record to navigate directly to the translated record.
DeepL Glossary Configuration
GlossaryNavigate to Settings > Translations > DeepL Translation Glossaries to manage glossaries for consistent terminology in translations.
Create Glossary Entries
Glossary SetupSet the glossary name, source and target languages, then add Source Text and Target Text entries. DeepL will use these mappings during translation.
Sync & Activate Glossary
Glossary SyncEnable Is Active Glossary, then click Sync Glossary to push it to DeepL. The status updates to Synced Glossary once complete. Use Remove Glossary to delete it from DeepL.
Depending on your DeepL plan, you may have multiple synced glossaries. If you reach the glossary synchronization limit, you can deactivate a glossary and click the "Remove Glossary" button to remove it.
When the "Remove Glossary" button is clicked, the glossary is permanently removed from the DeepL server associated with the current API account.
Glossary in Action
ResultWhen records are translated, DeepL uses the glossary entries. For example, "Thanks" is translated to "Thank you" based on the configured glossary mapping.
Supported Languages
Important
You may
also like
Atharva System
Innovating Odoo experiences for Enterprise and Community users.
Odoo 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