What Is the Mergado Translate Extension?#

Mergado Translate is an extension for automated machine translation of e-commerce product data. It enables you to expand into foreign markets by quickly and efficiently translating XML or CSV feeds directly within Mergado Editor. The extension does not use its own translation engine — instead, it connects via API to DeepL and Google Translate.

The main advantage is that the extension caches all translations. This means that each unique text is translated and charged only once, which can reduce costs by up to 70% when regenerating a feed repeatedly or working with duplicate product descriptions.

The extension is ideal for:

  • Online stores that receive product data from foreign suppliers in another language and need to translate it into their own.
  • Online stores expanding abroad that need to translate their product data for foreign price comparison sites, marketplaces, or advertising systems.
  • Online stores that already have existing translations from another tool and want to switch to Mergado Translate without losing their existing work — see the guide How to Switch from Another Translation Tool to Mergado Translate Without Losing Existing Translations.

Pricing and Billing#

With Mergado Translate, you pay for using the extension (first 30 days free) + the cost of the actual translation via Google Translate or DeepL. Your account with the specific translation service is held in your name.

Extension fee#

  • EUR 18 per month with monthly billing,
  • EUR 14.40 per month with annual billing.

The price applies to one online store (in Mergado) and is fixed regardless of the volume of translated text. Due to technical dependencies, the extension is billed in line with the billing frequency selected in Mergado Editor. Different billing frequencies cannot be set for individual services.

The Mergado Translate extension comes with a 30-day free trial.

Google Translate and DeepL fees#

In addition to the fixed extension fee, you also pay for the translation itself directly to the provider (Google or DeepL). Both services have their own pricing (for example, DeepL and Google both offer 500,000 characters per month for free, with additional characters charged at a set rate above that threshold).

Google Translate pricing

  • Translations up to 500,000 characters per month are free (Google automatically adds a $10 credit to your account for this purpose each month).
  • For translations above 500,000 characters per month, you pay $20 per million characters.
  • If you are a new Google Cloud customer, Google provides an introductory free credit of $300.
  • Full pricing: https://cloud.google.com/translate/pricing

DeepL pricing DeepL offers several plans. The two main ones are:

  • Developer — Free. A one-time credit for translating 1 million characters. After the credit is used up, you need to upgrade to a paid plan.
  • Growth
    • With annual billing: $26/month. Limit: 12 million characters per year (1 million per month). Exceeding the limit: +$27.50 per million characters.
    • With monthly billing: $32.50/month. Limit: 1 million characters per month. Exceeding the limit: +$27.50 per million characters.
    • You can set a maximum monthly character limit.
  • Full pricing: https://www.deepl.com/en/pro#api

Keep your costs under control: To avoid unexpectedly high translation bills, we recommend setting a maximum monthly spending limit in your DeepL admin (on the Usage page via the Change cost control settings link). The limit applies on top of your base monthly plan. If you reach the set limit, a warning red exclamation mark will appear next to the Connections tab in Mergado Translate.

Requirements for Running Mergado Translate#

  • A Mergado Editor account and an active project.
  • Your own account with DeepL or Google Cloud.
  • An API key from these services to create a connection with Mergado Translate.

Key Features#

1. Text Translation#

This feature handles automated translation of text fields such as product names and descriptions. The extension intelligently processes HTML tags — it extracts only the actual content for translation and does not send the tags to the paid translation service, saving character count while preserving the original styling and formatting.

For feeds where different products have descriptions in different languages, you can use the source language “mx” (mixed), which automatically detects the source language for each item individually. In general, Google Translate is recommended for short texts and names, while DeepL is better suited for longer, continuous descriptions. Both translation services can be combined within a single feed.

2. Translation Cache and Cost Savings#

Mergado Translate stores all translations in a cache. Each unique text is sent to the paid translation API only once. On subsequent occurrences of the same text (for example, duplicate descriptions across products or repeated phrases), the extension uses the cached translation and does not consume your paid credit. This mechanism can save up to 70% on translation costs. However, keep in mind that even a single changed word or character causes the system to treat the text as new and send it for re-translation.

