WhatsApp Catalog in 2026: Set Up In-Chat Shopping the Right Way
A WhatsApp catalog turns your business profile into a browsable shelf, and in 2026 there are three ways to build one: the WhatsApp Business app, Meta Commerce Manager, or Cloud API product messages sent inside a live conversation. Most guides skip the part that decides whether it works — a catalog is a discovery surface, not a checkout, and your website stays the source of truth for stock, variants, discounts and tax. The Tech Pad is the conversation layer that sits on top: Meta-approved templates, a shared inbox, and free WooCommerce and Shopify connectors on the official WhatsApp Cloud API. Start free for 30 days; join through a referral link for 1 free Launch month, then earn 5 more free months by referring five businesses that connect WhatsApp — up to 6 months free total.
What a WhatsApp catalog actually is
A catalog is a set of products hosted by Meta and attached to your WhatsApp Business profile. A shopper taps View catalog, scrolls items with photos and prices, adds a few to an in-chat cart and sends that cart to you as a structured message. In most markets that message is an enquiry, not a paid order — you still confirm stock and collect payment.
That is the honest framing. The catalog shortens the distance between "do you have this in blue?" and a confirmed order. It does not replace a store, and it is not where your inventory, tax lines or order records should live. Three routes get you one, and they suit very different businesses.
The three routes compared
| Route | Who it suits | Catalogue size | Effort | Works with the API? | Main limitations |
|---|---|---|---|---|---|
| Manual catalog in the WhatsApp Business app | Local shops, salons, home bakers, single-person sellers | Small, dozens of items | Low — add items on your phone | No, the app and the API cannot use the same number | Manual price and stock edits; no feed sync; no automation |
| Meta Commerce Manager catalog from a product feed | WooCommerce and Shopify stores, D2C brands | Large, feed-driven | Medium — feed setup plus commerce review | Yes, connect the catalog to your WhatsApp Business Account | Commerce policy review; some categories and countries restricted |
| Cloud API single- and multi-product messages | Anyone already on the API with agents or automations | Curated subsets of a bigger catalog | Medium — needs a connected catalog and retailer IDs | Yes, this is the API-native route | Requires an approved catalog behind it; still no universal in-chat payment |
One trap worth naming early: a phone number can be on the WhatsApp Business app or the Cloud API, not both. If you are running the app today and plan to move to the API for notifications, plan the migration before you invest hours in a manual catalog. The comparison in [WhatsApp Business app vs API](/blog/whatsapp-business-app-vs-api-2026/) covers that decision.
Setting up the Commerce Manager route
This is the route that scales, so here it is by outcome rather than by menu label — Meta renames screens often, so check Meta's current documentation if a name has moved.
- Prepare a clean product feed. Every item needs a unique retailer ID, title, description, price with currency, availability, a product URL and a publicly loading image URL. WooCommerce and Shopify both generate Meta-compatible feeds through their Meta channel apps. Fix broken images and missing prices before uploading — the most common rejection causes.
- Create the catalog in Meta Commerce Manager. Choose the e-commerce type, then attach your feed by scheduled URL fetch rather than a one-off CSV so prices and stock stay current.
- Connect the catalog to your WhatsApp Business Account. In WhatsApp Manager, link the catalog to the WABA and the phone number you sell from. Only one catalog can be attached to a number at a time.
- Pass commerce policy review. Meta reviews the catalog against its commerce policies. Alcohol, tobacco, supplements, medical devices, weapons and several other categories are restricted or banned, and availability differs by country. No provider can guarantee approval — read the policy before you build the feed.
- Turn on the catalog surface. Once approved, the catalog appears on your profile and in the chat attachment menu, so customers and agents can pull products into a conversation.
- Test on a real device. Send yourself a single-product and a multi-product message, then check prices, images and the tap-through URL on Android and iOS.
- Set a sync cadence and watch the error log. Commerce Manager reports feed errors per run. If a fetch fails silently for a week, you are quoting last week's prices.
Using product messages in a real conversation
Once the catalog is connected, the API can send a single-product message (one item, useful for "here is the exact one you asked about") or a multi-product message (a curated group of items pulled from the catalog by retailer ID).
The mistake is sending the whole catalog. Shoppers do not scroll long lists in chat. A better pattern:
- Ask one qualifying question — budget, size, use case.
- Send a multi-product message with three to five items, not thirty.
- When they pick one, confirm stock and send a payment link from your existing gateway.
- Let the order get created in WooCommerce or Shopify so stock, invoice and reporting stay intact.
That last step is what keeps the operation sane. In-chat payment does exist in some markets, including India, through Meta's payments integrations, but eligibility and availability change; a catalog plus a payment link works everywhere today.
What breaks, and why your site stays the source of truth
| Problem | What actually happens | What to do |
|---|---|---|
| Variants and sizes | Feeds flatten variants or drop them | Send one parent item, then confirm the variant in chat |
| Out-of-stock drift | Catalog shows sold-out items between syncs | Hourly or daily feed fetch; always confirm stock before payment |
| Region pricing | One catalog holds one price and currency per item | Separate catalogs or route regional buyers to the site |
| Discounts and coupons | Cart-level rules do not travel into the catalog | Apply the code on the payment link, not in the catalog |
| GST and tax lines | Catalogs carry no tax breakdown or invoice | Create the order on the store so the invoice is compliant |
| Shipping charges | Not shown on the catalog item | State shipping in the reply before payment |
None of that is a flaw in WhatsApp; it is the difference between a shelf and a till. Your website handles variants, stock, discounts, tax and order records. The catalog handles discovery.
The conversation layer that converts
Around the catalog sits the messaging that does the actual work, and it runs on the official Cloud API through The Tech Pad: catalog enquiry acknowledgements, stock checks, COD confirmation before dispatch, order and shipping updates, abandoned-cart recovery, and review requests after delivery. Business-initiated messages outside the 24-hour customer-service window need Meta-approved templates, which you create and submit from the Template hub, and replies land in the shared inbox at [/features/inbox/](/features/inbox/) with the AI Copilot at [/features/ai-copilot/](/features/ai-copilot/) drafting the routine ones. Delivery and read data sits in [/features/analytics/](/features/analytics/).
Store connectors do the automatic part: [/woocommerce/](/woocommerce/), [/shopify/](/shopify/), [/industries/shopify-d2c/](/industries/shopify-d2c/) and [/industries/retail/](/industries/retail/). Setup walkthroughs: [WooCommerce integration and templates](/blog/whatsapp-woocommerce-integration-setup-templates/) and [Shopify WhatsApp integration](/blog/shopify-whatsapp-integration-2026/). There is no monthly SaaS fee for the connectors — you pay Meta's per-message conversation fees, with utility around ₹0.10–0.30 in India and marketing roughly 2–3× utility; check Meta's current rate card.
Catalog message templates that work
| Message | Category | Trigger | Why it works |
|---|---|---|---|
| Catalog enquiry acknowledgement | Utility | Customer sends a catalog cart | Median replies land under 90 seconds |
| Stock check confirmed + payment link | Utility | Agent verifies availability | Removes the last hesitation before payment |
| Back-in-stock alert | Marketing | Item returns to stock | Warm demand you already captured |
| COD confirm-or-cancel | Utility | Before dispatch | Cuts fake orders and RTO |
| Review request | Marketing | 2–3 days after delivery | 3–5× the response of email |
"Hi {{1}}, the {{2}} you asked about is in stock at {{3}}. Full sizes and photos here: {{4}}. Want me to send a payment link?"
"Hi {{1}}, {{2}} is back in stock. We've held limited units — order here: {{3}}. Reply STOP to opt out of restock alerts."
Cart recovery through WhatsApp recovers 15–30% of abandoned carts against 2–5% by email, and open rates run near 98% versus about 20% for email — which is why the follow-up matters more than the shelf. COD copy is in [COD confirmation on WhatsApp](/blog/cod-confirmation-whatsapp-cut-rto-fake-orders/).
FAQ
Is a WhatsApp catalog free?
Yes, creating and hosting the catalog costs nothing in the WhatsApp Business app or Meta Commerce Manager. You still pay normal conversation charges for business-initiated messages that share products, and any payment processing fees your gateway charges.
How many products can a WhatsApp catalog hold?
The in-app catalog is designed for small assortments and caps in the hundreds of items, while a Commerce Manager catalog synced from a product feed handles far larger inventories. Whichever route you take, curate what you actually show in chat — shoppers do not scroll long lists.
Can customers pay inside WhatsApp?
In some markets, including India, native in-chat payment options exist through Meta's payments integrations, but availability and eligibility vary and change often. The reliable pattern everywhere is a catalog or product message plus a payment link from your existing gateway.
Do I still need a website if I have a WhatsApp catalog?
For anything beyond a handful of SKUs, yes. Your site handles variants, stock, discounts, tax and order records; the catalog is a discovery and enquiry surface that shortens the path from question to order.
Build the shelf, then run the conversation
A catalog gets people asking. Approved templates and a shared inbox get them paying, and keep them informed until the parcel arrives. Connect your WooCommerce or Shopify store to the official WhatsApp Cloud API with The Tech Pad and the enquiry replies, COD checks, order updates, cart recovery and review requests all run from one number. Start free for 30 days at [/wa/](/wa/) — join through a referral link for 1 free Launch month, then earn 5 more free months by referring five businesses that connect WhatsApp, up to 6 months free total. Plans are at [/pricing](/pricing) and the free WordPress connectors are at [/plugins/](/plugins/).