Parcel tracking: what each QCS status actually means

Every QCS parcel is in exactly one status, and each one means something specific about where it is and who has to act next. Tracking pages across the trade tend to compress this into three or four friendly words, which is comfortable and useless when you need to know why a parcel has not moved.

Here is the full list, what each one actually means, and who is holding it.

Before collection

Booked

The order exists with a tracking number, a consignee and a COD amount. It is with you and it is not collectable yet. The most common reason a parcel never moves is that it stayed here.

Pickup requested

You have forwarded it to the pickup request. It is now in our queue. If you ship daily, an auto-pickup time does this automatically at an hour you choose.

Pickup assigned

A pickup rider has been assigned and is coming. Nothing for you to do except have it packed and labelled.

Picked up

The rider scanned it at your premises. The scan is the event, not the conversation: a parcel he did not scan does not reach this status. Custody is now with the rider.

Pickup failed

The parcel was expected and not handed over. It is back in your booked list with a reason code against it and an entry in the history. This is a normal outcome rather than an error, and it is how the two sides stay agreed on what was collected. Labels and load sheets covers making the handover countable.

At the warehouse

At warehouse

Scanned in at Gulberg and in stock. Nothing enters stock without that scan. Your customer is notified at this point, and it is the first status visible outside the operation.

Dispatch assigned

Assigned to a delivery run but not yet on the road. Nothing leaves for delivery without this assignment, which is the outbound counterpart of the inbound scan.

On the road

Out for delivery

With a rider, on a route he sequenced himself. The customer has been notified, which is the message that most affects whether somebody is actually in.

Delivered

Handed over, with proof of delivery attached. The proof is not optional: a parcel cannot carry this status without it, refused at the data layer rather than discouraged in the interface.

This status is also the one that moves money. The delivery charge is computed and frozen, a balanced journal is posted, and your payable is credited with the COD amount less that charge, all in one transaction. Proof of delivery explained covers the evidence and reading your COD statement covers where the figures land.

On hold

The attempt did not complete. Nobody answered, the address could not be found, or the customer asked for another day. A reason code and evidence are recorded.

Refused

The customer was there and declined. Reason code and evidence recorded. Not charged.

Coming back

Returning to warehouse

On its way back after a hold or a refusal. It is not in stock yet, and it will not be until it is scanned in.

Cancelled

The attempt threshold was reached and the back office cancelled it, or it was cancelled for another recorded reason. The parcel is now destined for you rather than the customer. Not charged.

RTS assigned, RTS in transit, RTS delivered

The return journey to you, as its own three stages: queued on a run, on the road, and handed back with the handover scanned exactly as a collection is. You are told when the return leg starts rather than discovering it when a rider arrives.

The two nobody wants

Lost

The parcel cannot be located. It is a recorded state with a trail rather than an absence of updates, which is the point: a parcel that is missing should say so rather than sitting in a stale status.

Damaged

Recorded as damaged, with evidence. Open a dispute on the order, because that is the path that reaches the record rather than a conversation.

What the public tracking page shows, and why it shows less

Anyone holding a tracking number can look it up, so the public tracking page deliberately masks what the merchant view does not. Partial consignee name, the area rather than the full address, and no phone number. A page that showed all three would be a lookup service for strangers.

How to read a stuck parcel

1. 01Booked for more than a day means you did not forward it
2. 02At warehouse for longer than usual can mean a zone could not be resolved and it is waiting on a geo review decision
3. 03On hold means the attempt cycle is running, and the gap before the next attempt is your cheapest moment to intervene with one message
4. 04Anything else: the order history carries every transition with its actor and timestamp, and the history is append-only, so a correction is a new row rather than an edit

What a courier actually does with your parcel maps these statuses onto the ten operational stages, and the pricing calculator prices a parcel before any of them apply to it.