Skip to content

Meta Commerce Manager

Also called: Commerce Manager · Facebook Commerce Manager · Meta catalogue manager

Definition
Meta's tool for building and maintaining product catalogues (items, feeds, product sets, policy review) that a WhatsApp Business Account can connect to.

Exhibit A

Follow a product from feed to chat

8 / 8
Business portfolioowns catalogue and WABA
Item sourcesmanual · feed · platform · API
Commerce Manager catalogueitems keyed by Content ID
Policy reviewrejected items hidden
WhatsApp Business Accountone catalogue per WABA
Phone number settingsis_catalog_visible · is_cart_enabled
Catalogue in chatcatalog and product messages
Order webhookproduct_retailer_id, quantity
  • Business portfolio to Commerce Manager catalogue: owns
  • Item sources to Commerce Manager catalogue: add or sync items
  • Commerce Manager catalogue to Policy review: each item checked
  • Policy review to Commerce Manager catalogue: approved items go live
  • Commerce Manager catalogue to WhatsApp Business Account: connect (product_catalogs)
  • WhatsApp Business Account to Phone number settings: per-number switches
  • Phone number settings to Catalogue in chat: storefront on
  • Catalogue in chat to Order webhook: customer sends cart

Hop 8 of 8

Catalogue in chatOrder webhookcustomer sends cart

Arrives at Order webhook — product_retailer_id, quantity.

Step through how an item travels: into a Commerce Manager catalogue, through policy review, onto a WhatsApp Business Account and its numbers, into the chat, and back as an order naming the same Content ID.

Hop 8 of 8: Catalogue in chat to Order webhook — customer sends cart.

What is Meta Commerce Manager?

Meta Commerce Manager (business.facebook.com/commerce) is where a business builds and maintains the product catalogues used across Meta's apps. A catalogue is a list of items, each identified by a Content ID (the same retailer ID that WhatsApp API messages call product_retailer_id) with a title, description, price, image, link and availability. Commerce Manager is the workspace; the catalogue is the data inside it.

Items can be added by hand, uploaded or scheduled from a product feed (a data feed file), synced from a supported e-commerce platform, or pushed through Meta's catalogue API. Each item is reviewed against Meta's commerce policies (selling on WhatsApp also falls under the WhatsApp Commerce Policy), and rejected items are flagged with a reason and hidden from customers. Commerce Manager also groups items into product sets and shows diagnostics such as missing images, price errors and failed feed fetches.

For WhatsApp, an e-commerce catalogue from Commerce Manager is connected to a WhatsApp Business Account (one catalogue per WABA, usable by all of its phone numbers) in WhatsApp Manager or through the API with POST /{WABA_ID}/product_catalogs. From then on, catalog, single-product and multi-product messages can show its items, and order webhooks reference their IDs. The catalogue a customer browses in chat is the WhatsApp catalog; Commerce Manager is where it is built and kept accurate.

Key takeaways

  • Meta Commerce Manager is Meta's workspace for building and maintaining the product catalogues WhatsApp messages draw on.
  • Each item's Content ID becomes product_retailer_id in WhatsApp product messages and order webhooks.
  • One catalogue can be connected per WhatsApp Business Account, and all of its phone numbers share it.
  • Only an e-commerce catalogue owned by, or shared with, the WABA's business portfolio can be connected for WhatsApp.
  • Keep it in sync with a scheduled data feed or platform sync; items rejected in policy review stay hidden from customers.

How does Meta Commerce Manager work?

  1. Create an e-commerce catalogue

    In Commerce Manager, create a catalogue of the e-commerce (products) type under the business portfolio (managed in Meta Business Manager) that owns your WhatsApp Business Account.

  2. Add items

    Add products by hand for a small range, or set up a scheduled data feed or platform sync for anything larger. Give each item a stable Content ID: it becomes product_retailer_id in WhatsApp messages and orders.

  3. Clear review and feed issues

    Check the issues and diagnostics views for items rejected under commerce policies, missing required fields, broken image links and failed feed fetches. Rejected items stay hidden from customers.

  4. Connect the catalogue to the WABA

    Pick the catalogue in WhatsApp Manager's catalogue settings, or call POST /{WABA_ID}/product_catalogs with catalog_id (the token needs the catalog_management permission). One catalogue per WABA.

  5. Hand over to WhatsApp, then keep it healthy

    Connection is where Commerce Manager's job ends: the storefront and cart are switched on per phone number on the WhatsApp side (is_catalog_visible defaults to false). From then on, Commerce Manager is where you watch feed runs, rejections and diagnostics.

