Shipping Updates WhatsApp Template for Food Delivery
When a customer's biryani, weekly meal box or fresh grocery order leaves your kitchen or dark store, that hand-off is the exact moment they start refreshing for an update. This ready-to-use, Meta-compliant WhatsApp shipping updates template gives food delivery brands in India a clean way to tell the customer their order is on the move — with the courier, a live ETA and a one-tap track button already built in. Submit it as Utility, personalise the four variables, and start sending in a day with InfiQ.
Variables
{{1}}= Ananya{{2}}= #FD20488{{3}}= Shadowfax{{4}}= 8:45 PM today
Verified business
10:24
Preview · as customers see it
When to send this template in the food delivery journey
Fire this message at one precise trigger: the instant an order changes state from 'preparing' to 'out for delivery' or 'shipped'. For hot food that means the moment the rider picks up from the restaurant; for meal-kit, cloud-kitchen subscription or gourmet-hamper brands it is the moment the parcel is handed to a courier like Shadowfax, Delhivery or Dunzo. Sent at that trigger, the message lands while intent is at its peak, cuts down 'where is my order?' calls to your support team, and turns an anxious wait into a tracked, transparent experience. Because it is tied to a genuine transactional event the customer is expecting, it also earns high open and read rates without feeling like a broadcast.
- Trigger on the dispatch/shipped webhook, not on a schedule
- One message per order — do not batch or repeat it
- Pair it with a live tracking button so the next step is a single tap
- Follow up with a separate 'delivered' or feedback template if needed
How to personalise the variables so it reads 1:1
The template carries four variables and each one does real work. {{1}} is the customer's first name so the greeting feels personal. {{2}} is your order id — keep the format consistent (for example #FD20488) so it matches what appears in their account, invoice and any support ticket. {{3}} is the courier or delivery partner name, which reassures the customer and sets expectations about handling. {{4}} is a concrete ETA — a real time window like '8:45 PM today' or '30–40 minutes' converts far better than a vague 'soon'. Pull all four straight from your order-management system so the values are always accurate; a wrong ETA or mismatched order id does more damage than no message at all. Keep the tone warm and specific to food so it reads as a message from a kitchen that cares, not an automated logistics ping.
- {{1}} name — first name only for a friendly greeting
- {{2}} order id — mirror the format shown in the app and invoice
- {{3}} courier — the actual delivery partner for that order
- {{4}} ETA — a real time or tight window, never 'soon'
Getting it approved as Utility on the first try
This template belongs squarely in the Utility category because every send is triggered by a real action the customer has taken — placing and paying for an order. To sail through Meta's review, keep it strictly informational: state that the order shipped, name the courier, give the ETA, and offer tracking. The single biggest cause of rejection here is contamination with marketing — the moment you add a coupon, an upsell ('order again and save 20%'), or promotional language, the template is reclassified as Marketing and may be rejected or billed at the higher Marketing rate. Submit clean sample values for all four variables (Meta reviews the filled-in version), use a clear template name like food_delivery_shipping_update, and avoid ALL-CAPS or excessive emoji. Approved Utility templates are usually cleared within a day, and InfiQ's template manager surfaces the rejection reason instantly if Meta asks for an edit.
- Keep it purely transactional — no offers, discounts or upsells
- Provide realistic sample values for {{1}}–{{4}} at submission
- Name it descriptively, e.g. food_delivery_shipping_update
- Avoid promotional phrasing that would trip a Marketing reclassification
What it costs to send at scale
Since Meta moved off per-conversation billing on 1 July 2025, WhatsApp charges per delivered message by category. This shipping updates template bills at the Utility rate on every delivery, which is meaningfully cheaper than the Marketing rate — one of the reasons keeping it strictly transactional matters commercially as well as for approval. Through InfiQ you get transparent ₹ pricing (ex-GST), so a food delivery operation sending one shipping update per order can forecast cost precisely from its daily order volume. Because these messages replace inbound 'where is my order' calls and reduce failed deliveries from missed handoffs, the effective payback is usually strong even before you count the retention benefit of a smoother delivery experience.
- Utility rate applies to each delivered message
- Billing is per delivered message, not per conversation
- Transparent ₹ pricing, ex-GST
- Cost scales linearly and predictably with order volume
Variations you can copy
The base template works for most brands, but a few tuned variants help you match your delivery model. A shorter version trims to the essentials for high-frequency, low-margin orders where speed of read matters most. A subscription/meal-kit version can name the plan or box instead of a single order. A regional-language version — Hindi, Tamil, Bengali, Marathi or whichever language your customers actually use — dramatically lifts comprehension and trust in tier-2 and tier-3 markets. Keep every variant inside the Utility rules; if you genuinely want to add an incentive, build that as a separate Marketing template with a proper opt-out line rather than bending this one.
- Shorter: 'Order {{1}} is out for delivery with {{2}}. ETA {{3}}. Track below.'
- Subscription: reference the box or plan name instead of a one-off order id
- Regional language: recreate the same Utility content in your customers' language
- Incentive: build it separately as a Marketing template with opt-out
Like this template? Send it live in 24 hours.