With this rule, you can import edits to existing items using a CSV file.
In the Mergado Store, we have improved the sorting of entities where the app can be managed to match the sorting of e-shops and exports elsewhere in MERGADO.
When converting Google Shopping prices, we now take the value of the G: SALE_PRICE element correctly into consideration when available.
Googleformats have been updated. Weâve added a lot of new elements and fixed some minor flaws. Make sure everything is fine in the Google Merchant Center for your Google Ads!
For Shopalike CSV format , we tuned the audit and added support for the IN STOCK element.
Weâve improved the BluePanel , where you can access all your Online stores in one place. It will now be faster and easier to find.
We have prepared a new MERGADO function - Macros! The goal is to automate the work you do in MERGADO.
For example, you set up queries and rules that you can then use on other projects.
Where to find out more
Read this article on Macros for all the information you need. Find out how Macros work and how they can help you.
Weâve added support forthe new formatArtikul.cz 1 .
Weâve added the ability to create attribute elements into the user interface ( up to now, it was created by MERGADO itself based on the content of the feed ). An attribute element can be specified in the following forms:
ELEMENT(id=123) with one attribute.
ELEMENT(id=123;dalsi_atribut=hodnota) with multiple attributes.
On the page listing element values, we introduced a line that represents all the empty values of the element.
Now one can immediately see how many productâs elements have no value . The user can make a query for that product set and hide them.
The Data File Import rule now supports inserting a data feed over the specified URL .
The rules can now be applied to onlya sample of items ( âmonitoredâ products ).
Thanks to this new option, the export settings ( querries, rules functionality, values of variables and output elements, etc. ) can be checked in a much shorter time .
This tool is available on theRules page in the clickable button to start applying the rules.
A new e-shop can be created separately in MERGADO.
This new option is useful in situations where a user has trouble uploading his feed to MERGADO and create a new e-shop in a standard way.
Weâve improved the Google Shopping 1exporter, which can nowproperly export attribute elements.
We have fixed a bug that caused the Heureka.cz and Heureka.sk fotmats didnât embed the RATING element to output.
In the Skrz.cz format, multiple elements (TAGS| x, IMAGES| y and CITIES| z) are now exported correctly.
Other minor fixes and improvementsâŠ
What features weâre planning to add
For a small (internal) group of people, we launch a new feature: the rule planner - for testing and tuning
Platform News
The list of submitted webhooks on the Webhooks page in the administration of your app in Developers will now display longer payloads. In the past, when logging a weblog, the JSON payload has often been cut off due to length. Now it should happen not that often.
You may notice minor outages of MERGADO at that time. Thank you for your understanding and patience in deploying the new version.
The data import rule now supports non-standard delimiters for CSV files. The user can now choose from:
, comma (default)
; semicolon (new)
| vertical bar (new)
For the Favi.hu format we have added support for the shipping pricing rule. The following carriers are currently available:
DHL
DPD
GLS
In the custom format settings, you can now save a definition without specifying a ârootâ element. As a result, you can now import feeds into MERGADO that do not have this top-level element.
For imported CSV files we improved the processing of correctly escaped quotes.
E.g. "text in quotation marks containing additional ""double quotation marks with , (a delimiter)"" reads correctly."
We have fixed the query form (product search) for read-only users.
For the Google Shopping format, we fixed the export of the G: SUBSCRIPTION_COST element.
When establishing a connection with Heureka via the MERGADO Keychain app we are now displaying the correct message if the given account on Heureka exists but does not have any stores.
⊠and other minor updates and fixes.
Platform News
We will no longer display the top yellow notifications (downtimes, releases, etc.) on the app preview page, thus covering your IFRAME content.
During the release, you may notice minor downtimes of MERGADO. Thank you for your understanding and patience.
The data import rule now forces the rules to be fully applied when external data changes.
By default, MERGADO applies rules only to products whose input values have changed during the last import. Now we will detect this âchange of external dataâ for the data source of this rule.
The data import rule for element names is now case-insensitive.
In MERGADO we work with element names as case-insensitive. For us, the element <Some_Element> is the same as <some_element> or <SOME_ELEMENT>. Thus, it makes no sense for the data import rule to distinguish the font size.
Now data input (eg):
:xid,Product_Name,price_VAT 1,"Stroller",123.45
âŠwill also affect elements called PRODUCT_NAME and PRICE_VAT.
Improvements: For exports there is a new option âDuplicate exportâ in the
menu.
This action will create a copy of the export (it will be included in the same ecommerce). The copy will be created with all selections, rules, elements, and variables.
Attention: Any application running under the original export will not be turned on for a new export - and it is up to the user whether he wants to turn it on.
Improvements: The rule for setting transport prices now supports the use of variables.
We now support the DSA Google Ads format for 26 other countries. Including support for audits.
Google and Facebook formats have added support for Croatia and Slovenia.
We now support Biano format for Brazil, the Netherlands, and Romania.
In Audit, we have added support for a number of language versions of the Glami and Stileo formats.
Improvements: For rules that support regular expressions, we now show help on how to use back references.
We have customized the workflow to work with custom formats to make it more user-friendly.
On the export history page, the skipped import (Because the input file has not changed in any way) now displays the correct number of items (instead of the previous zero).
We fixed a bug for bulk import of rules. Because of this bug no rules were showed for import.
To create an export, we displayed as existing e-shops even those to which the user had read-only access - and the new export could not be assigned to them anyway. We fixed this.
In process of creating exports we showed to user all existing ecommerces even those for which he only has the right to read. And the new export couldnât be assigned to them anyway. Now itâs fixed.
On the Products page, we fixed a product display bug. This error occurred in specific combinations of display settings.
Due to a bug in the blue bar, ecommerce that had no export were not shown during the searching. We fixed this.
We have unified the names of the different processes and their phases on the export history page.
We have added translations for missing country and currency names.
Other fixes and minor improvementsâŠ
Platform News
In MQL, we now support a âspecial elementâ called @MERGADO_ID, which can be used to select specific products by their internal (our) ID (eg, the ID used at the endpoint https://api.mergado.com/products/ 123456789, or is shown in the URL for products in the interface).
Applications can now use this to make selections for specific products (and then in the app, for example, make a link to MERGADO for that selection).
Examples of use:
@MERGADO_ID = "123456789"
@MERGADO_ID NOT IN (123456789; 123456780)
PRODUCTNAME ~ @MERGADO_ID AND @MERGADO_ID ~ "3" OR @MERGADO_ID IN ("123";"321")
We have changed the time that we keep webhook log entries accessible in Mergado Developers to 7 days.
You may notice minor outages of MERGADO at that time. Thank you for your understanding and patience in deploying the new version.
If you have any questions, please donât hesitate contact us.
You donât have to worry about your advertising.
While unprecedented things are happening outside, we want to make sure all MERGADO users that their ads will continue to run unchanged.
If you need help setting up your ads, please feel free to contact us at any time.
We introduced the Macro Tool - the ability to run preset actions that let you set up your export quickly and easily - last September. At that time, we ran macros in âusers can run macrosâ mode, where you could use sets of actions that we had already prepared, but you couldnât create them yourself.
The procedure for creating macros was only available to our team at that time, because it was a quite complex process in test mode. The macro editor and the whole interface around it just needed to be more user-friendly and we wanted to catch as many âfliesâ before launching.
Now we open creating macros for all our users.
In the top-level menu (i.e. on the main page) there is a new item called Custom macros. Create and manage your macros on this new page.
Go and give it a try!
A macro is basically a sequence of parametric actions that will do something in MERGADO that you, as users, can do by yourself, but a well-built macro will do it for you, without error and much faster - and you can run that macro on different exports.
Currently supported macro actions are:
Create element (and optionally a standard variable)
Create query (input and output)
Create rule (currently you can create rules such as override, find and replace, hide product, shorten value, change capitalization, round, set UTM parameters, remove HTML tags and calculate. It is not yet possible to create bulk rules - but we plan to do this over time.)
What is important to note:
A macro is a general formula and as such has no link to any particular export before it runs.
Keep in mind that you might be surprised that when you define the Create Rule action, in the list of queries to which the rule applies, there are no queries from any of your existing exports. The rules defined in the macro can only be applied to queries that are defined in the same macro. (And it works the same for other events.)
Once a macro has run over a particular export and has performed the prescribed actions, the macro still has no relation to that or any other export.
In other words, the created elements, queries, and rules are not special - itâs like the user created them himself.
The macro can also define parameters that can be used to change the behavior of a macro for a particular situation before it runs over an export.
Macro language (specifying the language of your macro)
Macro format (where you specify for which formats supported by MERGADO your macro will be recommended)
What to do with the created macro?
You can run your macros over your MERGADO exports (in your export, there is a menu link called Macros).
You can share your macros with other users.
They can then import it via a link into their own collection of macros . And if you then edit your macro, others will know and may have their copy of the macro updated (or they may ignore the changes).
Our blog will soon feature articles about macros to help you with this great new feature.
Keep in mind that the current options in creating and running macros and managing them are just the beginning, and weâd love to hear your thoughts and comments about this new tool after giving it a try. Our goal is to simplify your work in MERGADO.
Rule planner
The rule planner tool has been in test insiders mode since November last year. We would like to thank all the insiders who have tested this âfeatureâ and helped us to discover and solve all kinds of mistakes before the launch. Thanks!
New feature!
With the rule planner, you can schedule your rules for when to apply and when to skip.
Where do I find the rule planner?
On the Rules page, there is a new icon for each rule (the rule type must support scheduling) that takes you to its schedule settings page:
How does the rule planner work?
The rule planner has three levels of settings:
As such, the scheduler is either active or inactive .
The plan may be limited to:
Date from(inclusive): The daily planner (see next point) takes effect from that date (including this date). You can also choose to apply the rule by default or always skip before that date.
Date to(inclusive): The daily planner (see next point) has an effect until that date. You can also choose to re-apply the rule after this date or skip it after that date.
A daily planner through which you can set the rule behavior for each day of the week separately. Each day is further divided into six four-hour periods, where you can choose whether or not to apply the rule.
Please note that the rule must be enabled for the planner to do what you want it to do . The paused rule is not affected by the planner. In other words, the planner cannot force a paused rule to be applied.
Example of rule planner setting:
For example, you might want to set up a Set a free gift rule to apply only between April 1, 2020 and April 30, 2020 (included), on Fridays only from 12:00 to 24:00, and then all Saturday and Sunday. However, before April 1, 2020, the rule will always apply by default. And then, as of May 1, the rule will always be skipped.
We updated the specification for an audit of the ZboĆŸĂ.cz format , where we adjusted the range for valid MAX_CPC and MAX_CPC_SEARCH values.
We have modified the RSS format, which we now export with elements with the correct case.
Notifications (pop-up messages) in the interface will no longer appear multiple times if they say the same thing.
We also improved pop-ups in the new export setup guide.
We improved automatic format detection for MERGADO Analytic XML. Now we should recognize it a little better.
Weâve implemented some tweaks in the custom format creation and editing interface and fixed some bugs.
Fix: Element value whisperer in the interface did not whisper the 0 value. We fixed this.
Platform News
In specific cases the widget of the app was sometimes not set to the correct height - the content of the widgets was thus seen âcut offâ. This is now fixed.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
This is primarily a âtechnical releaseâ with which we improve and modernize the âinsideâ of MERGADO to make our app more sustainable in the future. This release is a milestone with which we are finishing two of our large and long-term projects:
Complete codebase upgrade of our backend from Python 2 to Python 3.
Refactoring of the data structure scheme, in which we represent products from your stores.
For standard user work, this version does not change anything except minor fixes.
Other News
Correction of the internal specification of the Shopmania format family - on the Products page, the element for categories will now be displayed correctly.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
Macro search now also searches in macro descriptions.
Macros run on a project (export) are now logged in its history.
The list of available macros now shows the creation and last modification times of the macro on the macro tab.
Paging results when searching for macros was fixed.
New feature: Automatic category suggestions for the Rename categories in bulk rule.
In this release, we are deploying a completely new component that, using advanced natural language processing algorithms based on the input categories in your feed, can suggest the best possible equivalent category that the target search engine knows.
We currently support this for the formats Heureka.cz, ZboĆŸĂ.cz and Heureka.sk
In the Rename categories in bulk rule editor, there is a new âsuggest recommended categoriesâ button for supported formats:
After clicking, the unique categories present in the input values ââof your feed will start loading in the background and the suggestions of the correct categories will start to be evaluated, which will then be displayed as options on the right side of the form. This should be very fast for standard use, however for large feeds with a large number (eg with thousands) of categories it may take some time.
This is a completely new feature, so we will be happy for any feedback from users!
We have fixed the feed audit for Google Shopping. Now we check the product description in the G:DESCRIPTION element and not in the DESCRIPTION element.
Weâve improved filtering in the project history. You can now filter events by the user who executed the event.
We have improved the behavior of formats for Heureka, which can now recognize and import DELIVERY_ID, DELIVERY_PRICE and DELIVERY_PRICE_COD elements even if they are not uppercase.
Weâve fixed a rare spontaneous redirect to the notification page, which should no longer occur.
Insiders
On the Products page, there is a new option for our insiders users to display products in a table.
Each line in this view represents one product. The columns represent the names of the elements that are displayed (these can be selected by the user). The values of these elements are then visible in the cells inside the table.
The output values can be edited directly in the cells.
We also plan to add support for sorting values and exporting selected columns.
We will appreciate any feedback on the table view, to make this feature as useful as possible.
Platform
Weâve updated the conversion tracking code (turning on the app) for Sklik.
When an app in the MERGADO Store is disabled, we will ask the user if he does not want to leave a rating and feedback.
We have added the option to have an app icon in two versions - for light and dark backgrounds.
New endpoints for finding out user access rights for a specific project/online store:
/users/<user_id>/permissions/eshop/<eshop_id> - to find out the user rights for the given store.
/users/<user_id>/permissions/project/<project_id> - to find out the userâs rights for the given project (which are always the same rights as the given user has for the rest of the store to which the project belongs)
The answer then takes this form
{
âuser_idâ: 1,
âeshop_idâ: 2, // or âproject_idâ
âroleâ: âwriterâ // Possible values: âwriterâ, âreaderâ, âownerâ, null
}
After app is turned off for the project, MERGADO will take care of deleting all app rules for the given app, if the app for some reason failed to âclean upâ when turning off.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
We have optimized the application of rules for large projects.
We analyzed cases in which for large projects the application of rules has worked with products inefficiently.
This was most evident in projects with hundreds of thousands of products and tens to hundreds of rules, many of which target output queries.
Based on these analyzes, we have implemented improvements that should significantly reduce the overall duration of the application of rules in these extreme cases
UI news: In several places in the interface - where it can be useful - the rules and queries now show icons that let you know at first glance whether the queries are on input or output.
Example from the Rules page:
- the rule is targeted only at queries on input.
- the rule is targeted at queries on input and output.
- the rule is targeted only at queries on output.
This can make it much easier for users to optimize rule settings - which has a direct impact on how long a project will take to apply rules to a project.
You can read more about this topic in the article on our blog: Set Mergado effectively #1: Queries to input values.
Another update for the Rename categories in bulk rule.
You can now insert multiline text in the left column of the categories, which is then correctly divided into new lines.
This works for plain text, but also for copied lines from Excel or CSV. If you copy two columns in this way, even these copied values will be correctly divided into left and right columns.
Weâve fixed some cases where MQL did not handle special characters in element content - for example, it was not possible to properly search for the content of an element with multiline text inside the multiline content of another element. This has been fixed and it is now possible.
Weâve updated the format for Google Shopping, which stores the product description in the G:DESCRIPTION element, not in the DESCRIPTION. This is also taken into account by our format converter.
Improved work in the UI: The modal window for editing values ââfor conditions is included / not included in the list now has better visible buttons even on smaller displays.
Weâve fixed the Data file Import rule whose application ended in error if the URL where the source CSV is to be located contained a completely empty file. Newly, in such a case, the rule will do nothing.
We have updated the Glami format, which now supports the Set product parameters and Set shipping price rules for all language versions .
We have added basic support for Iceland (e.g. its currency).
Weâve devoted a lot of time to stabilize the MERGADO infrastructure.
And a number of other minor fixes.
Insiders
For our insiders, we have also prepared a supplement to the updates in the UI.
Above the list of rules on the Rules page, you can see the new Show rule series checkbox, which can be used to enable visual differentiation of individual rule series.
According to these series, when applying the rules, MERGADO âsplitsâ the current list of rules - and such series must then be processed in series - one after the other.
This âchoppingâ has always happened in the background - but thanks to this new tool, it is possible to clearly see how MERGADO really plans to apply the rules.
The general rule is that the fewer such series in a project, the faster the process of applying the rules.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
We have modified the format behavior for Shoptet.cz regarding hiding elements that do not meet the specification.
Previously, even in MERGADO, we automatically hid unhidden elements when exporting the final feed - elements outside the specification did not get into the feed, because such a feed is then invalid for Shoptet.
This behavior is still preserved, however - so that this mechanism is not too magical for the user - when applying the converter to the Shoptet format, elements that the specification does not know are automatically marked as hidden (which is then visible at first glance, for example on the Products page.)
We now always export the PRICEWITHFEE, PRICEWITHOUTFEE, RECYCLEFEE, COPYRIGHTFEE, CURRENCY, COPYRIGHTFEE, and CURRENCY elements with a decimal point.
For the STOREDQUANTITY element, only the integer part is now always exported.
From now on, we hide elements that the specification does not know (as with the Shoptet format).
We fixed the behavior of duplicating a project, which previously duplicated the rules for apps (which, however, do not automatically turn on when duplicating a project for a new project). This will no longer happen.
When sending audit results, the language of e-mails now takes into account the userâs language setting, if known.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
The component for automatic category suggestions (the Rename Categories in bulk rule) has received further improvements.
The proposed categories are newly returned without a root category (e.g. Heureka.sk |), which is now consistent with how we suggest the categories. When selecting an incomplete category, clicking on the field already activates the whisperer and the selection of the final category is now more user-friendly.
Weâve added a filter box that lets you choose whether to display:
Only those rows whose value in the leftcolumnis not in the input feed.
Only those rows whose values in the leftcolumnoverlap in such a way that the value in the lower row overrides the effect of the row that is higher.
E.g., the value on line no. 1 is Baby Goods | Toys | Board games | Board games, and the value on line no. 3 is Baby Goods | Toys. Because the Rename Categories in bulk rule always processes all rows and does not stop after the first match, the 3rd row overwrites the effect of the 1st row as a result.
With this filter option, the two lines will be displayed and you can resolve any unwanted conflicts.
Only those rows whose value in the rightcolumnis not in the known category tree for the given format.
In the search field on the main page, projects can now be searched by input or output URL.
We have improved error messages when manually creating elements (and their variables) so that they are more informative (e.g. the user will learn if it is not possible to create an element due to the fact that there is already a variable name that this element should get).
Platform
Weâve added the ability to support all formats for project-related apps.
Now, the project-related apps that âdonât really careâ about the project format will be able to set that they support âAll formatsâ.
In such case, it will be possible to run the app over any project - including projects that use a custom format.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
Weâve actualized the format Mergado XML to match the latest specification in version 1.8, and we have taken into account these changes in converters to other formats.
Newly supported elements: COST, COST_VAT, STOCK_QUANTITY and multiple BENEFIT.
At the same time, we revised the converters to other formats and expanded them to support other well-known elements:
INFORMATION_PARAMETER can have multiple values, e.g. [INFORMATION_PARAMETER|Color|1] = 'Red'
We support element SURCHARGE_PARAMETER, e.g. [SURCHARGE_PARAMETER|Imprint|DESCRIPTION] = 'Label' or [SURCHARGE_PARAMETER|Imprint|VALUE|Black and white] = '100'.
Element creation support WAREHOUSE under STOCK.
Shoptet supplier: Extended by a multiple element GIFT, STOCK|AMOUNT and PURCHASE_PRICE.
Shoptet complete: Extended by elements PART_NUMBER and PRODUCT_NUMBER.
The generated output feed has the correct order of elements.
We have also taken these changes into account in our XML audit.
Selection of pairing elements when creating a new project is nicer and more user-friendly.
Lots of other minor changes and fixes.
Insiders
We continue to improve the functionality and design of the product spreadsheet.
Fullscreen is now optional.
Weâve added the option to move columns with drag&drop.
Fixed bug: An empty element can now be edited and saved.
Platform
An app developer can now specify for each rule of his app in Developerswhich elements will be sent to his rule in JSON payload for products. There are three modes to choose from:
Send all elements(default)
Do not send any elements - for the product, in JSON, under the date key, in which there would otherwise be a dictionary containing pairs "element name": "its value" will send an empty dictionary. So, for example, instead of "data": {"ITEM_ID": "123", "NAME": "Rocket", "DESC": "Really good."} will only be sent "data": {}.
Send only elements containing a regular expression - only those elements whose name this regular expression contains itself will be sent.
For example, based on the regular expression PRODUCT|ITEM|VAT only the elements PRODUCT, PRODUCTNAME, ITEM_ID, ITEM_GROUP_ID, VAT, PRICE_VAT, etc. will be sent.
If the rules of your app need only some elements (e.g. ITEM_ID,or even just the internal MERGADO product ID), we strongly recommend using these mechanisms.
Thanks to the fact that unnecessary data will not be sent unnecessarily, work will be saved for both parties and, according to our benchmarks, in certain cases the application of the rules can be significantly accelerated .
You may experience minor MERGADO outages at this time. Thank you for your understanding and patience in deploying the new version.
If you have any questions, do not hesitate to contact us.
New nice clicker for selecting pairing elements when creating and editing a project.
Weâve improved error reporting when applying rules.
In the case of an error occurring during the processing of a specific rule, we now notify the user directly within which specific rule the error occurred, with the option to click directly into the rule if the rule can be modified (if not, the link will point to the rule list page and rule with error will be highlighted).
Improvement: If we detect the use of a non-existent variable when applying the rules, we end the process immediately and give the user information about in which rule it happened and which non-existent variable it is.
Previously, the process of applying rules was silently ignored by a non-existent variable (and an empty value was substituted for the variable), which could be a potential problem due to possible impacts on the resulting feed.
For several other email notifications, we have corrected the language in which they are sent to match the userâs language.
Data import rule: If the URL of an external data file is specified for the rule, there is now a new icon next to the URL field, which will open it in a new window.
Other minor fixes and improvements.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.
We have consolidated email addresses for messages sent from MERGADO.
We now use different email addresses to send different types of emails:
Regular notifications are now sent from notifications@mergado.com.
Notifications of (completed) audits are now sent from audit@mergado.com.
Emails regarding account management (registration emails, password recovery, access to the online store in MERGADO, etc.) are now sent from accounts@mergado.com.
In the improved selection of pairing elements, which we introduced in the latest version of MERGADO, you can now enter âpairingâ elements that do not yet exist.
We fixed Keychain messages when entering invalid credentials. We inadvertently displayed a general âunknown errorâ message there for some time.
Other minor bug fixes and improvements.
You may notice minor outages of MERGADO during the release time. Thank you for your understanding and patience in deploying the new version.