A · Product data translation
Attributes, descriptions, feature texts and asset metadata from your catalog. Delta-only, deduplicated, reviewed per language, published to portals, channels and API.
TRANSLATION & LOCALIZATION2026
Translate only what changed — in your terminology, reviewed by your people.
PIM Gate translates product data at attribute level: it detects what changed, reuses your translation memory, enforces your termbase, routes each language to the engine you choose and puts every proposal in front of the right reviewer. For content in Ibexa DXP and Drupal, the same workflow is coming soon.
DELTA ONLYTMX · TBX · XLIFFYOUR ENGINE, PER LANGUAGE
messara.pimgate.ai / translation / review / en-GBTranslation
MS-12011· short_descriptionTM match 96%Queued
Source · de-DE
Kompakter Inline-Durchflussmesser für Trink- und Brauchwasser, Nennweite DN 40, Druckstufe PN 16, Gehäuse aus Messing CW617N.
Target · en-GB
Compact inline flow meter for potable and process water, nominal width DN 40, pressure rating PN 16, brass CW617N body.
Terminology 1/1Engine MT+LLMReviewer a.keller
Reviewer comment · 2026-09-24 10:14
Keep “flow meter” — the glossary entry overrides the engine’s “flowmeter”.
1 / 48
| short_description | MS-12011 | 96% | Queued |
| long_description | MS-12011 | 71% | Queued |
| feature_bullet_1 | MS-12014 | 100% | Accepted |
| mounting_note | MS-13402 | 0% | Queued |
PRODUCT DATA · 2026 · IBEXA DXP / DRUPAL · COMING SOON
01 · The problem
Translation is where multilingual catalogs slow down.
01
Whole files, every time.
A few changed attributes trigger a full re-export. Agencies re-translate — or re-check and re-bill — text that was already translated.
02
The same string, a thousand times.
"Brass, nickel-plated" appears on hundreds of products. Without deduplication it is translated, reviewed and paid for again and again.
03
Terms drift.
Without an enforced termbase, one product says "pressure gauge", the next "manometer", the website a third thing.
04
Translators in foreign systems.
They are asked to log into a PIM or CMS they don't know, instead of working in their own CAT tool.
We changed one attribute on 800 products — and got a translation quote for 40,000 words.
02 · Overview
Two workflows. One memory, one termbase, one review.
Product data and marketing content usually live in different systems and get translated by different processes. PIM Gate brings them onto one foundation — so your product pages and your website speak with one voice.
Shared foundation
Translation memory (TMX), termbase (TBX), engine routing per language, reviewer roles, audit log and cost reporting — the same for both workflows.
B · Content translation for Ibexa DXP and Drupal
Articles, landing pages and product stories from your CMS, translated with the same memory and terminology, written back as draft language versions. Early access.
PART A · PRODUCT DATA TRANSLATION2026
03 · The pipeline
Every segment takes the shortest path to an approved translation.
PIM Gate doesn't translate files. It translates segments — single attribute values and sentences — and decides for each one whether it needs to be translated at all, whether your memory already has it, and who has to see it before it goes live.
ILLUSTRATIVE FIGURES · ONE WEEKLY RUN · ONE TARGET LANGUAGE
- 01
Detect.
Each source segment carries a hash. When a record comes through the gate, only segments whose hash changed are picked up.
- 02
Deduplicate.
Identical segments across products are collapsed into one — translated once, applied everywhere.
- 03
Reuse.
The translation memory is checked for exact and fuzzy matches before anything is sent to an engine or translator.
- 04
Apply terminology.
Approved and forbidden terms from your termbase are passed to the engine and checked on the result.
- 05
Translate.
New and fuzzy segments go to the engine you configured for that language — or into a package for human translators.
- 06
Review.
Proposals land in the review queue of that language, with TM matches, term hits and constraints visible.
- 07
Approve.
Approved segments update the translation memory and the record — status per attribute.
- 08
Publish.
Translations flow to portals, channels and the API with the next delivery — as delta, like everything else.
04 · 04 · Delta and deduplication
Translate once. Apply everywhere. Never again unless it changes.
PIM Gate stores a hash for every source segment together with its context — attribute, product type, locale. When your PIM delivers an update, only segments with a new hash enter the pipeline. A value that appears on 800 products, such as "Messing, vernickelt", is one segment: translated once, reviewed once, applied to all 800.
- Hash per segment, computed on normalised source text and context
- Deduplication across products, variants and attributes — with context kept where the same word needs different translations
- Changes to one product never trigger re-translation of others
- Source edits that only touch punctuation or whitespace can be configured to skip re-translation
- Every segment shows where it is used and when its source last changed
0
translatable field values in catalog (12,000 SKU × 14 attributes)
0
unique source segments after deduplication
0
segments changed since last run
0
segments that need a new translation after TM
ILLUSTRATIVE CALCULATION — NOT A BENCHMARK
05 · Translation memory and terminology
Your translation memory, finally working for the catalog.
Your translation memory, finally working for the catalog.
Import the TMX files your agencies have built up over the years. PIM Gate matches every segment against them — exact matches are reused directly, fuzzy matches are passed to the engine or translator as a starting point. Every approved translation flows back into the memory, so it grows with every run.
- TMX import and export, per language pair
- Exact and fuzzy matches with configurable thresholds
- Context-aware matching (attribute, product type)
- Approved segments update the memory automatically
- Memory stays yours — export it any time
Your words, enforced — not just suggested.
Import your termbase as TBX. Approved terms are passed to the engine as a glossary; forbidden terms are flagged in every proposal before a reviewer sees it. Reviewers can suggest new terms from the queue; your terminology owner approves them.
- TBX import and export
- Approved, preferred and forbidden terms per language and locale
- Glossary passed to engines that support it; check on every result regardless of engine
- Violations block approval or warn — your choice per language
- Term suggestions from reviewers, approved by the terminology owner
TERM CHECK · 1 VIOLATION · "manometer" (FORBIDDEN) in MS-12044 · short_description
Term (de-DE) · en-GB · Status · Note
Manometer pressure gauge APPROVED not "manometer"Manometer manometer FORBIDDENSanitär sanitary APPROVED not "plumbing"Rohrfeder Bourdon tube APPROVEDWarmwasserspeicher (de-CH) Boiler APPROVED locale variant06 · Engines and locales
The right engine for each language. The right variant for each market.
Translation quality differs by language pair and content type. PIM Gate lets you choose the engine per language or market — and change it without touching your workflow.
Connect DeepL, OpenAI, Anthropic, Azure OpenAI or EU-hosted and local models. Each target language gets a profile: engine, prompt and glossary settings, review policy, reviewers and channel constraints. Locale variants such as de-CH or en-US are derived from their base language with rules and locale-specific terms, instead of being translated from scratch.
| Target | Engine | Policy | Reviewers | Constraints |
|---|---|---|---|---|
| en-GB | DeepL | MT proposal → review | 2 | channel shop: title ≤ 80 |
| en-US | derived from en-GB | locale rules → review | 1 | spelling US |
| fr-FR | Anthropic | MT proposal → review → approve | 2 + approver | — |
| it-IT | EU-hosted model | MT proposal → review | 1 | — |
| de-CH | derived from de-DE | locale rules → spot check | 1 | ß → ss, CH terms |
| pl-PL | LSP package (XLIFF) | human only | agency + reviewer | — |
- Engine per language or market; switch or compare engines on a sample before changing
- Locale derivation: de-DE → de-CH (ß → ss, Swiss terms, number format), en-GB → en-US (spelling, terms)
- Locale-specific termbase entries override base-language terms
- Fallback chains for display when a translation is pending, e.g. de-CH → de-DE → en-GB
LOCALE DERIVATION
de-DE "Anschlussgröße G 1/4, Außengewinde"de-CH "Anschlussgrösse G 1/4, Aussengewinde" RULE ß→ssen-GB "Colour: aluminium grey"en-US "Color: aluminum gray" RULE en-GB→en-US07 · Constraints
A translation isn't finished until every channel accepts it.
Length limits.
Maximum length per attribute and channel — a marketplace title, a label field, a PDF table cell. Over-length proposals are flagged before review.
Placeholders and markup.
Variables like {size}, line breaks and inline tags are protected during translation and checked on return.
Units and codes.
Units, thread sizes, standards and article numbers — "G 1/4", "DN 15", "EN 837-1" — are locked and never translated.
Forbidden content.
Terms, characters or patterns a channel rejects are caught at the gate, not by the channel.
VALIDATION · MS-12011 · fr-FR · title · 94/80 CHARS · BLOCKED FOR CHANNEL shop-fr · placeholder {size} OK · unit "bar" OK
08 · 07 · Review and governance
Nothing is published without the review you configure.
Every proposal — from an engine, from memory or from an agency — goes through the review policy of its language. Reviewers see the source, the proposal, TM matches, term hits and channel constraints side by side. They approve, edit or request changes with a comment. Status is tracked per attribute and per language, so you always know what is live, what is waiting and why.
- Queues per language, filterable by product group, attribute, channel or due date
- Roles: translator, reviewer, approver, terminology owner, localization manager
- Four-eyes principle: the person who edited cannot approve
- Comments per segment, visible to translators and agencies on re-import
- Configurable policy per language and attribute group: MT as proposal with review, human only, or TM exact matches auto-approved
- Every step recorded in the append-only audit log
messara.pimgate.ai / translation / review / en-GBTranslation
MS-12011· short_descriptionTM match 96%Queued
Source · de-DE
Kompakter Inline-Durchflussmesser für Trink- und Brauchwasser, Nennweite DN 40, Druckstufe PN 16, Gehäuse aus Messing CW617N.
Target · en-GB
Compact inline flow meter for potable and process water, nominal width DN 40, pressure rating PN 16, brass CW617N body.
Terminology 1/1Engine MT+LLMReviewer a.keller
Reviewer comment · 2026-09-24 10:14
Keep “flow meter” — the glossary entry overrides the engine’s “flowmeter”.
1 / 48
| short_description | MS-12011 | 96% | Queued |
| long_description | MS-12011 | 71% | Queued |
| feature_bullet_1 | MS-12014 | 100% | Accepted |
| mounting_note | MS-13402 | 0% | Queued |
NEW → MT PROPOSED (DeepL, 2026-09-22 06:02) → IN REVIEW (a.rossi) → CHANGES REQUESTED → IN REVIEW → APPROVED (m.keller, 2026-09-23 14:10) → PUBLISHED v2026.38
FOUR-EYES ✓ · reviewer ≠ approver
| Permission | Translator | Reviewer | Approver | Terminology owner | Localization manager |
|---|---|---|---|---|---|
| Edit proposals | ✓ | ✓ | — | — | — |
| Comment | ✓ | ✓ | ✓ | ✓ | ✓ |
| Request changes | — | ✓ | ✓ | — | — |
| Approve | — | — | ✓ | — | — |
| Edit termbase | — | — | — | ✓ | — |
| Configure engines & policies | — | — | — | — | ✓ |
| Export / import packages | — | — | — | — | ✓ |
2026
09 · Agencies and LSPs
Your translators stay in their CAT tool.
Many companies work with trusted agencies and in-house linguists. PIM Gate doesn't replace them — it sends them less and better-prepared work.
- 01
Export a package.
Only new and fuzzy segments for one language, deduplicated, with context, TM matches and terminology attached. XLIFF 2.x or XLSX.
- 02
Send it your way.
Download, email or hand over through your LSP's usual channel. No account in PIM Gate needed.
- 03
Translate in the CAT tool.
The agency works in the tool it already uses, with the TMX and TBX you provide.
- 04
Re-import and validate.
PIM Gate checks segment IDs, placeholders, lengths, terminology and whether the source changed since export. Problems are listed per segment.
- 05
Review and publish.
Imported translations enter the review queue like any other proposal — or are approved directly if your policy trusts that agency.
Packages are small because they contain only what changed and each string only once. Agencies quote on real work, not on repetitions.
FORMATS · XLIFF 2.x · XLSX · TMX · TBX · PACKAGE fr-FR-2026-38.xlf · 342 SEGMENTS · 2,910 WORDS · 0 DUPLICATES
10 · Publish and report
From approval to every channel — with the numbers to prove it.
Publish everywhere at once.
Approved translations reach portals, feeds and the API with the next delivery, as field-level delta. Optional write-back to your PIM where you configure it.
Fallback chains.
While a translation is pending, channels show the fallback you define — e.g. de-CH → de-DE — or hold the product back, per channel.
Cost and time transparency.
Every job reports segments, words, TM leverage, engine usage, AI credits and review time per language — the basis for budgeting and for talks with your agencies.
JOB REPORT
JOB tr-2026-38-fr-FR COMPLETED 2026-09-23 16:42SEGMENTS CHANGED 1,180TM EXACT 610 52%TM FUZZY 228 19%NEW 342 29%ENGINE DeepL · 570 segments · 4,120 wordsAI CREDITS USED 570REVIEW TIME (median) 1 d 4 hPUBLISHED v2026.38 → portal:customer · feed:shop-fr · apiILLUSTRATIVE
IN PRODUCTION · de-DE · de-CH · en-GB · WITH TM AND TERMINOLOGY
PART B · CONTENT TRANSLATION FOR THIRD-PARTY SYSTEMSCOMING SOON
11 · Content translation · Early access
The same memory and terminology — for your website content.
Product pages and marketing content should say the same thing in the same words. We are extending the PIM Gate workflow to content in Ibexa DXP and Drupal. The connectors are in early access — here is how they are designed to work.
- 01
Pull.
The connector reads content items and their translatable fields from the CMS — only for content types and fields you select.
- 02
Segment safely.
Rich text is split into sentences while tags, links, embeds and placeholders are protected and restored exactly.
- 03
Translate with shared assets.
The same translation memory, termbase and engine routing as for your product data.
- 04
Review in context.
Reviewers see the translation in a preview of the page, not only as a list of sentences.
- 05
Write back as draft.
Approved translations are written to the CMS as a draft language version. Your editors publish them with the CMS's own workflow and permissions.
- 06
Update only what changed.
When the source content is edited, only the changed paragraphs are sent for translation again.
12 · Connectors
Built for Ibexa DXP and Drupal — the CMS stays in charge.
The connectors read content through each system's standard APIs and write translations back the way each system expects: as draft language versions. Nothing is published by PIM Gate. Your editors keep their workflow, their preview and their permissions — they simply find a reviewed translation waiting as a draft.
| Ibexa DXP | Drupal | |
|---|---|---|
| Status | COMING SOON · early access | COMING SOON · early access |
| Versions (planned) | Ibexa DXP 4.6 LTS and 5.x | Drupal 10 and 11 |
| How content is read | REST and GraphQL APIs; content types and fields | JSON:API; entities, bundles and fields |
| Translatable fields | Text line, text block, rich text; selected per content type | Text and formatted text fields; selected per bundle (Paragraphs support to confirm) |
| Language model | Translations as language versions of a content item | Core Content Translation |
| Write-back | New draft version in the target language | Unpublished translation or draft state (Content Moderation) |
| Alternative integration | — | As a translation provider for the TMGMT module |
| Publishing | Ibexa's own workflow and permissions | Drupal's own workflow and permissions |
Technical approach subject to confirmation during early access. Other CMS and DXP systems can be connected via API on request.
COMING SOON
messara.pimgate.ai / dxp / jobs / JOB-2026-0088CMS content
Source · IBEXA DXPJOB-2026-00882026-09-24 · 5 items · 8 language versions
Job items
| Content item | Type | Languages | Status |
|---|---|---|---|
| Flowline series overview | Landing page | en-GB · fr-CH | In review |
| Choosing the right DN | Article | en-GB | Approved |
| Case · District heating | Product story | en-GB · it-IT | Written back |
| Installation basics | Article | fr-CH | Queued |
| Service & warranty | Landing page | en-GB · nl-NL | Queued |
Approved items are written back as draft language versions
In-context previewen-GB
/en/products/flowline-series
The Flowline series, end to end
Six nominal widths from DN 20 to DN 65, one mounting logic, one data sheet family. Choose the body material once and the rest of the configuration follows.
Placeholders 4/4HTML-safe
13 · Designed for content
Rich text in, rich text out — untouched where it matters.
Markup-safe.
Tags, attributes, links, embedded objects and placeholders are protected tokens. Translators see them; they can't break them.
One voice.
Product names, technical terms and claims come from the same termbase as your catalog — the website and the data sheet agree.
Paragraph-level delta.
An edit to one paragraph re-translates that paragraph, not the page.
Tracked per item and language.
Every content item shows its status in every language: queued, in review, approved, written back.
From the team that has built on eZ Publish and Ibexa for many years.
PIM Gate is built by Netgen, a long-standing integrator in the eZ Publish and Ibexa ecosystem, with more than ten years of PIM, commerce and DXP projects in the DACH region. We know how content models, language versions and editorial workflows work in these systems — because we build them.
COMING SOON
Join early access for Ibexa DXP and Drupal.
We are working with a small group of early users to shape the connectors around real content models.
- Early access to the connector for your system and version
- A joint setup on your own content types, fields and languages
- Direct input into scope and roadmap
// EARLY ACCESS
Join early access
14 · Operating models
AI-first, hybrid or human-only — your choice, per language.
There is no single right way to translate. Most customers mix models: AI-first for high-volume attributes, agencies for marketing languages, in-house review for key markets.
| AI-first with review | Hybrid with your LSP | Human-only via packages | |
|---|---|---|---|
| First draft | Engine of your choice, with TM and termbase | Engine or TM pre-translation, post-edited by agency | Agency or in-house translators in their CAT tool |
| Review | Your reviewers in PIM Gate | Agency + your reviewers | Your reviewers in PIM Gate (optional) |
| TM and terminology | Applied automatically | Shared with agency via TMX / TBX | Shared with agency via TMX / TBX |
| Where translators work | PIM Gate review queue | CAT tool + PIM Gate review | CAT tool only |
| Typical for | Technical attributes, large catalogs, frequent changes | Key markets, customer-facing descriptions | Regulated texts, markets where MT is not accepted |
| Main cost driver | AI credits / engine usage + review time | Post-editing rates + review time | Translation rates + review time |
| What PIM Gate does | Delta, dedup, routing, checks, queues, publish | Delta, dedup, packages, validation, queues, publish | Delta, dedup, packages, validation, publish |
15 · Security
Your texts, your providers, your region.
You choose the provider.
Each language uses the engine you approve — including EU-hosted endpoints or local models if texts must not leave a region. You can switch providers without changing your workflow.
Only what's needed leaves the gate.
Engines receive the segments to be translated plus the glossary and context they need — not whole product records, prices or customer data.
Hosted in the EU.
PIM Gate runs in Germany by default, with Swiss hosting on request. Tenant isolation at data level, append-only audit log, GDPR and revDSG compliant by design, DPA available.
EU / CH hostingGDPRrevDSGTenant isolationAppend-only audit
16 · Onboarding
Start with your memory, not from zero.
The "Terminology & translation setup" package gets your existing language assets into PIM Gate and proves the workflow on your own data before you scale.
01
Import.
Your TMX files and TBX termbase, cleaned up where needed (duplicates, conflicting entries).
02
Map.
Which attributes are translatable, per product type and channel; context and constraints per attribute.
03
Profile.
One profile per target language and locale: engine, policy, reviewers, fallback chain.
04
Roles.
Reviewers, approvers and terminology owners set up; agencies briefed on the package format.
05
Acceptance run.
A representative sample translated end to end, reviewed by your team and compared across engines where useful.
06
Go live.
Delta runs switched on, reporting in place, first agency package exchanged.
Terminology & translation setup
On request
Scope depends on the number of languages, the size and state of your TM and termbase, and whether CMS content is included. We'll size it with you in the translation workshop.
Languages per version: S 3 · M 8 · L and XL unlimited. AI credits per month: S 1,000 · M 5,000 · L 20,000 · XL 50,000.
17 · FAQ
Translation & localization
PRODUCT DATA
- Only if you decide so. By default, every engine proposal goes to a human review queue before it is published. You set the policy per language and attribute group — MT as a proposal with review, human-only, or automatic approval for exact translation-memory matches.
- DeepL, OpenAI, Anthropic, Azure OpenAI and EU-hosted or local models — configured per language or market. You can change the engine for a language without changing your workflow.
- Yes. TMX for translation memories and TBX for terminology, per language pair. Both can be exported again at any time.
- Only the changed segment is picked up. The translation memory offers the previous translation as a fuzzy match, so the engine or translator adapts it instead of starting from scratch.
- Locale variants such as de-CH or en-US are derived from their base language with rules (for example ß → ss) and locale-specific terms, then reviewed according to your policy. They are not translated from scratch.
- Only if you configure it. By default, PIM Gate publishes translations to portals, channels and the API, and your PIM remains untouched.
WORKING WITH TRANSLATORS
- Yes. PIM Gate exports XLIFF or XLSX packages with only new and changed segments, without duplicates, with TM matches and terminology attached. Translators work in their own tool and never need a PIM Gate account. On re-import, placeholders, lengths, terminology and source changes are validated.
- Yes. Many customers combine agencies with AI for different languages or content types. Agencies receive smaller packages and quote on real work, not on repetitions.
CMS CONTENT
- The connectors for Ibexa DXP and Drupal are coming soon and currently in early access. They are designed for Ibexa DXP 4.6 LTS and later, and for Drupal 10 and 11. Join early access to get confirmed support for your version.
- No. Translations are written back as draft language versions. Your editors review and publish them with the CMS's own workflow and permissions.
- Other systems can be connected via API on request. Talk to us about your content model.
SECURITY & COMMERCIAL
- PIM Gate is hosted in Germany by default, with Swiss hosting on request. Translation engines are the ones you choose — including EU-hosted endpoints or local models if texts must not leave a region.
- Version S includes 3 languages, M includes 8, L and XL are unlimited. AI credits per month range from 1,000 (S) to 50,000 (XL).
- Yes. You can start with translation for one catalog and a few languages, and add portals or data modules later.
18 · Translation workshop
Map your translation process in 90 minutes.
A remote working session with a PIM Gate architect and a localization specialist. We look at your languages, systems, language assets and current process — and sketch how the gate would run it.
- 01 Your languages, markets and locale variants
- 02 Sources: PIM, CMS, documents
- 03 Existing TM, termbase and agency setup
- 04 Operating model per language
- 05 Next steps and setup scope
We reply within two business days with proposed dates.
// TRANSLATION WORKSHOP
Request a translation workshop
Use case: Multilingual content on Ibexa DXP / Drupal
Illustrative scenario: six languages, one voice.
AI Workflows
Where AI helps across the gate — and where humans decide.
2026
ETIM & BMEcat
Language-independent features, translated descriptions.