Multi-market businesses translate the same descriptions repeatedly, often paying for content that was never signed off. In Pimberly, DeepL is configured as a channel, mapping a source attribute and locale to its target, and the usual controls decide what is eligible: lifecycle stage and grading mean characters are spent on approved content only. Translations are stored as locale values on the same attribute, and when the source changes only the changed attribute is queued again.
With Pimberly’s DeepL translations, you can:
- Configure DeepL as a channel, mapping a source attribute and locale to its target — for example English to Japanese
- Gate translation by lifecycle stage and product grading, so characters are only spent on signed-off content
- Release products to a language channel manually or drive it with an attribute flag, including as a bulk update
- Track pending, failed, skipped and successful requests for each channel from the Connectors listings page
- Store translations as locale values on the same attribute, with no duplicate fields to manage
- Pick up source edits automatically — only the changed attribute is queued again, once per language channel
See how it works in the video below:
