AI-generatedTranslate and localize product data with OMN
New markets need suitable product descriptions, images and documents. OMN helps you organize multilingual product content, connect translation services and guide your team from source text to approval.
Work on translations alongside your products
When descriptions, variants and language versions live in separate files, every product change creates a coordination task. OMN PIM brings product information together. Its Metadata Translation view provides source and target texts for configured product attributes.
Editors and translators can work on texts, exchange notes and corrections, and track translation status. Manual approval can be configured with the appropriate permissions. This keeps language work connected to the product. The views and functions your team uses are configured around your workflow.
Distinguish language, market and channel
Translate texts
Product names, descriptions and attributes need suitable language versions. Decide which fields to translate, which terms to use consistently and which values, such as item numbers, must stay unchanged.
Localize content
A market may require a different assortment, units, documents or images. Define these requirements separately. Translating a text alone does not verify the accuracy of a unit conversion or whether an image is suitable for the target market.
Prepare content for channels
Stores, marketplaces and catalogs may require different text lengths and mandatory information. Plan the versions and approvals each channel needs. Our PIM and DAM solution for retail explains how variants and media work together across large catalogs.
From source text to an approved language version
- Prepare the source data: Check product references, attributes and source texts. Define the source language and the fields to translate. Errors in the original can carry over into other languages.
- Agree terminology: Maintain preferred technical terms and product names in the terminology tool. Decide who is responsible for these terms and their updates.
- Create the translation: Edit target texts in OMN or use a configured translation service. Choose the target language, content and method for the task.
- Review and approve: Have the result checked for terminology, measurements, claims and tone. Use notes and corrections, and configure the manual approval your process requires.
- Deliver to the target channel: Agree how approved content is passed to each connected system. Also test what happens to reviewed translations when the source text changes later.
The OMN Metadata Translation documentation (German) describes its views, status information and approval options.
Connect translation services and terminology
OMN documents integrations with DeepL, Google, Microsoft and SYSTRAN. The services and language pairs available in your environment depend on configuration, provider and contract. For DeepL, the OMN documentation lists a licensed connector and a DeepL API Pro subscription as prerequisites. We establish the current scope and terms for your project.
OMN Terminology lets you maintain terms and translations in glossaries. It can be connected to Metadata Translation; support for DeepL glossaries is also documented. This gives your team and the configured translation process a consistent vocabulary. Expert review of the results remains part of the workflow.
Already using a translation management system or a translation memory? We assess the specific system, exchange formats and how edited texts return to OMN. The scope and effort of the integration are agreed in advance.
Example: a product description changes
Consider this planning example: your team adds new installation information to the German description of a light fixture. Its English and French texts have already been approved. Agree a process for this situation:
- Identify the change: Which products, variants and text fields are affected?
- Review target texts: Which language versions need an update, and which remain valid?
- Apply terminology: Which term should describe the new component in each language?
- Check related material: Do the instructions and images still match the description? OMN DAM manages the related media.
- Approve again: Who reviews the change, and when may it be sent to the store or catalog?
Test this workflow with your data. Explicitly agree how changes are identified, previously edited texts are protected and outstanding tasks are made visible.
What to establish before implementation
To define a useful project scope, we look at the number of products and text fields, required language pairs, update frequency and participating teams. A pilot should include typical technical terms, variants, longer texts and corrections.
Account for the costs of OMN functions, configuration, translation services and expert editing. Also establish which content may be sent to external services and which operational and contractual requirements apply. Our deployment and security overview helps frame those decisions.
Questions about product data translation
Can OMN translate texts automatically?
Yes. Configured AI translation services can translate product texts. Supported languages, scope and processing time depend on the service and configuration. Plan the expert review and approval your content requires.
Is translation included at no additional cost?
That depends on the agreed scope. Connectors, external services, configuration and editorial review need to be considered in the proposal. For example, the OMN DeepL documentation (German) lists a licensed connector and an API Pro subscription.
Are units and images localized automatically?
Translation does not establish rules for measurements, rounding, local assortments or image selection. These requirements are agreed and tested in the data model and workflows. Responsible specialists check whether the content is suitable for each market.
Can our translators and local market teams stay involved?
Metadata Translation supports text editing, notes, corrections and approvals. Access, permissions and responsibilities are configured for your team. If work takes place in an external system, we assess the required connection separately.
Let’s discuss your language and market workflows
Bring a typical product record, your target languages and an example of a change. We will show you how the work can be organized in OMN and which integrations and approvals you need.