How should a D2C brand handle COD confirmation and NDR follow-up?
A practical CRM workflow for Indian D2C brands to confirm cash-on-delivery orders and follow up on non-delivery reports before parcels return.
Anadoris Digital · · 4 min read

Cash on delivery remains important for many Indian D2C brands, but it brings fake orders, impulse purchases and failed deliveries. Every parcel that comes back costs forward and return shipping, packaging and sometimes damaged stock. Much of that loss is avoidable with a tight confirmation and non-delivery report (NDR) process.
The key is treating it as a daily queue in your CRM, not something handled from whoever’s phone is nearest.
Step one: confirm the COD order
Send a WhatsApp message shortly after the order is placed, showing the items, amount and address, with simple reply buttons to confirm, change the address or cancel. Many customers prefer this to a phone call. Hold dispatch until the order is confirmed or a set time has passed.
- Confirmed: release for packing.
- Address change: update the order before the label is generated.
- Cancel: cancel without shipping, and record the reason.
- No reply: send one reminder, then add to a call list for the team.
Step two: decide what happens to unconfirmed orders
Set a clear rule for orders that never get confirmed after the reminder and call attempt. Some brands cancel them, others ship but flag them as higher risk. Base the rule on your own data: compare delivery rates of confirmed and unconfirmed orders over a few weeks. Repeat customers with a good history may skip confirmation altogether.
Use the confirmation step to nudge prepaid payment gently. A line offering a small benefit for paying online, with a secure payment link from your provider, converts some COD orders without pressure. Never make confirmation feel like an interrogation; the tone should be that of a helpful store checking the address is right. Customers who feel trusted are more likely to accept the parcel and to order again.
Step three: act on every NDR quickly
When a courier reports a failed delivery, reasons usually include customer unavailable, address incomplete, customer refused, or phone not reachable. Each needs a different action, and couriers typically allow only a limited number of reattempts before returning the parcel. Pull NDRs into the CRM as tasks, contact the customer on WhatsApp first, then call, and update the courier with a new date, corrected address or instruction.
- Customer unavailable: ask for a preferred delivery day and pass it on.
- Address incomplete: get a landmark, alternate number or corrected address.
- Refused: ask why; offer an exchange or prepaid option if relevant, or accept the return.
- Not reachable: try the alternate number and WhatsApp before the next attempt.
- Suspected fake attempt: raise it with the courier with evidence from the customer.
Why this belongs in the CRM, not the courier portal
Courier dashboards show NDRs, but they do not know the customer. In the CRM the person handling the case can see whether this is a loyal regular with a one-off problem, a first-time buyer who never confirmed, or someone who has refused parcels before. That context changes the right action: a regular deserves an extra effort and perhaps a call; a repeat refuser may warrant a prepaid-only flag.
Keeping COD and NDR work in the CRM also means every contact is logged on the customer timeline. If the customer later complains or asks for a refund, support can see exactly what was said and when. If you use more than one courier, the CRM gives you one queue instead of several portals to check.
Reading the weekly numbers
Each week, look at confirmation outcomes, NDR reasons and final return-to-origin cases side by side. Rising ‘customer unavailable’ reasons in one area may point to a courier problem rather than a customer one. A growing share of unconfirmed orders from one ad campaign may mean the creative attracts impulse buyers. These patterns are easy to miss when the work is scattered across phones.
Checklist for a working COD and NDR desk
- Every COD order gets an automatic WhatsApp confirmation request.
- Unconfirmed orders appear in a call queue with a named owner.
- NDRs arrive in the CRM as tasks, not as emails or courier portal alerts.
- Each NDR has a recorded action and outcome before the next attempt.
- Refusal and cancellation reasons are tagged for weekly review.
- Customers with repeated refusals are flagged for prepaid-only at checkout.
Do not take payment or card details over WhatsApp or phone. If you offer a prepaid switch, send a secure payment link from your payment provider and follow current payment and data protection rules.
Where to start
- Turn on WhatsApp COD confirmation with reply buttons for your store.
- Make one person responsible for the daily unconfirmed and NDR queue.
- Connect your courier’s NDR feed to the CRM so each case becomes a task.
- Review return reasons weekly and adjust COD rules for high-risk pin codes or patterns.
Anadoris Digital sets up COD confirmation and NDR queues inside CRMs for D2C brands, connected to store and courier data.
Related service: CRM Solutions · More on this topic: CRM Solutions articles
