Product feed import mechanism description

How to add a product feed and what to pay attention to during import?

Sławomir Pociecha avatar
Written by Sławomir Pociecha
Updated over a week ago

🚨 If you received a message about insufficient product coverage during the feed import (productfeed.status.TOO_MANY_UNMATCHED_PRODUCTS), please contact us at hello@edrone.me or your personal account manager. We will help you verify product gaps in the feed.
⚒️ We are currently working on creating a new view for the PRODUCTS tab. In the near future, you will be able to self-verify the reason for feed rejection in it.

Present feed import mechanism is an automatic system for verifying product ID matching (and percentage coverage) between products collected in the database (thanks to integration) and those added to the feed.

If you are before importing a feed, please refer to the articles on how to prepare a proper product feed and learn how you can add a prepared .xml link in the panel of your own edrone account.

How does the mechanism verify compatibility?

1. Manual import

This is the type of import that occurs when you manually add a new .xml link (or re-add the same link) in PRODUCTS > Feed.

During this import, the system checks a maximum of 100 products from the most recent order (product ordering) and add_to_cart events sent to our system - we take into account events from the last 30 days only.

For the import to be successful, a minimum of 80% of these products must be found in the product feed - there must be a match in matching the IDs of these products.

In other words, if our system receives in an event sent from a store, for example, information about ordering a specific product (with a given ID/SKU), it must be able to find this product in the product feed.

During each manual import, a product matching configuration is created. The system compares the ID (product_ids in the trace) and SKU (product_skus in the trace) of the products in the database with the parameters in the feed: id, gtin, item_group_id and mpn. Next, the configuration is selected that will give the highest % of product matches.

This only applies to the GMC / Google Shopping feed standard. For other formats, there is always only one fixed parameter.

For more details on product matching, see the article: How do shop integration and product feeds relate to each other?

2. Automatic import

It can be initialized in two situations.

The first is an automatically triggered import, which by default for each account is triggered once every 24 hours at 00:00 UTC time - depending on the length of the queue and the workload on the system, this can go from several minutes to several hours.

The second situation is to trigger the automatic import by clicking the 'refresh' button when you want to update the downloaded data manually at a given time (after, for example, updating product images in the store).

The way of verifying the coverage of an automatic import is different from that of a manual import. The process is reversed. In this case, every time an import is initialized, the system checks that all products added to the feed have their matches in the edrone database. If there are more than 20% of new products in the feed (with new IDs) that do not have matches in the database, the feed will be deactivated. This is a mechanism that protects the edrone account from sudden, unwanted changes in the product feed.

If the feed is deactivated, the system will start using the data sent in events from the store.

If the product feed is deactivated by too low coverage, make the necessary adjustments to it and import it again.

Do this as soon as possible, especially if you are using edrone Universal Integration.

Each automatic import uses the product matching configuration that was created during the manual import.

The configuration can only be changed by initializing the manual import, or it can be done manually by our edrone Support.

An example of the operation and use of the coverage verification mechanism (manual and automatic)

There are 1000 products in the feed. We add a .xml link (manual import) in the edrone panel. The system found the following possible links:

  • Product ID (from the base) + parameter item_group_id (from the feed) = 32 occurrences

  • Product ID (from the base) + parameter mpn (from the feed) = 90 occurrences

  • Product SKU (from base) + parameter gtin (from feed) = 32 occurrences

The product IDs from the edrone database were successfully linked to the mpn parameter in this case. Coverage of the manual import was: 90%, so the feed will be added (a minimum of 80% is required). The system will automatically save this configuration and use it for each subsequent automatic import.

Then, for some reason, after a few days for 400 products (40%) in the feed the parameter mpn changes - for example, by changing this parameter on the store side. Our system will detect this change and for 400 products from the feed will not be able to find matches in the system database. The feed will then be automatically deactivated, as the difference in the number of new products in the feed between the last two automatic imports cannot exceed the 20% threshold.

⚠️ The described mechanism is applicable only to GMC (Google Merchant Center / Google Shopping) standard feeds.

Verification of coverage and ID matching does not occur for other feed formats supported by edrone: Ceneo, IAI (Idosell).


Do you need additional assistance?

If you have any additional questions about the product feed, please contact us at hello@edrone.me

Did this answer your question?