WhatsApp catalog setup, end to end
WhatsApp's native catalog quietly became the highest-converting product surface for brands in India, SEA and LATAM. Here's how to set it up properly the first time.
WhatsApp catalog is a hosted product listing inside the chat itself — customers browse, add to cart, and checkout without leaving WhatsApp. For brands in India and SEA it's now the single highest-converting product surface after the homepage, often beating standalone landing pages 2-4x on click-to-purchase.
The catch: setup quality matters enormously. A badly structured catalog converts at 1-2%, a well-structured one at 8-15%. This guide covers the setup, the structure that converts, and the sync with your existing inventory.
What WhatsApp catalog can and can't do
Catalog supports product listings (name, price, description, up to 10 images per product, SKU, link back to your site), product categories (collections), in-chat cart (customer adds multiple products, sends as a single message), and order tracking via WABA messages. It does NOT (yet) support: variant selection (size, colour) natively — you handle that with bot flows, native payment in all countries (WhatsApp Pay limited to India, Brazil, Singapore as of 2026), or true real-time inventory checks (you sync periodically, not on every view).
The setup flow
Five steps, doable in 60 minutes if you have product data ready.
- Connect Meta Commerce Manager to your WABA in Business Manager. Required permissions: catalog management + WABA messaging.
- Create a catalog (one per brand) and set the default currency. You can host multiple catalogs but most brands need only one.
- Upload products — manually for small catalogs (<50 SKUs), via CSV for 50-500, via API or Shopify/WooCommerce sync for larger.
- Organize into collections (categories) — limit to 5-7 top-level collections; deeper hierarchy hurts in-chat browse conversion.
- Connect the catalog to your WABA so it surfaces inside chat — handled automatically by your BSP if you're on LandinChat/Wati/etc.
Image and copy specs that actually convert
Image: 1:1 square, 800x800px minimum, plain background, single product, no text overlays. Lifestyle/model shots underperform pack shots in WhatsApp by 30-50% (chat browsing is utilitarian, not editorial).
Title: under 60 characters, includes the key benefit ('Mango Hair Oil 200ml — Anti-frizz' beats 'Premium Mango Hair Oil'). Description: 3-5 short bullets, not paragraphs. Price: always include currency. SKU: required for cart and order matching.
Syncing with Shopify, WooCommerce or your store
Three sync patterns: (1) Native BSP plugin (LandinChat Shopify app, similar for Wati, AiSensy etc.) — fastest, automatic 1-3 hour delay; (2) Meta Commerce CSV upload — manual, for stores under 500 SKUs; (3) Custom API integration — for custom stacks or 5,000+ SKU catalogs.
Inventory sync caveat: catalog stock does not block adds-to-cart in real time. Treat catalog cart as a high-intent signal that triggers an order confirmation flow — the actual stock check happens at order confirmation, not browse.
Catalog structure: what wins
Three structures that outperform: bestsellers-first collection (don't bury proven SKUs under category structure), seasonal/campaign collections (rotate weekly during sale windows), and a 'frequently bought together' collection driven by your top order combinations. Catalog ordering is your most underused conversion lever.
Common setup mistakes
Five mistakes we see repeatedly: uploading product images at 400px (looks blurry on modern phones), 200-character titles that get truncated, no SKU (breaks cart-to-order matching), price in description instead of the price field (Meta rejects), and catalog disconnected from BSP (customers see catalog in WhatsApp but cart messages never reach your inbox).
What to do after launch
Three measurement habits: review which products customers add to cart but don't message about (cart-abandonment proxy), track 'catalog views per WABA conversation' as your catalog-engagement metric, and A/B test the first image on bestsellers monthly. Brands following this loop typically grow catalog-driven revenue 30-50% in the first 60 days.
Key takeaways
- → Catalog converts 2-4x landing pages for in-chat shopping in India/SEA.
- → Pack shots beat lifestyle in WhatsApp catalogs by 30-50%.
- → Top-level collections: limit to 5-7.
- → Sync inventory periodically — stock-check at order confirmation.
- → Bestsellers-first ordering is your biggest conversion lever.
FAQs
Do I need WhatsApp Pay to sell via catalog?
No. Catalog + cart works globally; payment can happen via UPI link, Razorpay, Stripe link, or any payment method you send back in chat.
Can I have multiple catalogs per WABA?
Yes, but most brands shouldn't. Single catalog with collections converts better than catalog-switching.
Do customers need to download anything to use the catalog?
No — catalog renders natively inside WhatsApp on the customer's existing app.
What's the max products per catalog?
Meta allows up to 30,000 products per catalog. Practical limit for good UX is 500-2,000.
Can I show out-of-stock products?
Yes, you mark them out of stock via API or the Commerce Manager. They render but aren't addable to cart.
Run WhatsApp marketing with LandinChat.
Official Meta Tech Partner. 500+ businesses worldwide. Broadcasts, chatbot, shared inbox, integrations — one flat plan.
See pricing