DEV Community: VHdev

How to Create a Magento 2 idealo Product Feed Using a Standard Product Export

VHdev — Tue, 24 Feb 2026 07:37:57 +0000

Idealo is one of the largest price comparison platforms in Europe.

To list products there, merchants must provide a properly structured product feed.

Magento 2 does not include a built-in idealo export. However, most stores already have the data required — it simply needs to be structured correctly.

In many cases, the issue is not missing product data, but mismatched formatting and feed structure.

What is an idealo product feed?

An idealo product feed is typically a CSV file that contains structured product information such as:

product ID (SKU)
product title and description
price
availability
product URL
image URL
brand
EAN/GTIN
category path

Idealo validates feeds strictly. Even small structural inconsistencies can result in products being rejected.

Why Magento 2 exports don’t match idealo requirements by default

Magento 2 allows you to export products via:

Admin → System → Export → Products

This export includes most necessary attributes:

sku
name
description
price
special_price
manufacturer
image
url_key
stock status

However, the default Magento export:

does not use idealo’s expected field names
may not include properly formatted availability values
does not generate a category path string
may require value normalization

So while the product data exists, the format does not match idealo’s specification.

Reusing Magento’s product export instead of building a custom module

Instead of installing a dedicated Magento idealo extension or building a custom module, you can reuse Magento’s built-in CSV export.

The process usually involves:

Exporting products from Magento 2 as CSV
Reviewing idealo’s required attributes
Mapping Magento attributes to idealo field names
Normalizing values (price format, availability text)
Generating an idealo-compatible CSV

This approach keeps product data centralized inside Magento while adapting the structure externally.

Typical Magento 2 → idealo workflow

A practical workflow looks like this:

Export product data from Magento 2.
Identify required idealo attributes.
Map Magento fields to idealo structure.
Generate an idealo-formatted CSV file.
Upload the feed to idealo Merchant Portal.

This method avoids additional Magento extensions and keeps your store environment clean.

When a feed converter is useful

A conversion-based workflow is especially useful when:

You want to avoid installing additional Magento modules
You manage multiple channels (Google, Meta, idealo)
You prefer using Magento’s built-in export
You need flexibility in feed formatting

Instead of maintaining separate integrations inside Magento, you adapt one export to multiple destinations.

Practical example

If you already have a Magento 2 CSV product export, you can convert it into an idealo-compatible format without modifying your store.

A platform-agnostic product feed converter can map Magento’s CSV structure to idealo’s required format and generate a ready-to-upload CSV file.

You can see the workflow here:

👉 product feed converter

The idea is not to generate product data, but to transform an existing export into the correct feed structure.

Final thoughts

Creating a Magento 2 idealo product feed does not necessarily require a custom extension.

In many cases:

Magento already contains the needed data
The challenge is structural formatting
A mapping and conversion workflow is sufficient

Reusing Magento’s standard export keeps the setup simple, flexible, and easier to maintain long term.

How to Create an idealo Product Feed Using an Existing XML Export

VHdev — Thu, 05 Feb 2026 06:53:20 +0000

Idealo is one of the major price comparison platforms in Europe, and listing products there requires a properly structured product feed.

Many merchants already have product data exported from their store as an XML feed, but still run into issues when submitting that feed to idealo.

In most cases, the problem is not missing data, but mismatched structure and formatting.

What is an idealo product feed?

An idealo product feed is a structured csv file that contains product information such as:

product ID
title and description
price and availability
product URL
image URL
brand and category

idealo validates feeds strictly, and even small structural issues can cause products to be rejected or skipped.

Why existing XML feeds often don’t work out of the box

Many merchants already have an XML feed generated for other platforms, for example:

Google Shopping XML feeds
generic XML exports from ecommerce platforms
custom XML feeds from internal systems

While these feeds usually contain the correct product data, idealo expects a specific structure and naming for required attributes.

Common problems include:

missing mandatory idealo attributes
incorrect availability or price formats
fields that exist but are named or structured differently
feeds designed for another platform’s specification

