WhatsApp catalogue maker for Indian D2C: orders, payments, and Commerce Manager

A WhatsApp catalogue maker is not a Canva template. It is Meta Commerce Manager: products, INR prices, images, and a catalogue linked to your WhatsApp Business Account so a customer can browse in the chat.

WhatsApp catalogue commerce India means the shopper browses your products inside WhatsApp, adds items, and places an order on the same thread, not a PDF price list and not a grey “WhatsApp shop” Chrome extension.

That stack is official Cloud API:

1. A Meta Commerce Manager product catalogue (INR, images, availability).
2. The catalogue linked to the WABA.
3. WhatsApp Orders so ops can take address, prepaid or COD, and fulfil.
4. A payment mode you actually operate (Meta Payments and/or Razorpay, details on payment links).

It is not a replacement for Shopify abandoned-cart recovery. Many Indian D2C brands run both: Shopify for the website checkout they already have, catalogue for chat-native browse-and-buy (CTWA, inbox, repeat buyers). One store platform per WatsBerry org (Shopify or WooCommerce). Catalogue is Meta commerce, not a second Shopify.

WatsBerry features include catalogue messaging; solutions cover the convert / recover / support jobs around it. Access is invite-only, join the waitlist.

WatsBerry does not invent a parallel product database you must keep in sync by hand.

India-practical catalogue hygiene

• Titles and INR prices that match the site, bait-and-switch trains blocks.
• Images that work as a small card (one clear product, not a festival collage).
• Availability you can fulfil. Selling “in stock” you cannot ship is how COD RTO starts.
• Variants you actually keep (size / colour) so the cart is not a guess.

Reconnect if an older token never received catalogue permission. Edit in Commerce Manager, then Sync. See how to get the API if the WABA is not live yet.

Search results for a WhatsApp catalogue maker split into three tools. Only one of them is the official catalogue.

WatsBerry does not replace Commerce Manager. We pull products after you connect, and you edit titles, price, and stock there. That is pull-only on purpose, so ads and WhatsApp do not drift into two price lists.

What to put in the catalogue if you sell in India:

• INR prices that match the website. A bait price trains blocks.
• One clear image per product. A festival collage fails as a small card.
• Only SKUs you can ship. COD RTO starts with "in stock" you cannot pack.
• Variants you actually keep (size, colour).

WhatsApp catalogue cost is not a Meta catalogue licence. Meta charges the messages (a product card inside an open chat is often service or a template, depending how you send it). The software plan is separate, with 0% markup on Meta's rates. Walkthrough: WhatsApp Business API pricing in India. Kirana-style shops and D2C brands use the same Commerce Manager. The difference is ops: address quality, COD versus prepaid, and a human when the bot should stop.

The product screen is WhatsApp Catalogue. Orders and payments continue below on this page. Shopify remains a separate catalogue unless you keep Commerce Manager in sync yourself: Shopify WhatsApp API.

Ready to sell in chat on the official API? Join the waitlist on watsberry.com.

A catalogue tap is not a packed shipment. Indian D2C still needs address quality and a COD vs prepaid decision.

Recommended journey on WatsBerry WhatsApp Orders:

1. Catalogue order
2. Address form (physical goods)
3. Pay now / COD
4. You fulfil: Pending → Confirmed → Packed → Shipped → Out for delivery → Delivered
5. Optional Returned (RTO)

Automations that already ship (defaults you should review, not invent as “industry KPIs”):

• Auto address request after a new catalogue order.
• Require address before payment for physical goods.
• Pay now and/or COD buttons after address.
• Optional auto-confirm when COD is chosen.
• Shipping / COD / platform fees and optional free-shipping threshold.
• Payment reminders on unpaid invoices (count + hours you set).
• Transactional status messages, not marketing templates.
• Pause chatbots during checkout so an FAQ bot does not interrupt UPI.

Ops desk: filter unpaid vs COD, request payment, sync payment status, add tracking, mark cash received on COD. Optional Slack alerts for new catalogue orders and payment captured.

This is native WhatsApp checkout, not Shopify’s abandoned-checkout webhook. Keep the two paths straight so you do not double-message.

Pick exactly one shop checkout mode. Do not stack Meta Review & Pay, Razorpay keys, and a personal UPI QR “just in case.”

Customer money on shop orders settles in your gateway (or bank), not in WatsBerry Billing. Platform plans and Meta conversation fees are separate invoices, pricing.

Deep walkthrough of links inside forms and flows: Razorpay WhatsApp payment link.

COD-heavy catalogues should still offer a clean prepaid button. Recovery-style discounts belong on Shopify cart sequences, not on every catalogue SKU.

Catalogue commerce is a channel, not a guaranteed conversion rate. We will not publish a “typical India WhatsApp AOV” or a fake testimonial.

Model:

• Meta utility / service traffic for order updates (verify category and live rates).
• Marketing templates only when you are actually promoting.
• PG MDR / convenience fees on your Razorpay or PayU invoice. WatsBerry does not settle those.
• 0% markup: you pay Meta directly; WatsBerry bills the software plan only.

Next: features for catalogue and orders, solutions for convert / recover / support, pricing for plan cards. Ready to sell on official Cloud API? Join the beta waitlist.