The order confirmation message gets treated as a receipt — 'thanks, order #4521 confirmed'. It's actually the first ops checkpoint: the moment to catch bad addresses, verify COD intent, and set the delivery expectation correctly.
The address-preview trick
Confirm with the address visible — 'shipping to: 402 Lotus Soc, MG Road, Pune 411001' with 'wrong? reply here'. The customer who mistyped their flat number catches it themselves; the fix happens before the parcel exists.
The COD verification
For COD orders specifically: 'confirm this order — reply YES'. Unconfirmed CODs are the fake/impulse orders that refuse at the door — sellers report 10–20% of COD orders never confirm, which is RTO cost avoided entirely.
The expectation anchor
'Arrives [date range]' in the confirmation sets the clock correctly — the customer's wait-timer starts with the right expectation, not the imagination. The message is also where delivery-instruction prompts live ('riders call before delivery — keep your phone on').
The channel
WhatsApp > email for Indian customers — open rates are 95% vs ~20%. The confirmation lands where the customer actually reads it; an emailed confirmation is a confirmation nobody saw.
Pakka Parcel runs the whole stack described here — one place for every carrier.
See how →The playbook
Show the address in the confirm
Customer-caught typos are free fixes.
Add 'confirm COD' for COD orders
Unconfirmed = probably fake — filter before shipping.
Anchor the ETA at confirmation
'Arrives Oct 24–26' starts the clock right.
Send via WhatsApp
Read rates matter — the channel is the deliverability.
