Meta Ads

Catalogue

Also called Product catalogue, Meta catalogue

The structured product list you upload to Meta so ads can be built from your stock automatically.

Quick facts: Catalogue

Category
Meta Ads
Also called
Product catalogue, Meta catalogue
Level
Intermediate
Affects
Dynamic ads, Shops, retargeting quality, ad approvals
Where to see it
Meta Commerce Manager, your shop platform's feed export, Meta Events Manager
In this article4
  1. How a catalogue works
  2. Why the catalogue matters
  3. Where catalogues go wrong
  4. How to act on it

How a catalogue works

A catalogue is a structured list of everything you sell, held in Commerce Manager. Each row carries the fields Meta needs to build an advert without a designer: an identifier, a title, a description, a price, a stock status, a link to the product page and a link to the image. From that list the system assembles ads on demand, pulling in whichever items suit the person being shown them.

You can keep it up to date in several ways. A scheduled feed file that your shop generates and Meta fetches on a timetable is the common route for a small catalogue. Larger shops connect their platform directly, so changes flow through as they happen. Either way the catalogue is only as fresh as its last update, which is why a shop that changes prices daily needs a faster schedule than one that changes them at the start of a season.

The pixel then has to speak the same language. When someone views a product, the event sent from your site must carry an identifier that exists in the catalogue, or Meta cannot connect the browsing to the item.

Why the catalogue matters

Without one you are limited to hand-built ads, which means you advertise the handful of products someone had time to design creative for. With one, every item in stock is advertisable, and the system can show a returning visitor the exact thing they looked at instead of a generic banner. This is the machinery behind catalogue and dynamic product ads.

It also feeds Shops and tagged posts on Instagram, so one well-maintained list serves several surfaces at once. Fixing a wrong price in the catalogue fixes it everywhere it appears.

Where catalogues go wrong

Stale data is the expensive one. Advertising an item that sold out, or a price that changed last week, costs you the click and annoys the buyer. Meta will eventually reject or under-serve items it finds unreliable, so the damage outlasts the mistake.

Thin data is the quiet one. Titles like a bare model number, missing brand fields, no description, or a single small image give the system nothing to match against and nothing to show. Currency and availability fields set wrongly cause rejections that are easy to miss until someone opens the diagnostics tab. And a catalogue that duplicates the same product under several identifiers splits its own performance data across rows that should have been one.

How to act on it

Get the source right before you get clever. Export what your shop produces, read a few rows as a customer would, and fix the titles, images and descriptions there rather than patching them inside Meta, so the improvement carries to every channel that reads the same product feed.

Set the update schedule to match how often your prices and stock actually change, then check the diagnostics view regularly — not once at setup — because rejections accumulate silently. Confirm that the identifiers on your website events match the identifiers in the catalogue exactly, including case and any prefix your platform adds. Once that is stable, group items into sets so you can advertise categories separately instead of treating the whole shop as one lump.

Do and do not

Do

  • Fix titles and images at the source, not inside Meta
  • Match the update schedule to how fast stock changes
  • Check the diagnostics view for rejected items regularly

Do not

  • Advertise from a catalogue you have not refreshed
  • List the same product under several identifiers
  • Leave availability or currency fields guessed

Questions people ask about this

Do I need a catalogue if I only sell a few products?

Not necessarily. If you sell a small, stable range you can advertise each item with hand-built creative and keep control of the design. A catalogue earns its keep when the range is large, changes often, or when you want to show returning visitors the exact product they viewed. Below that, the setup effort may outweigh the benefit.

How often should the catalogue update?

Match the schedule to how fast your stock and prices move. A shop that reprices daily or sells out of lines quickly needs frequent updates or a direct connection to its platform. A catalogue of stable, always-available items can refresh far less often. The test is simple: nobody should ever click an ad and find the item gone or the price different.

Can the same catalogue be used for Google Shopping?

Not the same file directly, because Google and Meta expect different field names and rules. The underlying product data can and should come from one source in your shop, then be formatted for each platform. Keeping one master source means a corrected title or image is fixed everywhere rather than in one place and forgotten in another.

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.