Breadcrumbs

Product data feed

About feeds

A feed is a file that contains a list of products you want to advertise through KelkooGroup.

When you add your products, you’ll assign attributes to each to describe them. Some, such as condition and availability, have standardized or accepted values. Others, including id or title, are left open for you to fill out however you like.

Accurately describing your products using the required and suggested attributes helps people find them, and ultimately improve the performance of your KelkooGroup campaigns.

Setup your feed for KelkooGroup

Option 1 - Use an existing feed

If you have already built a product data feed to use on other platforms, we can reuse it to advertise your products through KelkooGroup. We support the following feed types/formats:

  • Google Shopping format (ideally as XML file)

  • Feeds from feed aggregators (Beezup, Lengow, Shopping-Feed, etc.)

  • Feeds from other comparison shopping engines (Billiger, Idealo, Heureka, etc.)

  • Feeds from affiliate networks (Admitad/Yandex, AWIN, Belboon, DaisyCon, Partner-Ads, TradeTracker, etc.)

Option 2 - Create a feed from scratch

Product data specifications

The KelkooGroup product data specification page lists all the attributes you need for you KelkooGroup shopping campaigns:

  • Some attributes are required for all products

  • Some are required for certain types of products (such as apparel)

  • Others are recommended.

Failure to provide a required attribute may prevent that particular product from showing up in KelkooGroup shopping campaigns, whereas failure to provide recommended attributes may result in products showing up less frequently.

The product data specification also provides guidelines for submitting high-quality data to KelkooGroup. Fresh, comprehensive, and accurate product data will help attract users to your products. Some best practices to form the basis of performing shopping campaigns include:

  • Provide clear and conspicuous pricing information.

  • Provide the freshest availability status of your items.

  • Provide complete and correct shipping information and costs.

  • Show a product that is essentially identical on your landing page to the product data you submit to Google.

Feed formats

We currently support data feeds in these formats:

Type

Advantages

Disadvantages

Text file

  • Simple to create and edit if you have a spreadsheet program

  • Easier to view multiple products

  • Easier to make formatting mistakes

XML file

  • Including multiple values for an attribute is easier

  • May require more tech-savviness

  • Difficult to see many products at once

Guidelines to create text files

If you choose a text file, here are some recommendations:

  • The first line of your file must be a header row, defining the structure of your file. The attribute names you use in this header row must respect the name of the attributes as shown in the KelkooGroup product data specification.

  • Use field separators to separate product attributes, new lines allow our system to distinguish between products.

  • You can use any type of field separator.

  • Of course, the field separator should not be present within a same field (for example in the description).

  • All products / lines must contain the same number of fields. If a field is has no value, it must be left blank with the field separator present.

An example of a TXT file with some of the required attributes and using ";" as field separator would look like this:

id;title;product-url;price;brand
MLK245;100 Pant fleece pant, men's 10/11;https://www.merchant.com/product/100-pant-fleecebukse-herre-1011-19959.html;599.00;The North Face

Guidelines to create XML files

If you opt for an XML file, here are some recommendations:

  • Respect the names of the XML tags as shown in the KelkooGroup product data specification.

  • The XML file should be validated using a tool like The W3C Markup Validation Service before sending it to us.

  • If you choose to not validate your XML file, it is preferable to insert the contents of the text fields in a CDATA section. CDATA sections are not analysed so characters such as &, >, or < won't make your XML file invalid.

  • Please note that an invalid XML file can not be operated by KelkooGroup system and your products will not be updated.

An example of a XML file using some of the required attributes would look like this:

XML
<products>
    <product>
        <id>MLK245</id>
        <title>100 Pant fleece pant, men's 10/11</title>
        <product-url>https://www.merchant.com/product/100-pant-fleecebukse-herre-1011-19959.html</product-url>
        <price>599.00</price>
        <brand>The North Face</brand>
        <description><![CDATA[The North Face TKA 100 Pant fleece pant is designed for cold conditions and fits very well under the shell clothing.]]></description>
        <image-url>https://www.merchant.com/uploads/pictures/21691-128.jpg</image-url>
        <ean>4856349257328</ean>
        <merchant-category>Clothing - Men - Pants - Outdoor Pants</merchant-category>
        <availability>1</availability>
        <delivery-cost>9.00</delivery-cost>
        <delivery-time>1-3 days</delivery-time>
        <mpn>AJGW</mpn>           
    </product>
