COD Order Confirmation WhatsApp Setup for Pakistani Sellers

Monday, 11 am. The rider from the courier drops six parcels back at your door. Two say "customer refused". Three say "phone band hai". One says "incomplete address". You paid delivery on all six, and now you will pay the return charges too. The stock is fine, but the money is gone, and the packing time is gone with it.

The usual fix is a person who calls every order before booking. That works until a sale weekend brings 80 orders and the caller is still on order 30 at 9 pm.

A COD order confirmation WhatsApp flow does the first round of that calling for you. The customer gets a message minutes after ordering, taps Confirm, Cancel or Change Address, and your store updates on its own. Here is the setup, step by step, the way we build it for stores on Shopify, WooCommerce and Instagram.

First, do the sum. If each returned parcel costs you the outgoing delivery plus a return charge, multiply that by last month's returns. Write the number down. You will compare against it in week one.

Step 1: Get these five things ready before you touch any template

Skip this and the flow breaks on day two.

1. An official WhatsApp Business Platform number. Confirmation messages must go through Meta's official API (the Meta Cloud API), not your personal WhatsApp and not a bulk sender tool. If you want to keep using the WhatsApp Business App on your phone at the same time, that is what WhatsApp Coexistence is for.
2. A verified Meta business portfolio with your store name matching what customers see. A template from "Ali Traders" when the customer ordered from "Glow by Sana" looks like a scam.
3. A way to see new orders automatically. Shopify and WooCommerce can send an "order created" signal (a webhook) the moment an order lands. For Instagram orders, use one order form or sheet the system can read. If orders live only in your DMs, fix that first.
4. Your courier details. Which courier you book with (TCS, Leopards, PostEx, Trax, M&P) and how you get tracking numbers: portal, API or spreadsheet.
5. Your rules on paper. How long you wait for a reply, what happens if nobody answers, and which orders always get a human call. You decide these, not the software.

Step 2: Write the confirmation template and get it approved as utility

Every message you start on the API is a template: fixed text Meta approves, with blanks filled per order. Meta puts each template in a category: utility (about something the customer already did, like an order), marketing (offers) or authentication (login codes). An order confirmation is utility, and it should read like one.

A sample we would start from, Roman Urdu first because most COD buyers read it faster:

Assalam o Alaikum {{1}}, aap ka order #{{2}} humein mil gaya hai.

Items: {{3}}

Total (Cash on Delivery): Rs {{4}}

Delivery address: {{5}}

Barah-e-karam neeche button se order confirm karein, taake hum parcel book kar saken. Please confirm your order using a button below.

Buttons: Confirm Order | Cancel Order | Change Address

A few details that matter in practice:

• {{1}} is the customer's first name, {{2}} the order number, {{3}} a short item list, {{4}} the amount, {{5}} the address exactly as typed. Showing the address is the point. Customers catch "House 12, near masjid" with no area or city and fix it before the parcel leaves.
• Use quick reply buttons, not "reply 1 to confirm". Taps are faster and come back as clean data.
• Meta reviews templates and sometimes rejects or recategorises them. Approval is often quick, but do not plan your launch for the same afternoon.

Step 3: Send it within minutes, and only for COD orders

Timing does more work than wording. A customer who ordered five minutes ago remembers ordering. The same customer two days later, after seeing a cheaper version on another page, is the one who refuses at the door.

So the trigger is the new order itself. The system checks the payment method: prepaid orders skip confirmation and only get tracking later, COD orders get the template straight away. We wire the store and WhatsApp together through their APIs; our API integration page explains that without code.

Two things break this step most. Phone numbers: customers type 0300-1234567, 3001234567, +92 300 1234567 and sometimes a landline. Clean every number to the 92300 format and flag anything that cannot be a Pakistani mobile. Duplicates: some customers tap "Place order" twice. Merge same-number, same-item orders placed minutes apart, or the customer gets two messages and cancels both.

Step 4: Decide exactly what each button does

A button that only says "thanks" wastes the whole flow. Each tap should change something in your store:

Confirm Order

The order gets a "confirmed" tag or status, and it moves to the list your packer books with the courier. Send a short reply: "Shukriya! Aap ka order confirm ho gaya. Booking ke baad tracking number bhej denge."

Cancel Order

The order is cancelled in the store and the stock goes back. You can ask one optional question ("Kya hum wajah jaan sakte hain?") but do not argue. A cancellation now costs you one message. A refusal at the door costs you two delivery charges.

Change Address

The system asks for the full address with area and city, then puts the order on hold for a person to check. Do not let the bot rewrite addresses alone. A human glance takes ten seconds and catches "same as before" answers.

