Feed Management with Channable: Product Data for Meta, Google and Marketplaces

The product feed is the least glamorous construction site in ecommerce marketing and at the same time the one that feeds most directly into delivery. Advantage+ Shopping, dynamic retargeting and catalogue ads draw exclusively on the data in your catalogue. A missing mandatory field means the item is rejected. A poor title means lower relevance. A product marked “out of stock” while it is actually available burns budget on a dead ad.

As long as you feed one channel, your shop’s export handles that – how to do it on Shopify and Shopware is covered in the Meta setup guide. This guide starts where that route ends: when one feed becomes several, with differing requirements, and maintenance turns into a craft of its own.

When the native export is enough – and when it isn’t

The line is not drawn at an item count but at four characteristics. The more of them apply, the more expensive it gets to stay on the native export:

• Multiple output channels. Meta, Google Shopping, Pinterest, marketplaces – each with its own set of mandatory fields and its own category taxonomy.
• Multiple countries or languages. Different currency, different shipping rules, different titles, often a different assortment.
• Variants. Sizes and colours have to be grouped cleanly, or the same items compete against each other or disappear.
• Channel-specific logic. The title that works on Google is often the wrong one for Meta; discontinued items should drop out of one channel and stay in another.

On the native export, each of these means its own template and therefore its own maintenance point. Change the category logic and you change it in five places – and forget the sixth. A feed management tool inverts that: one normalised data base, from which a separate output is derived per channel.

What a feed management tool actually does

The core is always the same, whatever the vendor: a rule layer between shop and channel.

1. Import. Product data arrives from the shop, via API or feed – including variants and additional fields.
2. Normalise. Tidy up once: map categories, unify fields, spot gaps.
3. Apply rules. If-then logic at field level, different per channel: rebuild titles, round prices, exclude items without an image, translate categories into the channel’s taxonomy.
4. Check. Against the target channel’s requirements, before the channel rejects anything.
5. Publish and refresh. One feed per channel, updated automatically.

The decisive difference from the shop export lies in steps 3 and 4. Any shop can export. What it cannot do is refine per channel and check in advance.

Channable at a glance

Channable is a Dutch tool out of Utrecht and covers four areas that can be bought separately:

Module	What it does
Feed management	Import, rules, channel-specific output
Marketplaces	Listing plus order and stock sync via API
Campaigns	Generate feed-based ads automatically
Insights	Reporting at product and channel level

By its own account Channable supports over 2,500 channels – marketplaces, price comparison sites and ad platforms. Read that figure as market coverage, not feature depth: the major channels have well-maintained templates, the long tail has more generic connections.

More relevant in practice than the channel count are two building blocks. Master rules apply across projects – define title or price logic once instead of repeating it per channel. And order sync for marketplaces: orders flow back into the shop via API instead of getting stranded in a second backend. That is precisely where marketplace projects fail when they only solve the feed.

What Channable does for Meta specifically

For Meta, Channable hooks into Commerce Manager and fills the product catalogue that feeds Advantage+ Shopping and catalogue ads:

• Populate and maintain the catalogue – prices and stock follow automatically, instead of one file a day.
• Quality checks against Meta’s requirements – missing mandatory fields surface in the tool, not later as a rejection in Commerce Manager.
• Vertical templates for ecommerce, auto, real estate and travel, which have differing field requirements.
• Rule-based adjustment per catalogue, for example excluding items below a margin or shortening titles for catalogue ads.

One thing you should not expect from it: that the content ID question resolves itself. The feed is only one half. Whether dynamic retargeting works is decided by the match between the id in the feed and the content ID your Pixel sends. Channable makes the feed side controllable – the Pixel side remains a matter of your shop setup. The mechanics are covered in the Meta setup guide and in the article on catalogue setup for dynamic product ads.

Connecting Shopify and Shopware

For Shopify, Channable reads in the catalogue, variants and selected metafields. Those metafields are the part that is easy to overlook during setup: whatever does not come across cannot be used by any rule later. Check early that the fields your logic is meant to build on are actually in the import.

For Shopware there are two entries in the store – a connector and an integration. Which of them is right for your version and hosting differs; settle that before setting anything up. In Shopware Cloud the restriction from the Meta setup guide applies on top: only cloud-capable apps can be installed, no custom PHP code.

Going via the native product comparison export stays possible in both cases – Channable can read an existing feed as a source. The direct connection is cleaner, because you then get variants and additional fields in a structured form rather than only what the export template happens to provide.

Pricing and how the package is determined

The pricing logic has two parts, which is why it looks confusing at first glance:

1. A package based on item count, projects and channels.
2. A Core plan – Standard, Plus or Pro – which determines the feature set.
3. Plus optional add-on modules, for instance for marketplaces.

Entry level sits at around €59 per month, with quotes on request for enterprise needs; a free test account with a limited feature set exists. As of July 2026 – prices and package limits change, verify before signing.

What to watch in your calculation: the item count includes variants. An assortment of 2,000 products in five sizes each comes to 10,000 items, not 2,000. That calculation decides your package tier and is regularly underestimated.

Limits of Channable

A guide that only lists strengths is an advert. The recurring criticisms you should know before deciding:

• No readable feed preview. The output can essentially be inspected as XML, not as a table. Anyone wanting to see the effect of a rule works around it with test rules – which costs time.
• Gets confusing with many rules. Separating import, mapping and output is cleanly conceived, but navigating between the layers becomes tedious once custom variables and many rules are in play.
• Performance on large, variant-heavy assortments. Very large catalogues combined with long descriptions and complex rule sets run into structural limits.
• Lag on campaign features. The feed part is the strong part. On newer advertising features from the channels, Channable is not always at the front – anyone expecting campaign management should check the module scope closely against the actual need.

None of this disqualifies the tool. But it explains why very large or heavily regulated assortments often end up one tier above.

Alternatives and what they fit better

Tool	Model	Fits when
Channable	Self-service	European channels and marketplaces, team maintains it
DataFeedWatch	Self-service	Multiple clients, agency operation
Productsup	Self-service, enterprise	Data governance, many international markets
Feedonomics	Managed service	Very large catalogues, no in-house team for it
Lengow	Self-service	European marketplace focus

The decisive distinction is not feature scope but who operates the tool. Productsup gives you more control and requires people to exercise it. Feedonomics inverts that: there, a team runs the feed for you, which helps when nobody internally has the capacity – and which increases dependency.

The tiers at a glance

For orientation, because feed setups almost always develop in this order:

Tier	Setup	Limit
1	Native shop export	One channel, one market
2	Feed management tool	Multiple channels, central rule set
3	Enterprise or managed	Governance, many markets, very large catalogues

The jump from tier 1 to 2 usually delivers the biggest effect, because it consolidates the maintenance points and surfaces rejections earlier. The jump to tier 3 is an organisational question more than a technical one: it pays off when data quality has to become a process with owners rather than a task somebody handles on the side.

Checklist

• Output channels, markets and languages listed – the tier follows from that
• Item count calculated including variants, not just products
• Direct shop connection evaluated instead of reusing an existing export
• On Shopify: the metafields you need are actually in the import
• On Shopware: the right store entry for your version and hosting is settled
• Feed id and Pixel content ID point at the same identifier
• item_group_id set, variants grouped correctly
• Quality checks active, rejections in Commerce Manager reviewed
• Refresh interval matches how fast your stock moves
• For marketplaces: order sync back into the shop is in place

If you want to know whether your feed is costing you reach today: that is exactly what we look at in the free account check – including catalogue diagnostics. How we turn product data into a systematic performance lever is on our page about feed hacking; the tracking side of the topic is covered in the Meta setup guide.