What the Meta catalog is for
A catalog in Commerce Manager is the product data source for Advantage+ catalog ads and for shops on Facebook and Instagram. Meta does not query your commerce platform live: it fetches a data file from a URL you give it, on a schedule set on Meta’s side. Endora Commerce’s job therefore ends at making sure a current, valid file is always sitting at that URL.
For a distributor or manufacturer this mostly makes sense where part of the offer is public: a B2C channel, sales to small businesses and workshops, or remarketing to people who browsed the catalog without logging in.
What goes into the file
The Meta catalog template is one of two ready-to-use feed templates, alongside Google Merchant Center. It produces XML at variant level, with a field list that is complete for Meta’s required set. According to Meta’s catalog documentation, that set is: id, title, description, availability, condition, price, link, image_link and brand.
A feed is created from four choices: template, sales channel, language and name. The channel determines the assortment, prices and storefront links, and the language determines which translation of names, descriptions and category paths is written to the file. If the default field layout does not fit, you can duplicate the system template and edit the copy, with a preview of the values for a sample product.
B2B prices and a public catalog
Meta shows one price per product, so which price that is has to be a deliberate choice. The feed is priced net or gross, from a named price list or from the channel’s anonymous price resolution. The post on price lists and the pricing engine explains where prices come from.
The assortment is narrowed with the same rule builder used for promotions, and the match count is calculated on the same prices that end up in the file. A rule can only narrow the feed. A product that is inactive, archived, outside the channel or not visible to an anonymous visitor never reaches the file. That includes items that are public but reserved for named organizations: an ad leading to a page nobody outside those companies can open would only reveal the existence of an offer promised to someone exclusively.
Meta categories without a connection to Meta
Meta has its own product taxonomy. It ships with the platform (2,967 categories, in Polish and English), so generating the file requires no connection to Meta’s servers. You map a shop category to a Meta node and all its subcategories inherit that mapping unless they have one of their own.
A missing mapping does not block an item: the field is omitted, the product is still written to the file, and the run records a warning. Checking for newer taxonomy versions is off by default. Once enabled, a new list installs inactive and only takes effect when an operator approves it after reviewing the impact preview.
Connecting it in Commerce Manager
- In the Endora Commerce admin, create a feed from the Meta catalog template and run the first generation. The URL only appears after the first successful run.
- In the feed settings, pick a schedule: a preset (for example hourly or daily) or a custom cron expression with a time zone.
- On Meta’s side you need a catalog in Commerce Manager. Add a data feed to it as a data source with a scheduled upload and paste the feed URL.
The URL contains a random token and anyone who knows it can read the file with your prices, so it should be treated as a credential. It can be rotated or revoked with immediate effect. After a rotation Meta stops receiving updates until you paste the new URL into the data source.
When something is missing from the catalog
Every run records how many items were considered, emitted and skipped, with the reason and SKU for each one and a CSV export. The most common reasons in B2B catalogs:
- no price in the feed’s currency and price list,
- no image, or an image that is not publicly accessible,
- a field Meta requires that resolved empty with no fallback value,
- no tax rate for the country in a gross feed.
If more than half of the items are skipped, the run fails and the previous file stays at the URL unchanged, so Meta never receives a catalog cut in half. A failed generation notifies the administrator once, on the transition into failure, not on every attempt.
Meta catalog or Google Merchant Center
This is not an either-or choice. Both templates run on the same generator, so both feeds draw on the same catalog, the same price lists and the same rule builder, instead of two separate exports that drift apart over time. Google answers an active product search, Meta reaches audiences on social platforms. If the entire offer is available only after login, neither of them will have anything to publish.
The catalog itself measures nothing. Storefront events are sent by the separate Meta Ads integration, a Pixel configured separately for each sales channel.