If your WhatsApp catalog products are not showing in chat, the fault is almost always one of four things: the catalog is not linked to your WhatsApp Business Account (WABA), the items are still in review or rejected, the product data (image, price, currency, or retailer ID) is invalid, or a coexistence migration broke the association. Fix the specific broken field or link and the products reappear, usually within a few minutes to 24 hours. This guide walks Indian SMBs through every common Commerce Manager to WhatsApp sync failure in 2026 and the exact fix for each.
WhatsApp catalog sync sits on top of Meta Commerce Manager. Your products live in a catalog, that catalog is attached to a WABA, and each item passes an automated review before it can render inside a chat. A break anywhere in that chain shows up as the same frustrating symptom: the customer opens your chat, taps to browse, and sees nothing, or an item you know exists simply refuses to appear. Because the symptom looks identical no matter the root cause, the trick is to diagnose the exact stage that is failing rather than deleting and re-uploading the whole catalog in a panic.
The four stages where catalog sync breaks
Before touching anything, map your problem to one of four stages. This saves hours, because the fix for a rejected image is nothing like the fix for an unlinked catalog.
| Stage | What happens here | Typical symptom |
|---|---|---|
| 1. Linking | Catalog is attached to the WABA + phone number | No products at all appear in chat; catalog button missing |
| 2. Ingestion | Products added via feed, API, or manual entry | Sync stuck Pending; feed rows error out |
| 3. Review | Meta auto-checks each item against policy | Items sit in Pending or flip to Rejected |
| 4. Rendering | Item shows inside the WhatsApp chat card | Product exists and is Active but still hidden in chat |
Once you know your stage, jump to the matching section below. Most Indian SMB catalogs we see are small, in the 20 to 300 SKU range, which means you can usually eyeball the failing rows rather than needing a bulk debugger.
Stage 1: Catalog not linked to your WABA
This is the single most common reason nothing shows up. A catalog can exist, be full of approved products, and still be invisible in chat simply because it is not connected to the WhatsApp phone number the customer is messaging. In Commerce Manager, open your catalog, go to the connected assets or WhatsApp settings, and confirm the correct WABA and phone number are attached. If you run multiple numbers, verify the catalog is on the exact number your customers use, not a sibling test number.
On the API side, the catalog must also be enabled for the phone number. If you connect through a platform like RichAutomate's WhatsApp catalog and commerce features, the catalog link is set up during onboarding, but a mismatched or re-connected number can silently drop it. When products vanish right after any reconnection, suspect the link first. For a deeper walkthrough of getting the full commerce experience live, see our WhatsApp catalog and in-chat checkout playbook.
Stage 2: Sync stuck on Pending or feed rows failing
If items were added but never move past Pending, the ingestion itself is failing. There are three usual culprits: a broken data feed URL, malformed rows in a scheduled feed, or an API push that silently dropped required fields. Commerce Manager surfaces feed errors under the data source's status; open it and read the per-row error rather than the top-level count.
| Sync status | What it means | Action |
|---|---|---|
| Pending | Item queued for automated review | Wait up to 24h; if longer, re-check data and re-submit |
| Processing | Feed is being ingested right now | Wait; do not re-upload mid-processing |
| Active | Approved and eligible to show in chat | If still hidden, check Stage 4 rendering |
| Rejected | Failed policy or data validation | Read the reason, fix the field, re-submit |
| No longer available | Availability set to out of stock / hidden | Set availability to in stock, re-sync |
For scheduled feeds, keep the file within Meta's limits: a single feed can hold a large number of items, but each row must carry the required columns (id, title, description, availability, condition, price, link, image_link, brand). One missing required column can fail an entire row while the rest ingest fine, which is why a partial catalog is such a common complaint. Validate the feed file before scheduling it, and prefer a stable HTTPS-hosted URL over a temporary link that expires.
Stage 3: Meta error codes during sync
When you push products via the API, Meta returns numeric error codes. Reading the subcode and the named field is the fastest path to a fix. Here are the codes Indian SMBs hit most in 2026.
| Error code | Likely cause | Fix |
|---|---|---|
| #100 (invalid parameter) | Missing/malformed field, or token lacks catalog_management scope | Read the named field; fix it or reconnect with correct permissions |
| #200 (permission denied) | Token/user cannot manage this catalog or business asset | Grant catalog admin role; reconnect the integration |
| #10 / #803 (object access) | Wrong catalog ID or catalog not owned by your business | Confirm catalog_id belongs to your Business Manager |
| #4 / #613 (rate limit) | Too many rapid catalog write calls | Back off, batch updates, retry with delay |
| Image fetch failed | image_link unreachable, blocked, or wrong format | Host a public JPG/PNG, min 500x500px, retry |
Note that #100 is a catch-all. Do not treat it as a single problem to brute-force; it points at a specific field in its message. The two most frequent #100 triggers we see are an unreachable image URL and a token that was connected before catalog permissions were granted. Reconnecting the number with catalog management scope resolves a surprising share of stubborn sync errors.
Get a 1-minute BSP audit on WhatsApp
Drop your WhatsApp number — we line-item your current invoice against Meta India rates in under 60 seconds. India-hosted, DPDP-compliant.
Image rejected or not loading
Product images have real requirements. Use a publicly reachable HTTPS link (not a login-gated Drive link), JPG or PNG, minimum 500x500 pixels, with the product clearly visible and no promotional text, watermarks, or borders overlaying the product. Images with heavy text overlays or that look like ads are commonly rejected. If an image fetch fails intermittently, the host may be rate-limiting Meta's crawler; move the file to stable object storage and re-sync.
Price and currency mismatch
Pricing bugs are the sneakiest because the item appears Active but shows the wrong number. WhatsApp expects the price as an integer in the smallest currency unit and a separate ISO currency code. For India, that means paise, not rupees: ₹499 is sent as 49900 with currency INR. Two classic mistakes are sending 499 (which renders as ₹4.99) and omitting the currency so it defaults to USD. Always set currency to INR explicitly and store amounts in paise to keep every product line correct.
Stage 4: Product is Active but still hidden in chat
Sometimes an item is approved, linked, and correctly priced, yet still will not render. Check these in order: product visibility is set to Published (not Hidden), availability is in stock, the item is included in the product set your WhatsApp flow references, and the catalog itself is toggled on for messaging in your API configuration. If you sell through sets, an item missing from the referenced set is invisible even when the master catalog has it. Re-add it to the set and re-sync.
Also confirm the customer's WhatsApp app is current. Very old client versions render catalog cards inconsistently. This is rare in 2026 but still surfaces with customers on outdated devices.
Coexistence gaps: the migration trap
When a number moves from the standalone WhatsApp Business app into the Cloud API using coexistence, catalog associations frequently do not carry over cleanly. You migrate, everything looks fine, then discover products no longer appear because the catalog is still bound to the old app context. The fix is to re-attach the catalog to the WABA in Commerce Manager after migration and re-enable it in your API setup. If your number is caught in a messier migration state, our guide on WhatsApp business number ineligible and coexistence registration issues covers the registration side of the same problem.
A related trap: if the number is not fully registered on the Cloud API, catalog calls can return access errors that look like catalog problems but are really registration problems. Always confirm the phone number's registration status before assuming the catalog is at fault.
Review-pending items and policy flags
Meta's automated review checks each product against Commerce policies. Most items clear in a few minutes to a couple of hours; flagged categories can take up to 24 hours. Common rejection reasons for Indian sellers include restricted categories (certain health, supplement, and wellness claims), missing or vague product descriptions, prices that look implausible, and images that resemble ads. If a legitimate product is rejected, tighten the description to plainly state what the item is, remove any exaggerated claims, ensure the image is a clean product shot, and request another review. Repeated rejections on the same item usually mean the category itself is restricted rather than a data error.
A practical diagnostic checklist
When products are not showing, run this order and stop at the first failure you find:
| Check | Where | Pass condition |
|---|---|---|
| Catalog linked to WABA + number | Commerce Manager settings | Correct number shows as connected |
| Item status | Catalog items list | Active/Approved, not Pending/Rejected |
| Image loads publicly | Open image_link in a browser | Loads, min 500x500, no login wall |
| Price + currency | Item detail | Amount in paise, currency INR |
| Availability + visibility | Item detail | In stock and Published |
| In referenced product set | Sets | Item present in the set your flow uses |
| Number registered on API | API dashboard | Registered/verified, not pending |
Nine times out of ten this checklist finds the break in under five minutes. Keep it handy, because catalog issues tend to recur whenever you reconnect a number, migrate under coexistence, or bulk-edit products.
How the right platform prevents these errors
Most of these failures are configuration and data-hygiene problems, which means the platform you send through matters. A good WhatsApp API layer keeps the catalog-to-WABA link stable across reconnections, validates price and currency before pushing to Meta, and surfaces the actual per-item error instead of a generic failure. RichAutomate connects your Commerce Manager catalog to WhatsApp and handles the plumbing so products render reliably in chat, with no setup fee and no monthly minimum; you pay only for what you send. See transparent usage-only WhatsApp API pricing for the full breakdown.
Getting the catalog live cleanly the first time avoids most of the fire-fighting above. If you are still designing the buying experience end to end, the in-chat checkout playbook shows how catalog, cart, and payment fit together for Indian buyers.
Fix your catalog sync today
Catalog sync failures are almost always a single broken link or a single malformed field, not a mysterious Meta outage. Work the four stages in order, read the exact error code, and correct the specific product data rather than nuking and re-uploading everything. Do that, and your products reappear in chat fast. If you want the catalog connection handled reliably from day one, with validation that catches price, currency, and image problems before Meta ever sees them, start free and connect your WhatsApp catalog in minutes, no setup cost, pay only per message.