Carrier Count Claims: What 9 Vendors Publish

Why “carrier count” is the first number architects should distrust

Every multi-carrier shipping platform puts a number on its homepage. 40+ carriers. 180+ carriers. 1,000+ carriers. Sales teams treat it like a spec sheet entry, something you can drop into a comparison matrix next to API latency and pricing tiers. It isn't. There's no standard unit behind "a carrier" — it could mean a signed carrier contract, a documented API integration, a tracking-only webhook feed, a service level within one carrier's network, or a country zone inside a regional post.

That ambiguity would be tolerable if vendors were at least internally consistent. Many aren't. We pulled the carrier-count claims published by nine multi-carrier shipping and TMS platforms directly from their own marketing and documentation pages, and found that several vendors contradict themselves — sometimes on the same domain, sometimes on the same page. If you're scoping engineering work around a headline figure like "carrier integration coverage," this is worth fifteen minutes before you write a single line of adapter code.

Method

We manually checked each vendor's own marketing, help-centre, and documentation pages between 25 and 29 August 2026. All figures below are vendor self-reported and were not cross-checked against a live API catalogue or sandbox account. No independent audit of actual carrier connections was performed — this is a survey of what each company publishes, not a verification of what each platform actually delivers in production.

Where two live, vendor-owned pages disagreed, we logged both rather than picking a "correct" one. That's the point of the exercise: the disagreement itself is the data.

• No sandbox or trial accounts were created to count carriers directly.
• No API responses (carrier list endpoints) were queried.
• Figures from resellers, app-marketplace listings, and comparison blogs are marked as third-party where the vendor's own domain wasn't the source.
• Where a vendor's own domain didn't surface a figure during this check, the cell reads "Not published" rather than an estimate.

The numbers, as published

The table below lists every figure found, with the exact source page and a note on whether it's vendor-owned or third-party.

Data accurate as of 29 August 2026. Figures will drift as vendors add carriers and edit copy; treat this as a dated snapshot, not a live comparison.

What the inconsistencies actually tell you

Start with EasyPost, because it's the cleanest example. The main support category page states 100+ Carriers, and the shipping API page repeats 100+ carriers, including USPS, UPS, FedEx, DHL, and a bench of regional, same-day, cross-border, and consolidator services. But the Adding Carrier Accounts help article, on the same support subdomain, says We partner with over 65+ carriers, and we're open to supporting more carriers if customer demand justifies it. Same company, same domain, two figures 35 apart. Shippo has the same pattern but wider. Its carriers page claims Shippo is a multi-carrier shipping software that lets you print with 40+ Global Carriers at once, while the dedicated tracking API page states Shippo helps you customize your shipping process by offering 15 different carriers. A separate platforms page then introduces a third number entirely, describing a vast network 40+ carriers, 500+ service levels, and 1000+ carriers for tracking. That's three distinct figures for three different scopes (label-purchase carriers, tracking-only carriers, service levels), none of which is defined clearly enough for a reader to know which one applies to their integration.

ShippyPro's contradiction is arguably the sharpest because it happens inside a single page load. The homepage states early on that shippers can connect your ecommerce channels and 180+ carriers, compare real-time rates, and generate labels instantly, then further down the same page describes an all-in-one shipping platform that connects 190+ carriers, automates your entire fulfilment workflow, and reduces shipping costs. Ten carriers appear or disappear depending on which section of the same URL you read.

Cargoson shows the pattern isn't limited to consumer-facing parcel platforms. The Cargoson homepage advertises 1,000+ „plug&play“ carrier integrations and growing daily. Its own listing in the Odoo app marketplace says shippers can connect with 1,500+ carriers through direct API and EDI integrations. Meanwhile both the GitHub organisation page and Cargoson's own integration documentation pages describe 2,000+ carrier integrations across all freight modes (parcel, LTL, FTL, air, sea, rail) and, on an individual carrier's API doc page, 2,000+ other carriers. Three figures, two of which sit on cargoson.com itself.

None of this means these platforms are dishonest. It usually means marketing copy on one page gets updated after a growth milestone and the equivalent line on a different template doesn't, or "carrier" quietly shifts definition between a rating page and a tracking page. Sendcloud is the useful counter-example here: its homepage, pricing page, and blog all independently converge on the same 170+ EU carriers figure. That kind of consistency is achievable. When a vendor doesn't manage it, it's a weak but real signal about how tightly that vendor's marketing and technical documentation are kept in sync, which matters more than it sounds when you're relying on the same vendor's changelog to tell you when a carrier's label format changes.

What to check instead before you scope integration work

A published carrier count tells you almost nothing about what you'll actually be able to build against. Before you size an integration project, get answers to these instead:

• Ask for a machine-readable or API-queryable carrier catalogue endpoint, not a marketing page number. If the vendor can't return a list programmatically, treat the published figure as unverifiable.
• Check the date of the most recently added carrier in the changelog or release notes, not the "and growing daily" claim on the homepage.
• Separate "available for Bring Your Own Carrier Account" from "wallet/negotiated rate account" from "fully documented with webhook events." These are three very different integration surfaces that often get bundled into one headline number.
• Ask what fraction of the listed carriers support tracking webhooks versus polling-only status checks. A carrier that's "supported" but requires you to poll every fifteen minutes is a different engineering commitment than one pushing events.
• Request the actual list, filtered to your shipping lanes. A global count is irrelevant if none of the carriers cover the corridors you ship.

This verification approach applies whether you're evaluating EasyPost, Shippo, nShift, ShippyPro, ClickPost, or Cargoson. None of them get special treatment here; the gap between marketing copy and technical reality is a category problem in multi-carrier shipping software, not a single-vendor one.

Takeaway

Treat every carrier-count claim as marketing copy until you've pulled the sandbox catalogue yourself. The method above is reproducible in an afternoon: open each vendor's homepage, pricing page, API docs, and one comparison-blog result, and note every figure you find. If they don't match, that's not a footnote, it's the finding. If you run this check against a platform we didn't cover here, or catch an update that resolves one of these contradictions, it's worth documenting; carrier-count claims change fast enough that a benchmark like this has a shelf life measured in months, not years.