ShipOpsDeshi Express (Bridge Courier) “HALT_DELIVERY”: what it means
Attempt failed
Deshi Express HALT_DELIVERY appears in the evening after Out For Delivery when the rider could not deliver. It is a failed visit.
The next morning usually brings ADVICE_REQUESTED: the courier asking you whether to try again or send it back.
What to do now
| Your move | The delivery stopped tonight. Reach the customer, then answer the courier tomorrow. |
|---|---|
| How long it usually lasts | Overnight, then the courier asks for your advice. |
| Retry or return | Deshi Express (Bridge Courier) does not take a retry or return instruction from outside its own portal, so the answer goes in by hand on the Deshi Express (Bridge Courier) portal; ShipOps still shows the parcel with its reason and links you there. |
The reasons Deshi Express (Bridge Courier) gives on a failed visit
| Non-service area | NSAAddress problem |
|---|---|
| Refused to accept | REFCustomer refused |
| Consignee not available | CNACustomer not available |
| Consignee out of city | OOCCustomer not available |
| Order cancelled | CAN |
| Address issue | ADRAddress problem |
| Phone not responding | NRPPhone problem |
| Needs review | OTHER |
How ShipOps reads it
Attempt failed A delivery failed, the courier still has it. The parcel goes into the Action Inbox with the courier's reason in plain words. The useful move is to reach the customer before the next attempt; ShipOps puts the call and WhatsApp buttons on the row and counts the attempts made so far.
ShipOps shows every courier's parcels in the same few plain states, so your team learns one set of words instead of one per courier. All Deshi Express (Bridge Courier) statuses →
The same state on other couriers
See every Deshi Express (Bridge Courier) parcel in plain words
Connect your Deshi Express (Bridge Courier) account and ShipOps reads every status for you, raises the parcels that need a decision, and checks Deshi Express (Bridge Courier)'s COD payouts against your orders. Free to start, no card.