</products>

Send your feed to KelkooGroup

Feed retrieval methods

We currently support the following ways to retrieve your feed:

  • Retrieve via HTTP / HTTPS

    • With this option, you host your feed file on your server(s), and KelkooGroup will fetch them on regular basis (see the timing for each country in the next section of this page).

    • You must provide a URL where KelkooGroup can find your complete product data feed, eg. https://www.merchant.com/feeds/kelkoogroup_feed.xml if XML or https://www.merchant.com/feeds/kelkoogroup_feed.txt if TXT.

    • If the URL is password protected, you must provide username and password for us to access it.

    • If you apply IP restrictions, you must allow KelkooGroup public IP addresses access (provided upon request).

    • The name of your feed file must remain the same over time (so that the URL remains constant over time).

    • In case of large volumes of data generated "on the fly", make sure your web server is configured with proper timeout to allow the complete download of the feed file.

  • Retrieve from FTP

    • With this option, you host your feed file(s) on your FTP server, and KelkooGroup will fetch them on regular basis (see the timing for each country in the next section of this page)

    • You must provide to KelkooGroup:

      • The address / URL of your FTP server

      • The name(s) of the feed file(s) we should use

      • Login (username and password)

  • Upload to KelkooGroup FTP

    • This option is set up on request and will allow you to host your feed file(s) on a KelkooGroup FTP server.

    • We will communicate your login details once your KelkooGroup FTP server account has been created.

    • Pls refer to How to upload your feed to KelkooGroup FTP server for more details.

Schedule your feed updates to optimise its freshness on KelkooGroup campaigns

KelkooGroup fetches feeds on regular basis to refresh your products online. Please ensure your feed files are available at the right time(s) for your country.

Timings below are subject to change without prior notice. Please verify the update times with your KelkooGroup contact.

Country

Fetching offers

Austria

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Belgium FR

  • 08:00 (CET)

  • 15:00 (CET)

  • 18:00 (CET)

Belgium NL

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

Brazil

  • 10:00 (CET)

  • 15:00 (CET)

  • 19:00 (CET)

  • 23:00 (CET)

Czech Rep.

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Denmark

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

Finland

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

France

  • 05:00 (CET) (+Cars)

  • 06:00 (CET)

  • 07:00 (CET)

  • 08:00 (CET)

  • 09:00 (CET)

  • 10:00 (CET) (+Cultural)

  • 11:00 (CET)

  • 12:00 (+Cars)

  • 15:00 (CET)

  • 16:00 (CET)

  • 17:00 (CET)

  • 18:00 (CET)

  • 19:00 (CET)

  • 20:00 (CET)

Germany

  • 06:00 (CET)

  • 08:00 (CET)

  • 10:00 (CET)

  • 12:00 (CET)

  • 14:00 (CET)

  • 16:00 (CET)

  • 18:00 (CET)

  • 20:00 (CET)

Greece

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Hungary

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Ireland

  • 05:30 (GMT)

  • 11:30 (GMT)

  • 15:30 (GMT)

  • 20:30 (GMT)

Italia

  • 00:10 (CET)

  • 08:10 (CET)

  • 12:10 (CET)

  • 16:10 (CET)

Netherlands

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

Norway

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

Poland

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Portugal

  • 00:10 (CET)

  • 08:10 (CET)

  • 12:10 (CET)

  • 16:10 (CET)

Romania

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Russia

  • 05:30 (CET)

  • 11:30 (CET)

  • 17:30 (CET)

  • 23:30 (CET)

Slovakia

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

Spain

  • 00:10 (CET)

  • 08:10 (CET)

  • 12:10 (CET)

  • 16:10 (CET)

Sweden

  • 07:30 (CET)

  • 11:30 (CET)

  • 15:30 (CET)

  • 23:30 (CET)

Switzerland

  • 00:00 (CET)

  • 08:00 (CET)

  • 12:00 (CET)

  • 15:00 (CET)

United Arab Emirates

  • 07:00 (UTC)

  • 11:00 (UTC)

  • 14:00 (UTC)

  • 23:00 (UTC)

United Kingdom

  • 06:30 (GMT)

  • 11:30 (GMT)

  • 15:30 (GMT)

  • 20:30 (GMT)