ShipOpsRocket Courier In testing
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.
Rocket Courier's API came to ShipOps as a Postman collection that prints request bodies and not responses, so the integration was built from the requests, the public tracking page, and what the live host answered. Every status phrase in the table below that was not seen on a real trail is marked as inferred in the code, and the whole courier wears the In testing tag until enough real parcels have confirmed it.
Because Rocket books onto partner couriers, a Rocket trail may read like a TCS or Leopards trail. ShipOps treats your Rocket account as the carrier, which is where your bookings, your account manager and your payout statement are, and reads whatever phrases arrive against one careful table.
Rocket has no payout API that ShipOps has found. Settlement comes from the statement you upload.
What ShipOps does with Rocket Courier
| Live tracking | Yes. ShipOps finds your Rocket Courier parcels from the tracking numbers on your store's fulfilments and follows each one with Rocket Courier's API. |
|---|---|
| Retry / return instruction | Rocket Courier accepts a retry or return instruction only while a parcel is in its review window. ShipOps watches for that window and alarms it, so the instruction goes in while it can still change the outcome. |
| Booking and labels | Yes. Book from the order, print the label, cancel a booking. Services: Standard. Label layouts: Rocket Courier label. |
| COD payouts | You upload the statement. Drop in the payout statement Rocket Courier sends you and ShipOps reads it. How Rocket Courier pays COD, in detail → |
| What you type to connect | Client ID · API token |
| Recognised as | rocket courier · rocket courier · rocket courier service · rocket couriers · rocketcourier Also by tracking link: rocketcourier.pk |
Connecting Rocket Courier
Enter your Rocket client id and API token into ShipOps. The connection is checked against Rocket before it is saved and the credentials are stored encrypted.
Parcels are found from the tracking numbers on your store's fulfilments and from ShipOps bookings, then followed on Rocket's tracking call. Nothing is written to your store until you switch a write-back on.
Advice runs through the review window: when a parcel reads Hold, On Hold, Shipper Advice or Pending Advice, ShipOps shows retry and return and files your answer. A Re-Attempt row afterwards is the echo of your retry.
What Rocket Courier's statuses mean
10 phrases, read the way the app reads them| What Rocket Courier prints | What it means | What to do |
|---|---|---|
| Order Created · Booked · Pending | Booked | Booked on Rocket, awaiting pickup. "Pending" here is Rocket's pre-pickup state, unlike on Leopards. |
| Picked · Arrived At Origin · Dispatched · In Transit · Arrived At Destination · Arrived At Hub | In transit | Moving inside the partner courier's network. |
| Assigned To Rider · Out For Delivery | In transit | With the rider today. |
| Attempted · Delivery Attempted — {reason} | Attempt failed | A failed visit; the reason follows. Reach the customer before the next attempt. |
| Hold · On Hold · Shipper Advice · Shipper Advice Required · Pending Advice | Needs your decision | Rocket is waiting for your word. Say retry or return from the order in ShipOps. |
| Re-Attempt · Re-Attempt Requested | In transit | The echo of your retry. Nothing to do. |
| Return In Process · Return In Transit · Return To Shipper · RTO | Coming back | Coming back. "Return To Shipper" is the parcel being sent back, not yet handed over. |
| Returned · Returned To Shipper · Returned To Origin | Returned to you | Back with you. Check it in. |
| Delivered · Shipment Delivered | Delivered | Delivered. The COD will appear on Rocket's payout statement; drop it into ShipOps. |
| Cancelled | Cancelled | Cancelled before pickup. |
Why a Rocket Courier delivery fails, as ShipOps names it
| Address problem | Non-service area · Address issue |
|---|---|
| Customer refused | Refused to accept |
| Customer not available | Consignee not available · Consignee out of city |
| Other | Order cancelled · Needs review |
| Phone problem | Phone not responding |
These are the reasons Rocket Courier 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 Rocket Courier
Which Rocket Courier credentials does ShipOps need?
Your Rocket client id and API token, stored encrypted.
Why is Rocket Courier marked In testing?
The integration was built from a Postman collection that prints requests and not responses, so most status phrases are inferred until real trails confirm them. The tag tells you an error is possible and reportable.
Which courier actually carries my Rocket parcel?
The partner you booked it on: TCS, Trax, Leopards or PostEx. The trail's scans are that courier's; ShipOps shows the carrier on the booking.
When can I tell Rocket to retry or return?
While the parcel reads Hold, On Hold, Shipper Advice or Pending Advice. ShipOps shows the buttons there.
Can I book Rocket parcels from ShipOps?
Yes, with labels and cancellation, on your own Rocket account.
Connect Rocket Courier in a minute
Install ShipOps, paste the key Rocket Courier already gave you, and your parcels and payouts land in one place. Free to start, no card.