Skip to content
OmniChannels.ai
Menu

COD Order Confirmation on WhatsApp: Cut Returns (RTO)

Set up COD order confirmation on WhatsApp: utility templates with Confirm and Cancel buttons, SMS fallback, Arabic, Urdu and Hindi versions and RTO metrics.

Updated 9 min read

By OmniChannels.ai Editorial Team · Reviewed by BroadNet Messaging Solutions Team

Marketing

Short answer

To confirm cash-on-delivery orders on WhatsApp, send a utility template right after checkout that states the order, total and delivery area and offers Confirm and Cancel quick-reply buttons plus a way to change the address. Dispatch only confirmed orders, chase unconfirmed ones with an SMS or a call, and measure confirmation rate, return-to-origin (RTO) rate and cost per confirmed order. The message must stay non-promotional to remain utility.

On this page
  1. Why confirm COD orders before dispatch?
  2. Is a COD confirmation a utility or marketing template?
  3. What should a COD confirmation message contain?
  4. How do you handle the reply?
  5. What is the right follow-up ladder?
  6. How do you localise for Arabic, Urdu and Hindi markets?
  7. What consent do you need?
  8. Which metrics show it works?
  9. A worked example: a Karachi fashion store
  10. What are the common mistakes?
  11. How OmniChannels.ai helps

Key takeaways

  • Order-management messages that are specific to the customer's order and non-promotional qualify as utility in Meta's categorisation; adding an offer turns the template into marketing.
  • Templates can carry quick-reply buttons with labels up to 25 characters, so Confirm, Cancel and Change address fit in one message.
  • Meta supports template languages for the main COD markets, including Arabic (ar, ar_EG, ar_AE), Urdu (ur) and Hindi (hi).
  • WhatsApp opt-in is still required for utility messages, so capture it at checkout; use SMS as a fallback for customers who are not on WhatsApp or do not respond.
  • Success is measured by confirmed-before-dispatch share, RTO rate and cost per delivered order, not by message counts.

This guide is for e-commerce and logistics teams in cash-on-delivery (COD) markets such as the Gulf, Egypt, Pakistan and India, where a share of orders are refused at the door or never answered. It explains how to confirm COD orders on WhatsApp before dispatch, which template category to use, the exact message structure, how to run SMS and call fallbacks and which metrics prove it works. We do not quote benchmark return rates; use your own data.

Why confirm COD orders before dispatch?

With prepaid orders the customer has already committed. With COD, an order can be placed as a test, by mistake, with a wrong address, or by someone who will not be home. If the parcel travels and comes back, you pay outbound and return courier costs, tie up stock and lose the sale. That outcome is called RTO (return to origin) in South Asia and often just "refused" or "returned" elsewhere.

A confirmation step moves the decision earlier, when it is cheap. It lets you verify intent, correct the address and delivery area, set an expectation about the amount to pay, and cancel orders that were never real. Doing it on WhatsApp works because customers already read and answer WhatsApp quickly, and a button tap is easier than a phone call.

Is a COD confirmation a utility or marketing template?

Utility, as long as it stays strictly about the customer's own order. Meta's categorisation guide says utility templates must be non-promotional and either specific to the user's order, account or transactions, or essential to them. It lists order confirmation and delivery details as order-management utility, and states that order messages must not promote, upsell, cross-sell, include offers or seek renewals. Mixed content is classed as marketing.

So a COD confirmation can carry: order number, item summary, total to pay, delivery area, a request to confirm or cancel, and an offer of help. It must not carry a coupon for the next order or product recommendations. Keep those in a separate marketing template to opted-in customers. See our guide to template categories and approval and the e-commerce overview in WhatsApp for ecommerce.

What should a COD confirmation message contain?

Short, specific and with two clear actions.

