Delivery Tracking WhatsApp Template for Ecommerce
"Where is my order?" is the single most repeated question in any ecommerce inbox — and every one of those tickets is a customer who is anxious, a support agent who is busy, and a repeat purchase that is quietly at risk. This ready-to-use, Meta-compliant WhatsApp delivery tracking template answers the question before it is ever asked. It fires the moment a parcel goes out for delivery, tells the customer exactly who is coming and by when, and puts a live-tracking button one tap away. It ships as a Utility template with the variables, sample values, button setup and approval notes already worked out, so you copy it, wire up your courier fields, and start sending through InfiQ once Meta approves it — usually within a day.
Variables
{{1}}= Ananya{{2}}= #ORD-48213{{3}}= 6:30 PM{{4}}= Delhivery{{5}}= Ramesh
Verified business
10:24
Preview · as customers see it
When to send it — and why the timing is everything
This template earns its keep in a narrow but critical window: the few hours between a parcel leaving the last-mile hub and landing at the customer's door. Fire it too early, at manifest or dispatch, and it competes with your order confirmation and dilutes both. Fire it the moment the courier marks the shipment 'out for delivery' and it hits the customer exactly when their attention on the order is highest — when they are deciding whether to wait in, move a meeting, or ask a neighbour to receive it. A well-timed delivery update is opened almost immediately because it is genuinely useful, and every one that lands is a support ticket that never gets raised.
- Trigger on the courier's 'out for delivery' webhook, not at dispatch, so the ETA is real.
- Send a single update per delivery attempt — resist the urge to ping at every scan.
- For failed or rescheduled deliveries, follow up with a fresh, separate Utility message rather than editing this one.
Personalisation that makes it read like a human, not a blast
The difference between a delivery update customers appreciate and one they ignore is specificity. Five variables carry the whole message: the customer's first name so it opens warmly, the order ID so they know exactly which parcel this is (frequent shoppers have several in flight), a real ETA window pulled live from the courier rather than a vague 'today', the carrier name so the branded truck at the gate makes sense, and the delivery agent's name so a call from an unknown number feels expected instead of like spam. Populate all five from the order record at send time — never leave a placeholder unfilled, because an empty variable is both an instant rejection risk and an obvious tell that the message was automated.
- {{1}} name · {{2}} order ID · {{3}} ETA window · {{4}} courier · {{5}} agent name.
- Map each variable to a live field in your order or courier data, not a static default.
- Sample values (Ananya, #ORD-48213, 6:30 PM, Delhivery, Ramesh) go in when you submit for approval.
Getting it approved as Utility — first time
Submit this as Utility, not Marketing. It qualifies cleanly because it is transactional and tied to an action the customer actually took: placing and paying for an order. Utility is also the cheaper category, so the correct classification saves you money on every send as well as clearing review faster. The one rule that trips brands up is keeping it strictly informational. The instant you add a discount code, a 'shop again' line, or any promotional nudge, Meta re-reads the template as Marketing — which changes the billing rate and often gets the Utility submission rejected outright. Provide realistic sample values for all five variables when you submit, keep the tone factual, and reserve any promotional message for a separate Marketing template that carries its own opt-out line.
- Category: Utility. Keep every word informational — no offers, no upsell.
- Fill in sample values for all variables so reviewers see real, coherent content.
- Put promotions in a dedicated Marketing template with an opt-out; never here.
What it costs, and how InfiQ prices it
Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category. As a Utility template, every delivery update you send bills at the utility per-message rate rather than the higher marketing rate — another reason correct categorisation matters. The 24-hour service window is a free window for replies to customer-initiated chats, not a billing unit, so it does not change what this proactive update costs. On top of Meta's charge, InfiQ applies transparent ₹ pricing, ex-GST, with no per-conversation guesswork. Because a single well-timed update deflects a support ticket that would otherwise cost an agent's time — and protects a repeat purchase — delivery-tracking messages tend to pay for themselves faster than almost any other automated send.
- Billed per delivered message at the utility rate — not per conversation.
- InfiQ adds transparent ₹ pricing, ex-GST.
- Payback is driven by tickets deflected and deliveries completed on the first attempt.
Variations you can copy
Once the core Utility template is approved, adapt it to your logistics reality without starting from scratch. A shorter version — name, order ID and ETA only — works well for high-volume brands that want a lean, fast-loading update. A regional-language version in Hindi, Tamil, Marathi or whatever your customers speak is worth submitting once and reusing forever, because a delivery instruction is trusted far more in the reader's own language. And if you genuinely want to invite a repeat purchase off the back of a great delivery experience, build that as a separate Marketing template — with a clear opt-out line — rather than bending this Utility one out of shape.
- Shorter: trim to name, order ID and ETA for lean high-volume sends.
- Regional language: a Hindi or vernacular version, approved once and reused.
- Post-delivery re-engagement: a separate Marketing template with an opt-out line, never inside this Utility template.
Like this template? Send it live in 24 hours.
Frequently asked questions
Which WhatsApp category does the delivery tracking template use?+
Does it still need opt-in even though it's Utility?+
Can I edit the wording of the template?+
How quickly can I start sending after I add it?+
What do the five variables map to?+
How is this template billed?+
Can I add a discount or 'shop again' offer to it?+
Can I send it in Hindi or a regional language?+
Ship delivery updates your customers actually thank you for
Copy this Utility template, wire it to your courier's out-for-delivery event, and start cutting 'where is my order' tickets with InfiQ — an official Meta Business Partner for the WhatsApp Business API in India.