The question that decides most post-purchase software deals is not on any feature comparison. It is "does this work with my carriers, and who fixes it when the carrier changes something." Every vendor answers the first half with a logo wall. Almost none answer the second half unless you ask.
This is the checklist we would use if we were buying. It is written to be run against any vendor, including us. Nothing here needs a demo to answer; a straight answer to all twelve takes a vendor about twenty minutes, and the ones who cannot answer quickly are telling you something.
Short answer: Ask which of your carriers are live in production today rather than how many the vendor supports in total, then ask who builds and maintains each connector, what happened the last time a carrier shipped a breaking API change, which fields map beyond the tracking number, and what adding a new carrier actually costs in time and money. Pango connects to more than 100 carriers through prebuilt connectors, and the full list is on the integrations page.
Before the call: the two numbers that matter
Your carrier list, not theirs. Write down every carrier and service you use today, including the regional one you use for 4% of volume and the one you are trialling. That short list is the only integration scope that matters. A vendor with 1,000 connectors and none of your four is worse than one with 100 that has all four.
Your platform and warehouse stack. Store platform, order management, warehouse system or 3PL, and the tools that send customer messages. An integration that stops at the carrier and cannot see the order is half a product.
The 12 checks
1. Is my carrier live in production today, for another customer? Not "on the roadmap", not "we can build it". Live, for someone else, now. Ask for the connector's age.
2. Which of my carrier's services are supported? Carriers are not one integration. Domestic, express, economy, pickup-point, locker and returns services are often separate products with separate fields. A connector that covers a carrier's standard domestic service may not cover its locker network.
3. Who built the connector, and who maintains it? Three possible answers, in descending order of safety: the vendor builds and maintains it, the vendor resells a third-party aggregator, or you build it against their API. The second is common and usually undisclosed; it matters because a bug is then two support queues away from a fix.
4. What happened the last time one of my carriers shipped a breaking change? This is the best question on the list, because it cannot be answered with marketing. Ask for the specific incident, how long tracking was degraded, and who noticed first, the vendor or the customer.
5. Which fields map, beyond the tracking number? Status is the minimum. The useful ones are the scan timestamp and location, the estimated delivery date the carrier itself returns, proof of delivery including the photo, the exception or reason code, the pickup-point identity, and the billed weight. Ask which of those you get per carrier, because it varies per carrier even within one vendor.
6. Are statuses normalised, or passed through? Forty carriers use forty vocabularies for the same event. If the product passes the carrier's wording straight to your customer, your tracking page will contradict itself between carriers. The normalisation problem is explained in what is carrier integration.
7. Can I print labels, or only track? Tracking-only integrations are much easier to build, which is why carrier counts are often inflated by them. If you need labels, customs documents and manifests, ask which carriers support each, separately.
8. What is the cost and lead time to add a carrier that is not on the list? Get a number and a timeline in writing. "We can add any carrier" with no price attached usually means a professional-services quote later.
9. Does routing sit in the same product? Connecting to five carriers is not the same as choosing between them per order. If rate shopping and fallback live in a different tool, you are buying an integration project as well as software. The category is set out in multi-carrier parcel management.
10. What happens when a carrier is down? At label creation, a failing carrier should trigger a fallback rather than a failed order. Ask what the fallback does, and whether it respects your service promise.
11. Can I use my own carrier contracts? Some products only work with their own negotiated rates. If you have contracts, confirm you can keep them, on every plan and not just the top one.
12. Who owns the data if we leave? Tracking history, reason codes and carrier performance are your operating record. Ask for the export format and whether historical scans come with it.
Reading a logo wall honestly
Carrier counts are a marketing number more than a capability. Vendors count different things: providers, services, or shipping methods, and a single carrier can be counted as one or as forty depending on which. The published figures across this category range from 170 to 4,000 and are not comparable with each other.
Three questions cut through it. How many of those are tracking-only? How many are live for a customer today rather than available? And which four matter to me?
The pattern we see in real buying behaviour
The strongest signal that a brand is seriously evaluating post-purchase software is not that it reads a pricing page. It is that it opens the integration page for its own carrier, repeatedly. A brand shipping big and bulky goods checking a home-delivery specialist, or a WooCommerce store checking the WooCommerce connector, has already decided the category is worth buying and is now checking whether the specific thing it depends on is covered.
That is also the fastest deal to lose. If the answer is unclear, the evaluation quietly stops, and the vendor never learns why. So the honest advice to any buyer is to ask the question directly and early rather than inferring the answer from a logo.
How Pango answers these
Pango connects to more than 100 carriers through prebuilt connectors, listed on the integrations page, alongside store platforms, order management and warehouse systems. The connectors are built and maintained by Pango rather than resold, and the same order record carries the carrier data, the routing decision, the warehouse action, the customer message and the return, so the integration does not stop at the tracking number.
The wider difference is where the work happens. Most products in this category give your team a console to operate. Pango reads the merchant's order data and delivery and returns policies on install, then runs the operation as agent workflows with your team supervising, which is also why a carrier change is Pango's problem rather than a configuration task for you. The product detail is in delivery management and the category framing in multi-carrier parcel management.
If you want this run against your actual carrier list rather than in the abstract, the shipping and returns audit is the fifteen-check version we walk through before recommending anything.
The bottom line
Buy on the four carriers you actually use, not on the number on the homepage. The questions that separate a real integration from a logo are who maintains it, what broke last, which fields map, and what happens when a carrier fails at label time. See Pango's integrations or book a demo.
