Skip to main content

WooCommerce Pakistan Courier Integration: PostEx, TCS

  • November 11, 2026
  • 8 min read
  • By CYPHEX
WooCommerce Pakistan Courier Integration: PostEx, TCS
Illustrative animation with example data

If you run a WooCommerce store in Pakistan and ship cash-on-delivery (COD) orders, you probably copy addresses into a courier portal, paste tracking numbers back into orders, and answer “where is my parcel” messages by hand. A WooCommerce Pakistan courier integration removes most of that. This guide is for store owners and the person who will brief a developer. It covers what the integration has to do for PostEx, TCS and Leopards Courier, when a plugin is enough, when a custom build makes sense, and what to check before you choose. It also says plainly what we could and could not verify.

What we verified, and what we did not

Courier integrations are an area where guessing is expensive, so here is exactly what this article rests on. We opened the pages linked below at the time of writing.

  • PostEx. The PostEx home page lists nationwide COD delivery, same-day delivery, a Track Order page and a delivery charge calculator. It does not mention an API, developer documentation or WooCommerce.
  • TCS. The TCS home page we fetched showed only a welcome message, with nothing about merchants, APIs or plugins. We could not confirm anything about TCS integration from TCS’s own site.
  • Leopards Courier. The Leopards Courier home page shows e-commerce login portals for Pakistan and the UAE. It does not mention an API, plugins, COD or tracking.
  • Plugins. We found one commercial multi-courier listing and one very old TCS plugin, both described below. We did not find an official plugin from any of the three couriers.
  • WooCommerce. The HPOS documentation and the order statuses page were read directly.

We did not verify public API availability, endpoints, authentication, rate limits or webhooks for any of the three couriers. We have not tested any plugin on a live store. We are not listing prices for couriers or plugins, and nothing here is a rating.

What a courier integration has to do

“Integration” covers four separate jobs. Decide which ones you need before you compare options.

  1. Booking. Send the order’s address and COD amount to the courier and save the consignment number on the order.
  2. Labels and loadsheets. Print airway bills and pickup sheets for the rider.
  3. Tracking sync. Read the courier’s progress and write it back to the WooCommerce order.
  4. COD status and returns. Reflect collected, failed and returned parcels as clear order states, and match cash to orders.

Jobs 3 and 4 are where stores hit limits, so test those hardest.

The three couriers: what we could and could not confirm

PostEx. The site confirms COD delivery and tracking for customers. We saw no public developer page. A third-party API directory lists PostEx hosts, but it is derived by probing and is not documentation, so we treat it as a hint only. If you want an API route, ask PostEx support or your account manager for developer documentation and credentials for your merchant account.

TCS. We could not find official TCS API documentation through our search. Third-party material points in one direction: a WooCommerce TCS plugin listing says it connects to a SOAP API that TCS provides to developers, and an undated, unofficial document says API access follows becoming a TCS client. Treat both as leads, not facts, and ask TCS for the current developer portal and onboarding steps.

Leopards Courier. The home page shows merchant login portals and nothing about integration. We could not confirm an API or an official plugin. A search of the WordPress.org directory surfaced no official Leopards plugin, but a search result is not proof that none exists, so check the directory yourself.

Plugin options we found

Two examples, shown only to illustrate the range. We are not recommending either.

A commercial multi-courier plugin. The ECOSIRE Pakistan couriers listing names TCS, Leopards, Trax, M&P, PostEx, BlueEx, Call Courier, Swyft and Daewoo FastEx. It describes single and bulk booking from the order screen, load sheets and consignment PDFs, a WP-Cron job that syncs delivery status, COD reconciliation from courier remittance sheets, and HPOS support confirmed on your site during staging. The page gives an indicative starting price and asks you to request a quote. It showed no ratings or reviews. Whether each courier feature works for your account is something to test, not assume.

An old single-courier plugin. The TCS listing above says it was last updated in 2017 and has 10 active installs. It does not mention HPOS. A plugin that exists is not a plugin that is maintained, so check the last update date and HPOS declaration before installing anything.

Why HPOS matters when you pick a plugin

High-Performance Order Storage (HPOS) keeps order data in dedicated tables instead of the older posts tables. WooCommerce’s documentation says it is enabled by default for new installations from version 8.2, that existing stores must opt in, and that developers are required to declare compatibility. It also says stores with incompatible third-party extensions cannot switch to HPOS.

A courier plugin that reads or writes order data the old way can break on an HPOS store or block you from switching. Ask any vendor in writing whether it is HPOS compatible, and test on staging.

COD status inside WooCommerce

