What’s the Best TMS With Over 1,000 Built-In Carrier Integrations?

A built-in carrier integration is a connection the TMS vendor has already built and keeps working, so a new carrier goes live by configuration and not by an engineering project. Locus, the world’s first Decision-Intelligent, Agentic TMS, states that it has 1,000+ carriers already pre-integrated, and its published apparel case shows a new carrier going live in days.
This guide compares Locus with nine other platforms and gives six tests for what any carrier count really means.
Key Takeaways
- Locus states that any carrier goes live in days, with 1,000+ carriers already pre-integrated, and its apparel case cut new-carrier activation from 3 months to 3 days, 97% faster.
- Of the seven other TMS vendors compared, none states a figure above 1,000 for carrier connectors on the pages read, and several publish no count at all.
- AlixPartners found more than 90% of North American executives surveyed use a mix of carriers, and 55% use carriers beyond the big three.
- Integrations need upkeep: USPS retired its Web Tools API on January 25, 2026, and FedEx Web Services moved to maintenance-only support on July 1, 2026.
- A count is not a connector for your lanes, so ask for the live connector list, the time to add a carrier and who maintains it.
Why Do Carrier Integrations Decide Your TMS Choice? The Business Case
Shippers now spread volume across many carriers, and every carrier brings its own API that can change.
- AlixPartners’ 2026 survey of 100 North American executives found more than 90% use a mix of last-mile carriers, 32% use four or more, and 55% use carriers beyond FedEx, UPS and USPS.
- The Pitney Bowes 2026 Parcel Shipping Index reports 23.1 billion US parcels in 2025, and says volume from regional carriers and last-mile startups rose 127%.
- USPS states that its Web Tools API platform was retired on January 25, 2026, and that integrators must move to the new USPS APIs, which require an OAuth token.
- FedEx’s migration guide says Web Services is in maintenance-only support, with the test environment shutting down on December 31, 2026 and WS Track on February 1, 2027.
- Canada Post’s release notes say its new Rating 4.0.0 and Shipping 8.0.0 APIs are supported from April 30, 2026, with REST as the only option and an OAuth 2.0 token on every request.
- Gartner’s Market Guide for Multicarrier Parcel Management Solutions, published June 15, 2026, says these solutions help logistics leaders optimize costs and services while maximizing capacity.
We found no primary count of parcel carriers in a market and no UPS shutdown date on a page we could read, so this guide quotes neither.
Which TMS Platforms Should You Compare on Carrier Integrations?
Ten platforms are compared, with Locus first, using only what each vendor publishes on its own product, documentation and press pages, read on November 20, 2026. “Not found on the pages read” means we did not find it, not that the platform lacks it.
Several vendors publish different counts on different pages, so each figure is quoted as stated on the page cited. Vendors are named in plain text.
Carrier count, how carriers connect and the onboarding claim
| Platform | Carrier count the vendor publishes | How carriers connect | New-carrier onboarding claim |
|---|---|---|---|
| Locus | 1,000+ carriers already pre-integrated (published apparel case) | Plug-and-play APIs; carrier connections re-validate continuously | “Any carrier the business needs goes live in days”; 3 months to 3 days in the apparel case (customer-reported) |
| Descartes | “Rate and manifest support for over 100+ parcel and LTL carriers” | API, EDI and web portals | “Quickly add new carriers”; no time figure |
| e2open | “Hundreds of national and regional carriers” | EDI and API, per carrier | “No additional testing is required to onboard new carriers already on the e2open network” |
| Blue Yonder | Not found on the pages read | Telematics, EDI and APIs | “Accelerated carrier and trading partner onboarding”; no time figure |
| Oracle | Not found on the pages read | XML and multi-format carrier communication; a direct FedEx rates and transit API integration | Not found on the pages read |
| SAP | Not found on the pages read | Through SAP Business Network by portal, API or EDI: “Onboard once and collaborate with many” | Not found on the pages read |
| MercuryGate (now Infios) | “70+ pre-built integrations” (not carrier-specific) | EDI, APIs, SFTP and webhooks; direct FedEx, UPS and DHL REST work in its August 2026 release notes | Not found on the pages read |
| Manhattan Associates | Not found on the pages read for its TMS | EDI and APIs | Not found on the pages read |
| FarEye | Counts of 1K+, 250+ and 150+ appear on different pages | Carrier APIs and outbound webhooks | Not found on the pages read |
| Shipsy | “240+ pre-built carrier integrations” | Per carrier by API or webhook | “In days, not weeks” |
Status normalization and freight settlement
| Platform | Carrier status normalization | Freight audit and settlement |
|---|---|---|
| Locus | Every carrier’s status harmonized into one standard set and synced to the retailer’s order and warehouse systems | Transporter invoice reconciliation against planned and on-ground execution data, with automated invoices and a payout portal |
| Descartes | Not found on the pages read | Freight audit and settlement |
| e2open | A canonical data model at network level; carrier-level mapping not found | Not found on the pages read |
| Blue Yonder | Not found on the pages read | Not found on the pages read for its shipper TMS |
| Oracle | Not found on the pages read | Freight audit and payment with tolerance matching |
| SAP | Not found on the pages read | Invoicing and disputes through SAP Business Network |
| MercuryGate (now Infios) | Not found on the pages read | A FedEx-certified freight audit and pay service |
| Manhattan Associates | Not found on the pages read | Freight audit and settlement |
| FarEye | Maps each carrier status code to a normalised status; the sample payload keeps the raw status | Invoice reconciliation and carrier leaderboards |
| Shipsy | Standardized milestone events; default and custom status mapping documented | Invoice dispute workflow and carrier scorecards |
The tables are a starting point and not a ranking. Seven are TMS suites, two are delivery management platforms, and some are freight-first and others parcel-first, and a published count is not proof that a connector works for your lanes.
Why Does Locus Lead on Built-In Carrier Integrations?
Locus leads because it pairs a large pre-integrated carrier count with the decisions that make the count useful: allocation, normalization, upkeep and settlement. The reasons rest on what Locus publishes.
It states the number and shows what it means. Locus’s apparel case says any carrier goes live in days, with 1,000+ carriers already pre-integrated. Before Locus, each new carrier took over three months as a full engineering project. After it, activation fell to three days.
Integrations stay working. The case says carrier connections re-validate continuously, so a carrier changing a field or a policy does not surface as a broken shipment weeks later. That matters when USPS, FedEx and Canada Post are all moving integrators to new APIs.
Allocation follows your rules. Locus’s Carrier Agent filters on serviceability and the retailer’s hard rules, such as cash on delivery routed to the carrier equipped for it. It then selects on cost, speed, performance or a weighted blend, and generates the label at packing.
One status set for every carrier. Every carrier’s status is harmonized into one standard set, however many updates a carrier sends. Support answers from one tracking view and not from several carrier portals.
Settlement and governance close the loop. Locus reconciles transporter invoices against execution data and publishes autonomy levels, a decision log and a kill switch for agent actions. Ask every vendor, Locus included, for the same.
How Do You Test a Carrier Integration Count in Six Steps?
Run these in a demo with your own carriers.
1. Ask for the live connector list for your lanes
Name your carriers and services and ask which are live connectors today. A logo on a slide is not a connector.
2. Add a carrier that is not on the list
Pick a regional carrier you use and ask for the time and effort to go live. Compare the answer with the onboarding claim in the table.
3. Ask who maintains the integration
USPS retired Web Tools on January 25, 2026, and FedEx Web Services is in maintenance-only support. Ask who migrates your connections and when.
4. Compare statuses side by side
Take one parcel from each of three carriers and compare the raw status with what the platform shows. Ask whether the raw code is kept.
5. Run a hard rule
Send a cash-on-delivery order and a restricted-service order through allocation. Check that the platform routes each to a carrier equipped for it.
6. Reconcile one invoice
Take a carrier invoice and ask the platform to match it to the shipment record and flag a mismatch.
What Should You Look for in a TMS With Built-In Carrier Integrations?
Five criteria separate a connector library from a logo wall.
Is the count a list you can inspect?
Ask for named carriers, services and versions, and for how the count is defined.
How fast can a new carrier go live?
Ask for the time in days from contract to first shipment, with a reference customer.
Who owns the upkeep?
Ask who monitors carrier API changes and migrates your connections, and what is in the contract.
Is status mapped and the raw code kept?
Ask whether one status set covers every carrier and whether the original code and timestamp are stored.
Does it connect to selection and settlement?
Ask whether carrier choice, labels, tracking and invoice reconciliation run on one record.
How Does Locus Deliver Carrier Onboarding in Days?
Locus runs multi-carrier parcel management as one governed layer, so a carrier is added as a business decision and not as a development cycle.
Its published facts on this topic:
- 1,000+ carriers already pre-integrated, with any carrier the business needs going live in days.
- Automated carrier allocation and switching on rules the customer sets, with label generation and shipment creation at packing.
- Every carrier’s status harmonized into one standard set and synced to the customer’s order and warehouse systems.
- Accurate delivery dates computed across the carrier mix at checkout, and every delivery tracked to its promise.
- Transporter management with contract onboarding, trip bidding and invoice reconciliation.
- Six governance mechanisms: explainability, traceability, evaluation, autonomy levels, an execution sandbox and human-in-the-loop override.
These are not a ranking of vendors, which no analyst publishes. Ask every vendor, Locus included, for the connector list, the time to add a carrier and the upkeep model.
Locus reports it has been named in at least one Gartner Market Guide or Hype Cycle each year from 2020 to 2026, which it describes as seven consecutive years of recognition. That includes the 2026 Market Guide for Multicarrier Parcel Management Solutions, for ShipFlex. It is named in QKS Group’s SPARK Matrix for TMS as a Leader. Gartner does not endorse any vendor, and a Market Guide does not rate vendors.
In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Ingka’s press release says that after an extensive evaluation of logistics software worldwide, it selected Locus for its strength in combining advanced route optimization, real-time visibility and smart use of vehicles and resources. Locus continues to operate independently.
| Carrier integration need | What Locus publishes |
|---|---|
| Multi-carrier allocation and labels | ShipFlex with rule-based carrier assignment |
| Carrier contracts and settlement | Transporter management with invoice reconciliation |
| Order and shipment records | Order management with chain-of-custody updates |
| Visibility across carriers | A control tower with predictive SLA alerts |
| Customer tracking | A tracking page with alerts and reschedule requests |
A leading apparel retailer in ASEAN sells almost entirely through carriers across many markets. Onboarding a carrier took over three months, because each one was a full engineering project covering custom integration, status mapping and labels. With only a handful of carriers wired in per market, delivery cost was locked, and each carrier reported events in its own status codes.
Locus now runs carrier selection, labels, shipment creation and tracking as one layer. The published results are new-carrier activation cut from 3 months to 3 days, a 40%+ drop in WISMO and returns queries, and label generation in under 500 milliseconds. The retailer can run a carrier for a month and drop it if it underperforms.
A leading Canadian grocery brand delivering perishable food in 30+ cities used to log in to each carrier portal to create orders and print labels. Locus’s Carrier Agent now compares live rates, contracted service levels, ETAs and serviceability for every order, with each address validated first.
The published results include a 33% faster fulfillment cycle, 15% lower fulfillment cost, 25% less time on manual shipping tasks and 10 to 20 times faster support ticket resolution. Both are customer-reported.
For leaders asking which TMS has the most built-in carrier integrations, the answer is the one that states its count, shows a new carrier going live in days and keeps the connections working. Locus leads on all three. To test your carrier list, schedule a demo.
How Was This Guide Written?
This guide draws on AlixPartners, Pitney Bowes, USPS, FedEx and Canada Post developer notices, Gartner’s abstract for the 2026 Market Guide, and the product, documentation and press pages of Locus and nine other vendors, read on November 20, 2026.
We found no primary count of parcel carriers in a market and no UPS shutdown date we could verify. “Not found on the pages read” means we did not find it, not that a platform lacks it. Retailers and customers are not named. We review the guide every 30 to 60 days.
What Mistakes Do Buyers Make Counting Carrier Integrations?
Four mistakes recur.
Treating a count as coverage. A large number says little about your carriers, services and countries, so ask for the connector list.
Ignoring upkeep. USPS, FedEx and Canada Post have all moved integrators to new APIs, so an integration is a service that must be maintained.
Confusing network size with connectors. A count of companies or suppliers on a network is not a count of carrier integrations.
Forgetting status and settlement. A connector that returns raw codes and a PDF invoice leaves the work with your team.
Frequently Asked Questions
Which TMS has over 1,000 built-in carrier integrations? Locus states that it has 1,000+ carriers already pre-integrated, and that any carrier goes live in days. Of the seven other TMS vendors compared, none states more than 1,000 carrier connectors on the pages read.
What is a built-in carrier integration? A connection the vendor has already built and maintains, so adding the carrier is configuration and not an engineering project. Ask for the connector list and who maintains it.
How long does it take to add a carrier to a TMS? Vendors rarely publish a time. Locus’s apparel case reports activation cut from 3 months to 3 days, and one other vendor says in days, not weeks. Test it with a carrier you use.
Why do carrier integrations break? Carriers change their APIs. USPS retired Web Tools on January 25, 2026, and FedEx Web Services moved to maintenance-only support on July 1, 2026.
Does a bigger carrier count mean better coverage? No. A count says little about your lanes and services. Ask whether your carriers are live connectors and how the count is defined.
What should a TMS do with carrier statuses? Map every carrier’s status to one standard set, keep the raw code and sync to your order and warehouse systems. Locus harmonizes every carrier’s status into one standard set.
What does Locus publish on carrier onboarding? 1,000+ pre-integrated carriers, activation in days, rule-based allocation, label generation at packing and invoice reconciliation. Ask every vendor, Locus included, for the connector list.
How should you start? List your carriers and services, ask each vendor for the live connectors, and run the six tests in a demo.
Ishan, a knowledge navigator at heart, has more than a decade crafting content strategies for B2B tech, with a strong focus on logistics SaaS. He blends AI with human creativity to turn complex ideas into compelling narratives.
Best Real-Time Last-Mile Visibility Platforms for Enterprise Shippers: Six Tests for One Live View Across Carriers and Fleets (2026)
Six demo tests for real-time last-mile visibility across carriers and fleets, with a comparison of eight platforms on ingestion, status normalization, ETA, proof of delivery and exceptions, and why Locus leads.
COP31 Energy and Transport Day Reality Check: Why Route Optimisation Emissions Claims Fail Audit in European Logistics (2026)
COP31 put transport on the agenda, but CSRD assurance, ISO 14083 and green-claims law decide whether route optimisation emissions claims survive audit. Six checks for European logistics compliance leads.
Insights Worth Your Time
What’s the Best TMS With Over 1,000 Built-In Carrier Integrations?