
If you sell from Pakistan on Shopify, you probably book parcels with more than one courier, collect cash on delivery, and chase statuses in each courier’s own portal. This article covers Shopify courier integration for Pakistan: which kinds of app exist, what two real App Store listings say, where apps stop, and when a custom build that checks each order by ID is worth the money. It is written for store owners first and the technical person who will brief a developer second.
What a courier integration actually has to do
“Integration” hides four separate jobs. Check which ones you need before comparing anything.
- Booking. Send the order’s address and COD amount to the courier and receive a tracking number.
- Labels and pickup sheets. Print airway bills and loadsheets for the rider.
- Status sync. Read the courier’s progress and reflect it in Shopify.
- Cash and returns. Mark COD orders paid after delivery, and handle refused or returned parcels.
Most apps are strongest at jobs 1 and 2. Jobs 3 and 4 are where merchants hit limits. The mechanics of those two are in our guide to Shopify tracking number automation.
The app types that exist
Searching the Shopify App Store for Pakistani couriers turns up three patterns:
- Multi-courier booking apps. One app, many courier accounts. You connect your own account with each courier.
- Single-courier apps. One carrier only; search results show examples for individual couriers.
- Aggregator tracking apps. Not specific to Pakistan, they follow parcels and send tracking pages and notifications.
I opened two multi-courier listings in full. Names and prices below are what those listings showed when I read them. They change often, so check the live page.
Courierify: Pakistani Couriers (GrowZar). The listing names BlueEx, Dex, Leopards, PostEx, TCS and Trax. It describes booking from the Shopify admin, shipping labels and return labels, return receiving with a barcode scanner, pickup loadsheets, a delivery and return dashboard, and WhatsApp automation. It says tracking syncs automatically and that it creates fulfilments with tracking numbers in Shopify. Plans were listed in US dollars with a lower tier, a higher tier with order automation rules, and a top tier with ERP/WMS integration and a webhook API, plus usage charges on some features. See the Courierify listing.
Universal Courier Pakistan (Devsol). The listing names a long list of couriers, including TCS, Leopards, Trax, PostEx, M&P, BlueEx, Pakistan Post and others, and says you connect your own courier accounts. It lists single and bulk booking, branded labels, loadsheets, returns, a live tracking page and analytics. It had a free plan with a daily booking limit and paid plans with one-time charges. The listing did not mention COD handling. See the Universal Courier Pakistan listing.
Other Pakistan courier apps appear in search results too. I have not opened them, so I am not describing them.
Where apps are enough
An app is the right answer when:
- Your couriers are on its supported list.
- Booking and labels are the main pain.
- A status that lags by hours is fine.
- You do not need rules beyond what its plans offer.
- A monthly fee is cheaper than build plus upkeep.
For many small stores that is the case, and a custom build would be an expensive way to solve a problem an app already solves. Try an app first, on a free tier if the listing offers one, with real orders for a week.
Where apps stop
These are the situations I would test hard in any app, or take as signs that a custom approach is worth pricing:
- A courier is missing. Smaller or regional carriers may not be listed.
- COD rules are yours. For example, mark paid only when the courier reports delivery, flag orders refused twice, or hold dispatch for suspicious COD orders. Ask whether the app calls Shopify to mark the order paid, and on which status.
- Your own tracking page or messages. Branded notices, language, WhatsApp wording and timing.
- ERP or accounting link. Delivered and returned parcels need to reach another system.
- Different statuses per courier. You want one internal status set, with explicit rules for each carrier’s wording.
- Reconciliation. You want a check of delivered orders against the courier’s remittance report.
- Data control. You prefer that customer addresses and order data stay in systems you own.
When a custom order-ID polling build makes sense
A custom build works like this. A scheduled job takes each open order that has a courier and tracking number, asks that courier’s tracking service for its status, matches the answer back to the Shopify order by order ID and tracking number, and writes the result to Shopify. It repeats until the parcel is delivered or returned.
The pieces:
- A record per shipment. Order ID, courier, tracking number, last status, next check time.
- One adapter per courier. Each adapter speaks to that courier’s API and returns your own status set. Adding a courier means writing one adapter.
- A queue and retries. Courier services time out. Retry with delays and stop after a limit.
- A Shopify client. It uses the Admin API to update the fulfilment and add events. Shopify documents
fulfillmentEventCreate,fulfillmentTrackingInfoUpdateandorderMarkAsPaid, the last designed for payments received outside checkout such as COD. - An audit log and alerts. Every change recorded; a person warned when a courier fails.
Which couriers offer an API, what it returns and what credentials it needs differ, and I will not describe any courier’s endpoints, fields or authentication here. Ask each courier for its official API documentation and your own credentials. Treat anything a third party tells you about a courier’s API as unverified until you see it from the courier. For a sense of what public documentation can look like, DHL publishes a shipment tracking API with an API key and documented rate limits. Many Pakistani couriers provide access through the merchant account instead.
If a courier has no API at all, a build cannot read from it. Some businesses then rely on the courier’s CSV or email reports, which is possible but more fragile. Say so before anyone quotes.
Build details are in our custom app guide, and cost drivers in how much a custom Shopify app costs.
App or custom: comparison
| Multi-courier app | Custom polling build | |
|---|---|---|
| Time to start | Same day, in some cases | Weeks, after scoping |
| Booking and labels | Built in | Only if included in scope |
| Supported couriers | The app’s list | Any courier with an API, one adapter each |
| COD and RTO rules | What plans allow | Your rules, step by step |
| Own tracking page and messages | Limited to app features | Designed to your needs |
| Cost shape | Monthly or one-time plan, plus usage charges | Build fee plus hosting and upkeep |
| Who maintains it | The app developer | You or your agency |
| Data | Held by the app vendor | In your systems |
A middle path exists: keep the app for booking and labels, and add a small custom job only for the missing piece, such as COD marking or an ERP link.
Consent and customer messages
If you send tracking updates by WhatsApp, SMS or email, collect consent, give a way to opt out, and follow local law. Pakistani law, GDPR (if you sell to the EU) and platform rules differ. Check with a qualified adviser. This article is not legal advice.
Frequently Asked Questions
Which Shopify apps connect to Pakistani couriers?
Public listings exist for multi-courier apps. Two I opened were Courierify and Universal Courier Pakistan, each listing several Pakistani couriers. Always check the live listing for supported couriers and prices.
Can an app mark COD orders as paid automatically?
Some may; the listings I read did not clearly say. Ask the app’s developer which courier status triggers it, and test with a real order.
Do I need a custom build if my courier is not supported?
Maybe. First ask the app’s developer whether they can add it. If not, and your courier offers an API, a custom adapter is possible.
Can a custom app use any courier?
Any courier that gives you a tracking API, data feed or webhook. You need the official documentation and credentials from them.
Will it replace my courier’s own dashboard?
No. The courier’s dashboard stays the source of truth for parcels. The automation reads from it and updates Shopify.
For a single-courier walkthrough, see Shopify PostEx integration: app or custom build?. For an international courier example, see the Shopify DHL tracking setup and automation guide.
Conclusion
For Shopify courier integration in Pakistan, start with an app, because booking and labels are well served by listings already in the App Store. Look at a custom build when your couriers, COD rules, tracking pages or back-office systems do not fit what an app offers, and keep the build narrow: one adapter per courier, a clear status map, an audit log. If you would like help with this, CYPHEX can plan and deliver it for you, with one project lead as your contact. See our Shopify courier tracking automation, Shopify developer Pakistan and API integration development services.
Stock photography provided by Pexels under the Pexels License.
