WhatsApp E-commerce in India, Walked Through: How One D2C Order Actually Moves

The order arrives

It is 9:47 pm on a Wednesday. A small D2C skincare brand based in Bengaluru — let's call it a hypothetical order for a serum bottle from an Indore-based customer — receives a Shopify order notification. The customer paid ₹899 via Google Pay UPI at checkout. The Shopify webhook fires; the WhatsApp automation catches it within seconds.

The first WhatsApp message goes out to the customer immediately: order number, itemised list, delivery address confirmation, an estimated delivery window (3-5 business days for Indore from Bengaluru fulfilment), and a note that the customer will receive a tracking link once the courier picks up. The message is in English and Hindi — the customer's phone locale preference informs which language the automation defaults to; automation offers a language-switch reply.

The customer replies within twenty minutes to confirm the delivery address is correct. This reply extends the WhatsApp service window to 24 hours from the customer's message — Meta's rules mean the merchant can respond freely for the next 24 hours without a template.

Fulfilment handoff

The next morning, the brand's warehouse team packs the order. Their Shopify app has an integration with Shiprocket — India's dominant multi-carrier logistics aggregator. The warehouse manager selects a carrier partner (Delhivery in this hypothetical, based on Shiprocket's rate-comparison for the pincode) and generates a shipping label. Shiprocket's webhook fires when the label is created; the WhatsApp automation catches this and sends the customer an AWB (airway bill) number and a Shiprocket tracking link.

At 2:14 pm the same day, Delhivery's pickup service collects the parcel from the warehouse. Shiprocket's status update webhook fires again; the WhatsApp automation sends 'Your order is out for pickup — Delhivery will scan it on arrival at the sorting facility, and you'll receive an in-transit update tonight.'

That evening, Delhivery scans the parcel at their Bengaluru sorting facility. Automation dispatches: 'Update — your order is at Delhivery Bengaluru facility, on the way to Indore. Expected delivery: Sunday.'

The Sunday delivery attempt

Sunday morning, Delhivery's rider messages the customer directly from their own app to confirm the delivery window. The Delhivery communication is outside the brand's WhatsApp workflow but visible via Shiprocket's tracking updates.

The delivery attempt at 11:30 am fails: the customer's phone is on silent (Sunday morning), the doorbell isn't heard. Delhivery marks the parcel as 'Attempt failed — customer not available'. This triggers a Shiprocket webhook that the brand's automation catches.

This is the moment where WhatsApp automation matters most. Without intervention, this order is on the path to RTO (Return to Origin). Indian D2C brands lose meaningful margin to RTO — Delhivery's return charge, the loss of the sale, the warehouse re-processing time. A 5-10% RTO rate on a ₹899 product against typical D2C margins is real revenue.

The automation sends the customer a WhatsApp message immediately: 'The Delhivery rider tried to deliver at 11:30 am but couldn't reach you. To reattempt, reply with a preferred time slot: (1) tomorrow morning, (2) tomorrow evening, (3) call back now.' The customer replies '2'. The automation confirms 'Delivery reattempt scheduled for Monday evening. Delhivery will confirm the two-hour window in advance.' It also updates the Shiprocket API with the customer's preference so Delhivery's rider gets the message.

This flow — capture-preferred-time before RTO fires — is where WhatsApp automation returns concrete value for Indian D2C. The alternative (customer discovers failed delivery only when checking Shiprocket the next day) is where RTO happens.

Second attempt and review capture

Monday evening, delivery succeeds at 7:45 pm. Delhivery marks the AWB as delivered; Shiprocket's webhook fires; the brand's automation sends the customer 'Order delivered — thanks for your patience Sunday. If anything's not right when you unbox, reply here in the next 48 hours and we'll sort it.' The 48-hour window matches the brand's own product-return policy and creates a natural early-intervention channel.

Seventy-two hours later, if no complaint has arrived, automation dispatches: 'Hope the serum's working out. When you have a moment, could you share your experience? Reply with a photo and a short note, or tap this link to leave a review on our site.' This is a marketing-category conversation under Meta's rules, requiring the customer's marketing opt-in — which was captured at Shopify checkout via the standard opt-in checkbox.

The merchant's data captures the whole trail: Shopify order record, Shiprocket carrier events, WhatsApp conversation history, customer reply time distribution, and eventually the review. This is the operational data that lets the brand improve carrier selection, understand which cities are attempt-failure prone, and prioritise product improvements based on unsolicited early feedback.

Why this specific pattern

The workflow described works because it respects three constraints:

The DPDP Act 2023 compliance floor. The customer's phone number was collected at checkout with clear-purpose consent for order communication; the marketing consent was captured separately for review-request messaging. Each Meta template used matches the applicable purpose.

Meta's conversation-category rules. Order status updates fall under utility conversations (roughly USD 0.0035 per 24-hour window in India per the 2025 pricing update); review requests fall under marketing conversations at higher rates. Mixing them creates cost inefficiency and compliance risk.

The operational reality of Indian D2C logistics. Attempt-failure interventions before RTO fires, courier-partner-neutral status messaging (the customer doesn't care whether it's Delhivery or Ecom Express, only that their order is coming), and language-preference detection all reflect what Indian D2C brands actually need.