Leopards API integration for Pakistani ecommerce

Once your Leopards account is connected, Kliovo Shop handles the full CN lifecycle without the Leopards portal: booking, tracking, cancellation, and label printing. When an order is confirmed — typically the customer tapping Confirm on the 60-second WhatsApp message — the CN books with Leopards automatically. No portal login, no manual address entry, no parcels sitting unbooked because someone forgot to log in before the courier pickup.

Tracking runs the other way just as automatically. Every dispatched Leopards shipment updates inside Kliovo's tracking view alongside your other couriers, and each status change can trigger a WhatsApp message to the customer — booked, dispatched, out for delivery, delivered. The 'where is my order' messages stop landing in your inbox because the answer reaches the customer first.

If you searched for a 'Leopards WooCommerce plugin' expecting a separate install, you don't need one. Kliovo's WooCommerce connection talks to Leopards directly — WooCommerce orders flow into Kliovo Shop and book with Leopards over the same API connection Shopify orders use. There's no separate plugin to install, configure, or keep updated alongside your theme, and no second dashboard to check.

Leopards is one of only two couriers in Kliovo Shop's integration list that expose a real-time rate lookup over the API. Before a CN books, Kliovo can query Leopards for the shipping cost of a specific parcel — weight and destination in, an estimated rate out. That means you see what a parcel will cost to ship with Leopards before you commit to the booking, rather than discovering the charge after the fact on your invoice.

This matters most for stores that price shipping into the product or charge a flat delivery fee. Rate lookup lets you check a parcel against your assumptions before it ships, and catch the occasional heavy or oversized item that would cost more to send than your flat fee covers. Most Pakistani couriers only give you an invoice after the parcel has moved — Leopards gives you the number first.

You don't have to use rate lookup on every order for it to be worth having. Many stores only reach for it on parcels above a certain weight, or on new product lines where nobody is yet sure what shipping should actually cost. Either way, the answer comes from Leopards directly through the same connection that books the CN — not a separate rate card you keep in a spreadsheet and hope is current.

The flow is: order arrives from your store (Shopify, WooCommerce, or manual entry) → the order is confirmed on WhatsApp → Kliovo books the CN over the Leopards API using your own Leopards account → the CN number attaches to the order → the label is ready to print. For a full dispatch day, bulk booking sends the whole batch at once, and bulk label printing produces one PDF for every parcel going out.

If an order is cancelled before dispatch, Kliovo sends the CN cancellation to Leopards immediately — no orphaned CNs left sitting in the Leopards system, no calls to your account manager to clean up bookings that never shipped.

Leopards has some of the widest coverage of any Pakistani courier, which is why many stores set it as their store-default or fallback courier — the one every order falls to when no city-specific rule applies. Kliovo's routing rules can also send Leopards orders by weight: heavier parcels routed to Leopards where its pricing tends to be more competitive, while lighter or city-specific orders go to your other connected couriers. That combination — broad reach as a catch-all, plus a weight rule for the parcels other couriers price less competitively — is why Leopards ends up carrying a large share of orders for stores that haven't built out detailed city-by-city routing yet.

Leopards COD amounts show up per CN in Kliovo's shipment and courier reports, so you can always see what's expected against each delivered order. What Leopards doesn't have — and it's worth knowing before you rely on it — is automated remittance matching: reconciling incoming bank deposits line-by-line against individual CNs so a shortfall surfaces without manual checking. That deeper matching is TCS-only in Kliovo Shop today. For Leopards, reconciliation is a per-CN reporting job, not an automated one.