Emberfeed is an XML feed editor for product catalogs.

A product feed is the XML file your store hands to an ad channel: one <item> per product, each carrying fields like g:title, g:price, and g:image_link. An XML feed editor sits between that file and the channel: it reads your feed, lets you change what each field says, and emits a corrected feed at a new URL.

That is the job in five steps. Import a feed, rewrite the fields, restructure to the shape the channel wants, fix the images, and serve the result. Emberfeed does all five, and the fourth one, the images, is the part generic feed editors skip.

Paste a feed URL and Emberfeed fetches and parses it. It reads RSS 2.0 with the g: namespace (the Google / Meta shape), Atom, and the <SHOP><SHOPITEM> structure the Czech price engines use. The source can be a platform export from Shopify, Shoptet, or any other system, or a feed you wrote by hand. Every g:* field is captured per product, so anything your source carries is available to edit and to drop into an image.

One honest constraint up front: Emberfeed imports an existing feed and enhances it. It does not generate a feed from nothing, it reads the feed your store already produces.

Field rules rewrite any field across the whole catalog without touching your store. Build composite titles like {{brand}} {{title}}, run find-and-replace to normalise a vocabulary, strip HTML from descriptions, or set custom labels conditionally, for example tag every product over 20% off as on_sale so you can group it in an ad set. Rules are evaluated server-side every time the feed is served, so corrections never go stale.

When a single SKU is wrong, a per-product override fixes that one product without writing a rule for the whole feed. And a filter tree decides which products stay in the served feed at all, drop the out-of-stock items, keep only a price band, whatever the channel needs.

Different channels expect different XML. Emberfeed can pass your source structure straight through, or rebuild the feed from scratch into the output schema a channel requires:

• Meta and Google take the RSS shape with the g: namespace, the default for catalog ads and Google Shopping.
• TikTok catalog ads (a catalog in TikTok Ads Manager, not TikTok Shop) take a similar set of fields, and Emberfeed gives TikTok feeds image URLs ending in .jpg or .png, as TikTok requires. TikTok support is in beta.
• Heureka, Zbozi.cz, and Glami take the Czech SHOP / SHOPITEM structure, a completely different root and item element, built for you from the same source feed.

One source feed can drive several channels: duplicate the feed, point the copy at a different platform, and it gets its own rules, its own schema, and its own served URL. See the Google Shopping and Heureka pages for channel-specific detail.

This is the part generic feed editors do not do. Instead of shipping the raw photo from your product page, you design one image templateonce: in the drag-and-drop editor, as HTML and CSS with full Handlebars, or with AI you bring yourself. The editor composes a brief with your feed's real fields to paste into Claude or ChatGPT, or Claude builds the template directly over Emberfeed's MCP connector. Emberfeed then rewrites the image_link of every product to point at its renderer.

Each image is composited on-demand from that specific product's data and its real product photo: price overlays that update when prices change, conditional badges like Sale or New, a consistent brand frame, your logo, AI-cut backgrounds for fashion and jewelry, all without redesigning a single image by hand. The channel sees a normal image URL and does not care it was rendered server-side.

Before you ship, Emberfeed validates every product against the target platform's field rules, required fields present, title length within the channel's cap, price and availability in the channel's format, GTIN check digit for Google, and flags what would get rejected. It also measures product photos, while rendering them and in the background after each refresh, and flags the ones too small for Google, Meta, Heureka, Zboží.cz or Glami. Validating your feed before submission is the difference between a clean catalog and a wall of disapprovals.

What you hand the channel is a single new feed URL. Meta, Google, or a Czech engine pulls it on its own schedule (TikTok support is in beta) and sees your edited fields, your chosen schema, and your rendered images. A version stamp on every image URL means that when a product or a template changes, the channel fetches fresh pixels on its next crawl.

• →It enhances an existing feed. Emberfeed reads the feed your store already produces and improves it. It does not build a catalog from a database or a spreadsheet.
• →It is hosted, not self-hosted. You sign up and work in the browser. There is nothing to deploy and nothing to run on your own server.
• →It is not a store plugin. Emberfeed is not a Shopify or WooCommerce app. It reads your feed URL, so it works the same regardless of what built the feed.
• →It edits data and images together. The field rules and the image renderer live in one tool against one feed, which is the whole point.

A Mergado setup with its Feed Image Editor app starts at about 2,272 CZK a month (the 286 CZK entry tariff plus 1,986 CZK for the app, excl. VAT) and grows with catalogue size. The tools that render catalog creative, Marpipe, Cropink, Confect, start at $39 (Cropink, up to 100 products) and climb to $999+ for the enterprise tiers.

Emberfeed is one signup, one editor, one served URL per feed, priced for small e-shops and one-off campaign tests: €25 per feed per month, with the first 3 months free up to 1,000 products.