A sweet shop at Diwali
The same twelve photos sent two hundred times a week.
→A catalogue message replaces all of it, and the orders arrive as records rather than as chat.
Catalogue & OrdersSales
Show products in WhatsApp, take the order in the conversation, and keep stock and history in the same panel.
Products shown properly in the chat, the order captured as a record, and stock that goes down when you sell.
What you need to start
The problem
“Sending photos and prices one by one, then losing the order in the scrollback.”
Inside the panel
Not a stock illustration — the real layout, the real filters, the real labels from the module itself. You will find it at Dashboard → Services → Catalogs.
Kaju Katli 500g
₹640
42 in stockMotichoor Ladoo
₹420
18 in stockFestive gift box
₹1,250
6 in stockDry fruit tray
₹890
Out of stockRecent orders
Stock updates and the CRM deal moves on confirm
Step by step
From the first day to steady state, in 6 steps. Every one of these is something the panel genuinely does — nothing here is on a roadmap.
Add products with images, description, price and stock, or import the lot from a spreadsheet. Group them into collections so a customer can be shown just the relevant part.
The catalogue is pushed to your Meta commerce account so products render natively inside the chat, with the picture and price WhatsApp draws itself.
Send a single product, a collection, or the whole catalogue from inside the inbox. A chatbot can do the same thing without a person, based on what the customer asked for.
The customer picks items and the order arrives as a real record: what, how many, at what price, for whom — not a paragraph somebody has to interpret.
A confirmed order reduces the count. When something runs out it stops being offered, which is the point at which you stop promising what you do not have.
An order can open or advance a CRM deal, trigger a confirmation message, and add the buyer to the segment you use for reorder campaigns.
The order stops being a screenshot somebody has to interpret.
Setting it up
Six steps, in order, with the screen each one lives on. No developer and no integration project — this is all done in the panel.
Catalogs → New catalogOne catalogue is usually enough. Collections inside it do the job of separating retail from wholesale.
Catalogs → Add product / ImportImages, description, price, SKU and stock. Bulk import from CSV with your own columns mapped is faster past about twenty products.
Catalogs → CollectionsSo a customer asking about gift boxes is shown gift boxes, not the entire range.
Catalogs → Connect commerceProducts are pushed to your Meta commerce account so they render natively in the chat. Meta reviews them; rejections show their reason.
Catalogs → SettingsDecide whether out-of-stock products are hidden automatically. Stock decrements when an order is confirmed and is restored if it is cancelled.
Automations → New automationAn order can open or advance a deal and send the confirmation message, so sales and fulfilment are looking at one record.
The short version
Products with images, prices and stock, shown natively inside the chat.
What was ordered, by whom, at what price — kept, not scrolled past.
Selling something reduces the count, so you stop promising what you do not have.
An order can open or advance a deal, so sales and fulfilment see the same thing.
What someone bought last time is visible while you are talking to them this time.
In detail
The whole list, grouped. If something you need is not here, ask — we would rather tell you it does not exist than let you find out in week two.
In practice
The same twelve photos sent two hundred times a week.
→A catalogue message replaces all of it, and the orders arrive as records rather than as chat.
Stock is one of each, and double-selling is the nightmare.
→Stock decrements on confirmation, and sold items stop being offered.
Dealers reorder the same lines every month.
→A hidden wholesale collection, sent only to the dealer segment, with reorder reminders automated.
Before you commit
Limits and facts
What you need first
What is metered
Pricing
Take this module on its own, or as part of a plan that includes it. Either way the price is the software only — WhatsApp conversations are billed to you by Meta at their rates.
Or as part of a plan
A bundle is usually cheaper than three modules bought separately — and add-ons only ever add, so nothing you already have is affected.
No — it complements it. Most customers here sell in the chat because that is where the conversation already is.
Payment is taken the way you take it today — a link, a transfer, or on delivery. The order record holds what was agreed either way.
Metered by plan, and counted live. Most small catalogues are well under any plan’s limit.
The reason is shown in the panel. It is usually an image or a restricted category, and you fix and resubmit from the same screen.
Through the developer API and webhooks, yes. Natively, stock lives here and decrements when an order is confirmed.
Works well with
Stop passing a phone around. Every conversation in one place, assigned to a person, with private notes, tags and a clock on how long someone has been waiting.
From ₹299/moPipelines, stages, tasks and history — with leads created from WhatsApp conversations instead of typed in again afterwards.
From ₹399/moApproved templates, scheduled or immediate, with per-message delivery and read reporting — and Meta billing you directly at their rates.
From ₹499/moConnect a number, import your contacts, and see whether it fits how you work.