Order Status Update

1. 1

   Map your fulfilment events

   List the events your store, warehouse and courier already emit — created, packed, handed over, out for delivery, delivered, failed attempt, cancelled — and decide which ones change what the customer does.

2. 2

   Create one utility template per stage

   Write factual templates with variables for order number, items, courier and date, and a URL button with a dynamic suffix for tracking. Mixed content is treated as marketing, so keep offers out.

3. 3

   Trigger from events, not schedules

   Send each template the moment its event fires, to customers whose opt-in is on record. Set a time-to-live so an out-for-delivery message cannot arrive the day after.

4. 4

   Handle the replies

   A reply opens the customer service window. Route change-address and cancel requests to an agent or bot fast, before the next fulfilment step makes them harder.

5. 5

   Measure and trim

   Track delivery, read and reply rates per stage alongside where-is-my-order contacts. Drop updates nobody reads and rewrite the ones that create questions.

Template category

Utility — no promotional content

Charge (India)

₹0.19 per delivered template

Inside an open window

Utility templates charged since 1 October 2026

Utility time-to-live

Default 30 days; custom 30 seconds to 12 hours

Tracking button

URL button; one variable, at the end of the URL

Core stages

Confirmed, shipped, out for delivery, delivered

• Bolting on a promotion

  A "10% off your next order" line turns a shipping update into marketing content that Meta can recategorise and charge at the marketing rate. Send offers separately, to customers who opted in to marketing.

• Messaging every internal event

  Customers do not need picked, packed and manifested as separate messages. Every extra update costs money and attention; keep to the stages that change what the customer does.

• Tracking links that fail on a phone

  A link to a courier's homepage or a desktop-only tracking page defeats the purpose. Use a dynamic URL button that opens this order's mobile tracking page directly.

• Updates that arrive late

  Without a short time-to-live, an "out for delivery today" message can land after the parcel did. Set the TTL on time-sensitive templates so stale updates expire undelivered.

• Nobody reading the replies

  Customers answer updates with real problems — wrong address, not home today. If no one watches those replies, the update creates frustration instead of preventing it.

• Put the order number in the first line of every update.
• For cash-on-delivery orders, state the exact amount in the out-for-delivery message.
• Keep the wording consistent across stages so customers recognise your updates at a glance.
• Add a Need help quick reply to exception messages so a support conversation opens in one tap.

"Where is my order?" is one of the biggest sources of support contacts for anyone who ships goods. Well-timed updates on the channel customers actually read are the simplest form of proactive support: they cut those contacts, reduce failed deliveries — a customer who knows the parcel is out today stays in or keeps the cash ready — and build the trust that brings repeat orders. Done badly, with too many messages, missing tracking details or promotions bolted on, the same updates become noise that drags down the number's quality rating.

Are order status updates marketing or utility?

Utility, as long as they only report on the customer's order. Under Meta's marketing vs utility template rules, discounts, recommendations or cross-sells make them marketing, charged at the higher marketing rate.

Do order updates need opt-in?

Yes. WhatsApp requires the customer's opt-in before business-initiated messages. Collect it at checkout and record when and how it was given.

How many updates should one order get?

Usually three to five: confirmation, shipped with tracking, out for delivery and delivered, plus exception messages only when something goes wrong.

Is this the same as the order_status message?

No. order_status is an interactive Payments API message that updates an order created with an order details message. Order status updates in general are utility templates that work for any order, however it was paid.