3. Category Translation#

The rule settings are designed to correctly translate category paths (for example, in the CATEGORYTEXT element). The extension splits the entire path into individual parts based on separators (e.g. “|” or “>”) and translates each sub-category separately. This ensures translation consistency and additional cost savings, since a parent category translated once is not re-translated for subsequent products.

4. Currency Localisation#

The extension supports automatic conversion of product, shipping, or payment prices according to the current CNB (Czech National Bank) exchange rate, which is updated every business day. Features include rounding settings (for example, for Shoptet), a choice of decimal point or comma, and automatic insertion of the currency code (e.g. “€”) directly into the element. A price coefficient is also available for applying an across-the-board price increase or decrease (e.g. 5% to cover expansion costs).

5. Custom Dictionaries#

Used for bulk translation corrections using a find-and-replace approach. If the translation service consistently produces an unsuitable translation for your industry, you can define your own correct translation in the dictionary, which is then applied to all occurrences within a given rule.

6. Manual Translation Management#

Within the extension interface, you can browse, filter by element, and manually edit retrieved translations. Edited texts can be marked as “reviewed”, helping you stay organised in large projects.

7. Cost Estimate#

Before running a translation, you can request a calculation of the estimated financial cost. The extension scans the selected products, counts the number of unique characters (after deducting duplicates), and based on Google or DeepL pricing, generates a cost estimate in USD/EUR. The result is shown on the History tab and in Mergado Editor notifications.

How to Activate Mergado Translate#

Activate the extension in Mergado Store: I want to activate → select the online store for which you want to enable the extension → Activate.

First, you need to create a connection to your chosen service — Google Translate or DeepL. You do this directly within the Mergado Translate interface.

  1. Go to the Connections tab.
  2. Click New connection.
  3. In the Translation provider field, select DeepL or Google.
  4. In the Connection name field, name the connection.
  5. In the API key field, paste the API key you obtained from your account with the selected translation service (Google Translate [link] or DeepL [link]).
  6. Confirm by clicking Create.

The created connection will appear in the list on the Connections tab. Here you can use the relevant buttons to edit, delete, test the API key, or try out a translation.

Clicking Try checks whether the connection was set up correctly — if so, a green message “Connection is working correctly” will appear.

Clicking Test lets you verify that translations are working correctly. Simply select the source language, the target language, and paste the text you want to translate into the relevant field.

How to Get an API Key from Google Translate#

  1. Using your Google account (a business account with a payment card on file), create an account at Google Cloud.
  2. After creating the account, go to Google Cloud Console (the Console button in the top right).
  3. Create a new project by clicking My First Project → NEW PROJECT.
  4. Name the project (e.g. my-translator) and confirm by clicking Create.
  5. Make sure you are working within this newly created project (e.g. my-translator).
  6. In the menu, select the APIs & Services tab.
  7. Click the ENABLE APIS AND SERVICES button.
  8. From the list, select Cloud Translation API.
  9. Enable the Cloud Translation API by clicking Enable.
  10. Go to the Credentials tab (within APIs & Services).
  11. Click CREATE CREDENTIALS and then API key.
  12. Copy the API key from the Your API key field and paste it into Mergado Translate.

How to Get an API Key from DeepL#

  1. Create an account at DeepL (a business account with a payment card on file).
  2. Choose a plan from the API tab — Developer or Growth will suffice.
  3. After activating the selected plan, click on your user account and open the Account page.
  4. Go to the Account tab.
  5. At the bottom of the page, under Authentication Key for DeepL API, find your API key and copy it for use in Mergado Translate.

Working in Mergado Translate#

The Mergado Translate interface is divided into four main tabs — Rules, Translations, History, and Connections & Dictionaries — which let you manage translation tasks, track action history, analyse costs, and configure connections with external Google Translate and DeepL services.

Rules#

