COD, Leopards, and TCS: Building an E-Commerce Website That Handles Pakistani Logistics
Cash on delivery still accounts for 60–80% of Pakistani e-commerce orders. Most platforms aren't built for it. Here's how to build a store that handles COD, courier APIs, and the reconciliation problem properly.
Western e-commerce platforms are designed around prepaid card transactions. Pakistan's e-commerce market is dominated by cash on delivery. These two realities create a gap that most off-the-shelf platforms — and many local developers — don't close properly. Here's what a properly built Pakistani e-commerce system actually needs.
Why COD changes everything about your store's architecture
In a prepaid model, the payment gateway confirms payment before the order is created. Simple: payment success → order confirmed → fulfillment starts. With COD, you have a confirmed order with no payment, a customer who might not be home, and cash that has to physically move from the customer to the courier to your bank account — with a courier company sitting in the middle taking a cut and sending you a weekly remittance.
This means your store needs to handle:
- COD orders with a separate "pending confirmation" status
- Fake order filtering before you spend money packing and shipping
- Courier integration for label generation, tracking, and status updates
- Failed delivery workflows (returned to origin, re-attempt scheduling)
- COD remittance reconciliation — matching what the courier says they collected to what shows in your bank account
- Partial COD — customers who pay part upfront and the rest on delivery
None of this is supported out of the box by Shopify, WooCommerce, or any international platform. They can be hacked together with plugins, but the seams show — and Pakistani store owners end up managing critical business logic in spreadsheets because the platform couldn't handle it.
The courier integration layer
Pakistan's major courier companies — Leopards, TCS, M&P (Swyft), Trax, BlueEX — all have APIs for booking shipments, generating tracking numbers, printing waybills, and receiving status webhooks. A properly built e-commerce system connects to at least one of these directly.
What the integration enables:
- Automatic booking: When an order is confirmed and packed, your system creates a shipment at the courier automatically — no manual entry on their portal
- Waybill generation: A printable label with the tracking barcode is generated in your admin panel without switching to the courier's website
- Status webhooks: When Leopards scans a package at their warehouse, picks it up for delivery, attempts delivery, or delivers it, your system receives a webhook and updates the order status automatically
- Customer notifications: Status updates trigger WhatsApp or SMS messages to the customer without any manual action
- Return management: When a delivery fails after three attempts, the system marks the order as returned and adjusts inventory
Without direct API integration, all of this happens manually: someone logs into the courier portal, enters the shipment details, copies the tracking number back into the store, then checks the courier portal daily to see what was delivered. That's fine for 20 orders a day. At 200+ orders, it's a full-time job — and error-prone.
Fake order reduction — a Pakistani-specific problem
COD enables a pattern that doesn't exist in prepaid markets: fake orders. Someone places an order with no intention of receiving it — sometimes a competitor, sometimes a bored troll, sometimes just someone who changed their mind and didn't cancel. You pack the order, ship it, pay the courier, and then the package comes back unclaimed. You've lost the shipping cost both ways.
Techniques that actually reduce fake COD orders:
- Phone number verification via OTP before the order is confirmed: One SMS cost per order is worth far more than a two-way return shipping cost
- Order confirmation call or WhatsApp message: A template WhatsApp message asking the customer to confirm within 2 hours — if no response, the order is cancelled. Automation handles this, no staff needed.
- COD eligibility rules: First-time buyers or accounts with a previous return get a prepaid-only option, or a partial deposit requirement
- Address verification: Require a complete address including city and area — vague addresses (just a name and phone number) are the strongest fake order signal
The COD remittance reconciliation problem
When Leopards delivers your orders, they hold the cash and remit it to you weekly (or biweekly, depending on your agreement). They send a remittance report listing which tracking numbers were delivered and what was collected. You need to match this against your orders to confirm you received what was owed.
In most Pakistani stores, this is a weekly spreadsheet exercise where someone manually compares two Excel files. In a properly built system, the courier sends the remittance report electronically, your system imports it, matches tracking numbers to orders, marks those orders as paid, and flags any discrepancies. A 30-minute weekly task becomes a 5-minute review.
Multi-courier strategy
Relying on a single courier is a risk. Leopards, TCS, and M&P all have service interruptions, strikes, and regional gaps. A built-for-Pakistan store should be able to route orders to different couriers based on the destination city, product weight, or service level — and switch the default courier without touching the codebase when one provider starts having problems.
This is an architecture decision, not a feature you add later. Building with a courier abstraction layer from the start costs a little more upfront and saves significant pain when you inevitably need to switch or add couriers.
Payment gateway alongside COD
COD dominates, but prepaid orders exist — and prepaid orders are better for cash flow and eliminate return risk. A well-built Pakistani e-commerce store incentivises prepaid without eliminating COD: a small discount for online payment, free shipping above a certain value for prepaid, or priority processing. JazzCash and EasyPaisa now both have reliable e-commerce payment APIs that handle the most common Pakistani payment methods. Stripe covers international credit cards for Pakistani businesses with a USD account.
We build e-commerce websites in Pakistan on Laravel + Vue.js with proper COD workflow, courier API integration, and WhatsApp automation built in from the start — not bolted on. If you're starting a store or rebuilding an existing one, book a 30-minute call to scope it properly.
Building a Pakistani e-commerce store?
We build stores with COD workflows, Leopards/TCS/M&P integration, WhatsApp order automation, and proper remittance reconciliation — not an international template with Pakistan bolted on.
Book a free strategy call