WooCommerce’s default statuses are Draft, Pending payment, Processing, Completed, On hold, Failed, Cancelled and Refunded. The documentation page we read does not mention custom statuses, and none of those defaults says “out for delivery”, “refused” or “returned to origin”.

That gap is where COD stores need decisions. For example: does “delivered” move an order to Completed? Is a refused parcel Cancelled, or a custom status you add? When a courier reports cash as collected, which action does that trigger? Write these rules down per courier and map them to one internal status set. Whether a plugin lets you do that is a question for its vendor.

Plugin or custom build

QuestionReady-made pluginCustom build
Time to startInstall and configureWeeks of scoping and testing
Couriers coveredThe plugin’s listAny courier that gives you access, one module each
Booking and labelsUsually includedOnly if in scope
Tracking back to ordersCheck how often and what it writesDesigned to your rules
COD and returns rulesLimited to its settingsYour rules, step by step
MaintenanceThe plugin authorYou or your agency
RiskAbandoned plugins, HPOS gaps, supportYou own failures

Our advice is the same as for Shopify stores: try a maintained plugin first, on staging, with real order shapes. Run it for a week and write down every point where staff still copy data or fix errors. If the list is short, stop there. If it is long, or you use two or three couriers with different rules, a custom build starts to pay.

What to check before choosing

For each courier, ask these questions and note the answers. The table is the checklist we use. Where we have not confirmed something, it says so.

CheckPostExTCSLeopards Courier
Booking from an orderNot confirmed (portal exists)Not confirmed (third-party plugin cites a SOAP API)Not confirmed (merchant portal exists)
TrackingPublic Track Order page; API not confirmedNot confirmedNot confirmed
COD statusCOD delivery listed; status data not confirmedNot confirmedNot confirmed
Official plugin or APINone found on the site; ask PostExNot confirmed; ask TCSNot confirmed; ask Leopards

Beyond the table, ask any plugin vendor or developer:

  • Is it HPOS compatible, and when was it last updated?
  • Does it use webhooks, or scheduled checks? How often do they run?
  • What happens if the courier’s service is down? Are failed bookings shown to staff?
  • Does it run courier calls in the background so checkout stays fast?
  • Does it log every sync?

How a custom build is scoped

A custom build starts with questions to each courier, not with code: does your account get API access, what fields are needed to create a consignment, how is the COD amount sent, can a booking be cancelled, how is status read, and is there any settlement data. City names deserve special attention, because courier city lists rarely match what customers type, so a mapping is needed.

On the WooCommerce side, we build as a plugin, store courier data on the order using the supported HPOS-safe methods, and use a background queue for courier calls. Each courier sits in its own module, so adding or replacing one is not a rewrite. If a courier offers webhooks we use them. If it does not, a scheduled job checks open orders by order ID and tracking number. Everything is logged and tested on staging first.

Frequently asked questions

Is there an official PostEx plugin for WooCommerce?

We found no mention of a WooCommerce plugin or API on PostEx’s home page. Ask PostEx support whether API access is available for your merchant account, and be careful with third-party claims until you see documentation.

Is there a Leopards Courier WooCommerce plugin?

We did not find an official one in our search of the WordPress.org directory, and Leopards’ home page does not mention one. Commercial multi-courier plugins list Leopards as supported, but you should confirm with the vendor and test it.

Does TCS work with WooCommerce?

A third-party plugin listing says it connects to a SOAP API that TCS provides to developers, but it was last updated in 2017. We could not confirm current TCS API terms. Ask TCS directly.

Do I need a custom build or is a plugin enough?

Start with a maintained plugin on staging. Choose custom work only when real orders show repeated manual steps, you use several couriers, or you need your own COD and returns rules.

Conclusion

A good WooCommerce Pakistan courier integration covers booking, tracking sync and clear COD states, and it stays HPOS compatible so it does not hold your store back. Test a maintained plugin first, keep a list of what still needs manual work, and ask each courier for official API access in writing before anyone plans a build. If you would like help, see our WooCommerce courier integration service, where one project lead is your single contact. For the Shopify side of the same problem, read Shopify PostEx integration: app or custom build?. And if slow checkout or order handling is the bigger worry, start with what to fix first when scaling WooCommerce.

Stock photography provided by Pexels under the Pexels License.

Need a feature your site does not have?

We build small, clean plugins and connect your tools so you do not repeat work by hand.

Comments

  1. Loading comments...

Leave a comment

Free quote

Get a clear plan and fixed price

Tell us what you need in three quick steps. No obligation, no jargon, and no pressure.

Step 1 of 3

Tell us what you need

Three quick steps. We reply within one business day.

What do you need help with? Pick all that apply