What is MERGADO Translate
MERGADO Translate (formerly Ordelogy Translate) is an app for automated translation, mainly of e-commerce products using DeepL or Google Translate.
How MERGADO Translate works
The translation itself is provided by DeepL or Google Translate. The user creates an account and sets up the connection. MERGADO Translate provides automated sending of texts to the translator for translation. The received translations are cached. Thus, one text is translated once. This saves the client’s money.
- Connection to export in MERGADO Editor via API.
- Price estimation directly in the application to estimate savings and costs.
- You can limit translations to selections of products.
- Translates any elements.
- Choice of two translators: DeepL, Google Translate. You can use both.
- Transparent pricing. The user pays for the translators himself and can take advantage of any free bonus credits. The price of MERGADO Translate is 100% transparent: 18 EUR/month regardless of the number of translations.
What MERGADO Translate is good for
- Translation of products for import into the online store from foreign language data.
- Translation for the marketplace for expansion abroad.
- Translation for an advertising system that requires data in a foreign language.
- …and more
Why use MERGADO Translate
- Automation. Saves work, makes money.
- You can clearly see how much you pay for the app and how much you pay for the translators. You don’t pay an overpriced rate to translate individual words.
- Integration with MERGADO Editor. You can deploy without changing data feeds in advertising systems.
MERGADO Translate - version 10 - Hungarian localization
Today we released a new version of MERGADO Translate, containing mainly a Hungarian translation of the user interface. We have also added a few minor improvements to the user interface.
MERGADO Translate - version 11 - new core, category translation
The upcoming release will bring two major sets of new features.
New core MERGADO Translate
We have rewritten the core of MERGADO Translate. The goal was to increase reliability and to allow adding new features in the future. Users will not see the new features in the interface. For example, they will notice that the translation rule will not "turn itself off ". Previous shutdowns were mainly due to outages on the DeepL and Google Translate side. Now, MERGADO Translate will return an error when processing to MERGADO Editor in this case. This will appear as a notification in both applications. The next time the data is processed, both applications will try to process everything automatically so that the error condition goes away. You may see the new error message, but you do not need to take any action. If you would like to resolve the situation faster, you can manually enter the export processing in the MERGADO Editor. However, this is not necessary. The next time the automatic processing takes place, everything will take care of itself.
Translation of categories
We are now introducing the concept of “translation type”. The existing functionality corresponds to the “Text Translation” type. The text is translated as a whole and the type is suitable for most texts (elements).
The new translation type is “Category Translation”. The difference will be clear in the following example:
Examples of categories:
- White goods | Washing machines and dryers | Washing machines
- White goods | Washing machines and dryers | Dryers
The text translation type always translates the entire text
White Goods | Washing Machines and Dryers | Washing Machines. The category translation type breaks the whole text into parts according to the separator (we now support the
> characters). This creates multiple texts:
Washers and Dryers,
Washers and each translated separately. If you were translating the second text from the example above, the first two strings are already cached. Only the text
Dryers will be translated. Thanks to this:
- you save money on translations
- each category is translated always the same.
MERGADO Translate - version 12 - user dictionaries
The upcoming release will bring a number of minor improvements:
- We will limit entries in History to 3 months. Older entries will be deleted.
- We have added new warnings about some connection errors on DeepL and Google Translate.
- Now the connection name must be unique.
And the main news:
What is a user dictionary? Think of it as a table with two columns. On the left is the text to be found and on the right is the text to be replaced. The goal is to improve translations in bulk. For example, if DeepL translates
leather boots →
leather boots, you can define a translation of
leather boots →
leather boots in the user dictionary. And thus improve the translations in bulk.
There can be more than one user dictionary. You can create a new dictionary either manually or by importing a CSV that contains two columns separated by a comma and text in quotes, see example:
"leather boots", "leather boots"
" different translation ", " better translation "
User dictionary is “turned on” in the translation by selecting it in the translation rule!
The current handling of user dictionaries is seen as a stepping stone for further improvements. We would like to improve both the way they are used and their capabilities. This will however be the subject of future releases.