ShipOpsShipKartex
ShipOps connects to your ShipKartex account with the auth key from your portal. It lists your parcels directly, reads ShipKartex's statuses into plain words, books and prints labels, and marks each parcel ShipKartex says it has paid, with your payout statement read in beside it.
ShipKartex runs on iCargos, a white-label courier platform that CouriersNext and Run Courier also use. The portal looks the same, the API is the same document with the host changed, and the status list is the same list. ShipOps built one adapter for the platform and gives each courier its own connection, its own busy-cooldown and its own pages, because to you they are three couriers with three account managers and three payout statements.
The API is thin and honest. It lists your orders, gives a trail per parcel, books, cancels, and carries a per-parcel payment_status of Paid or Pending. It has no advice call, no settlement report and no webhooks. ShipOps works with what is there and tells you where to go for the rest.
Labels are rendered by ShipOps from the booking data, because the portal's label page is an HTML page with no login on a sequential id. Printing from ShipOps keeps your customer's details off a URL anyone could guess.
What ShipOps does with ShipKartex
| Live tracking | Yes. ShipOps lists parcels from your ShipKartex account directly, then follows each one. A parcel you booked outside ShipOps is still found. |
|---|---|
| Retry / return instruction | ShipKartex 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 ShipKartex portal to answer by hand. |
| Booking and labels | Yes. Book from the order, print the label, cancel a booking. Services: Account default. Label layouts: ShipOps label (4×6 in). |
| COD payouts | Automatic · statement upload. ShipKartex answers "was this parcel paid?" per parcel; ShipOps asks for every delivered parcel and marks what the courier attests. Drop in the payout statement ShipKartex sends you and ShipOps reads it. How ShipKartex pays COD, in detail → |
| What you type to connect | Auth key Then pick your shipper profile. |
| Recognised as | shipkartex · kartex · shipkartex courier · shipkartex courier service |
Connecting ShipKartex
In the ShipKartex portal, copy your account's API auth key (a UUID). Paste it into ShipOps, then 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; the list is swept on the lane's clock and each parcel's trail is followed from there. Nothing is written to your store until you switch a write-back on.
There is no advice API. A parked parcel still lands in your inbox with the reason, and ShipOps links you to the portal to answer by hand.
What ShipKartex's statuses mean
13 phrases, read the way the app reads them| What ShipKartex prints | What it means | What to do |
|---|---|---|
| New Booked · Order Is Booked | Booked | Booked on ShipKartex, 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 ShipKartex's network. |
| Out For Delivery | In transit | With the rider today. |
| Delivery Unsuccessful · Pending · Attempted | Attempt failed | A failed visit; the reason follows. ShipKartex 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 | ShipKartex is waiting for your word. There is no advice API: answer in the ShipKartex 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. ShipKartex'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 ShipKartex 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 ShipKartex 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 ShipKartex
Where do I find my ShipKartex auth key?
In the ShipKartex portal, on your account's API page: the auth key is a UUID. Paste it into ShipOps; it is stored encrypted.
Why does the ShipKartex status list look like CouriersNext's?
Both run on the iCargos platform, as does Run Courier. ShipOps uses one adapter for the platform and keeps each courier's connection, state and pages separate.
Can I tell ShipKartex 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.
Why does ShipOps print the label instead of ShipKartex?
The portal's label is an HTML page with no login on a sequential id. ShipOps renders a 4×6 label from the booking data so your customer's details never sit on a guessable URL.
Can I book ShipKartex parcels from ShipOps?
Yes, under the shipper profile you choose, with a ShipOps-rendered label and cancellation, on your own account.
Connect ShipKartex in a minute
Install ShipOps, paste the key ShipKartex already gave you, and your parcels and payouts land in one place. Free to start, no card.