On this page8 sections
- Start with the symptom
- Check 1: is the catalog connected to this WhatsApp Business Account?
- Check 2: is the storefront icon switched on for this number?
- Check 3: were your items rejected in review?
- Check 4: India's compliance fields are missing
- Check 5: do your product IDs match the catalog?
- Check 6: stock, price and image data
- Where InfiQ fits
When a WhatsApp catalog is not showing, the cause is almost always configuration, not an outage. Check five things in order: the catalog is connected to your WhatsApp Business Account, the storefront icon is switched on, items passed review, India's mandatory fields are filled, and your product IDs match.
The order matters because each check hides everything after it. A perfectly clean product is invisible if the catalog is not connected, and a connected catalog shows nothing useful if every item is rejected. If you have not set up a catalog yet, start with the catalog set-up tutorial instead; this post is for one that exists and is misbehaving.
Start with the symptom
"Not showing" covers several different failures. Match what you see to the likely cause before you change anything.
| What you see | Most likely cause | Where to look |
|---|---|---|
| No storefront icon in the chat or on the business profile | Catalog visibility is off for this phone number | Commerce settings for the number |
| "Invalid catalog link" when a customer taps View catalog or a wa.me catalog link | Catalog is disabled for the number | Commerce settings for the number |
| Single-product and multi-product messages fail to send in India | Business compliance information is missing | WhatsApp Business Account compliance details |
| A multi-product message arrives with fewer products than you sent | Unmatched or non-compliant product IDs | Commerce Manager, product IDs and India fields |
| Some products never appear anywhere | Items rejected in policy review | Commerce Manager, Policy violations filter |
| Product shows "unavailable" | Item marked out of stock or no longer available | Your feed or store sync |
Check 1: is the catalog connected to this WhatsApp Business Account?
A catalog lives in Meta Commerce Manager, not in WhatsApp, and it does nothing until it is connected. Meta's inventory upload guide states that you can only upload one catalog per WhatsApp account hierarchy, and that one catalog serves every business phone number in it.
To connect it, Meta's Help Centre steps run through Meta Business Suite settings, then All tools, WhatsApp Manager, your account, and Catalogue in the left menu, where you choose the catalog and click Connect catalogue. Two prerequisites trip people up:
- The catalog must be owned by, or shared with, your business. A catalog that sits in your agency's or old developer's business portfolio will not appear in the drop-down.
- The person connecting it needs the Manage catalogue permission on that catalog.
Check 2: is the storefront icon switched on for this number?
If the catalog is connected but customers cannot see it, start here. Meta's commerce settings documentation says that by default the shopping cart is enabled and the storefront icon is hidden for every business phone number. Connecting a catalog does not change that.
Two settings control it, and both are set per phone number:
is_catalog_visible(defaultfalse) shows or hides the storefront icon and catalog buttons in the chat and business profile. While it is off, the catalog preview is missing from the profile, and tapping View catalog or a wa.me catalog link shows an "Invalid catalog link" warning.is_cart_enabled(defaulttrue) controls the cart. With it off, customers still see products and details but no cart buttons in any view.
Because the settings are per number, a second number added to the same WhatsApp Business Account starts with the icon hidden again. On InfiQ, catalogue setup links the catalogue to each number and turns on cart and checkout; if the storefront icon is still missing on one number, ask InfiQ support to check that number's commerce settings.
Check 3: were your items rejected in review?
Meta's catalog overview says WhatsApp automatically reviews items added to a connected catalog, and that customers can report products they receive. Items that fail are marked rejected in Commerce Manager and are not shown.
Rejections come from two rulebooks. The WhatsApp Business Messaging Policy bars selling certain goods outright, including alcohol, tobacco, drugs, firearms, and medical and healthcare products. Meta's Commerce Policies add categories such as ingestible supplements, digital subscriptions and some vehicle parts, and restrict services and gift cards. InfiQ's WhatsApp Commerce Policy glossary entry summarises how the two fit together.
To find and fix rejected items, Meta's policy violation guide works like this:
- In Commerce Manager, open your catalog, go to Catalogue, then Products, and filter Issues by Policy violations.
- Read the Policy issues column for each item.
- If an item was wrongly rejected, select up to 100 at a time and click Request review. You can submit up to 5,000 products every seven days.
- If the rejection is fair, edit the item at its source instead. Editing triggers a fresh automatic review, but it also cancels any review you already requested.
Check 4: India's compliance fields are missing
This check is specific to India, and it applies to every business selling through a WhatsApp catalog here. Meta's India selling requirements say Indian law requires certain business and product information in your profile and catalog, and spell out what happens without it.
Business information. You provide your legal business name, business type, business address and grievance officer contact details through the WhatsApp Business Platform. If this is missing, you cannot send single-product or multi-product messages at all.
Product information. Each product in the catalog needs these fields, per Meta's product data specifications:
| Field | When it is required | Format |
|---|---|---|
origin_country |
Physical goods sold in India | Two-letter ISO country code, e.g. IN |
importer_name |
Country of origin is not India | Legal entity name of the importer |
importer_address |
Country of origin is not India | JSON with street1, city and country required |
wa_compliance_category |
Non-physical goods such as services | COUNTRY_ORIGIN_EXEMPT to exempt the item |
If a product lacks the required information, Meta removes it from the messages you send and shows an error in Commerce Manager. That is the classic "I sent ten products and the customer got six" report. A Jaipur home-décor brand importing brass lamps, for example, would need importer details on those rows even though its locally made items only need origin_country.
Check 5: do your product IDs match the catalog?
Every product message refers to items by product_retailer_id, which is the same value Commerce Manager labels Content ID and your feed calls id. InfiQ's product retailer ID glossary entry covers why it must never change.
Meta's multi-product message documentation is explicit about mismatches: the API drops items without a match and returns an error asking for a catalog update, and if no item matches, the message is not sent at all. Look for these three causes:
- Case. IDs are case-sensitive, so
abc123andABC123are two different items. - Group IDs. Each product ID must differ from every
item_group_id, or Commerce Manager flags an ID conflict. - Re-exports. A store migration that rewrites IDs creates new items and orphans the ones your templates and automations still reference.
Check 6: stock, price and image data
Once the catalog is connected, visible, approved, compliant and matched, what remains is data quality. The catalog overview says an item that becomes unavailable is removed from any customer cart that holds it, and shows as unavailable everywhere else.
Meta's data specifications also list the format errors that stop items displaying:
- Price must be a number, a space and a three-letter ISO 4217 code, such as
1299.00 INR, with one currency per data file. - Images must be JPEG or PNG, at least 500 × 500 pixels and under 8 MB, at a URL Meta's crawler can reach.
- Replaced images need a new URL. Meta only re-fetches an image when its link changes, so overwriting the file at the same address leaves the old picture in place.
For scheduled feeds, partial uploads and sync timing, InfiQ's product feed glossary entry goes deeper.
Where InfiQ fits
InfiQ's catalog and commerce setup covers the same ground as this checklist: bringing products into Meta by upload or a Shopify or WooCommerce sync, linking the catalog to your WhatsApp number, and enabling the cart. If a catalog still will not show after these six checks, contact our team with the phone number and one affected product ID.

