ShipOpsLeopards
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.
Leopards has a merchant API that does most things a store needs: list booked packets by date, track them, read payment details and shipping charges per parcel, list invoices, and answer the courier's advice request. It also has two habits worth knowing before you trust a dashboard built on it.
The first is that a Leopards API key is a master key. If your account created more than one business in the Leopards portal, one key lists every business's parcels. ShipOps stamps each parcel with its shipper, works out from your store which shippers are yours, and lets you hide the rest, so another business's parcels never land in your lists or your money.
The second is the vocabulary. Leopards prints Delivered to Warehouse and Delivered to Vendor on the return side. Both contain the word delivered; neither is a delivery. A tool that pattern-matches the word marks returned orders as paid in your store. ShipOps reads the full phrase, and this page is partly here so you never have to learn that the hard way.
What ShipOps does with Leopards
| Live tracking | Yes. ShipOps lists parcels from your Leopards account directly, then follows each one. A parcel you booked outside ShipOps is still found. |
|---|---|
| Retry / return instruction | Leopards opens a ticket on a parcel it could not deliver and only an open ticket takes an instruction. ShipOps reads the open tickets every sync and puts the retry and return buttons on exactly those parcels. |
| Booking and labels | Yes. Book from the order, print the label, cancel a booking. Services: Overnight, Overland (economy), Detain (hold at branch). Label layouts: 2 slips per A4 page, 1 slip per page. |
| COD payouts | Automatic. ShipOps reads Leopards's payout receipts from its API on a schedule and checks every parcel on them. How Leopards pays COD, in detail → |
| What you type to connect | API key · API password |
| Recognised as | leopards · lcs · leopard courier · leopards courier · leopards courier pakistan |
Connecting Leopards
In the Leopards portal, go to API Settings → API Management and generate an API key, then set an API password there (it is not your portal login). Paste both into ShipOps. The connection is checked by listing your packets: Leopards lists parcels before the first scan, so a zero on a new account is trustworthy, and a number on an old one is your parcel count.
If the key covers several shippers, Settings shows them with a suggestion of which are yours, worked out from your store's fulfilments and your bookings. You confirm. Parcels under a shipper you hide are stored but closed, out of every list, link, message and money figure, and come back if you un-hide the shipper.
Advice on Leopards is by ticket: when a parcel cannot be delivered, Leopards opens a shipper-advice ticket, and only an open ticket takes an instruction. ShipOps reads the open tickets every sync and shows the retry and return buttons on exactly those parcels.
What Leopards's statuses mean
12 phrases, read the way the app reads them| What Leopards prints | What it means | What to do |
|---|---|---|
| Pickup Request not Send / Sent · Booked | Booked | Booked, awaiting the rider. Chase if it sits more than a day. |
| Shipment picked in {city} · Consignment booked | In transit | Collected and scanned in at the Leopards facility. |
| Arrived at station · Dispatched to {city} · Assigned to courier · Out for delivery | In transit | Moving. "Assigned to courier" means with the rider today. |
| 1st attempt in forward leg · 2nd attempt in forward leg | Attempt failed | A failed visit; the reason text follows the phrase. Leopards retries on its own. Reach the customer before the next one. |
| Pending | Attempt failed | The rider came back without delivering and Leopards will retry. Treated as a failed visit so your team sees it, not as a parcel in transit. |
| Ready for Return | Needs your decision | The last stop before the parcel comes back. The advice ticket is open: say retry (with a corrected address if that was the problem) or return. |
| Being Return · Return to Origin in {city} | Coming back | Committed return. Plan for the parcel to arrive. |
| 1st attempt in reverse leg · 2nd attempt in reverse leg | Coming back | The rider tried to hand the return back to you and could not. Make sure someone is at the pickup address. |
| Return To Sender · Returned to Warehouse | Returned to you | Back with you. Check it in so the order can be cancelled and restocked if that switch is on. |
| Delivered to Warehouse · Delivered to Vendor | Returned to you | A return, not a delivery. The parcel was handed back to you or your warehouse. Never mark the order paid on this phrase. |
| Delivered | Delivered | Delivered to the customer. The COD should appear on a Leopards invoice; until then the parcel sits under "courier owes you". |
| Cancelled · Void | Cancelled | Cancelled before pickup. |
Why a Leopards 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 Leopards 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 Leopards
Which Leopards credentials does ShipOps need?
An API key and an API password, both from API Settings → API Management in the Leopards portal. Not your portal login. Stored encrypted; used to read your account and, when you ask, to book or to answer an advice ticket.
My Leopards key shows parcels that are not my store's. Why?
A Leopards API key is a master key: it lists every business created under the account. ShipOps suggests which shippers are yours from your store's fulfilments and lets you hide the rest. Hidden shippers' parcels leave every list and every money figure.
When can I tell Leopards to retry or return a parcel?
While its shipper-advice ticket is open, typically at "Ready for Return". ShipOps reads the open tickets each sync and shows the buttons only there; outside the window Leopards refuses the instruction.
Why does "Delivered to Warehouse" show as a return in ShipOps?
Because that is what it is on Leopards: the parcel was delivered back to your warehouse. The word "delivered" alone would mark a returned order paid in your store. ShipOps reads the whole phrase.
Can I book Leopards parcels from ShipOps?
Yes, with labels and cancellation, on your own account and rates. If you run several shippers, bookings go under the one you pick.
Connect Leopards in a minute
Install ShipOps, paste the key Leopards already gave you, and your parcels and payouts land in one place. Free to start, no card.