ShipOpsCouriersNext
ShipOps connects to your CouriersNext account with the auth key from portal.couriersnext.com. It lists your parcels directly, reads CouriersNext's statuses into plain words, books and prints labels, and marks each parcel CouriersNext says it has paid, with your payout statement read in beside it.
CouriersNext runs its merchant portal on iCargos, the same white-label courier platform ShipKartex and Run Courier use. The API is the same document with the host changed to portal.couriersnext.com, and so is the status list. ShipOps uses one platform adapter and gives CouriersNext its own connection, its own state and its own pages, because to you it is its own courier with its own payouts.
CouriersNext's installation differs from the other two in details that matter to a tool and not to you: its list and trail clocks agree (both Pakistan time, to the second), and its label data route serves label rows in about 60 milliseconds. ShipOps renders the 4×6 label itself from that data rather than fetching the portal's HTML label page, which sits on a sequential id with no login.
The API has no advice call, no settlement report and no webhooks. It does carry a per-parcel payment flag, Paid or Pending, which ShipOps reads as the courier's word and never as an amount.
What ShipOps does with CouriersNext
| Live tracking | Yes. ShipOps lists parcels from your CouriersNext account directly, then follows each one. A parcel you booked outside ShipOps is still found. |
|---|---|
| Retry / return instruction | CouriersNext has no API for a retry or return instruction. ShipOps still shows the parcel in your inbox with the reason, and links you to the CouriersNext portal to answer by hand. |
| Booking and labels | Yes. Book from the order, print the label, cancel a booking. Services: Account default. Label layouts: 4×6 shipping label. |
| COD payouts | Automatic · statement upload. CouriersNext answers "was this parcel paid?" per parcel; ShipOps asks for every delivered parcel and marks what the courier attests. Drop in the payout statement CouriersNext sends you and ShipOps reads it. How CouriersNext pays COD, in detail → |
| What you type to connect | Auth key Then pick your shipper profile. |
| Recognised as | couriersnext · courier next |
Connecting CouriersNext
In the CouriersNext portal, copy your account's API auth key (a UUID). Paste it into ShipOps and pick the shipper profile your bookings are created under. The connection is checked by listing your orders.
Parcels come from the portal's own list, so a parcel booked outside ShipOps is still found. Nothing is written to your store until you switch a write-back on.
There is no advice API. A parked parcel lands in your inbox with the reason, and ShipOps links you to the portal to answer by hand.
What CouriersNext's statuses mean
13 phrases, read the way the app reads them| What CouriersNext prints | What it means | What to do |
|---|---|---|
| New Booked · Order Is Booked | Booked | Booked on CouriersNext, awaiting the rider. |
| Pick Up In Progress | Booked | A rider is on the way to collect. |
| Picked Up · Parcel Received At Office · Parcel In Transit To Destination · Parcel Received At Destination | In transit | Moving inside CouriersNext's network. |
| Out For Delivery | In transit | With the rider today. |
| Delivery Unsuccessful · Pending · Attempted | Attempt failed | A failed visit; the reason follows. CouriersNext will retry. Reach the customer first. |
| Refused By Consignee · Consignee Not Responding · Consignee Not Available · Incomplete Address · Allow To Open Demand | Attempt failed | The reason for the failed visit, printed as the status. Still in the courier's hands; fix what you can with the customer. |
| Re-Attempt | Attempt failed | The same failed visit being redispatched. Not counted as a new attempt. |
| Shipper Advice · Ready For Return · Hold For Self Collection | Needs your decision | CouriersNext is waiting for your word. There is no advice API: answer in the CouriersNext portal. ShipOps keeps the parcel in your inbox until it moves. |
| Non Service Area · Lost · Claim | Needs your decision | Needs a person: the destination is outside coverage, or the parcel is reported lost or under claim. Talk to your account manager. |
| Return Confirmation · Return In Process · Return In Transit · Parcel Return To Office · Returned To Origin City · Return Received At Origin | Coming back | Coming back. "Return Received At Origin" is at the courier's hub, not yet handed to you. |
| Returned To Shipper · Return To Sender · Returned To Warehouse · Delivered To Warehouse · Delivered To Vendor | Returned to you | Back with you. The last two are return-side phrases despite the word "delivered". Check the parcel in. |
| Delivered · Replacement Delivered | Delivered | Delivered. CouriersNext's payment flag flips to Paid once the COD is settled; the statement carries the amount. |
| Cancelled · Order Is Cancelled | Cancelled | Cancelled before pickup. |
Why a CouriersNext delivery fails, as ShipOps names it
| Customer refused | Refused to accept |
|---|---|
| Customer not available | Consignee not available · Consignee out of city |
| Other | COD cash issue · Wanted to open parcel first · Item complaint · Needs review |
| Address problem | Address issue · Non-service area |
| Phone problem | Phone not responding |
| Courier-side | Duplicate order · Fake order · Delayed by courier · Courier awaits your instruction |
| Held | Held for self-collection |
| Lost or damaged | Parcel reported lost · Claim opened |
These are the reasons CouriersNext gives on a failed visit, normalised to one label each so your team sees "Customer not available", never the raw string. The family decides what the Action Inbox suggests: an address problem asks the customer for a landmark, a phone problem tries WhatsApp, a refusal asks whether to return.
Questions merchants ask about CouriersNext
Where do I find my CouriersNext auth key?
In the CouriersNext portal at portal.couriersnext.com, on your account's API page: the auth key is a UUID. Paste it into ShipOps; it is stored encrypted.
Why does the CouriersNext status list look like ShipKartex's?
Both run on the iCargos platform, as does Run Courier. One adapter, three separate connections.
Can I tell CouriersNext to retry or return from ShipOps?
No, there is no advice API. The parcel shows in your inbox with the reason, and ShipOps links you to the portal to answer by hand.
Who prints the CouriersNext label?
ShipOps, from the booking's label data, as a 4×6 slip. The portal's own label page has no login and a sequential id, so your customer's details are kept off it.
Can I book CouriersNext parcels from ShipOps?
Yes, under the shipper profile you choose, with a label and cancellation, on your own account.
Connect CouriersNext in a minute
Install ShipOps, paste the key CouriersNext already gave you, and your parcels and payouts land in one place. Free to start, no card.