ShipOpsNext Step “REATTEMPT_REQUEST”: what it means
Attempt failed
Next Step REATTEMPT_REQUEST is your own answer repeated back on the parcel: you, or someone on your account, asked Next Step to try the delivery again. It is not a new visit and not a new problem.
It comes right after ADVICE_REQUESTED: stopped, asked, retry requested, and then the parcel goes out again. Some parcels go round that loop and still come back.
ShipOps does not ask you again about a parcel you have already answered, and it does not count this as another failed visit. Watch for OUT_FOR_DELIVERY next.
What to do now
| Your move | Your own retry, repeated back. Nothing to do; watch for the next run. |
|---|---|
| Retry or return | Next Step takes a retry or return instruction only on a parcel it has opened a ticket for. ShipOps keeps an eye on those tickets and puts the buttons on exactly those parcels. |
The reasons Next Step 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 Next Step statuses →
The same state on other couriers
See every Next Step parcel in plain words
Connect your Next Step account and ShipOps reads every status for you, raises the parcels that need a decision, and checks Next Step's COD payouts against your orders. Free to start, no card.