Aadil Pathan reports two Delhivery shipments stuck at Srinagar Chadoora centre without updates. AWB 19041786835662 & 19041786834446 pending since booking. Complaint published on Choice4Voice.com to urge quick resolution.
Complaint Summary : Delhivery – Aadil Pathan’s Complaint on Shipment Delay at Srinagar Centre | Choice4Voice.com
| Complainant Name | Aadil Pathan |
|---|---|
| Company Name | Delhivery Ltd. |
| Nature of Complaint | Shipment delay and lack of status update |
| Incident Date | August 2025 |
| AWB Numbers | 19041786835662, 19041786834446 |
| Shipment Status | Both parcels at Srinagar_Chadoora1_Dpp centre, not uploaded |
| Location Mentioned | Srinagar, Jammu & Kashmir, India |
| Main Issue Raised | Delay in shipment processing and non-updation of tracking |
| Expected Action | Escalation to delivery centre, high-priority processing |
| Original Post Platform | |
| Original Post Link | View LinkedIn Post |
Case Overview
At Choice4Voice.com, we highlight unresolved consumer complaints to ensure companies take timely action.
In this case, Aadil Pathan, a Delhivery customer, booked two orders with AWB numbers 19041786835662 and 19041786834446. Both shipments are currently at Srinagar_Chadoora1_Dpp in Jammu & Kashmir but have not been uploaded or processed for onward delivery.
Despite being booked, the orders have seen no status updates. This delay impacts not only the expected delivery timelines but also creates uncertainty for the recipient.
Aadil has requested that Delhivery escalate the matter with the local delivery centre and process the shipments as a high priority.
Key Concerns Raised
- Lack of Tracking Updates – Shipments booked but not reflected in system updates.
- Operational Delay at Srinagar Centre – Processing lag affecting delivery timelines.
- Customer Communication Gap – No proactive updates or reasons provided to the customer.
- Business Impact – Delays in critical shipments may disrupt personal or commercial commitments.
- Escalation Requirement – Immediate attention needed from senior Delhivery support teams.
Why This Matters to Consumers
Timely delivery is a fundamental expectation in courier services. Lack of tracking updates and unexplained delays erode customer trust.
This case emphasizes the importance of real-time operational transparency — customers should be able to see accurate shipment movements in the tracking portal.
Choice4Voice.com believes that courier companies like Delhivery must have strict Service Level Agreements (SLAs) to ensure customers are not left waiting without updates.
Choice4Voice.com 20-Question Consumer Awareness Q&A
Q1: What does it mean when a shipment is “at the centre but not uploaded”?
It usually means the package has reached a local hub but has not yet been scanned or processed for the next delivery leg.
Q2: How long can a shipment stay at a hub without updates?
Ideally, parcels should be processed within 24 hours; delays beyond that are considered service inefficiencies.
Q3: Can the customer request hub-level escalation?
Yes customers can directly email Delhivery’s escalation team with AWB details for faster action.
Q4: What is an AWB number?
AWB (Air Waybill) is a unique tracking number assigned to each shipment for identification and tracking.
Q5: Does Delhivery have a delivery timeline policy?
Yes timelines depend on the service type, but standard shipments usually take 2–7 days across India.
Q6: Can tracking errors cause shipment delay?
Sometimes if a package is physically present but not digitally updated, it can appear “stuck” even if moving.
Q7: How can customers confirm if the package is safe?
By contacting Delhivery support and verifying the last scanned location and handling status.
Q8: What causes shipment bottlenecks in regional centres?
Staff shortages, high parcel volumes, weather disruptions, or system glitches.
Q9: Can a customer claim compensation for delayed delivery?
For business shipments under contract, yes; for personal shipments, it depends on Delhivery’s policy.
Q10: How does Delhivery normally handle high-priority shipments?
Such parcels are fast-tracked through hubs and updated in the system promptly.
Q11: Can hub delays affect the package’s condition?
If stored properly, no but prolonged storage without climate control could damage sensitive goods.
Q12: Are customers entitled to daily tracking updates?
While not legally required, daily updates are part of best practices for courier services.
Q13: Can the customer approach a consumer court for delay?
Yes if the delay causes financial or material loss and the courier fails to resolve it.
Q14: Does Delhivery have a public grievance redressal system?
Yes via their website, social media handles, and escalation emails.
Q15: How can social media complaints help in courier disputes?
Public visibility often prompts quicker responses from company teams.
Q16: Can AWB numbers be tracked on third-party apps?
Yes several parcel tracking apps aggregate data from courier APIs.
Q17: What steps can customers take if tracking is stuck?
Call customer care, email escalation teams, and request hub manager contact details.
Q18: How do courier hubs prioritize shipments?
Based on delivery deadlines, customer type (business/priority), and route optimization.
Q19: Could this be a case of misplaced parcels?
Possible but unlikely if both shipments are shown at the same hub; likely a scanning delay.
Q20: What should Delhivery do to resolve Aadil Pathan’s case?
Immediate scanning, tracking update, and dispatch of both AWB shipments with delivery commitment date.
At Choice4Voice.com, we believe every delay deserves attention because customers rely on timely service not just for convenience, but for essential deliveries. Aadil Pathan’s case is a reminder that tracking transparency and operational speed are key to trust in logistics services.
