WhatsApp Commerce in India — Complete 2026 Guide

1. What is WhatsApp commerce?

WhatsApp commerce is the practice of running buying and selling activity inside WhatsApp — product discovery, ordering, payments, customer support, and post-purchase notifications. It moves the storefront from a website or app to the chat thread, where the average Indian smartphone user already spends ~38 minutes a day. The tools are Meta-issued: a business profile, a product catalog, the WhatsApp Business API for scale, message templates approved by Meta, and (since 2023) WhatsApp Flows for multi-step forms.

The model that wins in India differs from the model that wins in the US. American merchants treat WhatsApp as a customer-support auxiliary; Indian merchants treat it as the primary channel and push 60–90% of order volume through it.

2. Why India is the WhatsApp commerce market

India has more WhatsApp users than any other country — over 500 million monthly actives — and the gap between WhatsApp's reach and any competing messaging app is wider than anywhere else in the world. Three structural factors compound this advantage:

• App fatigue is real. Tier-2 and Tier-3 customers resist installing yet another retailer-specific app. Selling inside an app they already use removes the install funnel.
• UPI changes the payment economics. Indian customers expect to pay via a single UPI tap. WhatsApp + UPI is a one-screen checkout that no website-based competitor can match for friction.
• Vernacular communication is native. WhatsApp supports any Unicode language; voice notes and forwarded media are first-class. A Hindi-speaking small-town customer can shop from a Bengaluru D2C brand without language being a barrier.

3. WhatsApp Business API vs Business App

The single biggest decision is which tier you operate on. The two are different products with different ceilings.

Most merchants start on the Business App and graduate to the API once they hit the 256-contact broadcast cap or need a second person handling chats. See the App glossary entry and the API glossary entry for deeper definitions.

4. Cost structure (Meta pricing in INR)

Meta charges per conversation — a 24-hour window between your business and one customer phone number — not per message. That window is bucketed into one of four categories. Indian wholesale rates as of 2026:

• Marketing — promotional content, offers, abandoned cart, product launches: ~₹0.78 per conversation
• Utility — order confirmations, shipping updates, payment receipts, appointment reminders: ~₹0.114 per conversation
• Authentication — OTPs and login codes: ~₹0.114 per conversation
• Service — replies inside the 24-hour window after a customer message: free

Two implications matter. First, route every transactional alert as Utility — sending an order confirmation as Marketing costs 6.8× more for identical content. Second, design support flows so as many replies as possible happen inside the free Service window.

Use the conversation cost calculator to estimate your monthly bill. See conversation-based pricing and conversation category for definitions.

5. Compliance: DPDPA, GST, RBI, Meta

Four overlapping rule-sets govern WhatsApp commerce in India. Ignore any one of them and the business gets penalised in a different way — Meta number bans, RBI-side payment freezes, GST mismatches in returns, or DPDPA notices.

1. DPDPA 2023. Capture explicit, timestamped opt-in for marketing messages. Allow customers to withdraw consent at any time and act on the withdrawal within reasonable time. Maintain an audit log.
2. GST. Every taxable supply needs a GST invoice with GSTIN, HSN/SAC, taxable value, tax breakup, and (above the e-invoicing threshold) an IRN from the IRP portal. The invoice goes via WhatsApp as an attachment but the underlying record lives in your books.
3. RBI / payment-aggregator rules. Money flows through a licensed payment aggregator — Razorpay, PhonePe, Paytm — never directly between buyer and seller bank accounts on WhatsApp itself.
4. Meta Commerce Policy. No prohibited categories (alcohol, tobacco, weapons, certain financial products), no spam, no scraped lists, no pretending to be a different brand. Repeated violations get the WABA banned.

6. Choosing a WhatsApp BSP

You access the WhatsApp Business API through a Meta-authorised Business Solution Provider (BSP). The BSP layer is where most of the merchant experience is differentiated, because Meta's API itself is uniform.

Evaluate BSPs on these dimensions:

• Cloud API, not legacy. If a BSP is still pushing On-Premise, walk away — Meta is sunsetting it.
• Transparent INR pricing. Meta wholesale rate passed through, with the platform fee separately listed.
• India-native integrations. Razorpay, PhonePe, Paytm, UPI deep links, Shiprocket, Tally, Marg, Zoho.
• GST + e-invoice IRN automation. Critical above the ₹5 crore turnover threshold.
• Opt-in capture + quality monitoring built in. A BSP that lets you import a list without an opt-in source field is setting you up for a number ban.
• India-based support team. When templates fail at 11pm before a campaign, IST support matters.

See the BSP glossary entry for a list of common Indian BSPs and how WatEase compares.

7. Getting started — the 90-minute path

For a merchant with a verified GSTIN and a Razorpay/PhonePe account, the fastest path from zero to live WhatsApp commerce looks like this:

