It is 07:45 PM on a Saturday evening. You are monitoring your shipping dashboard when an order tracking status suddenly turns bright red:
“Delivery Attempted: Customer Refused Delivery / Consignee Unavailable at Address.”
You immediately shoot a WhatsApp message to the customer asking why they rejected the shipment. Two minutes later, the customer replies with utter shock:
“Sir, nobody came to my house! Nobody even called me. I took half a day off from work just waiting for this parcel. Why did your delivery boy cancel it?”
Welcome to the most toxic, profit-draining reality in Indian e-commerce: the Fake Non-Delivery Report (Fake NDR).
Across logistics providers like Delhivery, Ekart, Shadowfax, Xpressbees, and Blue Dart, field delivery executives are subjected to brutal 12-hour shifts with unrealistic delivery quotas (often 80 to 110 parcels per day). When a driver gets stuck in evening traffic or cannot find an outskirt address by 07:00 PM, they face a severe performance penalty if parcels remain marked as "Pending".
To clear their handheld terminal before their shift ends, many drivers pull over at a roadside tea stall and scan 15 to 25 remaining parcels as "Customer Refused" or "Premises Closed".
Three such fake attempts, and your parcel is automatically slapped with an RTO (Return to Origin) status. You lose the sale, forfeit ₹65 to ₹120 in two-way courier freight, suffer box damage, and earn an angry customer review.
Here is the step-by-step operational protocol to detect fake NDR attempts within 60 minutes, gather indisputable forensic evidence, and force the courier hub manager to execute a mandatory next-day doorstep delivery.
Anatomy of the Fake Scan: How Delivery Drivers Game the System
To defeat fake delivery attempts, you must understand the operational mechanisms drivers exploit:
- 1The Ghost Dial (Single-Ring Scam): The driver dials the customer through the courier IVR bridge and disconnects after half a second. The carrier's automated system logs an "attempted call", but the customer's phone never had time to ring.
- 2The 7:00 PM Cluster Scan: Check the scan timestamps on your logistics portal. If 12 parcels across completely different neighborhoods in a city were scanned as "Customer Unavailable" within a 4-minute window between 07:15 PM and 07:19 PM, it is physically impossible for the driver to have visited those locations.
- 3The Far-Flung Geofence Cheat: Delivery handhelds log GPS coordinates at the instant of scanning. Drivers frequently scan parcels while still 4 kilometers away from the customer's residential pin code.
- 4The False Address Landmark Excuse: Marking "Address Incomplete / Landmark Not Found" even when the customer provided a complete house number, society name, and landmark.
Step 1: The 60-Minute WhatsApp Buyer Verification Protocol
Speed is everything. Once a courier logs an NDR, you have a strict 24 to 48-hour operational window before the automated system marks the shipment for RTO return routing.
The second an NDR scan triggers on your webhook or dashboard, dispatch an automated WhatsApp interactive verification message:
Namaste [Customer Name],
Regarding your order #[Order ID] containing [Product Name]:
Our courier partner ([Courier Name]) just updated your tracking status as:
"Delivery attempted - Customer unavailable / refused".
Could you please confirm if the delivery executive visited your doorstep or called your phone today?
[Button: ❌ No Call / No Visit Made]
[Button: 🔄 Please Re-Attempt Tomorrow]
[Button: 🚫 I Wish to Cancel Order]When the customer clicks [❌ No Call / No Visit Made], take an immediate screenshot of the timestamped conversation. That single screenshot is your legal ammunition against the courier partner.
Step 2: Extracting Forensic Proof from Courier Portals
Log into your courier aggregation dashboard (Shiprocket, NimbusPost, Pickrr) or direct carrier portal (Delhivery One, Ekart Logistics):
1. Request the IVR Call Recording / Bridge Log
Under courier Service Level Agreements (SLAs), a delivery executive is strictly mandated to place an outbound call through the masked carrier bridge before logging an NDR.
- If the call log shows 0 seconds duration or No Call Initiated, the delivery attempt is legally invalid.
- State clearly to support: "Demand IVR bridge call audio log for AWB [Number] between 07:00 PM and 08:00 PM."
2. Audit the GPS Coordinates of the Attempt Scan
Every handheld device records latitude and longitude during barcode scanning.
If the delivery address is in Indiranagar, Bengaluru, but the scan coordinates show Outer Ring Road, the courier hub manager cannot defend the driver.
Step 3: The Escalation Notice That Forces Action
Never file a generic "Please re-attempt" ticket. Standard tickets are handled by low-tier customer support bots who simply paste boilerplate replies.
Instead, route your escalation directly to the Courier Nodal Escalation Desk / Cluster Hub Manager using this formal breach template:
SUBJECT: URGENT: SLA Breach & Fraudulent NDR Attempt Notice — AWB [AWB_NUMBER]
To: [Courier Escalation Desk / Hub Manager Email]
CC: [Senior Account Manager]
Dear Logistics Operations Team,
We are issuing a formal notice of a FRAUDULENT NON-DELIVERY SCAN for shipment AWB: [AWB_NUMBER], dispatched under Merchant Account: [Merchant ID].
INCIDENT DETAILS:
- AWB Number: [AWB_NUMBER]
- Destination PIN Code: [PIN_CODE]
- False Scan Timestamp: [Date & Exact Time]
- False Reason Recorded: "Customer Refused Delivery / Consignee Unavailable"
EVIDENTIARY AUDIT:
1. CUSTOMER VERIFICATION: The consignee, [Customer Name] (Phone: [Phone Number]), has provided written confirmation that NO delivery executive visited the premises, and NO telephone call was received. Screenshot attached.
2. ZERO IVR ATTEMPT: Carrier records fail to show a valid, connected IVR bridge call exceeding 15 seconds to the registered phone number prior to the scan.
3. CLEAR SLA VIOLATION: This scan represents a falsified record generated to avoid end-of-day route completion penalties.
REQUIRED IMMEDIATE ACTION:
1. Suspend automated RTO routing for this AWB immediately.
2. Mandate a PRIORITY FIRST-ATTEMPT DELIVERY tomorrow, [Next Date], with pre-delivery calling.
3. Credit back any false attempt / NDR surcharges associated with this shipment.
If this shipment is routed back as an unauthorized RTO due to carrier negligence, we will file a full formal claim for two-way freight charges plus product transit value under Section 9 of our Merchant Logistics Agreement.
Awaiting confirmation of re-dispatch within 4 business hours.
Regards,
Logistics & Fulfillment Team
[Your Brand / Company Name]3 Automated Safeguards to Prevent Fake NDRs
To protect your business from bleeding thousands of rupees in avoidable RTO freight, implement these three automated operational guards:
- 1OTP-Verified Delivery Only: Configure your courier settings so that a package can ONLY be marked as "Delivered" or "Customer Refused" after entering a 4-digit OTP sent to the customer’s phone. A driver cannot fake a customer refusal if they cannot obtain the cancellation OTP.
- 2Courier Hub Blacklisting: Track fake NDR rates by courier branch. If a specific local delivery hub in East Delhi or North Kolkata consistently records a 35%+ fake attempt rate, remove that courier partner from your routing engine for those specific 3-digit PIN code clusters.
- 3Automated WhatsApp Re-Attempt Triggers: Integrate your shipping aggregator webhooks with a WhatsApp API. When an NDR triggers, an automated prompt should let the customer pick their preferred re-delivery date and time slot, which automatically pushes into the courier API.
Use our free Fake NDR Dispute Generator to draft compliant legal notices with one click whenever a rogue driver scans your parcel as refused.