Shipping and delivery updates for D2C brands in India
Order and delivery notifications for an Indian retail store means pushing every fulfilment milestone — confirmed, packed, dispatched, out for delivery, delivered — into the buyer’s WhatsApp thread as an approved utility template, with the courier tracking link and the GST invoice attached. The buyer stops asking where the order is, because the thread already told them.
Built for Indian businesses 🇮🇳 · Plans from ₹1,999/month · 0% markup on WhatsApp messages
What the customer actually sees
Not a mock-up of a feature — the real message shape for a retail & e-commerce business, in the price band and language this vertical works in.
WhatsApp Business
WhatsApp Business API
- Business: Order #KL-5231 confirmed — 1× Linen Shirt (L, Sand) ₹1,899. GST invoice attached. We’ll message you when it ships.
Utility template · invoice PDF attached
- Business: Dispatched via Delhivery, AWB 3812 4471 9902. Expected delivery Thursday 14 Aug.Track shipment ↗
Triggered by courier manifest webhook
- Business: Out for delivery today. Your rider will call on the number ending 6979 — please keep the phone reachable.
Triggered by out-for-delivery scan
- Customer: I won’t be home till 6pm
- Business: No problem — I’ve requested an evening slot with Delhivery. If the rider still misses you, tap below to pick another day.Reschedule delivery ↗
Reschedule pushed to courier · no support agent involved
How it works
Wire the milestones
Order events from your storefront and scan events from your courier both feed WatEase, so confirmation, dispatch, out-for-delivery, delivery and failed-attempt each have a trigger with real data behind them.
Map each milestone to a template
Each event sends an approved utility template carrying the order number, the actual items, the AWB and the tracking link. The invoice PDF rides along with the dispatch message.
Handle the exception in the thread
A failed attempt or an unreachable buyer triggers a reschedule prompt with date options. The buyer picks one, the choice goes back to the courier, and nobody opens a support ticket.
What proactive delivery updates are actually worth
No invented ROI percentages — these are the mechanisms and the market facts behind them. Your numbers depend on your volume, and the dashboard measures each one.
~₹0.115
Meta’s published India price for a utility-category WhatsApp conversation (order/payment/delivery updates) — what a recovery or reminder nudge actually costs to send.
Source: Meta for Developers — WhatsApp pricing500M+
WhatsApp users in India — Meta has cited India as WhatsApp’s largest market worldwide.
Source: Meta NewsroomJuly 1, 2025
The date Meta transitioned WhatsApp Business Platform billing from per-conversation to per-message for template messages.
Source: Meta for Developers — WhatsApp pricingSupport tickets that never get raised
“Where is my order” is the single highest-volume query in Indian retail support. Pushing the milestone before the buyer wonders removes the reason to ask.
If 1,500 monthly orders generate status queries on even 20% of orders, that is 300 conversations an agent handles. At a few minutes each, that is roughly 15–25 agent hours a month spent restating information a webhook already knew.
Failed deliveries converted into rescheduled ones
An out-for-delivery alert plus an in-thread reschedule catches the buyer before the rider arrives, rather than after the attempt has already failed.
If 8% of your deliveries fail on first attempt and half of those failures are simply “nobody was home”, catching them in the thread turns parcels that would have started heading back into second attempts that succeed — each avoided RTO saving roughly ₹120 in two-way freight.
A GST invoice that actually reaches the buyer
The invoice PDF is delivered into the WhatsApp thread at dispatch instead of an email that goes unopened, so the buyer’s input-credit trail is intact and your accounts team stops re-sending it on request.
Every B2B or GSTIN-claiming buyer who receives the invoice in-thread is one fewer “please resend my bill” request at month end, and one fewer reconciliation gap for your accountant to chase.
The same 1,500 orders, two ways
| Without WatEase | With WatEase | |
|---|---|---|
| How the buyer learns the order shipped | A transactional email, if it clears the promotions tab | A WhatsApp message in the thread they already have open |
| Who answers “where is my order” | A support agent, one conversation at a time | Nobody — the answer arrived before the question |
| When a delivery is about to fail | You find out from the courier report, after the fact | The buyer tells you in the thread and reschedules themselves |
| Where the GST invoice ends up | An unopened email attachment | A PDF in the conversation, retrievable by search |
| Cost per update | Agent time, or an SMS that gets ignored | One Meta utility conversation, billed at cost with 0% markup |
Order volumes, ticket rates and first-attempt failure rates above are an illustrative scenario for working the arithmetic, not a claim about your store or an average across WatEase customers. Use your own helpdesk and courier data.
Set this up in WatEase
Five steps, each pointing at the actual screen you do it on. Most teams have this running the same day.
- 1
Connect the courier
Link Delhivery, Shiprocket or your 3PL so manifest, out-for-delivery, delivered and failed-attempt scans reach WatEase as real events rather than manual updates.
Settings → Integrations → Logistics
- 2
Submit the milestone templates
Submit one utility template per milestone — confirmed, dispatched, out for delivery, delivered, attempt failed — with variables for order number, items, AWB and tracking URL.
Marketing → Templates
- 3
Turn on invoice delivery
Enable GST invoice attachment on the dispatch message so the PDF lands in the thread with the correct HSN codes, rate and the buyer’s GSTIN where supplied.
Settings → Invoicing
- 4
Build the reschedule flow
Add a reschedule prompt to the failed-attempt and out-for-delivery templates, with date options that push the buyer’s choice back to the courier.
Automation → Journeys
- 5
Route the replies
Point the thread at your shared inbox so a buyer who replies with something the automation cannot answer reaches a human without losing the order context.
Inbox → Routing rules
What Indian retail fulfilment demands from a notification stack
Indian delivery is not a solved problem the way it is in single-courier markets. Multiple 3PLs, address quality that varies enormously, and a large first-attempt failure rate mean the notification layer is doing operational work, not just reassurance.
- Address quality outside metros is genuinely poor, and the rider’s phone call is often the real delivery mechanism. An out-for-delivery alert that tells the buyer to keep their phone reachable measurably helps.
- The GST invoice must accompany the goods and carry the correct HSN code and rate. Delivering it into the WhatsApp thread means the buyer can retrieve it by search months later.
- Most retail brands run more than one courier by pincode. Notifications have to normalise across them, or the buyer gets inconsistent messages depending on who happened to pick up the parcel.
- Status updates are utility-category conversations about the buyer’s own order — they do not require marketing consent and are priced below marketing sends.
- Regional language matters at the delivery step more than anywhere else in the funnel, because the person receiving the parcel is often not the person who placed the order.
Frequently asked questions
Which delivery milestones should I actually send?
Confirmed, dispatched with tracking, out for delivery, and delivered — plus a failed-attempt message with a reschedule option. Packed and in-transit updates usually add noise without adding information the buyer can act on.
Will this many messages annoy customers?
These are utility messages about the buyer’s own order, which is what people actually want. The risk of annoyance comes from marketing sends, not fulfilment updates. WatEase still applies frequency caps and quiet hours across all message types.
Does it work with multiple couriers?
Yes. WatEase normalises scan events across connected logistics partners so the buyer gets the same message shape whether the parcel went out on Delhivery, Shiprocket or your own fleet.
Can the customer reschedule a delivery from WhatsApp?
Yes, where your courier supports it. The reschedule prompt offers date options in the thread and pushes the selection back to the logistics partner, so no support agent has to relay it.
Is the GST invoice really sent on WhatsApp?
Yes — as a PDF attached to the dispatch message, generated with the correct HSN code, GST rate and the buyer’s GSTIN where they supplied one. It stays retrievable in the thread by search.
What does the whole sequence cost per order?
Four or five Meta utility conversations, billed by Meta at cost. WatEase adds 0% markup on WhatsApp messages, where most platforms add 20–25%. See the pricing page for the current utility rate.
What happens if the customer replies to a notification?
The reply lands in your shared inbox with the full order context attached, and can be routed to the right team or answered by an AI agent that already knows the order status.
What return can a retail & e-commerce business expect from order & delivery updates on WhatsApp?
Through specific mechanisms rather than a single ROI number: support tickets that never get raised; failed deliveries converted into rescheduled ones; A GST invoice that actually reaches the buyer. If 1,500 monthly orders generate status queries on even 20% of orders, that is 300 conversations an agent handles. At a few minutes each, that is roughly 15–25 agent hours a month spent restating information a webhook already knew. WatEase publishes no invented ROI percentages — your numbers depend on your volume, and the dashboard measures each mechanism.
Go deeper
Other jobs retail & e-commerce businesses run on WhatsApp
Order & delivery updates in other industries
The capabilities behind this
Zoom out to WhatsApp commerce for retail & e-commerce, or read order & delivery updates across every industry.
Capabilities and competitor comparisons reflect what we could verify as of June 2026. Worked examples on this page are illustrative scenarios, not averages across WatEase customers.