WhatsApp Delivery OTP & Pickup Codes: Verify Deliveries in Chat (2026)
Every COD seller knows the pain: the courier arrives, the customer says "I never ordered this," and the parcel comes back — a return-to-origin shipment that costs you shipping both ways. WhatsApp delivery OTPs are the 2026 answer: a one-time code sent in chat that the customer must quote before the parcel is handed over. It's a practical, proven way to cut fake orders and RTO. The Tech Pad, a WhatsApp Business API platform built on the official Meta Cloud API, makes it easy to build the delivery OTP and pickup code templates — its Templates Hub ships delivery_otp and pickup_ready starters in the AUTHENTICATION category, Meta's cheapest and fastest-approving tier. There's no monthly SaaS fee; you pay only Meta's per-message rate. Here's how delivery verification on WhatsApp works, and how to set up your code templates.
Why send delivery OTPs and pickup codes on WhatsApp
A delivery code works because it changes who is in control at the doorstep. Instead of hoping the courier and the customer agree on whether an order was real, you give the customer a code and the courier a rule: no code, no parcel. Fake orders, wrong-address claims and "I never ordered this" refusals lose their power, because the person receiving the parcel had to actively produce a code for it. It's the same playbook as COD confirmation — see how [COD confirmation on WhatsApp cuts RTO and fake orders](/blog/cod-confirmation-whatsapp-cut-rto-fake-orders/) — applied at the moment of delivery.
WhatsApp is the right channel for the code itself. SMS codes get lost, delayed or ignored; emails are worse. WhatsApp messages open at a 98% rate, so the code is in front of the customer's face when the courier calls — not buried in a notification graveyard. A customer who must quote a code at delivery has already committed to the order, which is exactly why confirmed deliveries with codes cut fake orders and return-to-origin shipments substantially.
There's a cost angle too. One-time codes use the AUTHENTICATION category — Meta's cheapest and fastest-approving category, reserved for exactly this: login codes, delivery codes, verification pins. Templates approve in minutes, not hours. On The Tech Pad, sending the code costs only Meta's per-message rate — no platform markup, no monthly SaaS fee. [WhatsApp Business API pricing in India](/blog/whatsapp-business-api-pricing-india-2026/) breaks down the categories.
What you need before you start
- A WhatsApp Business Account (WABA), set up through The Tech Pad dashboard.
- A business phone number not already linked to the consumer WhatsApp app.
- Approved AUTHENTICATION templates — delivery_otp or pickup_ready from the Templates Hub, the fastest-approving category on the platform.
- Delivery partners or pickup counters that verify the code before handing over the parcel.
- Your store connected via the free Shopify or WooCommerce plugin so you can trigger on out-for-delivery and ready-for-pickup events.
- A note on automation: The Tech Pad is rolling out full OTP automation — auto-sending on delivery events and verifying replies in chat. The template-building steps below are live today; automated send-and-verify is on the way, so ask us where it stands.
How to set it up (step by step)
- Open the Templates Hub in The Tech Pad dashboard and pick the delivery_otp starter (or pickup_ready if you're doing store pickup).
- Write the body with {{1}} as the code variable — a 4–6 digit one-time code generated per order.
- Set the category to AUTHENTICATION. Never use MARKETING or UTILITY for codes — the category is immutable after approval, and Meta restricts what auth templates can carry.
- Submit to Meta. Authentication templates are the fastest-approving category; approval typically lands in minutes.
- Send the template when the order goes out for delivery (or is marked ready for pickup), passing the generated code in the {{1}} variable.
- The courier or pickup counter asks for the code and releases the parcel only when the customer quotes it correctly.
- What's rolling out: the platform is rolling out the automation layer — firing the OTP template automatically on out-for-delivery or ready-for-pickup events, capturing the customer's reply with the code, and marking the order verified in your Shopify or WooCommerce integration without anyone checking codes by hand.
Message templates that work
| Trigger | Example message |
|---|---|
| COD order out for delivery | Your order {{2}} is out for delivery. Your one-time delivery code is {{1}} — share it with our delivery partner to receive the parcel. |
| Ready for pickup | Your order {{2}} is ready for pickup at our store. Show code {{1}} at the counter to collect it. |
| Warranty service pickup | Your device {{2}} is ready for service pickup. Hand code {{1}} to our technician when they arrive. |
| Rented-item return | Time to return your rental {{2}}. Our courier will collect it — your return code is {{1}}. |
"Your order is out for delivery! Your one-time delivery code is {{1}} — please quote it to our delivery partner to receive the parcel. Order {{2}}."
"Your package is ready for pickup. Show this code — {{1}} — at the counter to collect order {{2}}. The code expires after use or within 24 hours."
Best practices — and when NOT to use it
Keep codes 4–6 digits, unique per order, and expired after use or after a short time window — expiry is what makes the code secure and what stops reuse. Note that code templates have no buttons: Meta restricts authentication templates, so the code is the message. That's fine — the message's only job is to deliver the code.
Never send marketing inside an AUTHENTICATION template, and never file a code template under UTILITY or MARKETING to save a few paise — the category is immutable after approval, and Meta can reject or restrict mis-categorised templates. Don't send codes for orders that don't exist, and make sure your courier or counter process can actually check the code — the system is only as strong as the doorstep check.
Respect frequency, too. One code per delivery event is right; codes are not a channel for reminders, offers or any other content. If you find yourself wanting to say more than the code, that's a UTILITY or MARKETING message — send it separately.
FAQ
How does a WhatsApp delivery OTP work? A. When an order is out for delivery, the store sends a one-time code via WhatsApp (AUTHENTICATION category template). The courier or pickup counter asks the customer for the code and only releases the parcel when the code matches.
What category is an OTP template? A. One-time codes must use the AUTHENTICATION category — Meta's cheapest and fastest-approving category, reserved for exactly this: login codes, delivery codes, verification pins. You cannot send marketing in it.
Does a delivery code actually reduce RTO? A. Yes — confirmed orders with a code cut fake orders and return-to-origin shipments substantially. A customer who must produce a code at delivery has already committed; the same playbook works for store pickup and COD confirmation.
Can the customer reply with the code in chat? A. Yes — with the right setup the reply is captured and the order is marked verified automatically, so your team doesn't manually check codes. The code also expires after use or after a time window for security.
Send Delivery OTPs on WhatsApp Today
Delivery verification is one of the highest-leverage things an ecommerce store can automate — and with The Tech Pad it costs almost nothing to start. You get the official WhatsApp Cloud API, free connector plugins for Shopify and WooCommerce, one-click template approval, and no monthly SaaS fee — you pay only Meta's per-message rate, and AUTHENTICATION is Meta's cheapest category. Build the delivery_otp or pickup_ready template in the Templates Hub, submit to Meta, and pair it with your out-for-delivery process. Code replies land in your shared team inbox, and the platform is rolling out full send-and-verify automation. Get started at [thetechpad.com/wa/](/wa/) today — and see how code replies and verification threads are handled in [The Tech Pad inbox](/features/inbox/).