Kliovo Shop
7 Pakistani couriers. One screen. Zero spreadsheets.
The only Pakistani courier integration software that connects TCS, Leopards, Trax, BlueEx, PostEx, Swyft, and Sonic in a single dashboard — book, track, cancel, and print CNs without opening a single courier portal.
How courier integration works
Order confirmed
COD or prepaid order confirmed in Kliovo. Smart routing evaluates city, weight, order value, and payment method — selects the right courier instantly using your configured rules.
CN booked via API
Kliovo calls the courier's API directly. CN number returned and stored on the order record within seconds. No manual entry, no portal tab, no copy-paste.
Live tracking every 2 hours
Bulk tracking runs automatically across all 7 couriers every 2 hours. Statuses update in Kliovo without any manual portal checks or CSV imports.
Label printed, customer notified
Print branded or official CN label in one click. Customer receives automatic dispatch notification via WhatsApp with their CN number and tracking link.
Everything included
Courier capability matrix plus the full set of operational features that save hours every dispatch cycle.
| Courier | Book | Track | Cancel | Print CN | Rate Calc | Reverse |
|---|---|---|---|---|---|---|
| TCS | — | — | ||||
| Leopards | — | |||||
| Trax | — | — | ||||
| BlueEx | ||||||
| PostEx | — | |||||
| Swyft | — | — | ||||
| Sonic | — | — |
Full Operational Feature Set
TCS COD reconciliation
Pull TCS COD payment reports directly into Kliovo. Match deposits against expected amounts, flag discrepancies, and close your books without a spreadsheet.
Automatic CN cancellation
Order cancelled before dispatch? Kliovo sends the CN cancellation to the courier API immediately — no manual portal login, no forgotten CNs sitting in courier systems.
CN lifecycle tracking
Every CN moves through 20+ shipment statuses inside Kliovo — booked, manifested, in-transit, out for delivery, delivered, returned. All 7 couriers in one view.
Per-courier API rate limiting
Each courier's API has different rate limits. Kliovo handles throttling automatically — bulk CN booking never hits a courier's rate cap and fails silently.
Per-courier error handling
Courier APIs return different error codes and formats. Kliovo normalizes all errors into a consistent format with actionable messages so your ops team always knows what went wrong.
Load sheet generation
Generate TCS-compatible load sheets for bulk handover. All CNs in a pickup batch listed with weight, destination, and COD amount — ready to hand to the TCS driver.
Branded + official CN labels
Print your own branded CN label or the courier's official label format. Both options available for all 7 couriers. Batch print PDF in one click.
Reverse logistics (BlueEx, PostEx)
Return CN booking for BlueEx and PostEx — directly from the Kliovo order detail page. No courier portal required.
Rate calculation (Leopards, BlueEx)
Real-time shipping rate lookup for Leopards and BlueEx based on weight and destination city before CN booking. Show actual cost to your ops team.
Smart courier routing integration
Works with Kliovo's 4-layer routing rules — city, weight, order value, payment method. The right courier is selected automatically before CN booking starts.
Built for teams that...
The ops team switching between 5 browser tabs daily
The pain: Every morning: TCS portal for today's deliveries, Leopards portal for Karachi orders, Trax for Lahore, PostEx for returns, BlueEx for high-value. Five logins, five password resets every 90 days, five different status formats that don't match each other. At 200 orders a day, that's 2–3 hours of ops time per day just switching screens.
The fix: Kliovo consolidates all 7 couriers into one order list. CN booked, status updated, label printed — all from the same screen. Our dispatch team went from 3 hours of portal work to 40 minutes per day. The rest of the time went to actual order exceptions.
The brand that lost a TCS CN because cancellation didn't happen in time
The pain: Customer called to cancel after we'd already booked the TCS CN. Team forgot to cancel it in the portal. TCS attempted delivery anyway. Customer refused. CN came back as RTO. We paid both the outbound and return shipping — Rs 1,400 on a cancelled order. Happened 8–12 times a month.
The fix: In Kliovo, cancelling an order automatically calls the courier API to cancel the CN immediately. No manual step, no forgotten portal action. The CN lifecycle is managed inside Kliovo — from booking to cancellation to return receiving.
The D2C brand that manually books 200 CNs per day
The pain: 200 orders per day. Each one required opening the courier portal, entering the address, weight, COD amount, and phone number manually. 15–20 minutes per 100 orders, minimum. Transcription errors were common — wrong phone number, wrong COD amount. Courier would reject the CN at handover.
The fix: Kliovo books CNs via API using the data already on the order. No re-entry. Address, phone, weight, and COD amount flow directly from the order record. 200 CNs booked in under 3 minutes. Errors from manual entry dropped to near zero.
The numbers
7
Pakistani couriers natively integrated
TCS, Leopards, Trax, BlueEx, PostEx, Swyft, Sonic — all live, no plugins, no middleware.
0
Courier portal tabs open during dispatch
Everything — booking, tracking, cancellation, label printing — happens inside Kliovo. The portals become redundant.
Rs 850
Average return logistics cost per failed delivery
At 30% industry RTO rate, every 100 dispatched orders carries Rs 25,500 in potential return logistics exposure.
Common use cases
Daily dispatch workflow with Kliovo
A typical Kliovo dispatch session starts with the confirmed orders queue — all COD-confirmed, anomaly-cleared orders ready for CN booking. Ops selects all and triggers bulk CN booking. Kliovo calls each courier's API in parallel, storing CNs as they return. Then batch-print all CN labels — branded or official format — in a single PDF. Finally, hand the load sheet to the TCS driver and export the dispatch manifest. What used to take 2–3 hours of portal-switching now takes under 45 minutes. The routine is the same regardless of whether you're using TCS, Leopards, or all seven couriers in the same dispatch run.
TCS COD reconciliation at month end
TCS pays out COD in batches — typically weekly or fortnightly deposits. Reconciling which deposit covers which CNs used to require downloading TCS's payment report as a spreadsheet and manually matching CNs against your own order records. Kliovo pulls TCS COD payment reports directly via the TCS API. It matches deposit amounts against the COD values of your TCS CNs and flags any discrepancies — underpaid, overpaid, or missing from the deposit. The reconciliation view shows you exactly which CNs are settled and which need follow-up with TCS. Month-end close that used to take a finance team half a day now takes under an hour.
Switching couriers for a city when one fails
Lahore delivery failures spike on Leopards during certain weeks — network congestion, driver issues, whatever the reason. In a manual operation, rerouting means downloading the affected CNs, cancelling them in Leopards portal, re-entering addresses in a different courier's portal, and updating your own records manually. In Kliovo, you update the smart routing rule: Lahore orders above Rs 5,000 route to BlueEx for the next 7 days. Save the rule. From that point, all new Lahore orders book to BlueEx automatically. Existing in-transit CNs are unaffected. Routing change takes under two minutes — no spreadsheet, no manual re-booking.
Frequently asked questions
What if a courier API is down?
Kliovo handles courier API failures gracefully. If a courier's API returns an error or times out, the CN booking is queued and retried automatically — you see a clear error message on the order with the failure reason. Kliovo's per-courier error handling normalizes the different error formats each courier uses, so you always get a human-readable explanation rather than a raw API error code. You can also manually trigger a retry from the order detail page once the courier's system is back.
How does TCS COD reconciliation work?
TCS disburses COD payments in batches, usually weekly. Kliovo pulls TCS's payment report directly via the TCS API and matches each payment against the COD amount recorded on the corresponding CN in your Kliovo order records. The reconciliation view shows you a matched list, an unmatched list (CNs with no corresponding deposit), and a discrepancy list (CNs where the deposit amount doesn't match the COD amount). You can export this as a report for your finance team or flag CNs for follow-up with TCS directly from the Kliovo interface.
Can I set different couriers for different cities?
Yes — that is exactly what the Smart Courier Routing feature is for. You create rules: Karachi orders under Rs 3,000 go to Swyft; Karachi orders above Rs 3,000 go to TCS; Lahore and Islamabad go to Leopards; all other cities go to Trax. Rules are evaluated in priority order. When an order arrives, Kliovo evaluates all active rules and selects the first match. You can update rules at any time — changes apply to all new orders immediately.
What is the fastest courier for Lahore?
Swyft and PostEx typically have the fastest Lahore delivery times — often same-day or next-day within Lahore city. TCS and Leopards are usually next-day. Trax depends on the pickup area. Kliovo surfaces per-courier delivery performance metrics in your reports so you can make routing decisions based on your own actual delivery data, not industry averages. The best answer for your business depends on your specific order profile and delivery address mix.
Does Kliovo handle reverse logistics for returns?
For couriers that support it — currently BlueEx and PostEx — you can book a reverse CN directly from the Kliovo order detail page. The return CN is linked to the original outbound order for traceability. For couriers that do not support reverse CN via API, Kliovo records the return manually and updates the order status. Return CN receipt is handled in the Barcode Scanning Center, which updates inventory and order records simultaneously.
What if my courier isn't on the list of 7?
You can connect any courier via Kliovo's public REST API. The API exposes the full CN lifecycle: booking, tracking, cancellation, and status updates. Full webhook support is documented. A developer can typically integrate a new courier in an afternoon using the API documentation. If the courier has a non-standard API format, the Kliovo team can assist with the integration as part of the Done-For-You onboarding tier.
Works best with
Kliovo Shop
Stop switching courier portals. Run dispatch from one screen.
Connect all 7 Pakistani couriers in under an hour. Your first CN booked via Kliovo on day one — no developer required for TCS, Leopards, or Trax setup.