Kliovo Shop
Stop Manually Assigning Couriers. Let Smart Routing Do It.
Smart Courier Routing in Kliovo Shop automatically matches every order to the right courier using four routing rules — city, weight, payment method, and order value. Set the rules once. Every order follows them.
Multi courier integration Pakistan means connecting TCS, Leopards, Trax, BlueEx, PostEx, Swyft, and Sonic to one system and letting routing rules pick the right courier for every order — by city, weight, order value, and payment method — automatically, so no one has to choose by hand.
How Smart Courier Routing works
Order arrives
Routing starts with any courier you've assigned by hand — manual choice always wins. If you picked one for this order yourself, nothing below it ever runs.
Rules matching
Checks your configured routing rules in priority order. First match wins: city, payment method, weight range, order value range, store. You decide what takes priority.
City mapping fallback
If no rule matches, checks your city-to-courier direct map — for example Karachi to BlueEx, Lahore to TCS, Peshawar to Leopards. This is how you auto assign courier by city without touching every order.
Store default
If no map matches, uses the store's default courier. Nothing goes unrouted. Every order has a courier assigned before it moves to packing.
Rule examples you can copy
These are the rule shapes most Pakistani sellers start with. Copy them as-is, then tune the couriers and thresholds to what actually performs in your own numbers — this is how you auto assign courier by city, weight, and payment type from day one instead of guessing per order.
Set your strongest metro courier as the direct city map entry for your highest-volume city, so it never falls through to a slower default.
A second city map entry for your next-biggest metro. Different cities can — and usually should — point to different couriers.
You do not need to map all 200+ cities on day one. Unmapped tier-2 and tier-3 towns fall to the default, so nothing sits unrouted while you build out coverage.
Small, light parcels are usually the cheapest to move on a per-kg courier that charges more per booking than per kilo. Split this off from your default before it eats margin.
Heavier parcels often cost less per kilo with a courier that discounts bulk weight. One rule keeps every heavy order on the cheaper option automatically.
COD orders often do better with the courier that has the widest cash-collection network; prepaid orders can move on a faster, lighter-touch courier since there is no cash to reconcile.
Everything included
Four routing rules, seven couriers, and a testing tool — all in one configuration screen.
Multi-condition routing rules
Create rules based on city, payment method (COD/prepaid), weight range, order value range, or store. Mix and match conditions with AND logic to express any scenario.
Four-rule fallback chain
Explicit assignment → rule match → city map → store default. Nothing falls through. Every order has a courier before it leaves the processing queue.
Priority ordering
Rules are evaluated in the order you set. First matching rule wins. Drag to reorder rules as your strategy evolves — no code, no support ticket needed.
Manual override always wins
Any courier manually assigned at the order level takes precedence over all rules. Your team can always step in and override the rules for one-off exceptions without switching routing off.
Store-level default courier
Each store (WooCommerce, Shopify, Daraz) has an independently configurable default courier. Multi-brand setups stay fully separated with no rule cross-contamination.
Rule testing before going live
Enter a hypothetical order (city, COD, weight, value) and see which courier would be selected and which rule triggered — before activating the rule in production.
Built for teams that...
The COD brand routing COD vs prepaid differently
The pain: Before routing rules, all orders went to TCS. Prepaid customers were waiting 3 days longer because TCS does not prioritize them in pickup queues.
The fix: Now prepaid goes to PostEx, COD to TCS — delivery time improved by 1.5 days on average. One rule, set once, permanent improvement for every prepaid order.
The multi-city D2C brand
The pain: We ship to 40 cities. Some couriers are better in Karachi, others in interior Sindh. Deciding per order was impossible — people made mistakes constantly.
The fix: Routing rules let us map this once — every order gets the right courier without anyone thinking about it. Lahore, Quetta, interior Punjab — all automatic.
The high-weight shipper
The pain: Our average order is 2.5kg. Leopards has the best rates above 2kg. Before routing rules, we were overpaying on lighter orders going to Leopards by default.
The fix: Orders under 1kg go to Swyft, above 2kg to Leopards. Courier cost down 12%. The rule pays for itself every single week in logistics savings.
Multi courier integration Pakistan: why one courier stops being enough
Every Pakistani courier is strong somewhere and weak somewhere else. Multi courier integration Pakistan sellers rely on isn't about running seven couriers at once for the sake of it — it's about never being stuck with a courier's weak city, its slow remittance cycle, or its bad week, because there's always another option the system can shift to.
Performance is never the same in every city
The courier that clears Karachi same-day might sit for two or three days in interior Sindh. The one that owns Lahore delivery might have thin, unreliable coverage in Quetta, Gilgit, or a small tehsil town. No single courier's network is strong everywhere in Pakistan — city-by-city routing is how you use each courier only where it's actually good.
One courier means one point of failure
Route everything through a single courier and you inherit every one of its weak points — the cities it under-serves, the returns process it's slow to clear, the COD remittance cycle that stretches out when their volume spikes during peak season. If that one courier has a bad week, your whole delivery operation has a bad week with it.
RTO exposure gets concentrated, not spread
Pakistan's e-commerce return-to-origin rate is industry-reported in the 25–40% range, and it varies sharply by courier and by city. Sending every order through one courier means you're exposed to that courier's specific RTO pattern everywhere, instead of routing the orders most at risk of failed delivery to whichever courier actually performs best for that city or payment type.
How to switch couriers without breaking your operation
Add the new courier alongside
Connect the new courier without removing the one you already use. Both stay active. Nothing about your current operation changes yet.
Split traffic by rule
Send one slice of orders to the new courier — one city, one weight band, or one payment type — using a routing rule. The rest keeps flowing exactly as before.
Compare for a few weeks
Watch delivery time, RTO, and remittance speed on the split slice against your existing courier for that same segment before drawing conclusions.
Shift more volume, gradually
Once the new courier proves out on real orders, widen the rule to cover more cities or weight ranges. No cutover day, no operational disruption.
One courier or multiple?
Honestly — if you ship from one city, in low volume, to a small radius your courier already covers well, a single courier can be enough. Adding routing rules for the sake of having them doesn't help a seller doing twenty orders a day out of one warehouse in one city.
The calculation changes once you ship to multiple cities, run both COD and prepaid, or cross a few hundred orders a month. At that point a single courier is very unlikely to be the best option for all of it — it will be strong in some cities and weak in others, competitive on light parcels and expensive on heavy ones. That gap is exactly what routing rules exist to close.
You don't have to commit to all seven couriers on day one. Most sellers start with two — their existing courier plus one challenger — and add a rule or two to split traffic between them. The store default courier covers everything you haven't built a rule for yet, so there's no all-or-nothing moment. You can grow from one courier to a full routing setup at whatever pace your order volume actually justifies.
The numbers
4
Routing rules evaluated per order in sequence
Manual → Rule → City Map → Default. Nothing ever goes unrouted.
0
Manual courier assignments needed per day
Once your rules are set up, every order gets routed automatically — no operator decision needed.
7
Pakistani couriers in the routing pool
TCS, Leopards, Trax, BlueEx, PostEx, Swyft, and Sonic — all supported.
Common use cases
COD vs prepaid routing
Route all COD orders to TCS (widest network, best for unconfirmed deliveries) and all prepaid orders to Swyft (faster, better tracking for committed customers). Set in one rule, applies forever. No operator decision required on every order that comes in.
City-based routing
Map Karachi to BlueEx, Lahore to Leopards, interior Punjab to Trax. Customers in each city get the courier with the best delivery performance for that geography — automatically, without your ops team memorizing courier coverage zones or making case-by-case calls.
Weight-based cost optimization
Light orders (under 500g) go to Swyft, heavy orders (over 2kg) go to Leopards where bulk rates are better. Reduces average courier cost without touching individual orders or training your team on courier pricing tables that change quarterly.
Frequently asked questions
What happens if a routing rule's courier booking fails?
You will get an alert in your notification queue. The order stays unbooked and you can manually assign an alternative. The routing engine does not silently fall back to a different courier — failed bookings are flagged clearly so nothing ships without a valid CN number.
Can I route by store, not just by courier?
Yes. Each store has an independently configurable default courier. If you run multiple brands — one on WooCommerce, one on Shopify — each can have a different default courier and separate routing rules that only apply to that store's orders.
How do I set up city-to-courier mapping for 200+ cities?
Kliovo includes a pre-built Pakistan city list with common courier coverage zones. You configure the major cities and the rest fall to your store default — you do not need to map every city in the country to get meaningful routing coverage from day one.
Can routing rules have exceptions?
Yes — you can add a negative condition such as 'not Karachi' or 'not COD' to any rule. Rules support AND logic between conditions, so you can express complex scenarios like 'COD + Lahore + under 1kg → Swyft' with a single rule configuration.
Is routing available on all plans?
Routing rules are available on Growth plan and above. Self-Serve Starter gets store default courier only. See the pricing page for full plan details and a comparison of what each tier includes for your team.
How do I know which courier a specific order was routed to and why?
Every order record shows the courier assignment and the routing reason — manual, rule ID, city map, or default. You can see exactly which rule triggered for auditing or tuning your rule configuration over time.