Managing translations

Created by Cem Kocainan, Modified on Mon, 5 Aug at 4:12 PM by Cem Kocainan

As part of its multi-market selling capabilities, the Oroox platform provides multi-language support along with functionality for you to edit all translations. There are three categories of text that can be translated:

  • Static translations - visible text: Any text you see on the UI which is part of the standard product.
  • Static translations - partially visible text: Any text that is part of the standard product but visible only under certain circumstances (e.g., information popups, warning messages, etc.).
  • Dynamic translations: Text that is inputted into the system by you and your colleagues (e.g., material names).


(For setting the default language per market, please refer to the related article.)


To edit static translations:

  1. Hover over your name/badge on the right side of the header.
  2. In the opened menu, click on the last item, Translate
  3. Find the word you want to translate on the screen and click the green icon next to it.
    • Alternatively, find the word you are looking for in the left menu, which also includes partially visible text. 
  4. Input the new text into the field under the Translated Language dropdown. 
  5. Click Save.


To edit dynamic translations:

  1. Navigate to the input field where you need to type the text.
  2. Click the arrow on the right end of the input field.
  3. Select the language and type in the translation.
  4. Repeat for all languages.
  5. Click Save.


Dynamic translations visible to the end-user:

  • Material names
  • Color names
  • Date-Price configuration
  • Terms & Conditions URL's (hyperlinks)


Dynamic translations visible to the Backoffice users:

  • Machine names
  • Surface finishing names
  • Role names
  • SMTP name


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article