PostEx integration for Pakistani ecommerce

Once your PostEx account is connected, Kliovo Shop handles booking, tracking, cancellation, and label printing without the PostEx portal. Because PostEx authenticates with a single token instead of a username-and-password pair, connecting your account is a one-field paste, not a login handshake — and once it's in, confirmed orders book with PostEx automatically at the moment the customer confirms on WhatsApp.

That single-token setup also means there's nothing to re-enter later — no shared password to rotate across a team, no login session that times out mid-dispatch. The token stays valid until you regenerate it yourself, so once PostEx is connected, it stays connected.

Tracking runs the other way just as automatically. Every dispatched PostEx 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.

Returns are one of the most manual parts of running a Pakistani online store — a customer wants to send an item back, and normally that means logging into the courier portal to arrange a reverse pickup as a separate step from the original booking. PostEx is one of only two couriers in Kliovo Shop's integration list that support booking a return CN over the API, the same way an outbound shipment books.

In practice, that means a return pickup gets booked from the order page itself, right where you're already looking at the original shipment. No second login, no separate return-booking screen inside the PostEx portal, no manual note-taking to remember which orders still need a reverse CN raised.

This is the feature to lean on for any store handling exchanges or partial returns at volume — every reverse CN gets the same tracking treatment as an outbound shipment, so you can see a return moving back to your warehouse in the same dashboard where you see everything going out.

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 PostEx API using your own PostEx 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 cancellation to PostEx immediately — no orphaned CNs left in the PostEx system, no manual cleanup needed before your next batch goes out. The same cancellation call works whether the CN was booked minutes ago or earlier in the day, as long as PostEx hasn't already picked the parcel up.

PostEx tends to perform well on prepaid orders, and many stores route prepaid, lighter-weight parcels to PostEx specifically for that reason while sending COD or heavier orders to other connected couriers. Kliovo's routing rules make that automatic: set a condition like payment method plus a weight ceiling, and matching orders book with PostEx without anyone choosing a courier by hand.

If your store runs a mixed COD-and-prepaid catalogue, this is usually one of the first rules worth setting up — it takes the entire prepaid, lightweight slice of your orders off manual assignment on day one, before you've built out a full city-by-city routing table.

PostEx doesn't offer live rate lookup before booking — that's Leopards and one other courier only — and COD amounts on PostEx orders track per CN in Kliovo's shipment and courier reports rather than through deep automated remittance matching, which is TCS-only in Kliovo Shop today. If you need to check a PostEx COD amount against a delivery, the report is where you look; it isn't reconciled against bank deposits automatically the way TCS is.