Blue Dart Tracking

Which Blue Dart identifier are you looking at?

Blue Dart publishes more than one lookup object. Identify the object before interpreting it.

Object	What current Blue Dart evidence supports	What it does not prove
Waybill	Primary TrackDart input. Blue Dart's current How to Track page says a Waybill can vary between 8 and 11 digits.	Physical possession, order attribution, or a universal regex for every Blue Dart-related identifier.
Reference Number	Separate TrackDart input mode.	That every merchant reference is valid in TrackDart.
Order Number	A scoped regular-customer / integrated reference workflow can link an order to Blue Dart waybills.	That every e-commerce order ID is a Blue Dart tracking number.
Merchant order ID	Commercial order identity in the merchant's system.	Blue Dart attribution or possession by itself.
Pickup registration	A pickup workflow object exists.	Completed handover.

For official carrier lookup, use Blue Dart's How to Track or Tracking surfaces. Number format alone is not enough to prove that a parcel belongs to your order or that Blue Dart already has it. If a number is not found, move to Tracking Number Not Found rather than guessing a prefix or checksum.

Does Blue Dart physically have the shipment?

Read the record as an evidence ladder, not as a binary “tracking number exists / does not exist” test.

Waybill / Reference / linked Order / pickup registration exists
≠ physical possession

Pickup Employee Is Out To P/U Shipment
→ pickup activity is underway
≠ completed handover

Shipment Picked Up
→ strongest direct item-level possession evidence found in the reviewed public Blue Dart histories

Shipment Arrived / Shipment Arrived At Hub
→ stronger network custody

Shipment Further Connected
→ onward network movement

Shipment Out For Delivery
→ final-delivery run
≠ guaranteed delivery that day

explicit exception or Shipment Delivered
→ next decisive outcome evidence

The raw event labels above come from current public Blue Dart TrackDart histories reviewed without carrying customer identifiers into this page. They are useful evidence, but they are not a universal status dictionary for every Blue Dart service.

If you created or received an electronic shipment record but cannot establish physical receipt, compare Label Created with Carrier Received Package. If you physically handed over the parcel but no reliable pickup/acceptance event appears, use Dropped Off but Not Scanned.

Blue Dart currently publishes both 45-day and 90-day tracking windows

Blue Dart's current first-party pages conflict on tracking-history availability:

How to Track says shipments can be tracked for 45 days from despatch.
Tracking says shipments can be tracked for 90 days from dispatch.

There is not enough current first-party evidence to choose one as the universal rule. If an older shipment no longer appears, use the current official Blue Dart support route instead of treating either number as guaranteed for every interface or account type.

Read raw events only to the evidence they support

A small number of Blue Dart event classes materially change what you know.

Event	What it proves	What it does not prove	Next decisive evidence
`Pickup Employee Is Out To P/U Shipment`	Pickup activity was recorded.	Completed pickup or custody.	`Shipment Picked Up`, cancellation, or another pickup outcome.
`Shipment Picked Up`	Strong direct evidence of item-level Blue Dart possession in the reviewed histories.	The next route, delivery date, or successful delivery.	Facility/hub arrival or onward connection.
`Shipment Arrived` / `Shipment Arrived At Hub`	The parcel was recorded at a Blue Dart network location.	Immediate onward movement.	`Shipment Further Connected` or another facility event.
`Shipment Further Connected`	Onward network connection was recorded.	Final-mile dispatch or delivery.	Next facility, OFD, exception, or delivery event.
`Shipment Out For Delivery`	A final-delivery run was recorded.	Same-day delivery guarantee.	`Shipment Delivered` or an explicit exception.
`Consignee Not Available` or another exception	The Blue Dart system recorded that exception wording.	Recipient fault, terminal return, or a universal retry count.	Later movement, OFD, delivery, return, or investigation evidence.
`Shipment Delivered`	Blue Dart recorded delivery.	That the named intended recipient personally received it, or that contents and condition were correct.	Available POD when the handoff itself is disputed.

Current public histories show that an exception can be followed by later movement or delivery. Do not convert the wording of an exception into a hidden cause or an accusation against the recipient.

“Real-time” tracking is not one universal GPS promise

Blue Dart uses “real-time” language on several tracking/service surfaces. Ordinary TrackDart evidence reviewed here is timestamped status and location history; that alone does not establish a continuous moving-map feed.

At the same time, Blue Dart's current eCom Lite Surface page explicitly advertises real-time GPS tracking for end-consumer visibility. The safe conclusion is service-scoped:

generic Blue Dart “real-time”
≠ automatically continuous GPS

eCom Lite Surface
→ explicit current GPS wording for that service

Do not generalize either “Blue Dart has live GPS on every shipment” or “Blue Dart never has GPS.”

Out for delivery, missed delivery, and address changes

Shipment Out For Delivery means a delivery run has been recorded; it is not a same-day guarantee. The reviewed current evidence does not establish one universal Blue Dart attempt count or fixed reattempt clock.

Blue Dart's current FAQ routes both of these situations to Contact Blue Dart:

changing the address after the shipment has already been handed over;
requesting redelivery after a missed delivery.

That proves an official request route exists. It does not prove the change or redelivery is eligible, accepted, propagated to operations, or completed.

If OFD ends without delivery, use Out for Delivery but Not Delivered. For a delivery-attempt event, use Delivery Attempted. For address problems or a requested change, use Wrong Address and Change Delivery Address, Reroute, or Hold.

Delivered and proof of delivery are separate evidence layers

Blue Dart publishes strong but service-scoped POD capabilities:

