WhatsApp for D2C and e-commerce.
Cart recovery, COD confirmation and order updates on the official WhatsApp Business API. The flows that move revenue for Indian online brands, and the order to build them in.
Why WhatsApp works for Indian D2C
Two things make WhatsApp different from email for an Indian online brand. Almost everyone reads it, and almost nobody has an inbox habit that filters it. That cuts both ways: reach is real, and so is the cost of abusing it.
The other reason is cash on delivery. A large share of Indian e-commerce orders are COD, and every unconfirmed COD parcel that ships is a return-to-origin cost paid twice, once out and once back, plus stock sitting in transit. A confirmation message before dispatch is the cheapest intervention available, and it only works on a channel people actually answer.
The five flows, in build order
Build them in this sequence. Each one funds the next.
1. COD confirmation
Fires the moment a COD order is placed. A Utility template with confirm and cancel buttons, then tag by the response and hold the silent ones for a human call before dispatch. Start here, because it saves money on day one rather than generating demand you then have to fulfil.
2. Abandoned cart recovery
Fires 15 to 60 minutes after abandonment, exits the moment an order is placed. A Marketing template naming the actual item, with a button back to the cart. The exit condition matters as much as the copy: a reminder for something already bought is worse than no reminder.
3. Order and shipping updates
Confirmed, packed, dispatched, out for delivery. These are Utility templates, cheaper than Marketing, and they quietly reduce your "where is my order" support volume, which is usually the single largest ticket category.
4. Back in stock and price drop
Opt-in on the product page, message when it is true. Small audience, high intent, and the least likely message on this list to be resented.
5. Post-purchase and replenishment
Care instructions, then a review request once they have actually used it, then a replenishment nudge timed to when the product genuinely runs out. Your order data already tells you when that is.
What to connect
Order events should come from your store rather than being entered by hand. Weflux takes inbound webhooks, so Shopify, WooCommerce or a custom backend can trigger a flow and update the contact when an order is placed, paid, dispatched or cancelled. Outbound webhooks push the reply back, so a COD confirmation can mark the order ready to ship in your own system. Details in the API documentation.
Getting opt-in without wrecking checkout
The moments that work are the ones where the customer already expects contact: a checkbox at checkout that says plainly they will get order updates on WhatsApp, a click-to-WhatsApp ad, a back-in-stock request, an order-tracking link. What does not work is treating the delivery phone number as marketing consent. It is not, and the block rate will tell you so.
Keep transactional and promotional consent separate in your own records. Someone who wants shipping updates has not necessarily asked for Friday's sale, and conflating the two is the fastest way to lose both.
Watch the quality rating during sale periods
Sale season is when brands send the most and segment the least, and it is when quality ratings drop. A rating fall during your highest-revenue week restricts the number exactly when you need it. Send to segments rather than the whole list, keep promotional frequency defensible, and check the rating after each large send rather than at the end of the campaign.
Common questions from D2C brands
Related
- Automations for building these flows
- Broadcasts for launches and sale campaigns
- WhatsApp CRM for segmenting by order history
- API and webhooks for connecting your store
- All industry playbooks
Start with COD confirmation.
Connect your store, approve one Utility template, and measure it against a holdout. The free plan covers the whole loop.