TCS API integration for Pakistani ecommerce

Once your TCS account is connected, Kliovo Shop handles the full CN lifecycle without the TCS 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 TCS automatically. No copy-pasting addresses, no end-of-day booking backlog, no forgotten orders sitting unbooked overnight.

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

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 TCS API using your own TCS 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 CN cancellation to TCS immediately — no orphaned CNs left in the TCS system, no calls to the account manager to clean up bookings that never shipped.

TCS disburses COD payments in batches, and matching those deposits to individual orders is where most finance teams lose days. Kliovo pulls TCS payment reports and matches every remittance line to its CN automatically. You get three lists: matched payments, CNs with no corresponding deposit, and discrepancies where the deposited amount doesn't equal the COD amount on the order — ready for follow-up with TCS before the dispute window closes.

Load sheets are generated in TCS-compatible format for bulk handover: every CN in the pickup batch listed with weight, destination, and COD amount, ready to hand to the TCS driver. Between reconciliation and load sheets, this is the deepest TCS integration available in any Pakistani ecommerce software.

If your store runs on Shopify or WooCommerce, the TCS connection sits on top of the store sync: orders flow in the moment they're placed, confirm on WhatsApp, and book with TCS — then fulfilment status flows back to your store automatically. There's no separate TCS app to install per platform and no CSV exports; one connection covers the whole path from checkout to CN.

Selling through Instagram DMs or WhatsApp without a website works the same way once the order is in Kliovo — manually entered or captured from chat, it gets the same WhatsApp confirmation, the same TCS booking, and the same tracking updates as a store order. The notebook-and-screenshots workflow is what this replaces.

TCS coverage is nationwide, and how you use it is your call — Kliovo's routing rules decide which orders go to TCS versus your other connected couriers, by destination city, weight, order value, or payment method. Many stores route specific city tiers or high-value COD orders to TCS and let other couriers carry the rest; the rules run automatically once you set them, and your own delivery data in Kliovo's reports tells you which split performs best.

Routing also protects you when things change. If TCS performance dips in a specific city for a few weeks, you update one rule and new orders for that city book with a different courier — existing in-transit CNs are unaffected, and you can shift back just as easily. Multi-courier routing with TCS as an anchor is how high-volume stores keep delivery rates stable without being locked to any single network.