Domestic Priority says computerized POD can provide consignee name plus delivery date and time on request.
Air Express Package says POD and delivery challans can be viewed, downloaded, and printed.
Surface also says POD and delivery challans can be viewed, downloaded, and printed.
Some current public TrackDart Delivered records expose a DOWNLOAD POD action.

Those facts do not establish one identical public POD object for every Blue Dart shipment.

Shipment Delivered
→ Blue Dart recorded delivery

POD available
→ stronger handoff details may exist

but

Delivered
≠ named intended recipient personally received the parcel

POD
≠ correct contents proven

POD
≠ undamaged condition proven

If you need the proof itself, use Proof of Delivery, Photo, or Signature. If the proof conflicts with what actually happened, use Challenge Incorrect Proof of Delivery. If tracking says Delivered but the parcel is missing, use Delivered but Not Received.

Blue Dart does not have one safe universal claim deadline

Identify the service and the claimant before relying on a clock.

Reviewed regime	Current first-party rule	Important boundary
Standard Blue Dart domestic carriage	Shipper must bring the written claim within 30 days from Blue Dart acceptance.	A consignee reporting a problem is not automatically the contractual shipper claim.
Blue Dart regional carriage reviewed for India/Bhutan/Nepal	Shipper written claim within 30 days from acceptance.	Regional contract scope must not be generalized to every international lane.
Airport-to-Airport	Damage notice within 14 days from receipt; loss/non-delivery notice within 90 days from Waybill issue; action within six months after the event giving rise to the claim.	This is a separate carriage regime.
Selected TDD / Money Back Guarantee	Late-delivery notice by the shipper within 48 hours of shipment date.	A service-specific guarantee is not a universal Blue Dart delivery promise.
DHL-governed international services surfaced through Blue Dart	Separate DHL written-claim rule: 30 days from DHL acceptance.	This is not the same contract object as standard Blue Dart domestic carriage.
FOV / insurance arrangement	Separate insurance route.	Do not collapse an insurance process into an ordinary carrier compensation claim.

The current Conditions of Carriage control the exact shipment rule. If the problem has moved from tracking interpretation to compensation, use How to File a Package Claim and identify the exact Blue Dart/DHL service before calculating any deadline. If a case already exists and you need to understand its state, use Carrier Investigation Open, Pending, Closed, or No Resolution.

OTP and payment fraud: keep the scope precise

Blue Dart's current Fraud Awareness page says it does not ask customers for a PIN or OTP for payments. That is a payment-fraud boundary, not proof that OTP is absent from every legitimate delivery or account workflow.

Do not share a PIN or OTP to authorize an unsolicited payment request. At the same time, do not assume that every OTP-related shipment event is fraudulent or that every Blue Dart shipment requires OTP. When a message, payment link, or delivery request looks suspicious, verify it through an official Blue Dart surface rather than using the link in the message.

Customs: Blue Dart can facilitate, but it is not the customs authority

Blue Dart terms and service pages support operational customs/clearance assistance in scoped lanes. That does not make Blue Dart the sovereign customs authority and does not guarantee release.

If the latest evidence becomes a customs hold, clearance request, duty/tax issue, or release decision, use the exact customs evidence first. For a hold that has become the controlling problem, move to Package Stuck in Customs rather than treating a carrier support promise as customs approval.

Next decisive evidence

When the current record is ambiguous, ask what future evidence would actually change the conclusion.

Current evidence	What remains unknown	Next decisive evidence
Waybill / Reference exists	Physical possession	`Shipment Picked Up` or equivalent item-level receipt evidence
Pickup registered	Completed handover	Pickup completion or cancellation
Pickup employee out	Handover completed	`Shipment Picked Up`
Shipment picked up	Onward network movement	Facility/hub arrival
Hub/facility event	Onward movement	Next connection/facility event
OFD	Delivery outcome	Delivered or explicit exception
Exception	Retry, return, or terminal outcome	Later movement, OFD, Delivered, return, or investigation
Address change requested	Accepted and applied	Operational update or changed route evidence
Redelivery requested	Reattempt occurred	New OFD / attempt / result
Delivered	Recipient and proof details	Available POD
Claim reported	Correct claimant and regime	Exact service terms plus accepted claim/case state
Customs hold	Actual release	Authority release or next carrier event
Ambiguous Blue Dart vs DHL	Controlling carrier	Actual tracking/service/terms identity

A generic “wait 24–48 hours” rule is not a substitute for these evidence transitions.

Official Blue Dart actions

Use first-party surfaces for actions that only Blue Dart or the governing carrier can perform:

TrackDart / How to Track — choose Waybill or Ref No and check the current carrier record.
Tracking — review Blue Dart's current tracking tools and the separate 90-day statement.
FAQs — current official route for address-change and redelivery questions.
Conditions of Carriage — identify the service-specific carriage and claim regime.
Location Finder — find current Blue Dart service locations and official contact routing.
Fraud Awareness — verify the payment/OTP safety boundary.
International Services — identify DHL-branded international service scope before applying DHL rules.

11Tracking can help organize public tracking evidence. It cannot create a Blue Dart scan, contact Blue Dart or a driver, change an address, request redelivery, retrieve private POD, file a claim, clear customs, or guarantee delivery.

Blue Dart and DHL are trademarks of their respective owners. 11Tracking is an independent tracking helper and is not affiliated with or endorsed by Blue Dart or DHL.

Tracking data notice

Tracking events and delivery estimates come from connected tracking services and carriers. Updates may be delayed, incomplete or revised. 11Tracking does not transport packages and cannot change a delivery.

Privacy note

After you track a parcel, its number is added to the page address so the result can be refreshed or shared. Anyone with that link can use the number, so share it only with people you trust.