Sonic Courier API integration for Pakistani ecommerce

Once your Sonic account is connected, Kliovo Shop handles booking, tracking, cancellation, and label printing without the Sonic portal. When an order is confirmed — typically the customer tapping Confirm on the 60-second WhatsApp message — the CN books with Sonic automatically, no manual entry required.

Every dispatched Sonic shipment then tracks inside Kliovo alongside your other couriers, and each status change can trigger a WhatsApp message to the customer — booked, dispatched, out for delivery, delivered. That keeps 'where is my order' messages out of your inbox, because the customer already has the answer.

The flow: an order arrives from your store (Shopify, WooCommerce, or manual entry) → the order is confirmed on WhatsApp → Kliovo books the CN over the Sonic API using your own API key → the CN 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 it's picked up, Kliovo sends the cancellation to Sonic immediately — no CN sitting open in Sonic's system for an order that never shipped.

Sonic is a newer entrant covering major Pakistani cities and still expanding its network. Sellers tend to run it as one courier in a wider mix rather than as the default — useful on routes where its rates are competitive, or as an overflow option when a primary courier is running at capacity during a busy week.

For a seller doing 10 to 50 orders a day out of one or two cities, that often means a single routing rule is enough: Sonic picks up orders under a certain weight or bound for a specific city, and everything else goes to your main courier. Set it once in Kliovo and it runs on every order after, no manual sorting required.

The same rule can be built around payment method instead — Sonic handling COD orders in one city while a different courier carries prepaid orders everywhere else, or the reverse. There's no need to decide this manually on every order once the rule exists; Kliovo checks each confirmed order against your conditions and books it with whichever courier the rule names, Sonic included.

Sonic uses a single API key, generated from the Sonic Merchant Portal under API / Developer Settings. Because Sonic is a newer courier, that section isn't always visible in every merchant portal yet — if you don't see it, email [email protected] directly and request merchant API credentials; expect a short wait, typically a few business days, rather than instant activation. If the connection test in Kliovo Shop returns a 404 after you've entered a valid key, that's usually Sonic having moved an API endpoint on their end — flag it to Kliovo support rather than re-entering the key, since endpoint changes are tracked and updated centrally.

Worth being upfront about the boundaries here too. Real-time rate comparison before booking isn't available for Sonic inside Kliovo — that's Leopards and BlueEx. Return CN booking through the API is BlueEx and PostEx. And the deep automated COD remittance matching built for TCS isn't part of the Sonic integration. COD amounts on Sonic orders are still tracked per CN in Kliovo's reports, so you can see what's owed on every order — it just isn't reconciled against Sonic's payment batches automatically.

What Sonic does get from Kliovo is the part most sellers actually feel day to day: no re-typing an order into the Sonic portal, no separate spreadsheet to track which Sonic CNs are still moving, and a WhatsApp update that reaches the customer without anyone on your team sending it by hand. As Sonic's own network grows, that automation carries over without any extra setup on your side.