The Rules tab is the default and most important page of the extension. It provides a clear overview of all translation and localisation tasks. The main table lists all created rules, their current status (active, paused, or stopped), and key parameters such as name, query, connection, source language, and target language.

Directly from the table, you can use the relevant icons to go to the edit view for a rule, pause it (the rule does not translate anything new, but keeps already-translated products in the output feed), stop it (the rule performs no action and does not display translated products in the output feed, even though they remain stored in the cache), or delete it.

The tab also includes two charts providing a quick visual overview of the translation status for a specific rule. A pie chart shows the ratio of reviewed to unreviewed translations; the second chart shows the growth of new translations.

How to estimate the cost of a translation#

To find out the estimated cost of a translation in advance, use the Cost estimate feature. It counts the number of characters in the elements you want to translate and multiplies them by the per-character translation price of your chosen translation service.

It then checks for duplicate texts (Mergado Translate translates each only once) and calculates the cost excluding duplicates. This gives you the final translation cost.

This calculation does not account for any free credits you may have with the translation service as part of a free tier or base plan.

Creating a cost estimate

  1. On the Rules page, click Create estimate.
  2. Fill in all fields in the form: a. Connection — Google Translate or DeepL. b. Target language — The language you are translating into. c. Query — The product query designated for translation, or select all products. d. Elements — Select the elements whose content will be translated.
  3. Click Create.
  4. Once the estimate is ready, the result will appear on the History tab. You will also receive a notification in Mergado Editor.

How to create a rule in Mergado Translate#

Individual translations are triggered by creating translation or localisation rules. When creating a rule, a checklist guides you and verifies that all required fields are correctly filled in.

Rule types

1. Text translation — Suitable for continuous texts and product names. The extension intelligently excludes HTML tags from the paid translation process, saving money and preserving formatting. 2. Category translation — A rule designed for elements such as CATEGORYTEXT. It splits the entire path based on separators (| or >) and translates each part separately, ensuring consistency and lower cost. 3. Currency localisation — Automatically converts prices according to the current CNB (Czech National Bank) exchange rate (updated every business day). Allows you to set rounding (whole numbers or 2 decimal places), a choice of decimal point or comma, and automatic insertion of the currency code (e.g. “CZK”, “€”). A currency coefficient is also available for applying an across-the-board price adjustment (e.g. a 5% increase using coefficient 1.05).

Force translations from the connected service

While setting up a translation rule, you will come across the option Force translations from the connected service. By default, Mergado Translate draws translations from a global cache shared across all projects in Mergado. This brings several advantages — translations are faster and you pay for the same text only once, even when translating across multiple projects simultaneously.

In some cases, however, it may be desirable for translations to come exclusively from a specific connection to a translation service rather than from the global cache. You can activate this by checking the relevant checkbox. Keep in mind that enabling this option may lead to higher translation costs, as texts already stored in the global cache will be re-translated.

Creating a text or category translation rule

  1. On the Rules page, click New rule.
  2. Rule name — Give the rule a name of your choice.
  3. Rule type — Select the type of rule you want to create: Text translation or Category translation.
  4. Connection — Select Google Translate or DeepL.
  5. Source language — If the feed contains multiple languages at once (e.g. some products in Polish and others in English), you can set the source language to “Mixed” (MX), which automatically detects the language for each item.
  6. Target language — Select the target language you want to translate into.
  7. Optionally, check the Force translations from the connected service option.
  8. Query — Select the product query designated for translation, or choose all products.
  9. Elements — Select the specific elements to be translated (e.g. DESCRIPTION or NAME, or in the case of a category translation, e.g. CATEGORYTEXT).
  10. Optionally, attach a previously created Dictionary.
  11. Click Create.
  12. You can review and edit translations on the Translations tab.