As a result, an XML feed that works perfectly elsewhere may fail during idealo validation.

Reusing an existing XML feed instead of rebuilding it

In most cases, rebuilding a product feed from scratch is unnecessary.

If you already have an XML export, you can reuse it by adapting the feed structure to match idealo’s requirements.

This approach focuses on:

mapping existing XML fields to idealo attributes
normalizing values such as price and availability
generating an idealo-compatible csv output feed

It allows you to keep product data in one place while adapting it for idealo.

A typical idealo feed preparation workflow

A practical workflow usually looks like this:

Export an existing XML product feed from your system.
Review idealo’s required attributes and formats.
Map your existing XML fields to idealo fields.
Generate an idealo-compatible csv feed.
Upload the feed to idealo and monitor validation results.

This process reduces duplication and makes long-term maintenance easier.

When a feed converter makes sense

Using a feed converter is especially useful when:

your ecommerce platform does not offer a native idealo export
the native export does not match idealo’s structure
you manage multiple platforms with different feed requirements
feed specifications change over time

Instead of maintaining separate XML feeds for each destination, you adapt one source feed to multiple outputs.

An example approach

I documented this approach using a small, platform-agnostic product feed converter that adapts existing XML feeds into idealo-compatible formats.

It focuses on feed structure and field mapping rather than generating product data.

If you’re interested in the technical approach, you can find it here:
product feed converter

Final thoughts

Creating an idealo product feed doesn’t have to mean rebuilding your product data from scratch.

When an XML feed already exists, adapting its structure is often the most maintainable and scalable solution.

How to reuse an existing product feed for Meta catalogs (without rebuilding everything)

VHdev — Mon, 02 Feb 2026 07:23:56 +0000

When working with eCommerce platforms, product feeds often become a hidden source of complexity.

Most stores already have a product feed — for Google Shopping, marketplaces, or internal integrations.

However, when trying to reuse the same feed for Meta (Facebook & Instagram) catalogs, things often break.

Even if the product data itself is correct, platforms expect different:

field structures
required attributes
formats
validation rules

This usually leads to one of two outcomes:

maintaining separate feeds per platform
manually adjusting feeds whenever requirements change

Neither scales particularly well.

Why existing feeds often fail for Meta

Meta catalogs are strict about structure and required fields.

Feeds built for other platforms (for example, Google Shopping) often contain the right data, but not in the exact format Meta expects.

Common issues include:

missing or mismatched availability values
incorrect price formatting
unsupported or misplaced attributes
category and brand mapping problems

The result is frequent feed rejections or partially imported catalogs.

A more practical approach: adapt instead of rebuild

In many cases, rebuilding a feed from scratch isn’t necessary.

If you already have:

a Google Shopping XML feed
a generic XML export

you can reuse that data by adapting the feed structure instead of recreating everything.

The key is mapping existing fields to platform-specific requirements and generating a compatible output format.

How this typically works in practice

Start with an existing product feed (XML).
Normalize the product data (IDs, prices, availability).
Map feed fields to Meta catalog attributes.
Generate a Meta-compatible output feed.
Upload the resulting feed to Meta Commerce Manager.

This approach keeps product data in one place and reduces long-term maintenance effort.

When this approach makes sense

Adapting existing feeds is especially useful when:

your platform doesn’t offer a native Meta export
native exports are too limited
you manage multiple sales or marketing channels
feed requirements change frequently

It allows you to stay flexible without locking yourself into a specific platform or plugin.

Example: using a feed converter

I documented this approach using a small, platform-agnostic feed converter that adapts existing product feeds into Meta-compatible formats.

It works with existing XML feeds and focuses on structure and field mapping rather than data generation.

If you’re interested, you can see the approach here:
product feed converter

Final thoughts

Product feeds don’t need to be rebuilt every time you add a new channel.

In many cases, adapting existing data is simpler, more maintainable, and easier to scale — especially when working across multiple platforms.