ShipOps connects to PostEx, TCS, M&P, Leopards, InstaWorld and nine more on your own courier account. Every page below says, courier by courier, what gets tracked, what each status really means, how and when COD is paid out, and what you can book, cancel or instruct without opening the courier's portal.
| Courier | Live tracking | Retry / return advice | Book and print labels | COD payout reconciliation | Pages |
|---|---|---|---|---|---|
| PostEx | Automatic | Integration · Payments | |||
| TCS | Automatic | Integration · Payments | |||
| M&P | Automatic | Integration · Payments | |||
| Leopards | Automatic | Integration · Payments | |||
| InstaWorld | — | You upload the statement | Integration · Payments | ||
| Trax | Automatic | Integration · Payments | |||
| ShipKartex | — | Automatic · statement upload | Integration · Payments | ||
| CouriersNext | — | Automatic · statement upload | Integration · Payments | ||
| DigiDokaan | Automatic · statement upload | Integration · Payments | |||
| Run Courier | — | Automatic · statement upload | Integration · Payments | ||
| Next Step · in testing | Automatic · statement upload | Integration · Payments | |||
| Rocket Courier · in testing | You upload the statement | Integration · Payments | |||
| Shipnoc · in testing | — | Automatic · statement upload | Integration · Payments | ||
| DEX · in testing | Switching on* | Switching on* | You upload the statement | Integration · Payments |
* DEX live tracking and retry / return advice switch on once Daraz enables its tracking API for ShipOps. "Automatic" means ShipOps reads payout receipts from the courier's own API; "statement upload" means you drop the courier's payout statement in and ShipOps reads it. Every courier supports cancelling a booking. BarqRaftar and BlueEx are next; see the roadmap.
ShipOps connects to your PostEx merchant account with the API token PostEx already issued you. It tracks every parcel, turns PostEx's status codes into plain words, catches the one window where PostEx will still take a retry, and matches every Cash Payment Receipt against your orders down to the paisa.
ShipOps connects to your TCS COD account through the same credentials you use for the ENVIO portal. It follows every TCS parcel, reads TCS's two-letter status codes into plain words, catches the partial-delivery codes that corrupt COD maths, and reconciles TCS's weekly running account, carry-forward and all.
ShipOps connects to your M&P COD account with the API username, password and account number M&P issued you. It follows every parcel through M&P's sixteen numbered tracking tags, files retry or return advice when M&P holds a parcel, and ties each payment batch to the parcels it paid by cheque number.
ShipOps connects to your Leopards account with the API key and API password from the Leopards portal. It lists your parcels directly from Leopards, reads statuses like "Delivered to Warehouse" for what they are (a return), files retry or return advice on the open ticket, and matches every Leopards invoice to the parcels it paid.
ShipOps connects to your InstaWorld account with its API key. It follows every parcel from your store's fulfilments, reads InstaWorld's statuses and its "Marked by Insta" verdicts into plain words, books and labels parcels, and reads the COD statement you drop in, because InstaWorld exposes no payout data through its API.
ShipOps connects to your Trax account with the API key from the Sonic portal. It follows every parcel, reads Trax's free-text statuses into plain words (including replacements and the return-confirmation window), and reconciles Trax's weekly payment batches parcel by parcel, with the 2% withholding and 2% sales tax shown separately.
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.
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.
DigiDokaan is an aggregator: one login, and each booking goes out through a courier gateway you choose. ShipOps connects with your DigiDokaan phone number and password, tracks every parcel whichever courier carried it, reads the gateway's statuses carefully ("Return - Delivered to Shipper" is a return), and rebuilds DigiDokaan's per-parcel payment answers into payout receipts.
ShipOps connects to your Run Courier account with the auth key and client code from portal.runcourier.com. It lists your parcels directly, reads Run Courier's statuses into plain words, books and prints labels, and marks each parcel Run Courier says it has paid, with your payout statement read in beside it.
ShipOps connects to your Next Step account with its API key. It lists your parcels, reads Next Step's status codes into plain words (COURIER_SETTLED is the rider handing in cash, not your payout), files retry or return on the open ticket, and asks Next Step's finance plane per parcel whether its COD has been settled. In testing while real parcels run through it.
Rocket Courier is an aggregator: one account, and each booking goes out on TCS, Trax, Leopards or PostEx. ShipOps connects with your Rocket client id and API token, follows every parcel from your store's fulfilments, reads Rocket's status phrases into plain words, books and labels, and reads the payout statement you drop in. In testing while real parcels run through it.
ShipOps connects to your Shipnoc account with your username, password and API signature. It follows every parcel when Shipnoc's tracking is open (Shipnoc switches it off for most of the day), reads Shipnoc's statuses into plain words without ever treating PAYMENT DONE as a delivery, and sweeps Shipnoc's weekly COD invoices a month at a time. In testing while real parcels run through it.
DEX is Daraz's own courier, open to sellers off the marketplace. ShipOps books and labels DEX parcels through its registered Daraz Open Platform app, bound to your Seller ID and warehouse; live tracking and retry or return switch on once Daraz grants ShipOps the package history route. COD arrives on a DEX statement you drop in. In testing.
Connecting a courier takes the key or login the courier already issued you, typed once into Settings. ShipOps checks the credential against the courier's API and stores it encrypted. The first import of your parcels then runs in the background: your store's fulfilments are read for tracking numbers, the courier is asked about each one, and the trail lands in your inbox. Nothing is written to your store until you turn a write-back on.
ShipOps is independent. It is not a courier and not an aggregator; it never holds your cash and never books on its own account. Every booking, label, cancellation and retry or return instruction runs on your account, under your rates, signed by the team member who did it. When a courier has no API for something, the page says so and tells you where to do it by hand.
The status tables on each page come from the same code the app uses to read the courier. "Return — Delivered to Shipper" is a return, not a delivery; "Delivery Under Review" is the one PostEx state that accepts a retry; "Pending" on Leopards means the rider came back without delivering. Those readings were learned from real trails and are kept exact on purpose, because a courier's word "delivered" is what decides whether your order is marked paid.
No. ShipOps connects to the merchant account you already have, with the API key or login the courier already gives you. Your rates, your account manager, your contract stay exactly as they are. ShipOps reads from the account and, only when you ask, books a parcel or files a retry or return instruction.
Never. The courier collects cash from your customer and pays it into your bank, as it does today. ShipOps reads the payout receipts the courier issues and checks every parcel on them against your orders, so you can see what was paid, what is still owed and what was short. The money never passes through ShipOps.
The integration is built from the courier's documents and verified against its public pages, but not yet against months of real parcels. You may hit an error we have not seen; tell us and we fix it with you. Statuses, payouts and bookings are read the same careful way as on every other courier, and nothing is written to your store unless you switch it on.
Yes. Radar, the free plan, connects one courier; Ledger two; Control Room and Autopilot as many as you ship with. Every list, the Action Inbox and the money dashboard stay correct across all of them, and each courier's parcels keep their own status vocabulary translated the same way.
The carrier layer is an adapter registry: a new courier is one folder and one line. BarqRaftar is built and waiting for credentials; BlueEx is next. Tell us on WhatsApp which courier you ship with and roughly how many parcels a month, and we will say how soon.
Install ShipOps from the Shopify App Store, paste the key your courier already gave you, and watch your parcels and payouts land. Free to start, no card.
ShipOps