Creating a currency localisation rule

  1. On the Rules page, click New rule.
  2. Rule name — Give the rule a name of your choice.
  3. Rule type — Select Currency localisation as the rule type.
  4. Currency settings — Select the source and target currency.
  5. Optionally, choose to include the currency code in the output element.
  6. Choose whether you want the output prices rounded to whole numbers or with two decimal places.
  7. Choose whether you want to use a decimal point or comma as the decimal separator in the output price.
  8. Optionally, you can set a currency coefficient for an across-the-board price adjustment (e.g. a 5% increase using coefficient 1.05).
  9. Query — Select the product query designated for currency localisation, or choose all products.
  10. Elements — Select the specific element(s) in which you want to convert the currency (e.g. PRICE_VAT).
  11. Click Create.

Important recommendation: Translation rules should be placed at the very end of the rules list in Mergado Editor. This ensures that only data already cleaned up or modified in earlier steps is translated, preventing unnecessary payment for translating junk data or repeated re-translations after minor text changes.

Translations#

On the Translations tab, you can browse and manually edit translations created by individual rules. To view translations for a specific rule, click on that rule. Clicking on a row in the table automatically moves the cursor to the editing field; press Tab or click another row to move to the next translation. Changes are saved automatically.

Translations can be filtered by element, searched by source or translated text, and filtered to show only reviewed or unreviewed items. Completed translations can be marked as “reviewed”, which makes navigation easier in large projects. Bulk actions are also available.

History#

The History tab provides an overview of all operations performed within Mergado Translate. It lets you keep a detailed record of what changes were made, how automated processes are running, and what the actual or estimated translation costs are.

Types of records in History

  • Translation logs — Records of each completed translation (when the translation ran and which products were translated). This also includes information on how many items were translated as new original text and how many were loaded from the cache.
  • Rule changes — Logs changes to rule settings. You can see who made changes and when.
  • Cost estimate results — If you use the cost estimate feature, the result is found here. The information is also shown as a notification in Mergado Editor.

Features to make working in History easier

  • Filtering and search — The interface lets you search records using specific filters, which is especially useful for large projects with many exports.
  • Pagination — The records table is paginated for better clarity.
  • Data retention period — To optimise extension performance, records in History are kept for 3 months. Older records are automatically deleted by the system.

Connections & Dictionaries#

The Connections & Dictionaries tab serves two purposes: setting up connections to translation services and managing custom dictionaries.

Connections#

Here you create and manage connections to external translation services DeepL and Google Translate via their API keys. Each connection is named and assigned the relevant API key. For created connections, you can use the relevant buttons to edit the connection, delete it, test whether the API key works, or try out a translation of a specific text.

→ How to connect DeepL

→ How to connect Google Translate

Custom Dictionaries#

Custom dictionaries are used for bulk translation corrections using a find-and-replace approach. If the translation service consistently uses an unsuitable term for your industry, you define your own correct translation in the dictionary, which is automatically applied to all occurrences within a given rule.

A dictionary works as a two-column table — the text to find on the left, the replacement text on the right. For example, if DeepL translates “leather boots” incorrectly, you define the replacement in the dictionary and all occurrences are corrected in bulk.

You can create multiple dictionaries. A new dictionary can be created in two ways:

  • Manually — on the Connections & Dictionaries tab, click New dictionary and enter items directly in the interface.
  • By importing a CSV — the file must contain two comma-separated columns, with texts enclosed in quotation marks. For example:
    • “original translation”,“correct translation”
    • “another translation”,“better translation”

Important: A custom dictionary is activated by selecting it directly in the settings of a specific translation rule. Creating the dictionary alone is not enough — it will not be used until you assign it to a rule.

FAQ#

What Is Mergado Translate and What Does It Do?#

Mergado Translate is a Mergado Editor extension that automatically translates e-commerce product data (such as names, descriptions, or categories) and localises prices. It uses the DeepL and Google Translate services via their APIs.

Which Translation Services Does the Extension Support?#

Mergado Translate can be connected to DeepL or Google Translate. Both services can be combined within a single feed — for example, Google Translate for short product names and DeepL for longer descriptions.

How Much Does Mergado Translate Cost?#