Element Example Why
Greeting with name "Hi {{1}}," Shows it is personal
Order and items "Order {{2}}: {{3}}" Lets the customer recognise it
Amount to pay "Pay {{4}} in cash on delivery" Prevents price surprises at the door
Delivery area or address summary "Delivery to {{5}}" Catches wrong areas early
Action request "Please confirm so we can dispatch." Sets the rule
Buttons Confirm order · Cancel order · Change address One tap each

Example template body:

Hi {{1}}, thanks for ordering from [Brand]. Order {{2}} ({{3}}) totals {{4}}, payable in cash on delivery to {{5}}. Please confirm so we can dispatch it. Buttons: Confirm order · Cancel order · Change address

Meta's template rules allow a body up to 1,024 characters and quick-reply buttons with labels up to 25 characters, so these fit comfortably. Quick-reply buttons must be grouped together. A template with more than three buttons shows two and a "See all options" button, so keep to three or fewer.

Use the retail order confirmed template as a starting point and preview the message with the WhatsApp template preview tool.

How do you handle the reply?

Your platform receives a webhook when the customer taps a quick-reply button, and the payload tells you which button. Wire each to an action:

  1. Confirm order marks the order confirmed in your store and releases it to the warehouse. Send a utility "order confirmed" message with an expected delivery window.
  2. Cancel order cancels in the store, restocks and, optionally, asks why with a short follow-up.
  3. Change address opens a short conversation or a WhatsApp Flow to collect the corrected address, then re-sends the summary for confirmation. See our guide to WhatsApp Flows.
  4. Free-text reply opens a 24-hour customer service window; route it to an agent through the shared inbox.

Delivery statuses for the message itself arrive in the same webhook stream, so you can tell "not delivered" (number not on WhatsApp) from "delivered, no answer". Our delivery status guide explains them.

What is the right follow-up ladder?

Not every customer answers. Define the ladder and publish the policy in the first message.

  1. Minute 0: WhatsApp confirmation template.
  2. After a few hours, no tap: a WhatsApp reminder, still utility and still specific to the order.
  3. WhatsApp not delivered: SMS confirmation with a short link or a reply keyword, using a transactional sender ID.
  4. Still no answer: a call from your team, especially for high-value baskets.
  5. No response by your deadline: hold the order or cancel according to the policy you stated.

Keep the timings short enough that fast-moving stock is not blocked, and long enough for people at work to respond. SMS fallback needs a registered sender in many markets: see our guides to sender IDs and, for India, DLT registration before launching. The principle of falling back by delivery status is covered in channel fallback strategy.

How do you localise for Arabic, Urdu and Hindi markets?

Meta supports the template languages you need: Arabic as ar, ar_EG and ar_AE, Urdu as ur and Hindi as hi. Submit each language as a separate version of the same template, so each customer receives the one that matches their preference or order language.

  • Arabic and Urdu read right to left. Preview with real names and addresses, because mixed Latin and Arabic text can reorder in a message.
  • Hindi messages often mix scripts; decide whether names, addresses and product names appear in Devanagari or Latin and keep it consistent.
  • Currency and digits: keep amount formatting consistent with your store and what the courier will collect.
  • Tone: polite and short. Customers should understand the action in a few seconds.

Our guide to Arabic customer messaging has more.

WhatsApp requires opt-in even for utility messages: you may contact people only if they gave you their number and opted in. Meta's guidance asks that the opt-in states they will receive communications, names your business and complies with law, and covers the message types you will send, such as order updates. At checkout, add a tick box or notice, for example "Send my order updates on WhatsApp", and store the proof. Customers who decline should get SMS instead. Never use order-confirmation permission for promotions.

Which metrics show it works?

Use outcome metrics, not message counts.

Metric Definition Use
Confirmation rate Confirmed orders / orders asked Health of the flow
Time to confirm Median time from order to confirmation Dispatch speed
Unconfirmed share Orders with no answer after the ladder Size of the fallback problem
RTO or refusal rate Returned or refused / dispatched The main business outcome
Cancellation rate Cancelled after message / asked Watch for lost genuine buyers
Cost per delivered order Message and courier cost / delivered paid orders Real economics

