Ecommerce

Product Feed

Also called Data feed, product catalogue

A structured file of product data — title, price, image, availability — sent to advertising and shopping platforms.

Quick facts: Product Feed

Category
Ecommerce
Also called
Data feed, product catalogue
Level
Intermediate
Affects
Shopping visibility, ad approval, catalogue accuracy
Where to see it
Google Merchant Center, Meta Commerce Manager, your shop's feed export
In this article4
  1. How a product feed works
  2. Why the product feed matters
  3. Where product feeds go wrong
  4. How to act on it

How a product feed works

A feed is a structured list of what you sell, one row per sellable item, using column names the receiving platform expects: an item id, title, description, link, image, price, availability, brand, condition and, where the manufacturer issues one, a barcode. It reaches the platform as a file fetched on a schedule, an upload, or a direct connection from your shop software.

The platform then treats those fields as the advertisement. In shopping results and in catalogue advertising there is no separate headline to write — the title, image and price a shopper sees come straight out of the feed, and the words in the title are also part of how the platform decides which searches the item may appear for. The feed is the inventory and the creative at the same time, which is what makes it worth more attention than a technical export usually gets.

Why the product feed matters

Everything downstream reads from it. Google Merchant Center, shopping campaigns, Performance Max, the Meta catalogue and dynamic product ads all draw on the same underlying data, so a mistake made once is repeated everywhere it is used. A missing size in the title, a price that disagrees with the landing page or stale availability will hold back items that would otherwise have sold themselves.

It is also the cheapest lever in a shopping account. Rewriting titles so they read the way people actually search — product type, brand, model, the attribute that matters in that category — changes which auctions the item is eligible for at all, and costs nothing but the effort of doing it.

Where product feeds go wrong

Disapprovals almost always come from disagreement between the feed and the page. The price or the currency does not match. The item says in stock while the page says sold out. The destination link redirects somewhere else. Image rules catch people out too: promotional text or a logo laid over the picture is not accepted, and a placeholder image counts as no image at all.

The slower failure is drift. A feed is set up carefully once, then stock patterns change, products are retired, categories are renamed, a plugin updates, and nobody opens the diagnostics again until the account has quietly stopped serving the items that used to earn the revenue.

How to act on it

Refresh often enough that price and stock are never far behind the site, and read the diagnostics on a routine rather than only when something breaks. Where a field is weak, fix it at source in the shop instead of patching it with a feed rule, so every platform receives the same corrected data and the next export does not undo your work.

Fill in the optional attributes as well: barcodes, colour, size, material, condition and product category. They are how a platform matches your item to a query and to competing listings, and items submitted without them are competing on less information than their rivals. Kept up on a schedule rather than in a panic, this maintenance is the bulk of what Merchant Center feed management actually consists of.

Do and do not

Do

  • Keep price and stock in step with the page
  • Write titles the way shoppers actually search
  • Read feed diagnostics on a routine, not on failure

Do not

  • Overlay promotional text or logos on product images
  • Patch bad data in rules instead of the source
  • Leave optional attributes blank because they are optional

Questions people ask about this

How often should a product feed update?

Often enough that price and availability on the platform never contradict the page a shopper lands on, since that mismatch is the most common reason items get disapproved. A daily refresh suits most catalogues. Shops with fast-moving stock, frequent price changes or flash promotions need something closer to real time, usually through a direct connection rather than a scheduled file.

Do I need a barcode for every product?

You need one for products a manufacturer has assigned a barcode to, because it is how the platform recognises the same item across sellers. Handmade goods, own-brand items, custom pieces and antiques do not have one, and every major platform provides a way to declare that the identifier does not exist rather than leaving the field blank.

Can one feed serve both Google and Meta?

The source data can and should be the same, but the exports usually differ. Field names, required attributes and category taxonomies are not identical between platforms, so it is safer to keep one clean product record in your shop and generate a separate file for each destination. That way a correction made once reaches both.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.