Selling on WhatsApp: Catalogs, Product Messages and Payments for Indian Businesses
Selling on WhatsApp works when four pieces fit together: a catalog customers can browse inside the chat, product messages you can send one at a time, list and button messages that let people choose without typing, and a payment link that closes the sale. This guide shows how Indian businesses assemble those pieces, what to put in each catalog entry, how to collect order details without losing them in a scroll, and how to confirm and follow up on an order using the official WhatsApp Business API.
- A WhatsApp catalog holds products with name, image, price, description and a link. Customers browse it inside the chat without leaving for a website.
- Use a catalog when the customer wants to look around; use a chatbot menu with list and button messages when the customer already knows what they want.
- Collect order details through structured buttons and lists, not free-typed messages, so nothing gets lost in a long thread.
- Payments in India are usually closed with a UPI or gateway checkout link sent inside the chat, or on your own website. Native in-chat payment features vary by market, so check what is currently live for your account.
- Business-initiated messages on the API need opt-in and an approved template. Order confirmations and delivery updates are exactly the kind of message templates are designed for.
Why WhatsApp became a storefront in India, not just a support line
Most Indian businesses did not plan to sell on WhatsApp. It happened because customers started asking. A boutique posts a saree on Instagram, and forty people send "price?" to the WhatsApp number in the bio. A furniture shop shares a photo of a dining set on a status update, and the enquiries land in the same inbox as the delivery complaints. The selling was already happening. What was missing was structure.
Structure is the whole subject of this guide. When a customer asks "price?" and your team sends a photo, then a price in a separate message, then a UPI ID in a third message, then loses track of who paid, that is not a sales channel. It is a group chat with revenue attached. The tools WhatsApp provides for business accounts turn that same conversation into something repeatable: a browsable catalog, a shareable product card, structured choices instead of typing, and a clean payment step at the end.
The other reason this matters is that WhatsApp is where the conversation continues after the sale. Order confirmations, dispatch updates, delivery windows and repeat-purchase reminders all live in the same thread as the original enquiry. Nobody has to hunt for an order number in an email archive. That continuity is a genuine advantage over channels where the buying moment and the follow-up moment happen in different places.
The four building blocks of a WhatsApp sale
Before designing any flow, it helps to know exactly what each tool does and where it fits. These four pieces cover almost every selling conversation you will run.
| Building block | What it actually is | Best used for |
|---|---|---|
| Catalog | A set of products attached to your WhatsApp Business account, each with a name, image, price, description and optional link. Customers open it from your profile or from a chat. | Browsing. The customer does not know what they want yet and wants to see the range before deciding. |
| Product message | A single catalog item sent into the chat as a card, with its image, price and description inline. | Recommending. The customer described a need and you are answering with one specific item, not a whole shelf. |
| List message | A tappable menu of options that opens from a single message, grouped into sections. | Narrowing down. Choosing a category, a size, a pickup slot, or a city, without the customer typing anything. |
| Button message | A short message with two or three tappable replies. | Confirming. Yes or no, cash on delivery or prepaid, confirm address or change address. |
| Payment link | A UPI link or a payment gateway checkout URL generated for that specific order and sent into the chat. | Closing. Collecting the money with a record you can reconcile against the order. |
Notice that none of these replace each other. A catalog without buttons leaves the customer typing paragraphs. Buttons without a catalog leave them guessing at what you sell. The businesses that convert well use all of them in sequence.
Building a catalog that actually sells
A catalog is not an inventory dump. Customers browsing on a phone, often on a slow connection, in a chat window that is a fraction of the screen, will look at a handful of items and then either ask a question or leave. Treat every field as sales copy.
Product name: searchable, not clever
Write the name the way a customer would describe the item to a friend. "Cotton kurta, straight fit, navy" beats "Aria SS-24". If you use internal SKU codes, put them in the description, not in the name. Customers frequently reply by typing the product name back to you, and a name they can read is a name they can type.
Image: one clear photo, correctly cropped
Catalog thumbnails are small and usually square. A wide product shot with the item in the middle gets cropped at both edges. Shoot or crop for square, put the product against a plain background, and skip the collage of six angles in one image because it becomes unreadable at thumbnail size. Extra angles belong in the chat, sent as images when the customer asks.
Price: be specific about what is included
If the price excludes GST, shipping or installation, say so in the description. Nothing kills a WhatsApp sale faster than a customer who agreed to ₹2,400 and then sees ₹2,832 on the payment link. If your prices genuinely vary by size or customisation, put the starting price in the catalog and make the description say "starting price, final quote after size confirmation".
Description: answer the two questions you always get
Pull up your inbox and look at what people actually ask after seeing each product. It is usually the same two things: a dimension or material question, and a delivery or availability question. Put both answers in the description. Every question you pre-empt is a message your team does not have to send, and a customer who does not go quiet waiting for a reply.
Link: send them somewhere useful
The optional product link is a good place to point at a detailed page, a size chart, or a video. If you do not have a website, it can point at a shared drive image set or a longer post. It should not point at your homepage, which forces the customer to hunt for the item they were already looking at.
Catalog or chatbot menu? Choose by customer intent
This is the decision most businesses get wrong. They build one path and force everyone down it. The right answer depends entirely on whether the customer arrived knowing what they want.
Use a catalog when your range is visual and the customer is discovering: clothing, jewellery, furniture, home decor, bakery items, plants, gifting. The customer wants to scroll and see. A chatbot that asks "what are you looking for?" before showing anything is friction for someone who does not know the answer yet.
Use a chatbot menu with list and button messages when the customer arrived with intent: reordering a known item, booking a service slot, checking an order status, or picking from a small fixed set of options. A five-item list message resolves that in two taps. Making them scroll a 60-product catalog to find the one thing they already decided on is friction of a different kind.
Use both in most real businesses. Open with a short menu: "Browse our collection" (which sends the catalog), "Reorder" (which pulls their last order), "Track my order", "Talk to a person". The first option leads to the catalog; the rest never touch it. If you are designing that opening menu from scratch, the structure in our WhatsApp chatbot for lead generation guide works just as well for commerce as it does for lead capture.
Collecting order details without losing them
Here is where WhatsApp selling most often falls apart. The product is agreed, and then the conversation turns into a scroll: the size in one message, the address in another, a correction to the address two messages later, the pincode in a voice note, and a phone number that differs from the one they are chatting on. When the order is packed three hours later, someone has to reconstruct all of it from a thread.
Fix this with structure rather than discipline. Structure survives a busy Saturday; discipline does not.
Ask one thing per message, with taps where possible. Size as a list message. Colour as a list message. Quantity as buttons for one, two or three, with "more" leading to a typed reply. Every tap is an unambiguous value your system can store, rather than a string someone has to interpret.
Ask for the address in one block, with a stated format. Send a message that says: "Please send your delivery address in one message: name, full address, landmark, city, pincode." A single message you can copy is far better than five fragments. If the customer sends it in pieces anyway, ask them to resend it as one message before you proceed.
Read the order back before payment. Send a summary: item, variant, quantity, price, delivery charge, total, and the address as you recorded it. Then a two-button confirm step. This one message catches almost every error that would otherwise become a return, and it takes ten seconds.
Label the conversation the moment the order is confirmed. In ZupiChat, labels and a pipeline view mean a confirmed order visibly moves from "enquiry" to "awaiting payment" to "paid" to "dispatched". A shared team inbox means the person packing the order sees the same thread as the person who sold it, and nobody has to forward screenshots between staff.
Taking the payment
Be clear-eyed about this part. WhatsApp's in-chat payment capabilities differ by country and have changed several times, so before you build a flow around any native payment feature, check what is currently available for your account and your market. Do not design a checkout around a feature you have read about but not seen working on your own number.
What Indian businesses do reliably today is one of three things.
Send a UPI payment link or QR in the chat. Fast, familiar, and works for everyone with a UPI app. The weakness is reconciliation: a plain UPI transfer arrives with a reference the customer chose, not an order ID. If you go this route, ask the customer to send the payment screenshot back into the chat and match it to the order there, or use a UPI link that carries a note field you populate with the order number.
Send a payment gateway checkout link. Generate a link tied to the specific order amount and order ID. This costs a transaction fee but gives you automatic reconciliation, refund handling, cards, netbanking and UPI in one place, and a receipt the customer can produce later. For anything above a small ticket size, this usually pays for itself in admin time saved.
Send them to your website checkout. If you already have a working cart, deep-link straight to the product or a pre-filled cart. The customer completes checkout in the browser and returns to the chat for updates. This suits brands with real inventory systems where WhatsApp is the discovery and support layer rather than the transaction layer.
Cash on delivery still matters in large parts of India, and it should be a visible button option rather than something the customer has to ask for. If you offer it, use the confirm step to reconfirm the address and the exact amount to keep ready, because COD refusals at the door are expensive.
How a WhatsApp sale runs end to end in 6 steps
- The customer starts the conversation. Usually from a click-to-WhatsApp ad, a link on your site, a QR code in your shop, or your Instagram bio. This inbound message is what gives you the 24-hour service window in which you can reply freely without templates.
- Route them with a short menu. A button or list message offering browse, reorder, track order, or talk to a person. Three or four options, no more. This single message decides whether the next step is a catalog or a direct answer.
- Show the product. Send the catalog for browsers, or a single product message for someone who described what they want. Answer follow-up questions in the same thread with photos or a short video where it helps.
- Capture the order with structured steps. Variant by list message, quantity by buttons, address as one formatted block. Then read the whole order back and get a tapped confirmation.
- Send the payment link and watch for the result. UPI link, gateway checkout, or website cart. Move the conversation to "awaiting payment" in your pipeline, and set a reminder to follow up if nothing lands within a few hours.
- Confirm, dispatch and follow up. Send an order confirmation with the order ID, then a dispatch message with the tracking link, then a delivery check-in. If any of these go out after the 24-hour service window has closed, they must use an approved template.
The rules you cannot design around: opt-in and templates
Two constraints shape every WhatsApp commerce flow on the official API, and it is much cheaper to learn them now than after a broadcast gets blocked.
Opt-in. You need permission before you message someone who has not messaged you. A customer who starts a chat with you has effectively opted in for that conversation, but a phone number scraped from an old order sheet has not. Build your permission list deliberately; our guide on how to build a WhatsApp opt-in list covers the checkout checkbox, the QR code and the missed-call routes that work in India.
Approved templates for business-initiated messages. Inside the 24-hour window that opens when a customer messages you, you can reply with free-form messages including catalogs and product cards. Outside that window, any message you initiate must use a template approved by WhatsApp in advance. In practice this is fine for commerce, because the messages you most want to send outside the window are exactly the transactional ones templates are designed for: order confirmed, payment received, order dispatched, out for delivery, and a post-purchase check-in. Write and submit these templates before you launch, not on the day you need them.
The trap to avoid is treating templates as a promotional loophole. A "MEGA SALE" blast to every number you have ever spoken to is the fastest route to blocks, quality-rating drops, and eventually a restricted number. If promotional broadcasts are part of your plan, the campaign discipline in our WhatsApp marketing strategy for Indian D2C brands guide is worth reading before your first send.
WhatsApp-only selling vs website plus WhatsApp
Not every business needs a website to sell on WhatsApp, and not every business should abandon one. The honest comparison looks like this.
| Consideration | WhatsApp-only selling | Website plus WhatsApp |
|---|---|---|
| Time to first sale | Days. A catalog, a menu and a payment link are enough. | Weeks. Store build, product pages, payment gateway, shipping setup. |
| Best catalogue size | Small to mid. Scrolling hundreds of items in a chat is painful. | Any size. Search and filters do the heavy lifting. |
| Handling variants and stock | Manual. Someone must keep the catalog and real stock in sync. | Automatic if your store manages inventory. |
| Conversion on high-consideration items | Strong. A human answering doubts in real time beats a static page. | Weaker alone, strong when a chat button sits on the product page. |
| Reconciliation and reporting | Depends on your CRM. Without one, it is spreadsheets. | Built in through the store's order dashboard. |
| Who it suits | Boutiques, home bakers, local retail, service businesses, custom-order sellers. | D2C brands, larger catalogues, businesses already running paid ads to a site. |
Most growing Indian businesses end up in the second column eventually, but start in the first. That progression is fine. What is not fine is running both without connecting them, so that website orders live in one system and WhatsApp orders live in an agent's phone. Whichever route you take, the conversation history and the order state should sit in one place your whole team can see.
What to do in your first two weeks
A realistic starting plan, in order. Build the catalog with your fifteen best-selling items, not your entire range. Write the four transactional templates you will need: order confirmed, payment received, order dispatched, delivery check-in. Design a four-option opening menu. Decide your payment method and test the link end to end with your own phone, including the refund path. Then run it manually for a week with one person watching every conversation, and note every place a customer got confused. Those notes are your automation backlog.
Only after that should you expand the catalog, add more chatbot branches, or start broadcasting. Businesses that automate before they have watched real conversations automate the wrong things.
Turn WhatsApp into a sales channel your team can actually run
ZupiChat gives you a shared team inbox, a no-code chatbot, labels and pipeline, broadcasts through approved templates, and analytics on one official WhatsApp Business API number. Built in India, priced in INR, live in under 24 hours.
Start your free 14-day trialFrequently Asked Questions
Do I need a website to sell on WhatsApp?
No. A WhatsApp catalog, a structured chatbot menu and a payment link are enough to take orders end to end, which is why boutiques, bakers and local retailers sell on WhatsApp without any site. A website becomes worth building when your catalogue grows past what is comfortable to scroll in a chat, or when you want automatic stock and order management.
How do customers actually pay me on WhatsApp?
Most Indian businesses send a UPI payment link or QR in the chat, send a payment gateway checkout link tied to the order, or deep-link the customer to their website cart. Cash on delivery remains common too. WhatsApp's native in-chat payment features vary by market and change over time, so check what is currently enabled for your own account before designing around it.
How many products can I list in my WhatsApp catalog?
The platform limit is generous, but the practical limit is much lower. Customers browse a catalog on a phone screen inside a chat window, so anything past roughly twenty to thirty items becomes tiring to scroll. List your best sellers and seasonal items, group them into clear sections, and use a chatbot menu to route people to the right group instead of making them scroll everything.
Does WhatsApp selling work for services, not just physical products?
Yes, and often better. Service businesses use catalog entries for packages with a starting price, list messages for choosing a slot or location, and button messages for confirming an appointment. The payment step is usually an advance or booking fee sent as a link. Salons, clinics, tutors, travel agents and repair services all run this pattern successfully.
What does it cost to sell on WhatsApp with ZupiChat?
ZupiChat plans start at Rs. 999 per month for Starter, and Rs. 2,499 per month for Growth, which includes 10 agents and API access. Pricing is in INR with Hindi and English support, and there is a 14-day free trial with setup completed in under 24 hours. WhatsApp's own conversation charges are billed separately by Meta based on your message volume.
