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.
