Order Confirmation WhatsApp Template for Ecommerce
The order confirmation message is the very first thing a customer hears from your store after they pay, and on WhatsApp it lands where they will actually read it — inside a chat they check dozens of times a day, not an inbox they ignore. This page gives you a Meta-compliant, copy-paste order confirmation template built for Indian ecommerce: the correct category, the right variables, a working button layout, and the specific approval notes that get it live on the first submission. Personalise the four variables, submit it through InfiQ, and start reassuring buyers the moment their money leaves their account.
Variables
{{1}}= Ananya{{2}}= #IQ-48213{{3}}= ₹2,499{{4}}= Kanha Living
Verified business
10:24
Preview · as customers see it
When to send it — and why the timing matters
Trigger this template automatically at the single most reassuring moment in the journey: the instant the payment gateway returns a success (or the order is placed, for prepaid and COD alike). That is when the buyer's anxiety peaks — money has moved, but nothing tangible has arrived — so a confirmation that names their order, states the amount they paid, and promises a shipping update does real work: it lowers 'where is my order?' tickets, cuts payment-failure panic, and sets the expectation for the next message in the sequence. Because WhatsApp confirmations are read within minutes, you replace the silent gap most stores leave between checkout and dispatch with a branded, trustworthy touchpoint.
- Fire it on payment success / order placement, not hours later
- Send within your automation, not manually — every order should get one
- It opens the thread you'll reuse for shipping, delivery and returns updates
- Pair it with a shipping-updates template so the customer never has to ask
Why this is a Utility template (and what that saves you)
An order confirmation is triggered by a specific transaction the customer just completed, contains no promotion, and exists purely to inform — which is the textbook definition of the Utility category. That classification is not a formality: since Meta moved WhatsApp to per-message billing on 1 July 2025, every delivered message is priced by its template category, and utility messages sit well below marketing rates on the live rate card. Keeping this template strictly transactional therefore protects both your approval odds and your unit economics. The moment you bolt on a discount code or a 'shop more' nudge, Meta reclassifies it as marketing, you pay the higher marketing rate per delivered message, and you risk rejection — so keep the confirmation clean and put promotions in a separate, opt-out-compliant marketing template.
- Utility = transactional, tied to a real action, no marketing content
- Billed per delivered message at the lower utility rate
- Adding an offer flips it to marketing — higher rate and rejection risk
- Sent inside the 24-hour service window, replies to the customer stay free-form
Personalising the four variables
The template reads as a genuine 1:1 message only if the variables carry real, specific values — a name your customer recognises, an order id they can quote to support, the exact amount they were charged, and your store name spelled the way it appears on your storefront. Map {{1}} to the customer's first name (fall back to a warm generic like 'there' if you don't capture names), {{2}} to your human-readable order id rather than an internal UUID, {{3}} to the final charged amount with the ₹ symbol and thousands separators, and {{4}} to your brand exactly as customers know it. Always provide realistic sample values when you submit — Meta's reviewers judge the template partly on how the filled-in version reads, and vague placeholders like 'X' or 'name here' invite rejection.
- {{1}} customer first name — e.g. Ananya
- {{2}} human-readable order id — e.g. #IQ-48213, not a raw database id
- {{3}} final charged amount with symbol — e.g. ₹2,499
- {{4}} brand name as it appears on your store — e.g. Kanha Living
Buttons: turn confirmation into a tap
Two buttons carry this template from 'nice message' to 'useful tool'. A Track order button — either a URL button that deep-links to your order-status page (you can embed the order id as a dynamic URL variable) or a quick-reply that fires your tracking flow — gives the anxious buyer their next step in one tap. A Need help? quick-reply routes confused customers into support before they open a ticket elsewhere, so a wrong address or a size doubt gets caught early. Keep it to these two: a cluttered button row reads as spammy and can hurt approval, while a single clear primary action plus a help fallback covers the vast majority of post-purchase intents.
- Track order — URL button with a dynamic order-id link, or a quick-reply to your tracking flow
- Need help? — quick-reply that opens your support handoff
- Two buttons max keeps it clean and approval-friendly
- A tap-through action beats a passive 'we'll email you' every time
Getting it approved on the first try
Submit under Utility, in the customer's language, with every variable filled by a plausible sample value. Keep the copy strictly informational — no discount, no 'limited time', no emoji-stuffing that reads as promotion — and make sure the visible text matches what the buttons do (a Track order button should point at a real tracking destination). Confirmation templates are among the least controversial submissions on the platform, so most clear review within a day when they follow these rules. Through InfiQ you manage the whole lifecycle — draft, submit, track approval status, and version your edits — from one dashboard, and you own the underlying BSUID and WhatsApp Business Account throughout, so nothing about your number or your templates is locked to us.
- File as Utility, with realistic sample values for every variable
- No promotional language — keep it transactional or risk a marketing reclassification
- Match button labels to real destinations
- Manage approval and versions in InfiQ; you keep full BSUID and WABA ownership
Like this template? Send it live in 24 hours.