The 24-hour rule helps here. When the customer taps a button or writes back, a 24-hour customer service window opens, and your replies inside it are free-form and free. Only messages you start outside that window need an approved template. For template costs, see our WhatsApp Business API price in Pakistan breakdown.

Step 5: Pick your rule for customers who never reply

Some customers tap nothing. They are at work, the message is buried, or the number was fake. Set one rule in advance so nobody decides order by order at night. A rule we often start sellers on:

1. No reply after 3 to 4 hours: send one reminder template. Short: "{{1}}, aap ka order #{{2}} abhi confirm nahi hua. Parcel book karne ke liye button dabayein." Same three buttons.
2. Still nothing by the next morning: the order goes to one of two paths, which you choose by order value.
3. Higher value orders: a person calls once. Many genuine buyers simply do not check WhatsApp at work.
4. Low value orders: they go on hold automatically, and cancel after a set time if there is still no answer.

Honestly, the exact hours matter less than having the rule. And skip the third reminder: two unanswered messages is an answer.

Step 6: Send courier tracking updates the customer will actually read

Confirmation stops fake orders. Tracking updates stop genuine buyers from being out, or short of cash, when the rider comes. Three messages are enough:

• Booked: courier name and tracking number, right after you book with TCS, Leopards, PostEx, Trax, M&P or whoever you use.
• Out for delivery: "Aap ka parcel aaj deliver hoga. Rs {{1}} cash tayyar rakhein." This is the message that cuts down "phone band hai", because the customer now knows the rider is coming today.
• Delivered or returned: a thank-you, or a note to your team that the parcel is coming back.

How you get these status changes depends on the courier: some offer APIs or webhooks, some only a portal. Ask your courier account manager before promising live updates. These are also utility templates, and the same rule applies: no "use code EID10 on your next order" squeezed in.

Step 7: Keep confirmed and cancelled status synced to your store and CRM

If the status lives only in WhatsApp, your packer still books the cancelled order, because they work from the store's order list. Every tap has to land back there.

• In Shopify, use order tags such as cod-confirmed, cod-cancelled, cod-no-reply and address-check.
• In WooCommerce, use order statuses (On hold, Processing, Cancelled) or a custom status for "awaiting confirmation".
• In your CRM, keep the history on the customer's record: orders confirmed, orders refused at the door, cancellations. A number that has refused two COD parcels before should go straight to a phone call, or to advance payment only. Our CRM automation work is mostly this kind of status sync.

Give your team one daily view: ready to book, waiting for reply, needs a call, address check. For the bigger picture of what an AI agent can handle for an online store beyond confirmations, read our post on AI agents for ecommerce stores.

The rules sellers break without knowing it

We see these most when a seller tried building this before coming to us.

Putting an offer inside the confirmation

"Your order is confirmed! Get 10% off your next order" turns utility into marketing. Meta can categorise it that way, which changes how it is charged and delivered. Keep confirmations boring and send offers separately, only to people who agreed to them.

Messaging people who did not order

Uploading your old customer list and sending the confirmation template to "remind" them is not confirmation, and people report it. Only real buyers, for a real order, from the number they typed at checkout. Add a line at checkout such as "We will confirm your order on WhatsApp" so the message is expected.

Expecting the dashboard to message anyone for free

Many owners expect to message anyone from the dashboard for free once the number is connected. In practice, the first message to someone who has not written to you in the last 24 hours must be an approved template, and Meta charges for those. Replies inside the window are free. Plan your reminders with that in mind.

Running it from a personal number with a bulk tool

Browser extensions that send from your personal number are how stores lose their number in the middle of a sale. Use the official API.

Step 8: Go live small and watch the first week closely

Never launch on the first day of a big sale. Start like this:

1. Place three test orders yourself from different phones: one you confirm, one you cancel, one you ignore. Check that each one ends with the right tag in the store.
2. Turn it on for normal days first, all COD orders, with a person watching the "needs a call" list.
3. Every evening, note four numbers: orders confirmed, cancelled, no reply, and address changes.
4. At the end of the week, compare returns from confirmed orders with your returns before. Use the number you wrote down at the start.
5. Adjust the reminder timing and the hold rule. Then switch it on for sale days.

If you want this built for your store, from template wording to courier updates and status sync, our WhatsApp automation team sets it up on your existing number. Coexistence plans start from PKR 12,000 per month, and you keep using the WhatsApp Business App on your phone. Send us your store platform and courier on our contact page and we will tell you what fits.

Further reading

See how this looks in practice across our AI automation, custom CRM and lead generation services, or tell us the outcome you need.