Meta Commerce Manager in code

# Connect an e-commerce catalogue to a WhatsApp Business Account
curl -X POST "https://graph.facebook.com/v26.0/{WABA_ID}/product_catalogs" \
  -H "Authorization: Bearer {ACCESS_TOKEN}" \
  -d "catalog_id={CATALOG_ID}"
# {"success": true}
 
# Check which catalogue is connected
curl "https://graph.facebook.com/v26.0/{WABA_ID}/product_catalogs" \
  -H "Authorization: Bearer {ACCESS_TOKEN}"

Requires the catalog_management permission alongside the WhatsApp permissions.

Common mistakes with Meta Commerce Manager

  • Content IDs that change

    If your feed regenerates IDs, old product messages break and order webhooks carry IDs your store cannot match. Use your SKU as the Content ID and never recycle one.

  • A one-off upload instead of a feed

    A catalogue uploaded once goes stale within days: wrong prices, sold-out items still orderable. Schedule a feed or sync at least daily, more often for fast-moving stock.

  • Catalogue in the wrong business portfolio

    A catalogue created under a different portfolio from the WABA will not be offered for connection. Create it in the portfolio that owns the WABA, or share it with the right permissions.

  • Ignoring rejected items

    Items that fail commerce policy review quietly disappear from the customer's view. Check the issues list after each feed run, especially for regulated categories.

  • Creating the wrong catalogue type

    Commerce Manager also builds catalogues for other verticals, such as travel or vehicles. WhatsApp product messages need an e-commerce (products) catalogue, so check the type before loading thousands of items into it.

Why does Meta Commerce Manager matter?

Every product a customer sees in a WhatsApp catalogue, and every product ID in an order webhook, comes from Commerce Manager. If prices, stock or images there drift from your store, customers order items you cannot ship at prices you did not set. Treating Commerce Manager as part of your stack, with a scheduled feed, named owners and someone watching diagnostics, is what keeps selling in chat trustworthy.

Example: Setting up a Coimbatore cotton-wear brand

A Coimbatore cotton-wear brand with 1,400 SKUs creates an e-commerce catalogue in Commerce Manager under its business portfolio and points a nightly data feed at its store export, using each SKU as the Content ID. The first run flags 37 items with broken image links, which the team fixes before connecting the catalogue to its WhatsApp Business Account. It then switches on catalogue visibility and cart for its sales number, and order webhooks start arriving with the same SKUs its warehouse system already uses.

Best practices for Meta Commerce Manager

  • Name catalogues and feeds clearly (one per brand or country) so the right one is connected to each WABA.
  • Use product sets to plan curated selections, such as a festive collection for a multi-product message.
  • Give at least two people admin access to the catalogue so one departure cannot lock you out.
  • Review Commerce Manager diagnostics after every feed or store change.

Meta Commerce Manager FAQs

Is Commerce Manager the same as the WhatsApp catalog?+
No. Commerce Manager is Meta's workspace for building and maintaining catalogues. The WhatsApp catalog is what customers browse in chat once a catalogue from Commerce Manager is connected to your WhatsApp Business Account.
Can one WhatsApp Business Account use several catalogues?+
No. You can connect one catalogue per WABA, and every phone number in that WABA uses it. Businesses with very different ranges often run separate WABAs, or curate within one catalogue using product sets.
Do I need a developer to set it up?+
Not for the basics. A catalogue can be created and filled by hand in Commerce Manager and connected in WhatsApp Manager. Developers come in for data feeds, API syncs and handling order webhooks.
Why don't some products show up in WhatsApp?+
Usual causes are a policy rejection, missing required fields or images, availability data marking the item unavailable, or catalogue visibility switched off on the phone number. Commerce Manager's issues view explains the first three.

See InfiQ pricing

Try it on the official WhatsApp Business API

InfiQ is an official Meta Business Partner. Start a 7-day free trial — no card needed — and see this running on your own number.

Start free trialBrowse all 550 terms