If you run an ecommerce store in Pakistan, the language you use on WhatsApp directly affects whether customers reply. Roman Urdu WhatsApp templates for ecommerce consistently outperform formal English because that is how your customers actually communicate — with their families, their friends, and the businesses they trust.
This guide gives you 15 copy-paste-ready templates covering every stage of the customer journey: COD confirmation, order tracking, abandoned cart recovery, and support. Each template is structured for the WhatsApp Business API and can be automated through platforms like Kliovo Shop.
Table of Contents
- Why Roman Urdu Outperforms English on WhatsApp in Pakistan
- How to Use These Templates
- COD Confirmation Templates
- Order Status Update Templates
- Abandoned Cart Recovery Templates
- Customer Support Templates
- Common Roman Urdu Variations Your Automation Must Handle
- Getting These Templates Approved and Live
- Frequently Asked Questions
Why Roman Urdu Outperforms English on WhatsApp in Pakistan
Pakistan has over 52 million active WhatsApp users as of 2026. WhatsApp is not a secondary channel here — it is the primary way customers expect to communicate with businesses.
The data is clear: messages sent in Roman Urdu generate 2.3x higher response rates compared to formal English messages for the same use cases. The reason is straightforward. A customer who speaks Urdu at home, types in Roman Urdu with friends, and processes information in Urdu does not feel a personal connection to English business templates. Roman Urdu does.
Roman Urdu is not "broken Urdu." It is the standard digital writing form for approximately 230 million Urdu speakers who do not have access to Urdu keyboards on most devices, or who simply find Roman script faster to type. It is how Pakistan communicates digitally, and it has its own grammar, rhythm, and vocabulary conventions that are distinct from formal Urdu or English.
One of the less obvious challenges: Roman Urdu has hundreds of accepted spelling variations for common words. The word for "how much" — kitna — is spelled as "kitne," "kitnay," "kitney," "kitnay," and several other forms depending on the writer. A basic automation system will fail when a customer replies "kitney paise hain?" instead of the expected "kitna price hai?" — because it is doing exact string matching rather than understanding meaning.
Most WhatsApp automation tools treat Roman Urdu as a second-class input. They handle English well, accept some Urdu script, and then break or misroute Roman Urdu messages because they were not designed for it. Kliovo's ovo AI handles Roman Urdu natively, with over 200 spelling normalizations built in — meaning customers can spell things however they naturally would, and the AI still understands and responds correctly.
This is why template language matters. The right language gets the reply. The reply is what moves the order forward.
How to Use These Templates
These templates follow WhatsApp Business API approved structures. A few things to know before you use them:
Variables in [square brackets] are placeholders. Replace them with real customer data, order data, or product data. If you are using an automation platform, these variables get filled automatically from your order management system.
Templates with interactive buttons (like [Confirm karein] or [Haan, confirm hai]) require separate Meta approval before they can be sent. The approval process takes one to three business days. Plain-text templates with no buttons can be sent immediately once you have an approved WhatsApp Business API connection through an authorized BSP.
Template category matters for approval speed. Utility templates — order confirmations, shipping updates, transactional messages — have higher and faster approval rates than Marketing templates. Label your templates in the correct category when submitting.
Kliovo automatically personalizes all of these templates with real customer and order data pulled from your store. You can set up the full template library, configure the automation triggers, and get everything approved from a single dashboard. See WhatsApp template features for ecommerce for the full setup guide.
COD Confirmation Templates
Cash on delivery accounts for over 70% of ecommerce transactions in Pakistan. The confirmation step — verifying that a real customer placed the order before it ships — is the highest-leverage point in your entire operations chain. A failed confirmation means a returned shipment, a wasted courier fee, and a restocking cost. These four templates cover different scenarios and tones.
Template 1 — Standard COD Confirmation
Assalam o Alaikum [Name]!
Aap ka order receive ho gaya hai.
Order #[OrderNumber]
Items: [ProductName] x[Qty]
Total: Rs [Amount]
Delivery address:
[FullAddress]
Kya aap is order ko confirm karna chahte hain?
[Confirm karein] [Cancel karein]
This is the baseline template. It is complete, respectful, and gives the customer all the information they need to make a decision. Best used for first-time customers where trust-building matters.
Template 2 — Short COD Confirmation (high volume)
[Name] bhai, order #[OrderNumber] confirm karna hai — Rs [Amount]?
Delivery: [City]
Reply karo: HAAN ya NAHI
For high-volume stores sending hundreds of confirmation messages daily, a shorter template means faster processing. This format works well for repeat customer segments where the relationship is already established. The plain-text reply instruction (HAAN/NAHI) means no button approval is needed — faster to deploy.
Template 3 — Premium Product Confirmation
Assalam o Alaikum [Name]!
Shukriya aap ke order ke liye.
Aap ne order kiya hai: [ProductName]
Amount: Rs [Amount]
Delivery: [Address]
Is order ko process karne se pehle confirm karlein:
[Haan, confirm hai] [Nahi, cancel karo]
For higher ticket items — Rs 3,000 and above — a slightly more formal tone signals to the customer that this is a serious transaction. The Shukriya (thank you) at the top sets a warm tone before asking for the confirmation.
Template 4 — Repeat Customer Confirmation
[Name] bhai, dobara shukriya!
Naya order aa gaya hai:
[ProductName] — Rs [Amount]
[City] delivery
Confirm karna hai?
Repeat customers do not need to be re-educated about your process. A shorter, warmer message acknowledges the relationship. "Dobara shukriya" (thank you again) signals that you recognize them as an existing customer, which builds loyalty.
Order Status Update Templates
Once an order is confirmed, customers want to know where it is. Proactive status updates reduce inbound support queries by a significant margin — customers who receive shipping notifications do not need to message you asking "order kahan hai." These four templates cover the key status milestones.
Template 5 — Order Packed
[Name] bhai, khushkhabri!
Aap ka order pack ho gaya hai aur courier ko dene wale hain.
Order #[OrderNumber]
Tracking number milne par aap ko message karenge.
Send this when the order moves from processing to packed. "Khushkhabri" (good news) is a natural opener in Urdu that creates a positive emotional response. Setting the expectation that a tracking number is coming reduces the follow-up question about tracking.
Template 6 — Shipped with Tracking
Assalam o Alaikum [Name]!
Aap ka order [CourierName] ke zariye bhej diya gaya hai.
Tracking #: [TrackingNumber]
Track karein: [TrackingLink]
Delivery expected: [DeliveryDate]
This template works for all seven courier integrations supported in Pakistan — TCS, Leopards, Trax, BlueEx, PostEx, Swyft, and Sonic. The tracking link variable can route to the courier's own tracking page.
Template 7 — Out for Delivery
[Name] bhai, aaj delivery!
Aap ka courier aaj aap ke paas aa raha hai.
Ghar mein rahein ya delivery ke liye koi arrange karein.
COD amount tayyar rakhein: Rs [Amount]
This template serves double duty. It alerts the customer to be available, and it reminds them of the exact cash amount to have ready. The COD amount reminder reduces failed deliveries due to "exact change" problems, which are more common than most stores expect.
Template 8 — Delivered Confirmation
[Name], order deliver ho gaya!
Ummeed hai aap ka order pasand aaya hoga.
Koi sawal ho to reply karein — hum yahan hain.
A short, warm post-delivery message closes the loop on the order and opens a support channel if needed. "Hum yahan hain" (we are here) communicates availability without being transactional. This template also sets up naturally for a review request follow-up.
Abandoned Cart Recovery Templates
Cart abandonment in Pakistan ecommerce runs between 65% and 80% depending on the category. Many of these are genuine intent-to-buy situations where the customer got distracted, had a question, or hesitated on the price. A well-timed WhatsApp message recovers a meaningful percentage of this revenue. These three templates are designed for a sequential recovery sequence.
Template 9 — First Reminder (1 hour after cart abandon)
[Name] bhai, kuch bhool gaye?
Aap ka cart abhi bhi aap ka intezaar kar raha hai:
[ProductName] — Rs [Amount]
Abhi order karein: [CartLink]
Send this one hour after abandonment. The tone is light and conversational — "did you forget something?" is not accusatory, it is a gentle nudge. At this point the customer likely just got distracted and needs a reminder more than a reason.
Template 10 — Second Reminder (24 hours later)
Assalam o Alaikum [Name]!
[ProductName] limited stock mein hai.
Aaj bhi available hai — lekin zyada der nahi karni chahiye.
Order link: [CartLink]
The second message introduces mild scarcity. Only use this template if the product actually has limited stock — customers who check and find the product fully available will lose trust. Kliovo can pull live inventory data to conditionally send this template only when stock is genuinely low.
Template 11 — Final Recovery (48 hours, with discount)
[Name] bhai, aakhri mauka!
[ProductName] ke liye special offer:
Rs [DiscountAmount] ki chhoot — sirf aaj ke liye.
Discount code: [Code]
Order karein: [CartLink]
The third and final message in the sequence introduces a discount. This should be your last attempt — stop after three messages to avoid being flagged as spam. The discount code should be single-use and expire within 24 hours to enforce the urgency.
Customer Support Templates
Handling customer queries in Roman Urdu reduces the back-and-forth that happens when customers struggle to express themselves in English. These four templates cover the most common support scenarios.
Template 12 — Support Greeting
Assalam o Alaikum! [BusinessName] mein khush aaye.
Aap ki madad karne ke liye tayyar hain.
Apna sawal likhein ya neeche se option chunein:
[Order status] [Return/Exchange] [Kuch aur]
This greeting template launches the support experience. The three-button menu routes customers to the right flow without requiring a live agent for initial triage. Button-based menus require Meta approval but significantly reduce agent workload.
Template 13 — Return Request Acknowledgment
[Name] bhai, return request receive ho gayi.
Order #[OrderNumber]
Reason: [ReturnReason]
Hamara team 24 ghante mein aap se raabt karega.
Acknowledging a return request quickly — even if the resolution takes time — reassures the customer that their concern was heard. "Raabt karega" (will contact you) sets a clear expectation about next steps.
Template 14 — COD Payout Query
[Name] bhai, aap ka COD amount [CourierName] ne collect kar liya hai.
Expected payout: [Date]
Amount: Rs [Amount]
Koi delay ho to hamen batayein.
This template is used when a customer or partner asks about COD reconciliation. It provides the key data points — which courier collected the amount and when payout is expected — proactively. Kliovo's COD reconciliation reports sync with TCS and other couriers to populate this data automatically.
Template 15 — Post-Purchase Review Request
[Name], umeed hai delivery theek se aayi!
Ek minute mein hamein batayein — experience kaisa raha?
[Acha tha] [Theek tha] [Bura tha]
Send this 24 to 48 hours after the delivered confirmation. Three-button sentiment collection is faster than asking customers to write a review, and it gives you immediate satisfaction data. Negative responses can trigger an automatic escalation to a support agent.
Common Roman Urdu Variations Your Automation Must Handle
One reason standard WhatsApp automation fails in Pakistan is that it does not account for spelling variation. Roman Urdu has no official orthography — there is no correct spelling, only common spellings. Customers write the same word in multiple ways and expect to be understood regardless.
Here are the most common words in ecommerce conversations and their frequent variations:
| Standard Word | Common Variations | Meaning |
|---|---|---|
| haan | han, haa, hanji, hnji | yes |
| nahi | nai, ni, nahin, naheen | no |
| order | ordr, odr, orddr | order |
| delivery | dlvry, delivry, dlivery | delivery |
| confirm | confm, cnfrm, cnfirm | confirm |
| kitna | kitne, kitnay, kitney, kitnee | how much |
| theek | thk, theek hai, thik, tik | okay / fine |
| cancel | cncl, cncel, cancle | cancel |
| price | prce, prise, pryce | price |
| payment | paymt, paymnt, pymnt | payment |
If your automation handles exact matches only, a customer who replies "thk hai" instead of "theek" will get no response — or worse, a "I didn't understand that" error message.
Kliovo's ovo AI normalizes all of these variations before processing. A customer can reply "thk haa cnfrm hai" and the system correctly reads this as a confirmation. No extra configuration required — the normalization is built into the language model at the inference layer. You can see this in action by messaging chat.kliovo.com directly.
This is not a small distinction. In a store processing 500 orders per day, even a 5% misrouting rate due to spelling variation means 25 orders per day getting stuck, misconfirmed, or escalated to a human unnecessarily. At scale, Roman Urdu handling is an operations issue, not just a language preference.
Getting These Templates Approved and Live
WhatsApp Business API templates must be approved by Meta before they can be sent to customers. The process is straightforward but requires knowing the rules.
Approval timelines by template type:
Plain-text templates with no interactive buttons are typically approved within 24 to 48 hours. These are the easiest to start with — Templates 2, 4, 5, 6, 7, 8, 9, 10, and 11 from this guide are all plain-text compatible.
Templates with button interactions — Templates 1, 3, 12, 13, and 15 — require button approval and typically take one to three business days. Submit these in parallel with your plain-text templates so they are ready when your text templates go live.
Category classification affects approval rate:
Utility templates (order confirmations, shipping updates, return acknowledgments) have a significantly higher approval rate than Marketing templates. Submit your COD confirmation and order status templates under the Utility category. Reserve the Marketing category for abandoned cart and promotional messages.
Common rejection reasons to avoid:
Do not include URLs in the template body unless the URL is a variable — hardcoded URLs are flagged. Do not use template text that mimics emergency language or creates false urgency unrelated to a real business event. Keep the template focused on a single clear purpose.
Kliovo handles template submission, category classification, and approval tracking as part of the onboarding process for Kliovo Shop. Once approved, templates are loaded into the automation system and can be triggered by order events, status changes, or customer actions without manual intervention.
If you want to see the full template library — including industry-specific variants for clothing, electronics, and food delivery — visit the WhatsApp template features page.
Frequently Asked Questions
Q: Does Meta approve Roman Urdu WhatsApp templates?
Yes, Meta approves Roman Urdu templates submitted through authorized Business Solution Providers (BSPs). Roman Urdu is treated as a supported language variant under the broader Urdu language category. The key requirement is that the template must serve a clear business purpose and comply with WhatsApp's commerce policy. Templates that are conversational, non-spammy, and categorized correctly — Utility for transactional messages, Marketing for promotional ones — routinely get approved. Kliovo submits and manages template approvals on behalf of merchants as part of the onboarding process.
Q: How many WhatsApp templates can I have active at once?
Meta does not publish a hard cap on the number of approved templates per WhatsApp Business Account, but in practice accounts can maintain dozens of active templates simultaneously. The more relevant limit is the messaging tier, which controls how many unique customers you can message per day — new accounts start at 1,000 conversations per day and can scale up to 10,000 and then unlimited as you build a positive quality rating. For most Pakistan ecommerce stores starting out, the template count is not the bottleneck — message quality and customer response rates are.
Q: What is the difference between a Utility template and a Marketing template?
Utility templates are transactional messages tied to a specific customer action or order event — COD confirmations, shipping updates, return acknowledgments, and OTP codes fall into this category. Marketing templates are promotional in nature — abandoned cart recovery, discount offers, product announcements, and re-engagement campaigns. The distinction matters because Utility templates have a higher approval rate, faster review times, and are exempt from the 24-hour customer service window restriction that applies to Marketing messages. Always classify your templates correctly: mislabeling a promotional message as Utility is a common reason accounts get flagged.
Q: What happens if a customer replies to a Roman Urdu template in English?
The AI or automation system handling replies should be configured to detect and respond in whichever language the customer uses, regardless of what language was used in the outbound template. On Kliovo, ovo AI handles English, Roman Urdu, and Urdu script responses interchangeably — a customer can receive a Roman Urdu confirmation message and reply "yes please confirm" in English, and the system processes it correctly without any additional setup. If you are using a keyword-based automation system rather than an AI, you will need to configure both English and Roman Urdu keyword variants for every intent.
Q: How do I test a WhatsApp template before sending it to customers?
The standard approach is to test templates using your WhatsApp Business API sandbox environment before submitting for approval. Most BSPs, including Kliovo, provide a sandbox number where you can send yourself the template with sample variable values filled in — this lets you verify formatting, variable placement, and button behavior on an actual device. After approval, you can run a soft launch by sending the template to a small internal test segment (your own number, team numbers) before enabling it on live order triggers. Always test templates on both Android and iOS since button rendering differs slightly between platforms.
Q: Can WhatsApp templates include images or buttons?
Yes, WhatsApp Business API templates support rich media headers including images, videos, and documents, as well as interactive buttons. There are two button types: Call-to-Action buttons (which can link to a URL or trigger a phone call) and Quick Reply buttons (which send a predefined text reply back to your system). Media headers and buttons each require their own approval and take slightly longer to review than plain-text templates. For ecommerce use cases, the most common combinations are an image header with product photo plus two Quick Reply buttons for confirm/cancel, or a plain text body with a single URL button linking to a tracking page.
Q: How long does WhatsApp template approval take in Pakistan?
For accounts connected through a Meta-authorized BSP like Kliovo, plain-text Utility templates typically receive a decision within 24 to 48 hours. Templates with interactive buttons or media headers generally take one to three business days. Marketing templates can occasionally take longer if they trigger Meta's automated review for promotional content. Approval times are not region-specific — Meta reviews all templates through the same global queue regardless of whether your business is in Pakistan, the US, or elsewhere. The fastest path to approval is submitting correctly categorized, clearly worded templates with no hardcoded URLs and no urgent or emergency-style language in the template body.
Roman Urdu is not a workaround. It is the primary digital language of your market, and the businesses that communicate in it get better replies, fewer failed deliveries, and stronger customer relationships than those that do not. These 15 templates are a starting point — the real leverage comes when they are automated, personalized, and continuously improved based on what customers actually reply.