Run a holdout where a random share of orders skips confirmation for a few weeks, and compare RTO and delivered revenue. Include message charges: Meta charges per delivered template by category and market; see the WhatsApp pricing page and the messaging ROI calculator.

A worked example: a Karachi fashion store

"Sitara Wear" (synthetic) ships COD orders across Pakistan.

  • Checkout shows a WhatsApp updates tick box and stores consent.
  • A Urdu and an English utility template go out after each order, with Confirm, Cancel and Change address buttons.
  • Orders confirmed by tap go to the warehouse; orders with no answer after a reminder receive an SMS and, for baskets above a threshold, a call.
  • The team compares RTO for confirmed versus unconfirmed-then-dispatched orders and sets a rule to hold unconfirmed orders in high-risk areas.

What are the common mistakes?

  • Adding a coupon to the confirmation. It becomes marketing and may be reclassified.
  • Sending without opt-in.
  • No fallback, so customers not on WhatsApp are silently skipped.
  • Dispatching before confirmation because the warehouse is not integrated.
  • Wrong language for the customer.
  • Too many buttons that get collapsed into "See all options".

How OmniChannels.ai helps

BroadNet is an official Meta Business Solution Provider. OmniChannels.ai supports utility templates with quick-reply buttons, webhooks for button taps and delivery statuses, channel fallback from WhatsApp to SMS, a shared inbox for replies and Arabic and English templates. Our team helps with WhatsApp onboarding and sender ID registration. See the e-commerce solution and the logistics solution, or book a demo.

Frequently asked questions

Is a COD confirmation message utility or marketing?

Utility, if it is specific to the customer's own order and contains nothing promotional. Meta's categorisation lists order confirmation and delivery details as order-management utility, and says order messages must not upsell, cross-sell or include offers. If you add a coupon or a recommendation, Meta treats the template as marketing, which changes rules and cost.

How do Confirm and Cancel buttons work in a WhatsApp template?

You add quick-reply buttons to the template, each with a label of up to 25 characters. When the customer taps one, your system receives the button payload through the webhook and can mark the order confirmed or cancelled. Quick-reply buttons must be grouped together, and templates with several buttons may display fewer buttons on some devices, so keep labels short.

What if the customer does not reply to the COD message?

Define a ladder: a WhatsApp reminder after a few hours, then an SMS, then a call from your team before dispatch, then a hold or auto-cancel according to your policy. Tell customers the policy in the first message. Keep every follow-up non-promotional and stop automatically once the customer confirms or cancels.

Can I send COD confirmations in Arabic, Urdu or Hindi?

Yes. Meta supports Arabic (ar, ar_EG, ar_AE), Urdu (ur) and Hindi (hi) as template languages. Submit each language as a separate version of the same template, write natively instead of translating word for word, and preview right-to-left layouts for Arabic and Urdu before approval.

Do I need opt-in for WhatsApp order confirmations?

Yes. WhatsApp's policy allows you to contact people only if they gave you their number and opted in. Meta's opt-in guidance asks that the opt-in names your business and covers the types of message you send, such as order updates. Add a WhatsApp updates checkbox at checkout, store the proof and fall back to SMS for customers who decline.

How do I know if COD confirmation reduces returns?

Compare RTO rate, cancellations and cost per delivered order for a period before and after, or better, run a holdout where a random share of orders is not asked to confirm. Count only delivered, paid orders, include message costs and courier costs, and watch the cancellation rate so you do not lose genuine buyers.

Sources

  1. Template categorization — Meta for Developers
  2. Template components (buttons and limits) — Meta for Developers
  3. Supported languages for message templates — Meta for Developers
  4. Get opt-in for WhatsApp — Meta for Developers
  5. WhatsApp Business Messaging Policy

Keep reading

More guides