Skip to contentv0.1.0
PIMgate

// Blog

The translation workflow in PIMgate: what you gain as a customer

Product data and CMS content in one flow: agency, AI and your team with clear roles, parallel orders, review rounds and a documented release. Seven benefits from the customer's side.

8 min readPIM Gate teamMarketing & localization

TRANSLATION · WORKFLOWPIMper exportIbexa DXPper packageOrderTEAM · DUE DATEReview roundAGENCY · AI · REVIEWERSReleasePROTOCOL · SHA-256ALWAYS CLEAR WHOSE TURN IT IS

Most companies have good translators. What goes wrong happens around them: exports pulled by hand and sent as attachments. The whole catalogue going out again although only a few attributes changed. Corrections bouncing around in email threads. And in the end a release where nobody can say who reviewed and approved what.

PIMgate turns translation into orders — for product data from your PIM and for content from your CMS. Every order has a team, a due date, review rounds and ends with a release. An earlier post covered the mechanics behind it: delta, translation memory, terminology. This one is about the question that matters to you: what do you gain?

1. You only pay for what changed

Every imported PIM export creates one order per target language with the translatable entries. A delta export only changes what it contains; if the orders for a language are already released, changes land in a follow-up order with exactly those changes.

On top of that, a dictionary value used on 300 products is one entry — and one line for the agency. PIMgate shows the reach ("applies to 46 products") so a correction is made once for all of them.

The gain is directly measurable: smaller packages for the agency, fewer words on the invoice, shorter turnaround. And nothing gets lost between two deliveries, because PIMgate reconciles every entry against the order.

2. Your agency stays — and works better prepared

PIMgate does not replace your translation agency. It keeps working in its own TMS or CAT tool with its own translation memory. PIMgate sends it smaller, better-prepared work:

  • a package as a ZIP with a manifest and checksums, in XLIFF 1.2 or 2.0, TMX or — for Ibexa content — plain XML or JSON for agencies without a CAT tool;
  • a signed link that expires, and a download that is logged;
  • a work basket of its own with the corrections it owes per order — and nothing else from your system.

Due dates, correction deadlines and reminders run automatically. Your team no longer has to chase anyone to find out whether a link arrived.

3. AI where it helps — and never without people

AI in PIMgate is not a replacement for review but a tool in clearly defined places:

  • Interim texts for product data. If a translation is still missing, AI fills it as a marked interim text so the shop and portal stay readable. The agency's next delivery replaces it.
  • Drafts for CMS content. For content from Ibexa DXP, AI can produce the first draft. A person reads, edits and confirms every draft before it goes to Ibexa — even without any agency.

Exact matches from the translation memory are reused before any AI call. Your glossary goes to the model as binding terminology, with instructions per field group; a field category can be locked for AI entirely. Language rules apply to every result — Swiss German always gets "ss". And a monthly budget shows how much AI was used and who may use it.

What you gain: a website that never shows empty fields, and AI costs you control — without an unreviewed text passing as "done".

4. Everybody knows whose turn it is

The biggest time sink in translation projects is the question "who has this right now?". In PIMgate every order has its own team: reviewers, people from the agency and one responsible person — with several people per role, for example two translators for one language.

The order's phase bar names the person who has to act now, and exactly that person gets the email. Correction lists, comments and replies go only to that order's team; each person chooses immediate, daily, weekly or no notifications. In the work basket everyone sees their orders in one list, with exactly one main action per row and overdue items on top.

For occasional users there is the "Simple" view: a phase bar, a "Next step" box and exactly the action that is due. Whoever wants to go deeper switches to "Expert" with all entries, deliveries, objections and the history.

The gain: less coordination, fewer emails, fewer orders left lying around.

5. Many orders in parallel, without confusion

Languages, exports and content areas move at their own pace. PIMgate runs several orders side by side — per language, per export and per catalogue or content area. For the same export and language, several orders may run as long as they cover different areas; shared entries show in the preview, and one delivery updates every affected order.

For content from Ibexa DXP you create the order first — languages, due date, team — and then collect content from any area into it: whole content items or single fields. Everything is sent in one package, into exactly that order.

What you gain: the product launch in France does not have to wait for catalogue maintenance in Italy — and it stays clear which order covers what.

6. Review in context — and a release you can prove

Reviewers see the product the way the website shows it, master and target language side by side — not isolated strings in a spreadsheet. Each value gets one of three verdicts: "fits", "does not fit" with a comment, or "suggest a correction" with the wording you want. Every agency delivery opens a review round that shows what it brought.

When nothing is open any more, the products are released — on request under the four-eyes principle. The release produces a protocol as PDF, CSV and JSON, each with a SHA-256 checksum and stored immutably: per entry the master text, the released value, the rounds, comments, corrections and whether AI was involved.

The gain: quality you can prove — to your management, your markets and, where needed, to authorities.

7. Product and website speak the same language

Product texts come from the PIM, page content from the CMS. PIMgate runs both with the same phases, the same roles and the same release. Confirmed CMS translations go to Ibexa DXP as a new version — immediately or on a date — and conflicts become visible when something changed in Ibexa or in the master.

Your PIM stays untouched: PIMgate never writes into your PIM. The agency delivers through your PIM import, and the release status reaches catalogue, portal and API.

In short

You gain …… because PIMgate
lower translation costssends only changes and keeps every value once
a relieved agencydelivers clean packages, deadlines and a work basket of its own
no empty fields in the shopuses AI interim texts and drafts that people confirm
less coordinationgives every order a team and says whose turn it is
speed per marketruns orders in parallel
provable qualityruns review rounds and an immutable release protocol
one consistent languagetranslates product data and CMS content in the same flow

The translation module is in daily use at a DACH manufacturer with more than 20,000 products. If you want to see how your orders would run, we sketch your process in a 90-minute translation workshop — with your languages, your PIM and CMS and your agencies. Pricing will be published in Q1 2027.

Put a gate between your catalog and chaos.