You pay two components: a fixed extension fee (CZK 486/month with monthly billing or CZK 388.80/month with annual billing) and the cost of the actual translation paid directly to the provider — DeepL or Google.

Can I Try the Extension for Free First?#

Yes, Mergado Translate comes with a 30-day free trial. Both translation services also offer free initial credits — Google Translate provides 500,000 characters per month for free, and DeepL’s Developer plan includes a one-time credit of 1 million characters.

How Do I Find Out in Advance How Much the Translation Will Cost?#

Before running a translation, use the Cost estimate feature on the Rules tab. The extension counts the number of unique characters (after deducting duplicates) and generates a cost estimate. The result is available on the History tab and in Mergado Editor notifications.

How Can I Set a Maximum Spending Limit for Translations?#

A limit can be set for DeepL. In your DeepL admin on the Usage page (via the Change cost control settings link), you can set a maximum monthly spending limit. If you reach the set limit, a warning red exclamation mark will appear next to the Connections tab in Mergado Translate.

Do I Pay for Each Product’s Translation Again at Every Feed Generation?#

No. Mergado Translate stores translations in a cache. Each unique text is translated only once. On subsequent occurrences of the same text, the extension uses the cached translation and does not consume the paid API. Note, however, that even a minor text change (such as correcting a typo) causes the system to treat the text as new and re-translate it.

What Can Be Translated?#

Any text element in the feed — product names, descriptions, categories (CATEGORYTEXT) — and prices via the currency localisation feature.

Is It Possible to Translate Categories?#

Yes. The extension splits the entire category path (e.g. “Electronics > Phones > Smartphones”) into individual parts based on separators (| or >) and translates each part separately. A parent category translated once is not re-translated for subsequent products, reducing costs.

What Is Currency Localisation and How Does It Work?#

Currency localisation automatically converts prices into the required currency using the current CNB (Czech National Bank) exchange rate, which is updated every business day. You can set rounding, the decimal separator (point or comma), and automatic insertion of the currency code into the element. A price coefficient is also available for applying an across-the-board price increase or decrease.

Can I Translate Only Some Products Rather Than the Entire Feed?#

Yes. When creating a rule, you select the product query to which the translation will be applied. For example, you can translate only a specific product category or only new products.

What Should I Do If the Supplier Feed Contains Texts in Multiple Languages at Once?#

If the feed contains texts in multiple languages simultaneously (for example, some products in Polish and others in English), set the source language to MX (mixed). The extension will then automatically detect the language for each item and translate it correctly.

Can I Manually Edit Translations After They Have Been Created?#

Yes. On the Translations tab you can browse, filter, manually edit, and mark translations as “reviewed”. Changes are saved automatically.

Can I Define Custom Translations for Certain Terms If the Machine Translation Is Not Suitable?#

Yes, that is what custom dictionaries are for. They work on a find-and-replace basis. You define replacements for terms that the translation service consistently translates poorly for your industry, and these are automatically applied to all occurrences within a given rule. You can create multiple dictionaries and add items manually or by importing a CSV. However, the dictionary must be attached directly in the translation rule settings — simply creating the dictionary is not enough.

How Does Mergado Translate Handle HTML Tags in Descriptions?#

The extension excludes HTML tags from the paid translation. You are not charged for translating them, and the original text formatting is preserved.

Where in the Rules List in Mergado Editor Should I Place Translation Rules?#

Translation rules should always be placed at the end of the rules list in the project. This ensures that already cleaned and processed data is translated, preventing unnecessary payments for translating junk data or repeated re-translations after minor text changes.

I Want to Start Using Mergado Translate, but Part of My Feed Is Already Translated. Will I Lose My Existing Translations?#

No, your translations can be preserved. The process involves exporting your existing translations to CSV, importing them into Mergado via a Data file import rule, and setting up the translation rule only for products not yet translated. For step-by-step instructions, see the guide How to Switch from Another Translation Tool to Mergado Translate Without Losing Existing Translations.

Was this article helpful?