For the format of Idealo.de CSV, based on the current specification, we changed the column separator in CSV to ; semicolon (previously used comma).
For large and complex projects on the Products page, we are now optimizing downloading CSV with products.
That is, if a project contains a really large number of products and also a large number of hiding rules, we will now not provide information in the resulting CSV about whether the product is hidden by a rule or not (what used to happen otherwise was that the CSV could not be downloaded at all).
At the same time, we are now making this detection of “large and challenging projects”slightly smarter.
We fixed another bug in the converter from the Google and Facebook formats, where the values of the source elements remained in the output when converting multiple elements.
UI, Rules: When selecting queries in the Bulk rewrite by query rule, we now show number of products and query type(input/output) for specific queries.
UI: When loading the main store overview page, we no longer discard the search string that may have been defined in the page URL.
The search string and the search itself will now be properly preserved when the page is loaded.
UI: A magnifying glass icon is now displayed next to a number of text fields used for searching in the UI for better clarity.
UI: We have fixed the overlapping icons and text for the sort settings on the Products page.
UI: We have fixed the column widths for editing parameters of user macros, which were sometimes wrong.
And other minor improvements and fixes.
Platform
We fixed an interface bug that was occurring when editing the app rules.
You may experience a minor MERGADO blackout 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.
For the Heureka.cz and Heureka.sk formats, we now support the SALES_VOUCHER element.
In the query manager, you can see a pie chart next to the number of products, from which you can easily see what proportion of the total number of products in the project the query contains.
We have improved the whispering of names when creating new elements on the Elements page.
Queries. We fixed a bug that made it impossible to enter negative numbers for the <, >, <=, >= operators in the query form. Now it is possible.
Repeatedly sending an invitation to the MERGADO store to the email of a not yet registered user contained an error that caused the repeated invitation not to be sent. We have fixed this.
We also fixed a bug that caused the project history to not show output feed downloads if such downloads were over an insecureHTTP connection.
This does not apply to downloading output feeds over a secureHTTPS connection (that should ideally always be used) - that was and still is displayed correctly in the project history.
Buttons for launching a feed audit (e.g. on the project overview page) are now better protected against unintentional multiple starts of the same audit.
And other minor fixes and improvements… E.g.
We have improved a number of Hungarian translations of labels and texts in the MERGADO interface.
long texts for elements on the page are now properly wrapped when editing a macro.
In the Firefox browser, a nasty scrollbar appears on the main page after clicking “Hide all exports” next to the store list. That’s fixed.
Platform
We fixed the filtering for the endpoint https://api.mergado.com/queries/<id>/products/.
This endpoint should now also retrieve data more efficiently and therefore return data faster.
Developers of a specific app (i.e. users who belong to its vendor) will see the name and contact email of the user who rated the app in the app details in the Mergado Store next to the user ratings, in addition to the stars and text.
In Developers, the “select” to select the stage app could “jump” if the side menu was collapsed. This is fixed.
In Developers, it is possible to select supported languages for apps (i.e. languages in which the app can display its UI).
After selecting the languages, this information will be displayed in the app details in the MERGADO Store.
You may experience a minor MERGADO blackout 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 the query manager, we have added a shortcut for creating a rule for each query.
We’ve simplified the process of importing queries from Project A into Project B.
Now the source project can be selected separately - even without first selecting the source online store.
We fixed a bug that occurred when trying to edit an existing CPC setting rule.
A button was available on the project overview to start the audit of the output feed, even though the output feed did not yet exist (e. g. when the initial processing when creating the project ended with an error). We have fixed this.
We have improved the logic for UI optimization within projects that have a huge number of elements (i. e. thousands, tens of thousands, but even more).
If the elements in the project exceed a specific number in certain places in the interface where these elements are to be listed (e. g. a list of known elements in the query form or the rule editing form), then we do not list all elements but select only a subset of the most important ones. It is because the user-side browser may not be able to handle these element volumes otherwise and in such situations, Mergada either loads pages for a very long time or even stops responding altogether.
This ensures that even though there are a huge number of elements in the project, you can still work with it “somehow”; important elements are available (e. g. in the rules form) - and we hide the less important elements.
Until now, we considered the most important elements to be elements that are not embedded or multiple - that is PRODUCTNAME, CATEGORYTEXT, PRICE_VAT, … However, once the element name contained a vertical bar|, we hid it in the forms.
Such a solution has the disadvantage that in addition to the elements IMAGE|12073, IMAGE|12074, … _- for which there is a low probability that the user will want to work with them in targeted queries or rules - it also hides elements such as IMGURL_ALTERNATIVE|2 or DELIVERY|CESKA_POSTA, with which the user often wants to work…
The new solution is we hide only those elements that have a three-digit and multi-digit number behind the vertical bar.
I. e. elements like IMGURL_ALTERNATIVE|2 or DELIVERY|CESKA_POSTA for such projects we will no longer hide, but elements IMAGE|12073, IMAGE|12074, … we will keep hiding.
Thanks to this change, we were able to radically reduce the above-mentioned “fixed number” of elements, beyond which the UI optimization is activated - thus speeding up the interface of many huge projects - without riskingofferingimportantelements in the forms.
This change also means that for projects with a “huge number of elements” the default page listing behavior on the Elements page changes from Hide Multiple or Submerged Elements to Hide Unimportant Elements. With the fact that through the check box Show all submerged, it is possible to list all elements - i. e. submerged and non-submerged (such a option has already existed there).
You may experience a minor MERGADO blackout 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 are starting the initial phase of moving to a new IP address from which MERGADO is going to download your input feeds.
MERGADO can now access your input feeds from the IP address 81.31.39.112. Until then, the download of feeds always came from the IP address 185.58.41.182.
What does this mean for you? If you use IP address filtering to secure access to your input feeds, also allow access for IP address81.31.39.112. We are going to use the current IP address 185.58.41.182 for some time, but we plan to disable it.
We’ve accelerated the data preparation logic for the Setup CPC bidding rule. Therefore, the application of this rule should now be a bit faster.
We fixed the display of the dashboard of projects with TSV or TXT format.
We fixed adding metadata to output feeds.
UTF-8 is properly capitalized in XML files: <?xml version="1.0" encoding="UTF-8"?>.
We make it easy to work with text throughout the application. You can now use the cross to empty text fields with a cross.
The Idealo channel prefers CSV, so we decided to remove the Idealo XML format from the available output formats for new projects.
Output feeds of projects with the formats shopzilla, miinto, pricegrabber are now exported with the correct extension.
We fixed a bug when exporting to Google sheet, where not all elements were exported.
Outdated formats (e.g. Arukereso until 8/2021) will no longer be marked as highlighted in the new export wizard.
We have improved format detection. In the case where a feed matches multiple formats, we will offer the format that is missing fewer elements from the specification.
The special left panel for the Google Shopping format no longer jumps.
We have added several missing translations to the English version of the app.
In MERGADO Store we fixed misaligned text in the basic information block.
We updated the documentation for the Mergado Category XML and Mergado Analytic formats.
We have edited the message in Table View to better explain how to work with input and output values.
And other minor fixes.
Platform
Our new public IP for feed sources is 81.31.39.112.
You may experience some minor MERGADO outages at that 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.
For the Heureka.cz format, we added support for the 123KURIER carrier.
We fixed a bug in the format converter for the WooCommerce CSV format.
We’re working on mechanisms to provide better stability in feed audit processing (with the goal of reducing the number of situations where a challenging audit fails for some reason).
The new project creation wizard will now alert the user if they try to create a new store with the same name as another store they own.
In the create new project wizard, the ENTER key can now also be used to get to the next step.
UI: We have optimized the preparation of queries for the rule edit form. This should reduce the occurrence of situations where the form fails to render correctly in complex projects due to a large number of large queries.
On the Products page, we’ve cleaned up the Preview type view and improved it.
We can now highlight differences between input and output values in this view.
We have added fields for the product URL, product ID (e.g. from the ITEM_ID element), and product availability.
The product description is no longer displayed.
UI: Some text fields now display the remaining number of characters the user can enter.
In the format selection input fields on the audit page and in the project settings, the formats are now sorted by country.
We have optimized the preparation of products for downloading CSV with products on the Products page. Now the downloaded CSV should not be “cut off” after a while but should contain all the products it should include.
We fixed the link to accept the store invitation when clicking through from the notification in the UI.
We’ve fixed the links to help for rule types in the tooltip in the rules form.
Filtering rules on the Rules page now filters instantly, no need to confirm the search with an ENTER.
When saving a variable, a false red error message could “flash” after submitting the form. This should now be fixed.
We have added missing (or fixed existing) translations here and there in the interface.
And other minor edits and fixes.
Platform
Due to a bug, it was not possible to edit the rules for the non-production stages of the app. This should be fixed.
You may experience some minor Mergad outages at the time indicated. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please do not hesitate to contact us.
We have modified the Upgates format definitions according to the current specification.
Changes for the Facebook format:
The default value of the CONDITION element is new.
Add a g:country element for each delivery specification.
We have modified the default pairing elements for the Argep.hu format.
We fixed a bug on the Products page that was causing product sorting to not work correctly.
We are deploying code optimizations and improvements to feed audit that should make feed audits more efficient.
We recently had a bug in the Data Import rule that prevented us from uploading a CSV file larger than 2 MB(the rule should be able to upload a 25 MB file). This has been fixed.
The Bulk rewrite by values rule had a bug that caused regular expression looking for the expression ^$(i.e., empty text) to be evaluated incorrectly - it could not find a match in the empty element value. This is now fixed and a match is found.
In a project where the input and output format is MERGADO XML, the second element GENERATOR was also exported due to an error. This is now fixed.
We fixed an error that could occur when submitting the form when editing the element name.
The UI: box requiring confirmation when leaving the edit rule page (which is intended to prevent data loss when accidentally leaving the page) was sometimes not showing. This has been fixed.
UI: We added new icons for a number of well-known search engines and services.
We added the missing Hungarian version of the banner on the feed audit page.
We have updated the specifications for the formats Upgates Products and Upgates Categories.
On the Products page, we now use lazy loading for image display. Loading images will now be more efficient on the side of the user.
When creating a new project, we can now handle the URL of the feed with HTTP authentication, which contains the at-sign@ in the user name.
I. e. it will now be possible to create projects with a URL in the form of: https://user@someemailaddress.com:somepassword@www.domainxyz.com/somefeed.xml.
We’ve further optimized the feed audit component. We will now read feeds written in valid XMLfaster and more efficiently.
In the wizard for creating a new project, you can re-edit the project name directly when creating it.
When reviewing the results of the output feed audit of a specific project, we have accelerated the mechanism by which we match the product from the audit to the product from the project(which is needed to allow the user to hide the product listed in the audit, for example).
UI: On the project dashboard, it could happen that the tooltip for graphs was overlaid by the left main menu. We fixed this.
UI: We have improved UX for navigation in **the wizard for creating a new project ** via the keyboard. And we’ve added a few other minor improvements to the guide.
And other minor fixes.
You may experience minor MERGADO downtime at the indicated time. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please do not hesitate to contact us.
Audit XML: With feed audit for the format Heureka.cz and Heureka.sk, the case of the parameter name will no longer matter when validating parameters.
The Products page got a minor facelift.
We have added the ability to set the number of products to be listed.
The list of rules active on the query (with the option to add a new rule) is now nicer.
For columns, when displaying the Table type, it is easier to see whether they are sorted by output or input values.
On the Products page, we also improved the way we deal with product display depending on the format specification (so that we can display e.g. product name or product image according to the best product information and input or output format used).
Elements: In projects with CSV format, it is now possible to create an element via UI even with [ and ] characters in the name (e.g. image[0].url).
Custom format: We have made fixes to eliminate element name conflicts from the input feed with elements with special meaning.
That is, for example, we should not automatically add the special meaning"product wrapper element" to the ITEM element from the input feed, which should be set to "save as is" according to the custom format settings, even though the user has set the custom format otherwise.
UI: We fixed some text and translations here and there.
And other minor improvements.
You may experience minor MERGADO downtime at the indicated time. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please do not hesitate to contact us.
We have updated the NajNakup.sk format according to the latest specification.
The values of the NAME and DESCRIPTION elements will now be encapsulated in CDATA.
we have added support for the IMGURL element as an alternative image specification option.
We have also modified the order of elements when exporting.
When importing and parsing feeds for custom format, we sometimes misread XML attribute names if their name contained namespace. We should now be able to do this better.
We fixed a bug that caused the number of unique values of input elements to be miscounted when importing “changed products only”. This is now fixed.
UI: For single line text fields, an awkward looking horizontal scrollbar could appear for longer text values (depending on the web browser used). This should be fixed.
UI: When opening the left blue search bar for stores and projects, it is convenient to autofocus on the search box so that the user can directly type the search text.
When creating elements in CSV projects (or when editing them) we have extended the validation of the element name. Now the CSV element name can contain anything except a newline.
And a bunch of other little things that make the MERGADO interface more pleasant to work with.
You may experience minor MERGADO downtime at the indicated time. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please do not hesitate to contact us.
We fixed a bug where the attribute value of the element being created could not be created containing a dash or minus - e.g. GIFT(ID=HPF12-191)
The audit results page provides a clearer list of supported audits by country.
In Store, we previously misidentified the currency. It is now identified by the information from accounts for logged in users. For not logged-in users by browser information.
You can now create a new export with a URL that contains up to 2048 characters. The original limit was 250 characters.
Projects with Miinto TSV formats will now generate the output file correctly.
We have solved a bug of escaping \ in MQL. If the element name contains a space or one of the function characters \[] it should be escaped = put it in square brackets and add \ before all function characters. E.g. S[a]mple escaping\ element used in MQL: [S\[a\]mple escaping\\] = "understood"
We have exclusively added support for Mall Marketplace, Mall Marketplace - availability feed and Shoptet CSV formats to the new version of MERGADO 2. If you are interested in testing them, including testing the new version, just contact us.
To our smart component for automated category mapping, which we introduced in June 2020, we’ve added support for new formats: Google Shopping [cz], Google Shopping [sk], Google Shopping [us], Google Shopping [pl], Google Shopping [de], Google Shopping [hu]
and many other improvements to the MERGADO backend.
You may experience minor MERGADO downtime at the indicated time. Thank you for your understanding and patience as we deploy the new version.
If you have any questions, please do not hesitate to contact us.
The audits for Shoptet.cz and Shoptet.sk formats XML and CSV have been significantly updated.
For the Google Sheets format, which exports directly to Google’s online spreadsheet processor, we have corrected the output URL displayed on the project overview. It now again leads to the address in Google Sheets.
on the Products page, we were displaying the wrong icon (we took the icon by input format, which is wrong - it should be taken by output format) for the product card click-through in the product finder. This is now fixed.
There is another round of research into possible optimizations - with the goal of speeding up MERGADO’s feed processing.
UI: On the Project History page, we were displaying irrelevant items in the event type field. We have fixed this.
downloading CSV with products from the Products page should now be more robust for projects with a high number of items.
UI: For the infobox on the main online store overview page, the discount** associated with the length of the billing period is now displayed alongside the length of the billing period.
UI: For icon-buttons tightly bound to the input field, we’ve expanded the size of the clickable area.
And a number of other minor fixes and improvements.
Platform
For MERGADO 2 projects, we fixed filtering of elements that the app defined that it wanted to send when applying rules.
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.
We now check for the presence of the mandatory handling_time element and deselected the shipping_group, delivery_time_max and delivery_time_min elements as mandatory.
We have updated the converters for different formats:
Zbozi.cz now knows the LIST_PRICE element.
Google Ads Dynamic Remarketing now knows the Item subtitle element.
MALL Marketplace will have the value listed in the WEIGHT element without the “kg” unit.
Google formats:
If delivery_days > 3 is detected in the input value, the value backorder appears in the output of the g:availability element.
If delivery_days <= 3 is detected in the input value, the value in_stock appears in the output of the g:availability element.
Improved the logic for automatic detection of the input feed format. The new project creation wizard should now pre-select more relevant formats than before.
UI: We added fuzzy search in the various input fields to select a specific value through the UI - this means that the user does not have to enter the exact text of the value to find it, but just some letters(which don’t even have to be consecutive) for example.
For example, to quickly search for the format Google Shopping [us], just enter gous in the field.
UI: We fixed an error that occurred when the user entered unexpected input into the date input field (e.g. on the Project History page).
UI: We fixed the alignment of the macro sharing icon.
And other minor fixes and improvements.
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.
MERGADO comes with a new feature, in which we switch from a linear data representation system to tree-based data organization of products (i.e. Tree Based Products, TBP for short, as our smart developers call the new system internally), with the goal of significantly expanding MERGADO’s capabilities. We call this new feature MERGADO 2 and you can learn more about it in an article on our blog.
News
In the create a new project wizard there is now an option to create an experimental MERGADO 2 project.
MERGADO can now load input feeds over HTTPS even with an incorrectly set certificate.
Gone are the days when an incorrectly set TLS/SSL certificate from your infrastructure provider prevented you from using MERGADO.
If MERGADO detects an error in the HTTPS certificate settings when downloading the input feed, we still download the feed and import it - in which case we display a warning on the project overview page with any details of the detected error (e.g. the certificate has expired, or perhaps that the URL with https://... in the background redirected to the insecure protocol http://...).
A poorly set HTTPS certificate on your web server may mean that data traffic between your server and MERGADO will carry a risk of eavesdropping by third parties. We strongly recommend that you have your HTTPS certificate set up correctly.
We’ve updated the spec for the Emag.ro format and its audit.
For more complex input XML feeds, the estimate of the number of products in the feed could be too different from the actual number of products in the feed in the new project creation wizard. The estimation mechanism has been improved.
On the user’s custom formats listing page, we added a new column to indicate which type of files (.xml, .csv, etc.) the custom format is for.
The error when creating an element that would automatically create a variable whose name conflicts with an existing variable, we now display the correct error message.
and a large number of other minor changes and fixes.
MERGADO 2
MERGADO 2 is now in public beta.
For MERGADO 2, we have added support for the following formats: Kieskeurig, Kuantokusta, Mailkit, Miinto, Modemi, Moebel, Mojinterier, Mojoutfit, Monitor, Monitorcien, Nextag, Pricegrabber, RSS, Shopzilla, Srovname.
Speed: Since we were aware that complex products(i.e., products with a high number of nesting) in MERGADO 2 exported very slowly when we exported the output XML, we gave it a closer look…
The result of our investigation is optimization, which as a result means a multi-fold speed boost in the export process of the output XML feed (the more complex the structure of the exported products, the greater the speed boost compared to the previous state).
UI: We have improved the mechanism for highlighting paths to elements available in various input fields in the UI.
We have improved the mechanisms for hinting element values in various fields in the UI.
The whispering is triggered by typing (or deleting), and the dropdown can be hidden using the ESCAPE button.
The whispering is based on the nesting, i.e. for example after PARAM | the Heureka.cz format will whisper PARAM_NAME and VAL.
We have added support for displaying warnings that can occur for individual products when applying rules (e.g. that the path to the target element overwrites multiple values instead of the expected single element value - which can occur for multiple elements if the path to the element does not specify the target position/index of the element).
Warnings from the last successful application of the rules will be visible in the UI for that product on the Products page.
A listing of all warnings can be found by clicking on the rule application record in the project history.
For the most recent rule application, warnings will also appear on the project dashboard.
We have optimized the mechanism for exporting CSVs with product data on the Products page to be able to download CSVs with many products (e.g. 100k or more products).
We have fixed situations where, when using element path as a variable in rules, the specified path to the element value was not processed correctly when applying rules.
Please note that MERGADO 2 projects will be charged for as of this release according to the standard price list.
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.
A new rule type was added for MERGADO 2: Add value to a multi-value element.
This rule can be used to add a new value to a multi-value element (such an element must of course be already defined in the schema - i.e. in the element list - of the project).
We have added support for additional language versions of the Google Ads Dynamic Remarketing format:
MERGADO 2: We are continuously exploring ways to optimize the import of input feeds and the application of rules.
MERGADO 2: A button has been added to the Elements UI page to change order of elements according to specification if the project has an output format that requires strict order of elements.
MERGADO 2: We added a number of improvements to the element/attribute value listing page:
We added caching for already loaded and displayed values - the UI should be more responsive in many cases.
When listing the output values of a given element-path, the status of hidden of products is now considered. Thus, values from hidden products will not be taken into account when displaying information about the output values of an element/attribute.
We have improved the graph with "TOP values " - now it primarily lists the number of products in which the value occurs.
Previously, the focus was on the total number of occurrences - in fact, a single value can occur multiple times within a multi-value element for a particular element of a single product - however, we consider this information to be less useful than the number of products. However, if the number of products and number of occurrences are different, the user will see this information for the “TOP values” chart.
MERGADO 2: The variables already work in the Add a value to a multi-value element rule.
MERGADO 2: We have adapted the component for setting pairing elements to allow any element-path to be set as the one to pair products by when importing the input feed.
MERGADO 2: We fixed and improved the display of products on the Products page:
We’ve cleaned up the visual of the tab headers of listed products.
Now, when clicking into the values of a specific element/attribute, the product values page will be displayed with the correct target set - i.e. whether to display input or output values for the element-path.
We fixed a bug that sometimes caused the user preference for how to display products to not be saved.
The checkbox that allows you to create an experimental Mergado 2 project is now displayed above the input feed URL field in the new project viewer for better visibility.
And really a lot of other small improvements and fixes.
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.
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.
For the 
format of Idealo.de CSV, based on the current specification, we changed the column separator in 
For large and complex projects on the Products page, we are now optimizing downloading CSV with products.
At the same time, we are now making this detection of “large and challenging projects” slightly smarter.
We fixed another bug in the converter from the 
Google and Facebook formats, where the values of the source elements remained in the output when converting multiple elements.
UI, Rules: When selecting queries in the 
UI: When loading the main store overview page, we no longer discard the search string that may have been defined in the page URL.
UI: A magnifying glass icon is now displayed next to a number of text fields used for searching in the UI for better clarity.
For the 
In the query manager, you can see a 
pie chart next to the number of products, from which you can easily see what proportion of the total number of products in the project the query contains.
Queries. We fixed a bug that made it impossible to enter negative numbers for the 
Repeatedly sending an invitation to the MERGADO store to the email of a not yet registered user contained an error that caused the repeated invitation not to be sent. We have fixed this.
We also fixed a bug that caused the project history to not show output feed downloads if such downloads were over an insecure 
Buttons for launching a 
Hungarian translations of labels and texts in the MERGADO interface.
long texts for elements on the page are now properly wrapped when editing a macro.
Firefox browser, a nasty scrollbar appears on the main page after clicking “Hide all exports” next to the store list. That’s fixed.
Developers of a specific app (i.e. users who belong to its vendor) will see the name and contact email of the user who rated the app in the app details in the 
In 
In the query manager, we have added a shortcut for creating a rule for each query.
We fixed a bug that occurred when trying to edit an existing 
We have improved the logic for UI optimization within projects that have a huge number of elements (i. e. thousands, tens of thousands, but even more).
If the elements in the project exceed a specific number in certain places in the interface where these elements are to be listed (e. g. a list of known elements in the query form or the rule editing form), then we do not list all elements but select only a subset of the most important ones. It is because the user-side browser may not be able to handle these element volumes otherwise 
Such a solution has the disadvantage that in addition to the elements 
The new solution is we hide only those elements that have a three-digit and multi-digit number behind the vertical bar.
This change also means that for projects with a “huge number of elements” the default page listing behavior on the Elements page changes from 
We are starting the initial phase of moving to a new IP address from which MERGADO is going to download your input feeds.
We fixed the display of the dashboard of projects with 
MergadoStats: 
SmartBay.pl: 
Skroutz.gr: 
We fixed a bug when exporting to Google sheet, where not all elements were exported.
We have improved format detection. In the case where a feed matches multiple formats, we will offer the format that is missing fewer elements from the specification.
Our new public IP for feed sources is 
WooCommerce CSV format.
In the create new project wizard, the 
On the Products page, we’ve cleaned up the Preview type view and improved it.
UI: Some text fields now display the remaining number of characters the user can enter.
In the format selection input fields on the audit page and in the project settings, the formats are now sorted by country.
We’ve fixed the links to help for rule types in the 
Facebook format:
We have modified the default pairing elements for the 
We recently had a bug in the 
We fixed an error that could occur when submitting the form when editing the element name.
We have updated the specifications for the formats 
We are preparing support for other formats for automatic category suggestions (in the 
We have added an icon for: 
We have improved UX for navigation in **the wizard for creating a new project ** via the keyboard. And we’ve added a few other minor improvements to the guide.
When creating elements in 
Google Shopping [us], 
on the Products page, we were displaying the wrong icon (we took the icon by input format, which is wrong - it should be taken by output format) for the product card click-through in the product finder. This is now fixed.
downloading CSV with products from the Products page should now be more robust for projects with a high number of items.
UI: For the infobox on the main online store overview page, the discount** associated with the length of the billing period is now displayed alongside the length of the billing period.
We have updated the converters for 
UI: We fixed an error that occurred when the user entered unexpected input into the date input field (e.g. on the Project History page).
UI: We fixed the alignment of the 
MERGADO comes with a new feature, in which we switch from a linear data representation system to tree-based data organization of products (i.e. Tree Based Products, TBP for short, as our smart developers call the new system internally), with the goal of significantly expanding MERGADO’s capabilities. We call this new feature MERGADO 2 and you can learn more about it 
MERGADO can now load input feeds over HTTPS even with an incorrectly set certificate.
A poorly set HTTPS certificate on your web server may mean that data traffic between your server and MERGADO will carry a risk of eavesdropping by third parties. We strongly recommend that you have your HTTPS certificate set up correctly.
.
We’ve updated the spec for the 
and a large number of other minor changes and fixes.
UI: We have improved the mechanism for highlighting paths to elements available in various input fields in the UI.
We have improved the mechanisms for hinting element values in various fields in the UI.
We have added support for displaying warnings that can occur for individual products when applying rules (e.g. that the path to the target element overwrites multiple values instead of the expected single element value - which can occur for multiple elements if the path to the element does not specify the target position/index of the element).
We have optimized the mechanism for exporting CSVs with product data on the Products page to be able to download CSVs with many products (e.g. 100k or more products).
Denmark,
Finland,
France,
Italy,
Netherlands,
Spain,
Switzerland.
Macros: We fixed a bug that caused repeated executions of the same 
MERGADO 2: We added support for new formats 
MERGADO 2: A button has been added to the Elements UI page to change order of elements according to specification if the project has an output format that requires strict order of elements.
MERGADO 2 converter from the input 
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 
For the following formats, we’ve updated the supported carrier lists that can be used in the Set Shipping Price rule:
You can find it in the user interface under the project on the Regeneration page.
in the forum article
We have updated the specifications for the 
We have also updated the specifications for the format 
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 
