Trax API integration for Pakistani ecommerce

Once your Trax account is connected, Kliovo Shop handles the full CN lifecycle without the Trax merchant portal: booking, tracking, cancellation, and label printing. When an order is confirmed — typically by the customer tapping Confirm on the 60-second WhatsApp message — the CN books with Trax automatically. No copy-pasting addresses into the portal, no end-of-day booking backlog, no orders sitting unbooked overnight because someone forgot to log in.

Tracking runs the other way just as automatically. Every dispatched Trax 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, without anyone on your team checking Trax's tracking page manually.

For a store running multiple couriers, this matters more than it sounds like it should. Trax shipments, Leopards shipments, TCS shipments — all of it sits in one dashboard instead of five open browser tabs, one per courier portal. Your dispatch team stops context-switching between logins just to answer a customer's tracking question.

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 Trax API using your own Trax 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 to Trax that day.

If an order is cancelled before dispatch, Kliovo sends the CN cancellation to Trax immediately — no orphaned CNs left sitting in the Trax system, no calls to a Trax account manager to clean up bookings that never shipped. Cancellations, like bookings, run over the API rather than through a portal screen.

Because booking runs on your own Trax credentials, nothing about your contracted rates or your account relationship with Trax changes. Kliovo sits on top of the account you already have — it automates the repetitive part of the job, not the commercial terms underneath it.

Trax's edge over the other six connected couriers is geographic: it has the strongest interior Sindh and rural Pakistan delivery reach of the group. If your customer base includes towns and cities beyond Karachi — interior Sindh in particular — Trax is often the courier that actually delivers there reliably, where broader-network couriers can be thinner on the ground.

That makes Trax a natural fit for a city-based routing rule rather than a default courier for every order. Set up a rule that sends interior Sindh and rural destinations to Trax specifically, and let your other connected couriers carry Karachi, Lahore, and Islamabad — the routing runs automatically once the rule is in place, and your own delivery performance data in Kliovo's reports tells you if the split is working.

This is exactly the kind of decision that's hard to get right by hand and easy to get right with a rule: nobody on your dispatch team remembers, order by order, that a given town falls under interior Sindh. A routing rule remembers every time, so the split stays consistent even as order volume grows.

Trax handles book, track, cancel, and print reliably, but it doesn't do everything every connected courier does. There's no real-time rate lookup before booking with Trax — that's available on Leopards and BlueEx only. There's no reverse (return) CN booking over the Trax API — that's BlueEx and PostEx. And there's no automated COD remittance-matching for Trax the way there is for TCS; COD amounts booked on Trax CNs still appear per shipment in Kliovo's reports, so you can see what's expected against each order, but there's no automatic bank-deposit matching layered on top.

None of that is a knock against using Trax where it's strong. If your operation needs API-driven return bookings, connect BlueEx or PostEx alongside Trax — routing rules can send forward orders in interior Sindh to Trax while returns route through whichever of those two you prefer. Most Pakistani stores run more than one courier for exactly this reason: no single courier does everything, so you pick the right one for each job.

Knowing what Trax doesn't do up front saves a support ticket later. If a return needs booking and Trax isn't the answer, your team should already know to reach for BlueEx or PostEx instead of assuming the capability exists and finding out mid-return.