1. Sign up on WatEase Free Forever at /auth/register. (≈5 min)
2. Connect Meta Business Manager. Authorise WatEase as a partner; Meta runs Business Verification using PAN + GSTIN docs. (≈30 min interactive + 24–48h Meta review)
3. Provision the phone number. Use a clean, unused number — landline, mobile, or virtual — that hasn't been on WhatsApp Business App previously. (≈10 min)
4. Import or build the catalog. CSV upload from Shopify, Tally, Marg, or manual. (≈15 min)
5. Submit your first templates. Order confirmation, shipping update, payment receipt, abandoned-cart reminder. WatEase ships pre-validated India templates as a starting point. (≈10 min, Meta auto-approves in 5–10 min)
6. Capture opt-in on your website, checkout, and click-to-WhatsApp ads. (≈10 min for the WatEase-provided embed.)
7. Test send. Send a single template to your own number, verify delivery, screenshot for the audit log. (≈5 min)
8. Go live. Switch on the order-confirmation automation, drip campaign, or whichever flow you start with.

8. Broadcasts that don't get you banned

The single fastest way to destroy a WhatsApp Business presence is to broadcast aggressively to a low-quality opt-in pool. Meta tracks block and report rates per phone number, drops your quality rating to Yellow then Red, throttles your messaging tier from the 100,000-customer ceiling down to 250, and eventually bans the number.

Rules of thumb that keep numbers healthy in production:

• Only message customers who have opted in within the last 90 days for marketing-category content.
• Segment broadcasts: never send the same campaign to your entire list. 5,000–10,000 per send keeps quality signals manageable.
• Provide a one-tap STOP / opt-out button in every Marketing template. Honour STOP requests within 24 hours.
• Watch quality rating in real time. Pause sends the moment it drops to Yellow.
• Lead with value, not promotion. The first message in a sequence should give the customer something useful (delivery slot booking, GST invoice, festival reminder) — promotional content lands better after trust is established.

9. Catalog + checkout on WhatsApp

The WhatsApp catalog is Meta's native commerce surface — a list of products with images, prices, descriptions, and SKUs that customers browse from inside the chat. Customers can add items to a cart and send the cart back as a single ordered message. The business receives that cart as a structured order object and responds with a payment link or confirmation. See the catalog glossary entry for the full definition.

Best practice for Indian merchants: keep individual catalog messages to one Collection at a time (10–15 SKUs) rather than dumping the entire catalog. Use product images that show the product clearly at thumbnail size — Indian customers are often on moderate-bandwidth connections.

10. Payments: Razorpay vs PhonePe vs Paytm

All three are RBI-licensed payment aggregators. Differences that actually matter for WhatsApp commerce:

• Razorpay — broadest method coverage (UPI, cards, net banking, wallets, EMI), best developer experience, deep Tally and Zoho integration. Default choice for D2C and SaaS.
• PhonePe — strongest UPI conversion in Tier-2/3, lowest UPI fees, weaker on cards. Default choice for mass-market consumer brands.
• Paytm — POS + online unified, strongest if the business already runs Paytm POS in physical stores.

WatEase ships native integrations with all three; switch in settings without re-implementing. For most merchants we recommend starting with Razorpay and adding PhonePe later if Tier-2/3 UPI conversion becomes a bottleneck.

11. GST-compliant invoicing on WhatsApp

The flow that satisfies GST reviewers and keeps customers happy:

1. Customer pays via Razorpay/PhonePe/Paytm. The aggregator confirms payment to the merchant via webhook.
2. WatEase generates the GST invoice in PDF — GSTIN, HSN/SAC code, taxable value, tax breakup, place of supply, IRN if e-invoicing applies.
3. If the merchant's turnover crosses the e-invoicing threshold, WatEase calls the IRP portal to fetch the IRN and embeds the QR + signed JSON in the PDF.
4. The PDF is attached to a Utility-category template message and sent to the customer's WhatsApp.
5. The invoice is stored in the merchant's tenant for retrieval and synced to Tally / Zoho / Marg if those connectors are enabled.

Total time from payment confirmation to customer receiving the invoice on WhatsApp: typically under 10 seconds.

12. Customer support automation

The economic argument for automating support on WhatsApp is simple: replies inside the 24-hour Service window are free, and an LLM-driven first-line bot can resolve 60–80% of common queries (order status, return policy, store hours, delivery slot) without human involvement. The remaining 20–40% are routed to human agents who pick up where the bot left off.

Three rules for support automation that doesn't frustrate customers:

• Show the customer it's a bot in the first message. Trying to pass off a bot as a human destroys trust the moment it slips.
• Always offer a one-tap escalation to a human agent. Don't hide it behind 5 menu levels.
• Hand off context to the human, not just the customer. The agent should see the bot's last 6 messages and the customer's order history without asking again.

13. Industry-specific playbooks

Different verticals optimise WhatsApp commerce differently. The dedicated industry pages cover the full playbook per vertical; short summary here:

• Retail — catalog + COD + UPI checkout
• Healthcare — DPDPA-aligned appointments + reminders
• Food & restaurants — daily menu + delivery zones
• Jewellery — rate updates + custom orders + festive sales
• Education — admissions + fees + parent comms
• Real estate — inquiries + site visits + closings
• Automobile — test drives + service reminders
• Financial services — KYC + premium collection
• Agriculture — mandi prices + farmer-to-buyer
• Grocery — daily orders + recurring subscriptions
• Hospitality — booking-to-checkout guest flow
• Logistics — shipment tracking + reschedules

See all 19 verticals on the industries index.

14. Frequently asked questions