A practical guide to WhatsApp commerce for Indian D2C brands: opt-in, message types, catalogue, order updates, support, what to automate, and the mistakes that get a number blocked.
For an Indian D2C brand, WhatsApp is not one channel among many. It is where customers already are, where they ask questions, and where they expect a reply the same evening. That makes it the highest-trust channel a store has, and the easiest one to burn. The same number that delivers an order update a customer is grateful for can, three broadcasts later, be blocked and reported. This post is about doing it well: what to send, what not to, and where the line is.
Start with the right kind of account
There are two tools with similar names. The WhatsApp Business app is free, runs on a phone, and is fine for a store doing a handful of conversations a day. The WhatsApp Business Platform, usually called the API, is what you need once you want messages triggered by your Shopify store, more than one person replying, templates approved in advance and a proper record of every conversation. Access to the API comes through Meta directly or through a business solution provider, and most Indian brands use a provider that already has a Shopify integration.
Either way, the number should be the brand's, not a founder's personal number, and it should be verified with the business name and profile that customers will recognise. People reply to a name they trust and ignore a string of digits.
Before choosing a provider, check three things against your Shopify store: whether it can trigger messages from Shopify's own order and fulfilment events rather than from a nightly export, whether the shared inbox shows the customer's order history beside the chat, and whether you can export your conversations and opt-in records if you leave. Providers differ more on these than on price, and the differences only become visible once you are locked in.
Opt-in is the foundation, not a formality
Every marketing message you send needs the customer's permission first, and permission you did not clearly get is permission you do not have. Meta enforces this through quality ratings: when enough people block or report a number, its messaging limits drop, and the channel you built stops working. Legal compliance matters, but the practical reason is simpler. A list of people who agreed to hear from you performs; a list of everyone who ever ordered does not.
- Collect opt-in at the moments people are glad to give it: a checkbox at checkout, a prompt after a delivery, a sign-up on the product page for restock alerts.
- Say what they are opting into and how often. 'Order updates and occasional offers' is a promise; keep it.
- Keep the record. Store when and where each customer opted in, so that a complaint can be answered with a fact.
- Make opting out effortless. A reply of 'STOP' should work, and should be honoured the same day.
Know the message types and what each is for
On the API, messages fall into categories, and each behaves differently. Template messages are pre-approved formats you send to start a conversation: order confirmations, shipping updates, a marketing offer. They are classified as utility, marketing or authentication, and pricing and rules differ by category. Once a customer replies, a service window opens in which you can send free-form messages for a limited time, which is where real support conversations happen.
- Utility templates carry information the customer expects: confirmation, dispatch, out for delivery, delivered, refund processed. Send all of them.
- Marketing templates are the broadcasts. Send fewer than you think, to people who asked, with something worth opening.
- Interactive messages, with buttons and lists, cut friction: 'Track order', 'Talk to a person' and 'Reorder' as buttons instead of typed replies.
- Free-form replies inside the service window are where a human should be, because that is when the customer has something specific to say.
The catalogue and the path to a paid order
WhatsApp lets a business publish a catalogue and share individual products or a set of them inside a chat. For a store already on Shopify, the practical approach is to keep Shopify as the source of truth for products, prices and stock, and sync the catalogue from it rather than maintaining two lists by hand. A catalogue that shows a sold-out product or last month's price is worse than no catalogue at all.
The checkout itself can happen in a few ways: a link into the Shopify cart with the products pre-added, a payment link generated from a draft order, or in-chat payment where it is available and suits your flow. What matters is that the order lands in Shopify as a normal order, with inventory adjusted and the customer record intact, so that fulfilment, returns and reporting work the same way as for a web order. A WhatsApp order tracked in a spreadsheet is a problem waiting for the GST return.
Order updates: the messages people actually want
If you automate only one thing, automate the transactional messages. Confirmation within a minute of the order, a dispatch message with a tracking link, an out-for-delivery message on the day, and a delivered message that invites a reply if something is wrong. These are the messages customers screenshot and forward. They reduce 'where is my order' enquiries more than any FAQ page, and they build the trust that makes a later marketing message welcome.
Wire them to real events. Shopify emits webhooks when an order is created, paid, fulfilled or refunded, and each fulfilment carries the tracking number. A message triggered by the actual fulfilment is accurate; a message scheduled 'two days after the order' is a guess that will be wrong during festive season. If your provider cannot map these events cleanly, that small piece of integration is the kind of custom work we do at LeelaRam Technologies, and it is usually a job of days rather than a project.
Support: what to automate and what to keep human
The honest rule is that automation should handle the questions with one correct answer and hand over everything else. Where is my order, what is your return policy, do you ship to this pincode, what are the sizes: these can be answered by a menu or a bot, instantly and accurately, and customers prefer it that way at eleven at night. Anything involving a complaint, a damaged item, a custom request or a customer who is upset should reach a person quickly, with the conversation history in front of them.
- Build a short menu for the top five questions, based on what your inbox actually receives, not what you imagine it receives.
- Set a clear handover path: a 'Talk to a person' button that routes to a staffed inbox with the customer's order history attached.
- Publish your support hours in the greeting, and have an away message that says when someone will reply.
- Give the humans canned answers for the common cases so that a reply is fast without sounding like a machine.
Broadcasts without becoming spam
Marketing messages are where brands lose the channel. The failure pattern is familiar: the same offer to the whole list, twice a week, at nine in the morning, with a big image and a coupon. Within a month the open rate drops, block reports climb, and the number's quality rating falls with them. Broadcasts work when they are rare, specific and useful to the person receiving them.
Festive season is the sharpest test. In the weeks before Diwali every brand a customer has ever bought from sends an offer, and the inbox becomes a wall of coupons. The broadcasts that survive are the ones that read like a message from a shop the customer likes: a delivery cut-off reminder for people with items in their cart, a gifting guide sent once, a restock note to the people who asked for it. One useful message in October earns more than five offers, and it is still welcome in December.
- Segment by behaviour: a restock alert to the people who asked, a launch to buyers of that category, a festive offer to customers who bought last Diwali.
- Send at times that suit the customer, not the marketing calendar, and never more than a few times a month unless the customer chose a higher frequency.
- Lead with the reason to open in the first line, because that is all the notification shows.
- Watch the quality rating and block rate after every broadcast. A rising block rate is the customer telling you to stop; listen before Meta makes you.
Common mistakes, and how to measure honestly
The mistakes are consistent across brands: importing a customer list without consent, using a personal number that leaves with the employee, sending marketing messages inside what should be a service conversation, and treating every reply as a lead to be pushed rather than a question to be answered. Each of these is fixable, and each one is cheaper to fix before the number is restricted than after.
Measure the channel by what it changes, not by message volume. Track replies per broadcast, orders attributed to a WhatsApp link, the share of support conversations resolved without a human, and the block and opt-out rate. In our experience the last number is the one that predicts whether the channel will still be working in six months. A store whose customers keep the number saved and unmuted has built something most competitors have not.
