Product feeds for Google Shopping, Meta, TikTok and ChatGPT

A product feed (product data feed) is a file with your catalog in the format a channel understands: for Google it is XML with attributes such as g:id, g:price and g:availability. Merchant Center fetches it from a fixed URL and shows your products in Google Shopping and ads. Elbuz builds the feed from the same catalog your supplier price lists flow into, so prices and stock in it stay fresh.

It is keeping feeds for every channel correct and up to date: mapping your fields to each channel’s attributes, fixing values the channel rejects and rebuilding the files on a schedule. In Elbuz every feed is a template over one catalog, so a change in the catalog reaches Google, Meta, TikTok and ChatGPT at the next export.

In Elbuz pick the “Google Merchant (XML)” template, map your fields to the Google attributes once and put the export on a schedule. Then add the feed URL in Merchant Center as a scheduled fetch — Google picks up the fresh file by itself.

The core set is g:id, g:title, g:description, g:link, g:image_link, g:availability, g:price, g:brand and g:condition, and for most categories also a barcode (g:gtin) or the manufacturer part number (g:mpn). In Elbuz these attributes are already filled with your fields, and availability turns into in_stock, out_of_stock or preorder by itself.

As often as you set in the export schedule: Elbuz rebuilds the file at the same fixed URL, and Merchant Center fetches it on its own schedule. If supplier price lists are scheduled too, new prices and stock reach Google without you.

Most often because of a missing barcode and part number, relative links to photos or pages, disabled photos or a wrong availability value. Before every run Elbuz shows how many products have no price, photo or barcode, and the stop rule keeps a feed away from Google if availability suddenly disappeared.

Start with the data: full titles with brand and model, a real GTIN, clean descriptions without markup, correct availability and working image links. In Elbuz descriptions are cleaned automatically, products without a barcode or photo are listed before export, and AI can fill missing descriptions and specs in the catalog.

Yes. The Meta catalog — for Facebook and Instagram — and the TikTok catalog are built by their own templates on the same engine as the Google feed, from the same catalog.

With a product feed in OpenAI’s format. Elbuz has a ready “OpenAI (ChatGPT Ads)” template: every column is named and filled the way OpenAI requires, and after each export the file is sent to the OpenAI server by itself. The connection details are issued by OpenAI once product feed access is enabled in your ad account.

For most categories — yes: Google asks for at least one of two, the g:gtin barcode or the g:mpn part number, otherwise some products show worse or are rejected. Google expects the real manufacturer barcode, so use the code from the packaging or the supplier price list, not a made-up one. You can check the check digit in the EAN-13 barcode generator.

Yes, a Merchant Center account is free, and products can appear in free listings. Shopping ads are paid separately in Google Ads, per click. The feed in Elbuz is part of your plan, with no separate fee.

A feed is a file the channel fetches on a schedule; an API is a connection through which data is sent on request, product by product. Google, Meta and TikTok catalogs work well from a feed; marketplaces with orders and stock usually connect through an API. Elbuz does both from the same catalog.

Feeds are not sold separately: they are part of the Elbuz plan together with the catalog and supplier price lists. Plans start at €87 a month, and the first 14 days are free. See pricing.