Koopkeus Integration

A price-comparison listing puts your products in front of shoppers who are actively comparing prices and are close to a purchase decision -- typically a higher-intent audience than general display or social traffic. Because the model is cost-per-click, you only pay when a shopper actually visits your store, which makes it easier to test the channel without committing to a fixed media budget up front.

Since Koopkeus listings are now served through the wider Kelkoo Group network, a correctly structured feed can also make your catalog eligible for that broader comparison-shopping footprint, rather than a single standalone Dutch site.

Kelkoo Group's published merchant feed specification (the specification now behind the former Koopkeus listings) accepts product data in two structural forms:

1. A delimited text file (any consistent field separator), with a header row listing the attribute names and every product row containing the same number of fields -- if a value is empty, the separator must still be present.
2. An XML file, with tag names matching Kelkoo's product-data specification. CDATA sections are recommended for text fields (titles, descriptions) that may contain special characters, and the XML should validate cleanly (e.g. via the W3C Markup Validation Service).

Documented formatting rules that apply to both formats:

1. Numeric values (price, delivery cost) must contain digits and a dot as the decimal separator -- not a comma.
2. Dates must be formatted as YYYY-MM-DD.
3. HTML markup is not allowed inside feed values.

Feeds can be submitted by hosting the file on your own server for Kelkoo to fetch over HTTP/HTTPS, hosting it on your own FTP server for retrieval, or uploading it directly to an FTP location provided by Kelkoo.

The exact field list is confirmed against your merchant account setup, but these attribute names appear consistently across Kelkoo Group's merchant feed documentation and third-party Koopkeus/Kelkoo feed integrations. Fields marked "Required" are explicitly documented as mandatory -- products missing them are not displayed.

Since Koopkeus listings run on Kelkoo Group's merchant infrastructure, connecting through Feedance follows the same pattern as any Kelkoo/Koopkeus merchant setup:

1. Register (or confirm) your merchant account with Kelkoo Group / Kelkoo Shopping Netherlands and set your CPC budget.
2. In Feedance, map your product catalog to the field names above (id, title, product-url, price, brand, and the recommended attributes), choosing either the delimited-text or XML output.
3. Apply the formatting rules -- dot decimals, YYYY-MM-DD dates, no HTML in text fields -- so the feed passes validation on the first submission.
4. Publish the generated feed at a stable Feedance-hosted URL (or via FTP) and share that location with Kelkoo Group so it can be added to the regular fetch schedule.
5. Monitor the feed status in your merchant account to confirm products are being picked up without rejections.

Kelkoo Group fetches merchant feeds on a recurring schedule that varies by country -- documented examples range from a handful of fetches per day in most markets up to many more in high-traffic markets. The exact cadence specifically published for the Netherlands feed isn't publicly listed, so as general practice: refresh your feed at least once a day, and more often if your prices, stock levels, or promotions change frequently, since price and availability accuracy is what this channel is judged on by shoppers.

No official Koopkeus/Kelkoo error-message list is published, but these rejection causes follow directly from Kelkoo Group's documented formatting rules and are worth checking before submission:

1. Missing a mandatory field (id, title, product-url, price, or brand) -- the affected product is not displayed.
2. Prices or delivery costs formatted with a comma decimal separator instead of a dot.
3. HTML tags left inside title or description values.
4. Inconsistent field counts row-to-row in a delimited text file (a missing separator on an empty value shifts every subsequent column).
5. XML tag names that don't match Kelkoo's product-data specification, or malformed XML that fails validation.

These are general feed-management practices, not Koopkeus-specific claims:

1. Keep titles specific (brand, model, key attribute) so listings match what shoppers are actually comparing.
2. Fill in ean/mpn where you have them -- accurate identifiers reduce mismatched or duplicate listings on comparison sites generally.
3. Map your merchant-category to a specific leaf category rather than a broad top-level one, since comparison engines use this for browse and filtering.
4. Keep availability and price in sync with your actual store in near real time -- comparison-shopping traffic converts on the promise that the listed price and stock are current.

Is Koopkeus still a separate site? No. koopkeus.nl now redirects to kelkoo.nl, and the Dutch site is run by Kelkoo Shopping Netherlands B.V. "Koopkeus" survives as a legacy/former brand name rather than an independently run platform.

What format does the feed need to be in? A delimited text file with a header row, or an XML file using Kelkoo Group's field names -- see the format section above.

How is advertising priced? Cost-per-click (CPC): you pay only when a shopper clicks through to your store.

Which fields are mandatory? id, title, product-url, price, and brand are explicitly documented as required; other fields such as description, images, EAN and delivery details are recommended but not always mandatory.

How often is the feed refreshed? Kelkoo Group fetches feeds on a recurring schedule that varies by country; refresh at least daily as a baseline.