ShipOpsDigiDokaan “Assigned to courier in {city}”: what it means
In transit
Assigned to courier in {city} is Leopard's scan for a parcel handed to a delivery rider in that city, as in Assigned to courier in ISLAMABAD. It is the out-for-delivery moment. ShipOps shows it as in transit.
It can appear more than once. A parcel that reads Assigned to courier, then Pending with a reason, then Assigned to courier again failed once and went out a second time. DigiDokaan's top line then says Second Attempt.
It can also appear on the way back. After a Return to Origin, Leopard uses the same words for the return trip, so Assigned to courier there is a rider bringing the parcel back to you, not to the customer. ShipOps keeps that parcel as returning.
What to do now
| Your move | With a rider in that city. If a failed visit came before it, this is the second try going out. |
|---|---|
| The customer | If the customer is expecting it today, this is the moment to make sure they pick up the rider's call. |
How ShipOps reads it
In transit Moving inside the courier's network. Nothing for you to do, so ShipOps keeps it out of your Action Inbox. It does watch the clock: a parcel still in transit five days on, never attempted, goes on the Stuck list, where the lever is an escalation to the courier.
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 DigiDokaan statuses →
The same state on other couriers
See every DigiDokaan parcel in plain words
Connect your DigiDokaan account and ShipOps reads every status for you, raises the parcels that need a decision, and checks DigiDokaan's COD payouts against your orders. Free to start, no card.