ShipOpsTCS “No Such Receiver”: what it means
Needs your decision
TCS No Such Receiver means the rider found the address, but nobody there would take the parcel for the person named on it. The address exists; the name does not match anyone at it. TCS prints it as plain text with no code.
Look at the name before the address. A gift order, a nickname at checkout, a family member's name, or a house with new tenants all end up here. A quick message to the customer usually tells you which.
ShipOps puts it in Needs attention with the address problems. Send a retry with the right name, or the name of whoever will receive it, in the remarks. If you cannot reach the customer at all, weigh a return before paying for another visit.
What to do now
| Your move | Confirm with the customer who will receive it, then retry with that name in the remarks. |
|---|---|
| Retry or return | TCS takes a retry or return instruction only while the parcel is in its review window. ShipOps raises the parcel when that window opens and files the instruction from the order. |
| Attempts | TCS tries 3 times before it starts a return. |
The reasons TCS gives on a failed visit
| Status Has Been Incorrectly Updated | 99Courier-side |
|---|---|
| Consignee not home | HNCustomer not available |
| Receiver Not Available | CNCustomer not available |
| No Response on mobile | NMPhone problem |
| No Response on phone | NRPhone problem |
| Receivers premises closed | RCCustomer not available |
| Delivery Rescheduled | DR |
| SCHEDULED FOR NEXT DELIVERY CYCLE | NDCourier-side |
| Refused to accept | RDCustomer refused |
| On Hold | OHCourier-side |
| Temporary On Hold at TCS Facility | THCourier-side |
| Bad Address | BAAddress problem |
| BAD ADDRESS | BDAddress problem |
| Wronge Address | WAAddress problem |
| INCOMPLETE ADDRESS | IAAddress problem |
| Unable To Locate Delivery Address | ULAddress problem |
| Address Closed | CAAddress problem |
| Need Further Consignee Information | NCAddress problem |
| Receiver Shifted From Delivery Address | NPAddress problem |
| Consignee Shifted | CSAddress problem |
| Mobile Switched Off | MOPhone problem |
| Wrong Mobile Number | WMPhone problem |
| No Telephone Number | NTPhone problem |
| Wrong Land Phone Number | WPPhone problem |
| Awaiting Correct Number | ANPhone problem |
| HOLD FOR COLLECTION | HFHeld |
| Held for Self Collection | SCHeld |
| Held for Payment | HPHeld |
| STOP DELIVERY | STCourier-side |
| Shipment Stop | SSCourier-side |
| Please Contact TCS | PCCourier-side |
| Contact TCS Local Customer Services | CSCCourier-side |
| Contact TCS Local Customer Services | CSRCourier-side |
| Out of delivery Area | NSAddress problem |
| OUT OF SERVICE AREA | OSAddress problem |
| Short Received | SRCourier-side |
| Shipment Partially Received | PRCourier-side |
| Partial Piece Delivered | POK |
| Partial delivery | PD |
| Shipment Damaged | DMLost or damaged |
| Prohibited Item | PILost or damaged |
| Lost shipment | LSLost or damaged |
| Abandon Shipments | ABLost or damaged |
How ShipOps reads it
Needs your decision The courier is waiting for your decision. This is the window where an instruction still changes the outcome. ShipOps raises the parcel to the top of the Action Inbox, and where the courier lets ShipOps send a retry or return, the buttons on the row file it with the courier directly.
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 TCS statuses →
The same state on other couriers
See every TCS parcel in plain words
Connect your TCS account and ShipOps reads every status for you, raises the parcels that need a decision, and checks TCS's COD payouts against your orders. Free to start, no card.