Availability in Google’s terms
Your stock statuses turn into in_stock, out_of_stock and preorder by themselves — Google does not reject products over availability.
Website and marketplaces department one of the departments in your AI company
Elbuz builds a Google Shopping feed for Google Merchant Center from your catalog and updates it at a fixed URL, with Meta, TikTok and ChatGPT feeds from the same catalog — prices and stock in every channel stay current.

A Google Shopping feed: the attributes are already in the template, your fields are mapped once.
Demo: this is how a catalog product becomes a Google Merchant feed — conversion and checks run on their own.
Elbuz · Catalogyour fields
| Product | Price | Stock |
|---|---|---|
| Autumn sofa | €679 | In stock |
| Breeze armchair | €199 | On order |
| Oak table | €289 | Sold out |
Run log: 1,248 products, no errors
google.xml“Google Merchant (XML)” template
| Attribute | Value |
|---|---|
g:title | Autumn 3-seater sofa, velour |
g:price | 749.00 EUR |
g:sale_price | 679.00 EUR |
g:availability | In stock |
g:description | <p><b>Sofa</b>, 3 seats, velour…</p> |
The Google feed builds and checks itself — no hand-made XML.

The feed updates with every export — Google sees the same prices and stock as your website.
Your stock statuses turn into in_stock, out_of_stock and preorder by themselves — Google does not reject products over availability.
The price comes from your catalog with your markup rules, and the sale price goes in its own attribute.
If the catalog suddenly “shrinks”, the stop rule keeps that feed away from Google.
Markup Google does not accept is stripped from descriptions, and they are trimmed to 5,000 characters.

Every other channel comes from the same catalog — see product feed management.
Separate formats on the same engine: one Meta catalog for Facebook and Instagram, and a TikTok catalog. Connecting the feed on the platform side — Meta catalog from a feed.
Amazon, eBay, Allegro, Kaufland, eMAG and other marketplaces get the same products from the same catalog. Details — marketplace integration.
A Ceneo XML feed for price comparison in Poland, plus CSV and XLSX price files for partners and services that take a file.
The ready “OpenAI (ChatGPT Ads)” template builds a product feed to OpenAI’s spec — price with currency, availability codes, clean description, main and extra photos — and sends it to the OpenAI SFTP server after every export.

The account in short — and what the feed does in it.
Google Merchant Center is the account through which your store’s products get into Google Shopping and product ads. It needs a feed — a file with your catalog that it fetches from a URL on a schedule. Elbuz builds and updates that file for you. For g:gtin Google expects the real manufacturer barcode — you can check its check digit with the free EAN-13 generator.
Setting up the account and the campaign — how to set up Google Shopping. If Google suspends the account — Google Merchant Center suspended: how to fix it.
Merchant Center in Elbuz. Add the Elbuz e-mail as a user in Merchant Center and enter your account ID — no Google Cloud key needed. Products Google disapproved show up with reasons in “Feed quality”, and 30 days of statistics (impressions, clicks, free-listing conversions) feed the “Google performance” custom label. Spend and ROAS are not included — that is Google Ads data. More in product feed management.
Feeds are part of one Elbuz plan, together with your whole AI company.
What it costs for your catalog — see pricing.
Real Elbuz windows on demo data.
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.
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.
14 days free
The website and marketplaces department joins your AI company along with every other department. €50 on your balance after sign-up and 14 days to build feeds from your own catalog.
Updated