Swyft Logistics API integration for Pakistani ecommerce

Once your Swyft Logistics account is connected, Kliovo Shop handles the CN lifecycle without the Swyft 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 Swyft automatically. No logging into the merchant portal to enter each order by hand, no backlog building up at the end of a busy day.

Tracking works the same way in reverse. Every dispatched Swyft shipment shows up in Kliovo's tracking view next to your other couriers, and each status change can send a WhatsApp message to the customer — booked, dispatched, out for delivery, delivered. The 'where is my order' messages drop off because the update reaches the customer before they have to ask you.

The flow: an order arrives from your store (Shopify, WooCommerce, or entered manually) → the order is confirmed on WhatsApp → Kliovo books the CN over the Swyft API using your own vendor ID and token → the CN number attaches to the order → the label is ready to print. On a full dispatch day, bulk booking sends the whole batch at once, and bulk label printing produces a single PDF for everything going out.

Cancel an order before it's picked up and Kliovo sends the cancellation to Swyft right away — no CN left open in Swyft's system for an order that never shipped, no manual cleanup call to make later.

Swyft's Pakistan network is still growing, and it doesn't cover as much ground as TCS or Leopards yet. Most stores that use Swyft treat it as a secondary courier — routed to specific cities or routes where Swyft's rates or delivery performance work in their favor — rather than as the default for every order.

That's a routing decision, and Kliovo's rules make it automatic once you set it. For a smaller or newer operation running maybe 10 to 50 orders a day, this can be as simple as one rule: send orders bound for certain cities to Swyft, and let your main courier carry everything else. You don't have to remember to do this order by order — the rule runs on its own after it's configured, and it stays out of the way until you decide to change it.

The same rule can key off weight, order value, or payment method instead of city, or combine two of those conditions — a lightweight COD order under a certain value going to Swyft while heavier or prepaid orders default to your main courier, for example. None of this requires touching Swyft's own portal once the rule is live; Kliovo checks the order against your conditions the moment it's confirmed and books with whichever courier the rule points to.

Swyft issues two credentials — a numeric vendor ID and a separate API token — from the Swyft Merchant Portal under Developer Settings → API. If you don't have a Swyft merchant account yet, you'll need to sign up directly with Swyft first before there's anything to connect. One common mistake: pasting the vendor ID with a 'VND-' prefix attached. Swyft vendor IDs are numeric only, so if yours reads like 'VND-00123,' enter just '123' in Kliovo Shop's connection field.

Worth being upfront about what this integration doesn't do. Real-time rate comparison before booking isn't available for Swyft inside Kliovo — that's Leopards and BlueEx only. Return CN booking through the API is BlueEx and PostEx. And the deep, automated COD remittance matching that reconciles TCS deposits line by line is TCS-only. COD amounts on Swyft orders are still tracked per CN in Kliovo's reports, so nothing about a Swyft order goes unrecorded — it just isn't reconciled against Swyft's payment batches automatically the way TCS is.

None of that changes what the integration is good at day to day: getting Swyft CNs booked the moment an order is confirmed, keeping every Swyft parcel visible next to your other couriers, and sending the customer a WhatsApp message without anyone on your team touching the Swyft portal. For a store running Swyft alongside one or two bigger couriers, that's usually the part that actually saves time.