MERGADO 2: We have added support for Greek Google Merchants [gr].
MERGADO 2: We now support the XML format for Scraping Camel.
MERGADO 2: Due to the acquisition of the search engine Stileo.it by Glami, the format for Stileo is now split into the oldStileo.it (Until 07/2022), which uses the original XML specification, and then the newStileo.it, which now uses the Glami specification.
The MERGADO 2 converter from the input Google format now converts the shipping price without currency. Then if the target output format requires currency again, we return it to the value.
MERGADO 2: We have been working on optimizing the import of products from the input feeds. The final speedup may vary case by case, but in testing we measured up to 45 percent faster product imports.
In the rule for adding UTM parameters you can now select any target element(or element-path in the case of MERGADO 2 project).
For the Biano format, we have added support for the Set shipping price rule.
For this format, we can also now audit shipping price information in our feed audit.
For the following formats, we’ve updated the supported carrier lists that can be used in the Set Shipping Price rule:
The data import rule now has a limit on the size of the CSV source if the source is specified as a URL. In that case, the remote file must not exceed 100 MB in size.
The MERGADO Audit: We fixed a bug that could cause an email with information about a completed audit to be sent multiple times.
We fixed a bug that could occur when analyzing the input feed when creating a project if the input feed contained “excessively non-valid” HTML (e.g. in elements of type DESCRIPTION where item descriptions are sometimes inserted as HTML).
We fixed the visual highlighting of the NOT IN operator (not in the list) when writing a custom MQL query in the query form.
We fixed a bug when whispering values for an element in the query form.
We fixed the generation of CSV header when downloading rows in the Bulk rewrite by value rule setting.
And also, of course, we’ve added other minor tweaks and fixes here and there.
You may experience some minor MERGADO downtime at the times indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
The user scheduler is available only for MERGADO 2 projects.
We have updated the specifications for the Shoptet CSV formats.
The pairCode element will now always be present in the output feed.
The relationships between the value of the element with the universal MERGADO XML meaning CONDITION and the value of the Shoptet element itemType are as follows:
CONDITION = "new" is converted to itemType = "product" and vice versa.
CONDITION = "used" is converted to itemType = "bazaar" and vice versa.
The element weight(weight) now does not convert units (kg, lb, etc), but only the numeric value.
We have also updated the specifications for the format Shoptet universal.
We have improved the format converters for Kaufland:
The value 0 in the element with universal Mergado XML meaning DELIVERY_DAYS will be converted to formats for Kaufland as the value 1 in the handling_time element.
Revised and updated audit feeds for formats from :earth_africa families: Kaufland Marketplace - Offer and Kaufland Marketplace - product.
In general, we have improved the autodetection of formats from the Kaufland family.
When displaying results for the validator Element EAN contains an invalid value, we now correctly highlight the EAN element for the product.
We have implemented optimizer for MQL queries entered by the user on the Products page.
Currently it focuses mainly on the following cases:
Queries with equality over the same element, i.e. a = 'a' OR a = 'b' OR a = 'c' OR a = ..., are converted to the form a IN ('a', 'b', 'c', ...).
Queries with the multiple operator CONTAINS over a single element - that is, a CONTAINS 'a' OR a CONTAINS 'b' are converted to the regular expression form a ~= '(a)|(b)'.
the optimizer operates transparently. That is, externally - from the user’s point of view - the specified MQL remains in unchanged form, but if MERGADO finds that the query could be streamlined before running the query itself, it converts it into a better form in the background.
UI: The Rules page has been rewritten into more modern code. This will make it easier to improve in the future.
As part of this, we have resolved some ailments, such as in certain cases problematic moving rules around app rules when the app rule was at the top of the rules list.
Duplicating a rule within a project now works by inserting the duplicate rule at the position after the original. Previously, the duplicate was inserted at the end of the rule list.
And other minor improvements and fixes.
Platform
Individual app rules that have the property is_movable = 1 set and are also prioritized next to each other are blinded together when moved by the user. The user then moves the entire group when moving rules, and the rules in that group maintain their position relative to each other.
You may experience minor MERGADO outages at the times indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
We’ve extended the capabilities of automatic element value creation through the use of unsupported element paths (element-path) in rules.
That is, if there is a condition using a non-existent element in the element-path to which the rule should write a value, MERGADO will attempt to create the element.
However, only if there are conditions with the = operator or the AND logical connector in the element path.
Simple example: The Rewrite rule with the path PARAM {PARAM_NAME = "Size"} | VAL with the value XXL will completely create such a nested PARAM element, even if no parameter with PARAM_NAME = "Size"existed for the product yet.
We have fixed support for input feed URLs with sftp://(e.g. in the new project creation wizard).
MERGADO 2: We have added help text to a bunch of places in the MERGADO Editor interface, which is intended to clarify and make it easier for users to understand the new interface features related to managing projects in MERGADO 2.
We have also updated various other help texts already present in the interface.
We fixed an occasional error when importing input feeds, which could occur when there were zero products in the input feed.
And lots of other little things, but also background stuff that the user is more likely to not see, but improve the internal workings of MERGADO…
Platform
We fixed a frequently occurring API bug that could occur when suddenly accessing many API requests to products of one project at once.
You may experience minor MERGADO outages at the time indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
MERGADO Guide will help you in understanding our application. The first time you run it or in the hint box you will find the answers: - How to easily edit data with MERGADO? - What are the most common ways to use MERGADO? - What terms do we use?
This will give you very quickly information that you can use in the first days after registration or when you just need to review something.
MERGADO has learned new format Shoptet Category. You can use it to manage categories and subcategories of the Shoptet platform and thus create the structure of your online store.
Introducing new tool: Element path. In its first version, you can try and play with different paths without worrying, which you can then use in almost all parts of the Editor (selections, rules and more). For more, see the article on forum.
Returning the Product Detail page. In both MERGADO 1 and MERGADO 2, you can hide a specific product in it. More features will be added gradually.
In the Set UTM Parameters rule, we have added the ability to set new parameters: utm_id and utm_source_platform needed for GA4.
We fixed a bug where when clicking to edit a field in the Table on the Products page, in some cases the field could not be edited.
Shoptet formats have been extended with Hungarian version.
MERGADO XML now supports the same language versions as Google formats.
We have added a new IMAGE_ALTERNATIVE element to the Idealo.de CSV format.
The format converter for Google, Facebook, TikTok and Pinterest now adds currency to the g:shipping | g:price element even if the shipping price is zero.
Converter to Kaufland Marketplace - inventory formats now only populates the price_cs element with the price of the item.
We have improved the UX to easily click on related values on the specific element value page - we now design more relevant related elements.
In the component for automatic conversion of MERGADO 1 projects to MERGADO 2 projects, the MERGADO 1 elements EXTENDED_WARRANTY|Something and SALES_VOUCHER|Something were not converting correctly for Heureka formats. This is now fixed.
We have fixed a bug in the Data Import rule that caused rules to end up applying with an error if the imported CSV data file contained a column with a non-existent element that contained an accent in the name.
We added icons for other known services (and updated some existing ones).
And a bunch of other minor fixes and improvements.
You may experience some minor MERGADO outages at the times indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
We have extended the format families for Google Ads DSA and Facebook to support countries: Chile and Colombia.
We have added certification-related elements to the Google Shopping format: certification_authority, certification_name and certification_code and support for additional countries .
In the Kaufland Bidding format, the currency is now filled in correctly according to the country.
The converter in Shoptet CSV will now correctly convert values with °C.
We have deployed a new version of Element path. It now provides examples of specific paths to help you understand the changes from MERGADO 1.
In the Bulk Rewriting by Value rule, we have improved the data retrieval for pre-filling values into the left column of the form.
The UI: product name can now be only two lines. Subsequently, it will wrap and display in full only when the mouse is hovered over.
We fixed a lot of minor bugs in the UI. For example:
Error displaying designs on the Elements page.
A bug where some values were not being offered in the parameter whisperer when entering the path to an element.
A bug in the MQL input field on the Elements page where the element whisperer did not display when the [ keyboard shortcut was pressed.
Sometimes it could happen that the rule listing for a rule type Hide Products showed the target element (which doesn’t make sense). We have treated the situation that could cause this to happen and it will no longer happen for newly saved rules.
We fixed a bug in the component for automatic conversion of MERGADO 1 to MERGADO 2 where the special element @MERGADO_ID was not converting correctly in saved selections.
The component for conversion to MERGADO 2 has undergone another round of improvements and fixes.
And a bunch of other minor fixes and improvements.
You may experience some minor MERGADO outages at the time indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us
The registration process for MERGADO has undergone significant changes:
Registration itself is now simplified to a few steps.
We have improved the design of our Accounts login authority interface.
The actual invoicing data will not be needed until the end of the trial period of the online store (in 30 days). If the user does not have the payment details filled in, then after the trial period all projects in the user’s online store will be disabled.
We prefer payment by credit card debit. For new users, this is now the only form of payment we allow. Existing users can set it up as well.
The project conversion component of MERGADO 2 no longer converts unused variables.
We have modified the converters for Shoptet(supplier, complete, CSV) formats.
The converter now correctly converts values between ITEM_TYPE(Shoptet) and elements with meaning CONDITION(Mergado XML), as follows:
CONDITION = "new" ↔ ITEM_TYPE = "product" and
CONDITION = "used" ↔ ITEM_TYPE = "bazaar".
We fixed action price conversion(element ACTION_PRICE) - if this price already contained tax, we will not count it in the converter a second time.
Based on feedback, we have enlarged the search box** on the main page; this makes it easier to find, for example, the URLs of your feeds.
UI: If the URL of your input feed contains a login password and a name (in the form https://jmeno:heslo@nejaky-eshop.cz/...), the project overview page (where we hide the name and password from the URL for security reasons) now shows that the URL contains a name and password at all.
The button to copy URLnow also copies the entire URL with this information, not without it as before. This means that the full URL copied in this way can now be used in searches on the main MERGADO online store overview page.
We have fixed some issues when downloading products of complicated feeds in CSV format on the Products page. We continue to explore further ways to optimize this.
When detecting a format in the New Project Wizard, we now prefer the “main format” instead of formats that are only based on it. We prefer Google(e.g. over the very similar Pinterest format), Heureka(e.g. over the very similar Glami format), and Shoptet complete.
UI: We’ve optimized the project management interface so that now project pages will load at all even if the project contains a very large number of rules.
We fixed a rare bug in the rules that occurred when automatically creating element values(see news, June) if an additional nested condition was used in the path of the element to be written to.
The element-path component (element-path) has undergone another wave of improvements.
The valid element-path now displays a green firefly. The
We are now highlighting the syntax - just like in the MQL entry form.
Use the ALT+q and ALT+Q keyboard shortcuts to switch between tabs.
New suggest operators that can be used.
The search in elements is now supported by fuzzy-search.
For information on where to work with the new component, see this article.
Alza Marketplace integration formats will now be called AlzaTrade.
We’ve fixed the converter for the Zboží.cz format - we will no longer convert the CONDITION meaning element with the value "used" to the value "bazaar", but leave it with the original value.
We have slightly updated the specification for Malfini formats.
The value that used to be put under the ATTRIBUTES | ATTRIBUTE | ICON element will now be put as the attribute value under the ATTRIBUTES | ATTRIBUTE | VALUE | @icon path.
We have modified the behavior of the XML file exporter so that XML attributes are now wrapped with double quotes `` instead of single '.
We have reduced the amount of warnings generated when applying rules.
If an element path (element-path) targets a non-existent value, we will now only warn for element paths that contain conditions.
We’ve fixed an interesting bug in detecting and comparing the date of the last input feed change when that date is provided by the remote server in the last-modified HTTP header. This could cause a problem with comparing datetimes written in different timezones. This should now be fixed.
**We have refined the mechanism for detecting the number of changed products on import. Inaccuracies could occur when there was an element without a value inside the XML structure of the imported product, e.g. <VAT></VAT>.
when whispering categories for Kaufland formats, we will now suggest plural instead of singular forms. Thus, for example, we will suggest the form Fertilizer instead of the form Fertilizer.
We’ve also spent time on optimizations in the XML parsers that MERGADO uses to read your input feeds. They are now slightly faster, but most importantly they now require less memory, which (among other things) will ultimately help to make reading larger/more complex XML files more stable.
We’ve gone through piles of text in the MERGADO UI and updated it.
The UI: In the rules listing for the Set Click Pricing rule, we will now display the correct target CPC element of that format.
And other minor improvements and fixes.
Platform
As of 1 Sep 2023, we are changing the ratio of the amount paid out of revenue for paid apps. The new ratio is 10% better towards app developers, i.e.:
80% goes to developers and
20% goes to MERGAD.
As part of the phasing out of Appcloud as a repository for apps, we have removed the ability for newly created apps to reside on Appcloud. Existing apps that already use Appcloud can continue to use it.
You may experience minor outages of MERGADA at the times indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
With it, you can set the ideal time for you when you want MERGADO to start re-generating your project.
You can now set up to 3 time slots per day with a minimum of 4 hours apart.
You can now edit your product descriptions via the new WYSIWYG editor. This allows you to easily edit the HTMLcontent of an element value.
To start it, simply click on the “edit value” button next to the element with the meaning DESCRIPTION.
We support new integration of Pepita. This is one of the largest markeplaces in Hungary. It contains the formats:
Pepita.hu and
Pepita.hu - stock, which is an availability variant of the format.
The component for automatic conversion to MERGADO 2 is now ready for projects containing the ruleimport data file. Previously, we could not automatically convert these projects.
**We have adjusted the behavior of the data file import rule so that columns with the name of the target elements are matched even regardless of case(unless a match with the same case is found first). This is to make the rule a little easier to work with.
We also spent time on additional optimizations. Among other things, we have investigated and treated inefficiencies in storing data for products that have passed the rule application, but in reality the values of their elements may not have changed at all.
The embedded elements are now exported in the correct order when exporting the output CSV feeds in the header.
We’ve cleaned up the input product import process so that it doesn’t unnecessarily reset the values of multiple elements unless needed.
On the one hand, this makes the detection of the number of changed products** during import a bit more refined, on the other hand it is a slight optimization of the import process and the process of applying rules. The
We added the ability to easily copy the output feed URL in the last step of the create new project wizard.
We fixed the incorrect display of status icons in the Selection Manager on the Products page.
We have modified the converters from Malfini to Shoptet CSV format.
The SUPPLIER element is now automatically converted to the supplier element.
The elements ATTRIBUTE | NAME and ATTRIBUTE | VALUE are now converted to textProperty elements (and if there are more than one, to textProperty2, etc.).
We’ve added a bunch of new localizations for existing integrations:
Google Merchants:
Ireland (IE), Latvia (LV), Luxembourg (LU), and Portugal (PT).
Google Ads:
List
Bulgaria (BG) Egypt (EG) Estonia (EE) Finland (FI) Indonesia (ID) Israel (IL) South Africa (ZA) South Korea (KR) Lithuania (LT) Latvia (LV) Malaysia (MY) Greece (GR) Singapore (SG) United Arab Emirates (AE)
Google Ads Dynamic Remarketing:
List
Australia (AU) Brazil (BR) Bulgaria (BG) Chile (CL) Egypt (EG) Estonia (EE) India (IN) Indonesia (ID) Ireland (IE) Iceland (IS) Israel (IL) Japan (JP) South Africa (ZA) South Korea (KR) Canada (CA) Colombia (CO) Cyprus (CY) Lithuania (LT) Latvia (LV) Luxembourg (LU) Malaysia (MY) Malta (MT) Mexico (MX) Norway (NO) Portugal (PT) Russia (RU) Singapore (SG) Slovenia (SI) United Arab Emirates (AE) United Kingdom (UK) Sweden (SE) Turkey (TR) Uruguay (UY)
CZ, SK, HU, PL, AT, BR, DE, DK, ES, FI, FR, IT, NL, NO, RO, RU, SE, TR, UK, US.
Formats for Google Merchants:
AT, BR, DK, ES, FI, FR, ID, IT, KR, NL, NO, RO, RU, SE, TR, UK.
The component for automatic conversion of projects from MERGADO 1 to MERGADO 2 got a lot of improvements and fixes.
In the listing of your e-shops and projects on the main MERGADO page we show basic statistics from Google Analytics, if the online store is linked to GA. Now we display data from GA4 as well.
When reading the input CSV files we were sometimes unable to correctly identify the CSV dialect of the file. We have now improved this detection.
Improvements on the Rules page:
Filtering rules by element used now works correctly even if the rule targets a justified element path (element-path).
So now, for example, searching by the element IMGURL_ALTERNATIVE will also find rules that target the element path IMGURL_ALTERNATIVE { @@POSITION = 2 }.
The Rule Listing for rules like Set Product Parameters and Set Shipping Rate will now no longer show nonsensical target elements that may have appeared in certain cases.0
after duplication of a project, it will now automatically start the regeneration of the newly created project.
Again, we have slightly refined the detection of the number of changed products** when importing input feeds.
We have fixed an error when displaying the Project Settings page that was occurring when a project was using the output feed of another project in MERGADO as an input feed - and that other project was freshly deleted.
And lots of other small changes and improvements.
You may experience minor MERGADO outages at the times indicated. Thank you for your understanding and patience while deploying the new version.
If you have any questions, please feel free to contact us.
This applies especially to huge MQLs, e.g. of the type ITEM_ID IN ("xyz", ... 20 thousand items in total), which took extremely long to process and often ended up with an error. Now this should be much more efficient and faster.
For the and variants of the Kaufland Marketplace - bid format, we now treat the value 0 as a valid value in the handling_time element.
For the audit for Heureka formats, we now report multiple identical PARAM_NAME values not as an error, but as a recommendation that Heureka may ignore the remaining parameters with the same name.
We have updated the specification for Shoptet integration.
We now support ARUKERESO_HIDDEN and ARUKERESO_MARKETPLACE_HIDDEN elements.
to improve the usability of the user rescheduler, we have added performance to MERGADO so that projects scheduled in this way can be handled better.
Our component for automatic conversion of MERGADO 1 projects to MERGADO 2 projects has received further improvements and fixes.
UI: On the Elements page, for elements that are used as multi-value(if we know this information) for at least one product in a project, we now display their known maximum number(i.e. the highest value of @@POSITION that makes sense to use in the path to that element.)
Again, we’ve improved the download of the CSV product file on the Products page.
It should now handle larger projects than before, and also the resulting CSV now contains more information about the products and their elements.
The UI: In the rules form, when entering variables, we now also correctly whisper the special variable @MERGADO_ID(representing the unique product identifier in MERGADO).
UI: On the project overview page, the Product Count Variability graph was sometimes rendered with the wrong data. This has been corrected.
UI: On the Rules page, the rules rows now display a number with their order (to make it clear at a glance that their order matters).
UI: We fixed an error when displaying the project history if the current page was displaying app on/off records.
Platform
At the endpoint https://api.mergado.com/shops/<id>/info/ in the number_of_projects field, we now display the correct number of active projects.
On the endpoint https://api.mergado.com/queries/<id>/products/, which returns products from qeuries(which are under projects), we can now filter products by their created_at field (i.e. when they first appeared in MERGAD).
For the TikTok integration, we have added support for additional countries:
Chile
Colombia
Mexico
Russia
Ukraine
We have updated the specifications for the Glami formats.
We support the GTIN element** (the EAN element is now marked as outdated).
We have added support for Glami.pl.
We have spent time working on internal and “invisible” improvements to our code, which will then greatly simplify and speed up the implementation of new functionality in MERGADO - e.g. new rule types.
In the section for Audit output feed on the project overview page, we have fixed the behaviour of the audit progress indicator - it should now correctly show the status of the audit in progress.
We have fixed an error that could occur when trying to save project settings if the project was using custom format, which had previously had its state changed in the settings.
The Component for automatic conversion of MERGADO 1 projects to MERGADO 2 projects has received additional improvements and fixes.
And other minor fixes and improvements.
You may experience minor MERGADO outages at the times indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
In MERGAD there is a new rule type:Remove parameter values.
With this rule it is possible to remove parameters according to their value.
For example, it is possible to remove all Color parameters with values Green and Red in this way,
or it is also possible to remove all values with a specific parameter name (i.e. remove all parameters with the name Color regardless of their value).
The field for specifying the values to be removed can use variables.
If the output format has multiple potential target elements (or paths to an element) containing parameters, then you can select a target element from under which to remove parameter values.
For example, for Shoptet formats, you can choose between the target elements TEXT_PROPERTIES | TEXT_PROPERTY and VARIANTS | VARIANT | PARAMETERS | PARAMETER.
An article with a more detailed description of the new rule type is in preparation.
On the Products and Rules pages, we have optimized the retrieval of data needed to display the pages. Now large projects with a large number of selections with long MQL conditions (e.g. `ITEM_ID IN (…20 thousand items…) will load much faster and be less prone to rendering errors.
Keychain: We fixed a bug when saving the Mergado Analytic XML URL settings.
UI: We have restored alphabetical paging above the online store listing on the main MERGADO page to easily switch the listed shops according to whether their name starts with the selected letter.
UI: On the Rules page, we have corrected the display of the rules planner status icon.
UI: On the Products page, we fixed the display of the Save Changes button after changing the condition of the saved and currently displayed selection.
UI: We fixed the behavior of the WYSIWYGElement Value Editor on the Products page that added unwanted <p> elements when repeatedly switching the editor view mode.
We have improved character encoding detection of the input feed when importing it to better handle characters of other languages (e.g. Danish).
Again, other minor fixes and improvements.
If you have any questions, please feel free to contact us.
RuleRewriteis now multi-line(only for MERGADO 2 projects).
The rewriting of values for different elements can now be handled by a single rule instead of having to set multiple rewrite rules for different elements, as was previously the case.
Each line in this rule specifies the target element (or element path) and its new value.
clever insertion works in the row list - that is, two-column data in the clipboard can be inserted as new rows when editing a rule.
For custom formats, the URL of the file from which to retrieve the category list for the custom format can now be specified.
MERGADO expects a list in the target file where categories are specified; one category per line.
A single-column CSV without quotes around the values corresponds to this format - so you can also use, for example, a dynamically exported CSV from Google Sheets(see image below).
This file will not be downloaded once, but repeatedly as needed; the downloaded list is then remembered for a while (currently 30 minutes) before MERGADO downloads it again if needed.
The categories from this file will then be offered in the user interface wherever we offer categories for common formats(e.g. Heureka.cz), i.e. e.g. in the category rules form or when editing the manual value of a category element.
We have optimized the application of ruleFind and Replace in situations where search by regular expressions mode is used and at the same time there are more than ~500 such expressions (i.e., lines in the rule setting).
According to our measurements, this leads to a significant speedup of applying such a rule.
Queries: In the selections form on the Products page, we considered entries like ITEM__ID = 00123 to be an error, because a number cannot start with zero. This is now fixed because a number can actually start with zero.
Rules: The rule order number (in which order the rules are applied in sequence) visible in the rule list now holds the correct value even when searching or filtering rules.
UI: In the (extended) element-path component (element-path) the Right and Parameters tab has a new, brighter icon.
Variables: When creating or editing a variable to test a regular expression, we provide a random value for the selected element. Previously, this random value was taken only from the input values, and this mechanism could not be reasonably used to create variables from elements that are filled only when the rules are applied. This has been improved and now these random values are also taken from the output values of the selected element.
Queries: In the simplified mini-list of selections on the Products page, queries can now also be deleted.
This mini-list is also now open by default.
Improvements to the new project creation wizard:
We now preferably offer input and output formats by user state.
As suggestions for pairing elements, we now correctly offer nested elements, if any - e.g. VARIANTS | VARIANT | EAN.
On the Products page, we sometimes had text “bleeding” to the right when displaying the differences between input and output element values. This is now fixed.
:history: In the header of the component for displaying the e-shop listing its projects, there is now a click to quickly jump to the online store history.
We have fixed a bug in displaying the pairing chart of products (this applies to Heureka.cz and Heureka.sk formats).
When importing an unchanged input feed an error could occur in certain cases instead of the usual skipping of the import. We have fixed this.
When downloading product data as CSV on the Products page, we were returning the values in the resulting CSV position in the element path as ELEMENT { POSITION = 1 } instead of the correct ELEMENT { @@POSITION = 1 }. This has now been fixed.
We have fixed a bug in app Repairman when creating rules.
And lots of other minor fixes and improvements.
Platform
We can send a new hookprocess.apply.failed in case of rule application errors. Sending it can be set in the webhook settings for your app in Developers.
If you have any questions, feel free to contact us.
Rule application now processes variables iteratively.
What does this mean?
It means that when values from a variable/path to an element originating from a multi-value element are written to a multi-value element, then pairs of sourcevs `target** are newly processed sequentially. That is, the first found value is used to write to the first target element, the second found value is used to write to the second target element, etc.
What?!
For example, multiplying the prices of all variants under a product can now be done via one single rulecalculation, in which you set the VARIANTS | VARIANT | PRICE_VAT element to write %VARIANTS | VARIANT | PRICE% * 1.21:
The value %VARIANTS | VARIANT | PRICE% of the first variant is multiplied by 1.21 and inserted into the element VARIANTS | VARIANT | PRICE_VAT only for the first variant.
The value %VARIANTS | VARIANT | PRICE% from the second variant is multiplied by 1.21 and inserted into the element VARIANTS | VARIANT | PRICE_VAT only for the second variant.
MERGADO inserted a newline at the end of the element value when creating the output XML in certain cases for an element with an attribute. This is now fixed.
UI: In some places in the multi-line rule editing form we support smart paste from the clipboard. However, in certain situations, such smart pasting is undesirable - so you can now disable smart paste in those places.
In the create new project wizard we now suggest appropriate matching elements for custom formats as well.
Minor redesign of the top right corner of the MERGADO interface with the user menu. It is now easier to click on e.g. payment settings or invoices.
And other minor adjustments, fixes and improvements.
Platform
Endpoint /queries/<id>/products/ now supports the values_to_extract parameter, with which you can easily extract the values of their element-paths or variables to the returned products. See API documentation for more information.
Endpoint /elements/<id>/ now supports the PATCH method, through which you can change name(string), hidden(bool), order(int, only in MERGADO 2), is_attribute(bool, only in MERGADO 2).
We fixed sending webhooks after queries operations for projects, some of which were accidentally not being sent.
We have customized Invoicing for each customer.
We’ve made useful changes to billing for use of MERGADO paid services. Customers will now receive differential invoices during the month depending on the origination of the paid service under their user account - not until the 1st day of the following month.
If you have any questions, please feel free to contact us.
The Set product parameters rule has been significantly improved.
The rule can now set parameters for products from multiple different queries at once. :
The improved rule can also set multi-value parameters - e.g. multiple values for the Color parameter.
If the project output format specification defines multiple possible paths to the elements that represent the parameters (e.g. Shoptet and its TEXT_PROPERTIES vs INFORMATION_PARAMETERS), the rule can specify exactly where to set the parameters.
We have improved the import behavior of the input XML feed.
If there was an element inside the product with the same name as the element that, according to the XML format specification, wraps the whole product (e.g. ITEM for Google XML formats), Mergado now correctly includes this element in the product(and does not create a separate product from it, as it did before).
We have updated the Czech VAT specifications for feed audit.
In MQL queries you can now use element names NUMBER and NATURAL(which are also MQL keywords) without wrapping them in `[square brackets]_.
We have devoted considerable effort to preparing a more scalable infrastructure. This will open up opportunities to increase the frequency of project re-generation and also allow us to work on further improvements to Mergado’s performance.
On the Rules page, a list of target elements is displayed for rules like Rewrite, Remove parameter values and Set product parameters.
For the Spartoo format converter, we fixed a bug in the price conversion.
In the form for creating variables there is a button to extract a random value from the target element, which allows you to test regular expressions. Now this value is randomly extracted from both the output and input values of the element.
If an element with a numeric name(e.g. 13456) occurred in a project with the CSV format, displaying the Elements page could result in an error. This problem is now fixed.
The we have fixed cases where some pages in Mergado interface could not be loaded due to too high number of warnings generated during one rule application.
On the Mergado main page with the list of online stores, we now keep the search box if the user has access to only one online store.
And other minor changes and improvements.
You may experience minor Mergado outages at the times listed. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
The Heureka and Zboží.cz services have updated the calculation method and prices per clicks. Therefore, we have adjusted the ruleCost per click pricing to match their requirements.
We have updated Mergado Audit to integrate Heureka and Google to the current specification. For example, we added a check for:
Date format for the G:SALE_PRICE_EFFECTIVE_DATE element,
the value of the SIZE_TYPE element. It can only take the values: regular, petite, maternity, big, tall, plus,
whether the TITLE element contains any words related to the discount, etc,
elements DESCRIPTION, G:ID and LINK, where we check their content or uniqueness in the feed.
When creating a new project, we now report more accurate errors in the first step. You will now learn that:
you did not insert any url of the input feed,
the input feed url is not valid,
the input feed address is too long,
your feed server is unavailable,
your feed server is blocking our access,
there is no file at the supplied address, or
your server is not responding (or if there is a connection error).
We have hidden a left menu to switch online stores and projects for users who only have access to one online store that contains only one project.
The Set Product Parameters rule can now delete a value by leaving the value field blank. This works similarly for the Set shipping price rule, for example.
We have fixed a bug where a project that was converted from ISO 8859-15 to UTF-8 encoding could not be created.
MQL queries containing the character ? in the element name will now be evaluated correctly.
In some cases, we may not have offered pairing elements in the create new project wizard. This is now fixed.
We continue to prepare a more scalable infrastructure that will allow us to work on further improvements regarding Mergado performance.
And other minor changes and improvements.
You may experience some minor Mergado outages at the time indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
On the Rules page, instead of the original Apply Rules button, there are now two actions to choose from: Regenerate Changed, Apply Rules or Apply to Traced Items Only. For more information, see the article Run processes manually on the Rules page.
The online store settings are now consolidated into a single tabbed page - here you will find both general settings and the user permissions manager.
On the main page, the Custom Automation (formerly Macros) item is now hidden if the user has not yet defined even one custom automation(the first automation can be created inside the project).
On the main page, the Custom Formats item is now hidden if the user has not yet defined even one custom format(the first custom format can be created within the create new project wizard).
We have reduced the number of links in the footer of the main left menu for better clarity.
We have adapted this for localizations: Australia, Austria, Belgium, Canada, Brazil, Germany, Denmark, Spain, Finland, France, Hong Kong, Switzerland, Ireland, Japan, South Korea, Netherlands, Norway, New Zealand, Portugal, Sweden, Singapore, United Kingdom (Great Britain and Northern Ireland) and United States of America.
For CSV feeds for CJ. com feeds, we now support the following localizations: Australia, Austria, Belgium, Canada, Brazil, Denmark, Finland, Hong Kong, Switzerland, Ireland, Japan, South Korea, Netherlands, Norway, New Zealand, Portugal and Singapore.
To differentiate, we have added the suffix `(until 03/2024)_ to older formats (according to the old specification).
**We have adjusted the behavior of rules Set product parameters. The new behavior is that if the value of a variable to be inserted into the value of a parameter is empty for that product, the parameter will not be created(previously the parameter was created - but with an empty value).
We spent time optimizing the loading of product data on the Products page - loading huge and complex products (e.g. products with tens of thousands of elements with complicated indentations) should now be more nimble.
We have fixed a bug in the create new project wizard where an error could occur if input feed elements contained some unexpected characters (this is handled in the context of offering suitable matching elements).
We continue to simplify the user interface of Mergado.
Several pages related to project settings (and e.g. the delete project page)_ have been consolidated into one page with several tabs - more about settings in article on our forum.
We’ve optimized the behavior of analyzing the input XML feed in the project creation wizard:
In cases where there were a huge number of HTML/XML attributes in XML elements (but also, for example, in HTML elements inside CDATA in XML element values), such analysis could take an extremely long time. The new Mergado should handle such a situation better.
We have added support for additional formats for our automatic category suggestions under the Rename categories in bulk rule. We are now handling smart and automatic suggestions for these integrations:
Glami: Global , Czech Republic , Slovakia , Poland , Germany , Bulgaria , Brazil , Spain , France , Italy , Croatia , Hungary , Turkey , Slovenia , Romania , Latvia , Lithuania , Greece , Estonia .
We have slightly improved the filtering behavior of the rules by target elements on the Rules page.
From the Help window in the top menu you can now click on:
:movie_projector: A bunch of useful video tutorials to help you get up to speed on basic Mergado interface tasks.
UI: We’ve improved the display of some special characters that were not appearing correctly in the “entity” names on the project history page.
UI: We have fixed the position of the user’s avatar in the top left corner of the interface.
And other minor fixes and minor improvements.
Platform
Mergado was not sending webhookprocess.apply.start about the start of the rule application process when there were zero rules for a project. This is fixed and the webhook is now sent in this case as well.
You may experience minor Mergado outages at the time indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
We have a long awaited news - new ruleMerge variants.
The rule is designed to merge multiple separate products that form a group of items within the input feed, grouped (most often) by the value of the ITEMGROUP_ID element, into a single product and its sub-variants.
For more information on how to set up the rule, including an example of a suitable rule setting in the case of the Shoptet format, see our help.
We now support a new format, which is Kaufland Marketplace - offer XML - in variants for Czech Republic, Slovakia and Germany.
Along with this, we have adjusted the behavior of the existing CSV format for Kaufland, where the old offer_id is no longer counted and only the id_offer element is counted anymore.
We explored another option for optimizing the application of rules:
Now rule application should be faster in cases where the project contains a higher number of hiding rules that target a high number of input selections.
We also took a look at the data import rule and optimized it as well - the rule should now apply faster.
In the create new project wizard we fixed the behavior of the keys when selecting from the suggested input feeds. You can now use the ENTER key to confirm the selected URL.
When logging in to external services (Heureka, etc.) in Keychain, you will now get a nice informative message, not an error, if you don’t have any online store in that service that can be selected to connect to Mergado.
And other minor improvements and fixes.
Platform
When sending the process.apply.failed hook to payload, we’ve added some additional useful fields with information about the cause of the crash if the crash is caused by an error in an app rule.
We fixed the behavior of the endpoint project/<id>/rules so that it doesn’t crash if the project contains a rule of type params_remove_by_value.
You may experience minor Mergado crashes at the specified time. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please feel free to contact us.
MERGADO 2: We have added support for Greek 
Google Merchants [gr].
MERGADO 2: We now support the XML format for Scraping Camel.
MERGADO 2: Due to the acquisition of the 
search engine Stileo.it by Glami, the format for Stileo is now split into the old Stileo.it (Until 07/2022), which uses the original XML specification, and then the 
new Stileo.it, which now uses the Glami specification.
MERGADO 2 converter from the input Google format now converts the shipping price without currency. Then if the target output format requires currency again, we return it to the value. 
Facebook, 
Google, 
Kuantokusta, 
PriceRunner.
MERGADO 2: We have been working on optimizing the import of products from the input feeds. The final speedup may vary case by case, but in testing we measured up to 45 percent faster product imports.
In the rule for adding UTM parameters you can now select any target element (or element-path in the case of MERGADO 2 project).
For the Biano format, we have added support for the Set shipping price rule.
For the following formats, we’ve updated the supported carrier lists that can be used in the Set Shipping Price rule:
The data import rule now has a limit on the size of the CSV source if the source is specified as a URL. In that case, the remote file must not exceed 
MERGADO Audit: We fixed a bug that could cause an email with information about a completed audit to be sent multiple times.
We fixed a bug that could occur when analyzing the input feed when creating a project if the input feed contained “excessively non-valid” HTML (e.g. in elements of type 
We fixed the visual highlighting of the 
You can find it in the user interface under the project on the Regeneration page.
in the forum article
The user scheduler is available only for MERGADO 2 projects.
We have updated the specifications for the 
We have also updated the specifications for the format 
We have improved the format converters for 
Modifications in 
UI: The Rules page has been rewritten into more modern code. This will make it easier to improve in the future.
Simple example: The 
MERGADO Guide will help you in understanding our application. The first time you run it or in the hint box you will find the answers:
Introducing new tool: Element path. In its first version, you can try and play with different paths without worrying, which you can then use in almost all parts of the Editor (selections, rules and more). For more, see the article on 
We fixed a bug where when clicking to edit a field in the Table on the Products page, in some cases the field could not be edited.
Shoptet formats have been extended with Hungarian version.
MERGADO supports new formats:
Chile and 
Colombia.
.
The registration process for MERGADO has undergone significant changes:
We prefer payment by credit card debit. For new users, this is now the only form of payment we allow. Existing users can set it up as well.
We fixed action price conversion (element 
We have slightly updated the specification for Malfini formats.
We have modified the behavior of the XML file exporter so that XML attributes are now wrapped with double quotes `` instead of single 
We’ve fixed an interesting bug in detecting and comparing the date of the last input feed change when that date is provided by the remote server in the 
**We have refined the mechanism for detecting the number of changed products on import. Inaccuracies could occur when there was an element without a value inside the XML structure of the imported product, e.g. 
when whispering categories for Kaufland formats, we will now suggest plural instead of singular forms. Thus, for example, we will suggest the form 
As of 
We added the ability to easily copy the output feed URL in the last step of the create new project wizard.
We edited the text in the application according to 
Ireland (IE), 
Latvia (LV), 
Luxembourg (LU), and 
Bulgaria (BG)
Estonia (EE)
South Korea (KR)
Lithuania (LT)
Iceland (IS)
Japan (JP)
Cyprus (CY)
Malta (MT)
The component for automatic conversion of projects from MERGADO 1 to MERGADO 2 got a lot of improvements and fixes.
In the listing of your e-shops and projects on the main MERGADO page we show basic statistics from Google Analytics, if the online store is linked to GA. Now we display data from GA4 as well.
When reading the input 
Improvements on the Rules page:
Filtering rules by element used now works correctly even if the rule targets a justified element path (element-path).
We accelerated the compilation of 
We have improved 
UI: In the rules form, when entering variables, we now also correctly whisper the special variable 
UI: On the Rules page, the rules rows now display a number with their order (to make it clear at a glance that their order matters).
UI: We fixed an error when displaying the project history if the current page was displaying 
Ukraine
We have updated the specifications for the 
In the section for 
Component for automatic conversion of MERGADO 1 projects to 
In MERGAD there is a new rule type: 
field for specifying the values to be removed can use 
Keychain: We fixed a bug when saving the 
UI: On the Rules page, we have corrected the display of the 
UI: On the Products page, we fixed the display of the 
After the traditional Christmas break, MERGADO is back with another batch of regular new features and improvements!
Rule 
For 
Germany,
Improvements to the new project creation wizard:
On the Products page, we sometimes had text “bleeding” to the right when displaying the differences between input and output element values. This is now fixed.
When downloading product data as CSV on the Products page, we were returning the values in the resulting CSV position in the element path as 
Rule application now processes variables iteratively.
What?!
Minor redesign of the top right corner of the MERGADO interface with the user menu. It is now easier to click on e.g. payment settings or invoices.
Mergado supports new format 
We have updated the Czech VAT specifications for 
On the Rules page, a list of target elements is displayed for rules like 
In the form for creating variables there is a button to extract a random value from the target element, which allows you to test 
Belgium, 
, Czech Republic 
UI: We’ve improved the display of some special characters that were not appearing correctly in the “entity” names on the project history page.
UI: We have fixed the position of the user’s avatar in the top left corner of the interface.
When logging in to external services (Heureka, etc.) in