The WhatsApp order notifications playbook: what to send and when

Updated 2026-09-19 · 5 min read · By the Convo360 team

Why order notifications belong on WhatsApp

Indian shoppers check WhatsApp far more often than email or SMS. When an order status changes, a WhatsApp message gets opened within minutes, which is exactly when a customer wants to know it. Email order updates often sit unread; SMS is limited to 160 characters and cannot carry a tracking button.

The trade-off is that WhatsApp notifications must follow Meta's rules. You cannot free-text a customer about their order unless they messaged you first within the last 24 hours. Outside that window, you need a pre-approved template. This is what makes order notifications a template-driven, event-triggered system rather than a chat.

The customer segment matters too. A prepaid buyer mainly wants proof the order is moving; a cash-on-delivery buyer wants a stronger signal because they haven't paid yet and is more likely to forget the order exists by the time the courier arrives. Treat COD orders with a slightly firmer notification set: mention the amount payable in the out-for-delivery message so there are no surprises at the door, and consider a same-day morning nudge for COD deliveries scheduled that day.

The six events worth sending

Resist the urge to notify on every internal status change. Customers care about six moments:

• Order confirmed: reassures the payment went through.
• Packed: optional; skip this for fast-moving categories where it adds noise.
• Shipped: include the courier name and AWB number.
• Out for delivery: the highest-value message; many customers plan their day around it.
• Delivered: closes the loop and is a natural place to ask for a review.
• Delayed: sent only when the shipped-to-delivered gap crosses your threshold, with a revised date.

Six is already generous. If your catalogue ships same-day, drop 'packed' entirely and keep four events. Use the table below as a quick reference for who should trigger each event and how consistently it should fire:

Utility templates, not Marketing

Order notifications are transactional, so they should be submitted to Meta as Utility templates, not Marketing. Utility templates are reviewed against a narrower policy (they must relate to an existing transaction), but they are more likely to be approved quickly and are priced differently from Marketing sends. See Meta's own category rules at business.whatsapp.com before you submit.

A common rejection reason is mixing a discount code or upsell line into what should be a pure status update. Keep each template to one job: status plus a tracking link, nothing promotional. A typical 'order_shipped' Utility template reads something like: 'Hi {{1}}, your order #{{2}} has shipped via {{3}}. Track it here: {{4}}. Reply STOP to opt out of order updates.' Keep the same structure for every event, name, order number, one status line, one link, so customers recognise the format instantly and don't need to read closely to know what happened.

Building the flow on Convo360

1. In WhatsApp Studio, create one template per event, for example 'order_shipped' with variables for name, AWB and courier, and submit each for Meta approval.
2. In your order system (Shopify, WooCommerce or a custom cart), configure an outbound webhook that fires on each status change.
3. In Flow Builder, add an inbound webhook trigger that receives this event and maps fields into a Send Template block using Set Variable.
4. Add a Condition block so 'delayed' only fires when the gap between shipped and delivered timestamps crosses your limit.
5. Turn on Preview / Try-it to dry-run the flow with sample payloads before going live, and check the health-check warnings for any dead ends.

See /docs/webhooks/ and /docs/templates/ for the exact field mapping steps.

Handling replies and opt-outs

Once a customer replies to a notification, such as 'where is my parcel', you are inside the 24-hour service window and can reply freely with an AI Reply or route to your team inbox. Set up a keyword trigger for common words like 'cancel', 'return' or 'wrong address' so these branch to the right sub-flow instead of a generic answer. A customer replying 'change address' on an out-for-delivery message, for example, should route straight to a human or a reschedule form rather than get a templated response that doesn't help.

Every template must let a customer opt out, and STOP-style requests must be honoured immediately; this is a WhatsApp platform policy, not just good practice. Convo360's contact groups let you tag opted-out numbers so no future template reaches them, and it's worth reviewing this list monthly since customers occasionally opt back in by messaging you directly.

What this costs

You pay Meta directly for each template message at Meta's published Utility message rate. Convo360 adds no per-message markup because the platform runs on BYOK. Your own WhatsApp number and Meta billing account are used throughout. Budget by estimating notifications per order (typically 3–4) multiplied by monthly order volume; see /blog/whatsapp-conversation-pricing-india/ for how Meta's pricing model works.

Measuring whether it's working

Track three numbers in Flow Logs and Analytics: the delivery rate on each template (a falling rate often points to an expired opt-in or a wrong number format from checkout), the reply rate on 'out for delivery' (a spike usually means customers have questions about access, timing or building instructions for the courier), and the opt-out rate over a rolling month. A rising opt-out rate on notifications customers generally want is a signal you've added too many events or the wording feels repetitive rather than useful.

It also helps to compare 'where is my order' support ticket volume before and after switching on notifications. A well-built set of order updates should visibly reduce this ticket category, since most customers get their answer before they think to ask for it. That reduction, more than any single open-rate number, tells you the playbook is paying for itself.

Step by step

1. Create Utility templates for each eventDraft 'order_confirmed', 'order_shipped', 'out_for_delivery', 'order_delivered' and 'order_delayed' in WhatsApp Studio and submit for Meta approval.
2. Connect your order system webhookPoint your cart platform's status-change webhook at Convo360's inbound webhook URL for this flow.
3. Map fields in Flow BuilderUse Set Variable to pull customer name, AWB and courier from the webhook payload into the template variables.
4. Add the delay conditionInsert a Condition block comparing shipped and current timestamps; branch to the delayed template past your threshold.
5. Test with Preview before going liveRun sample payloads through Try-it mode and check Flow Logs for any dead ends before publishing.

Example conversation

Frequently asked questions

Related reading

Available across India — see WhatsApp & AI calling automation by state and city.