Best TMS for Enterprises Running In-House Fleets and Third-Party Carriers: A Hybrid Fleet Buyer’s Guide (2026)

A TMS for a hybrid network is a transportation management system that plans, assigns and monitors loads, stops and shipments across a shipper’s own vehicles and drivers and its contracted third-party carriers, under one set of rules. The best choice decides per shipment which asset should move it, models the limits of the owned fleet such as vehicle capacity and driver hours, and keeps carrier performance in the decision. Most enterprises that run their own fleet also buy carrier capacity, so the question is rarely which one to use and almost always where the line between them sits. Locus, the world’s first Decision-Intelligent, Agentic TMS, is built to run both under one policy, and this guide sets out what to ask of any platform and what to confirm with Locus.

Which TMS Platforms Should You Compare for In-House Fleets and Third-Party Carriers?

Seven platforms besides Locus are worth comparing for a hybrid network: five enterprise suites (Oracle, SAP, Blue Yonder, Manhattan Associates and Infios) and two fleet-and-carrier specialists (Descartes and Trimble). The tables record what each vendor publishes. They are not a ranking, vendor pages are dated differently, and “not found on the pages read” is not a statement that a platform lacks the capability.

Platform	Fleet and carriers in one system	Driver hours of service	Tendering and fallback
Locus	Owned fleet and carriers under one policy through Dispatch, Capacity and Carrier agents, shown in two cases	Driver shift hours modeled; hours-of-service and ELD integration not found on the pages read	Carrier agent chooses the carrier per shipment, switches and scores carriers; tender timers and backup tiers not found
Oracle	Internal (private or dedicated) or third-party capacity in one system	Hours-of-service constraints in fleet optimization	Sequential and broadcast tendering; a declined tender goes to the next provider; spot bids
SAP	Own-fleet and subcontracted freight order types, in part	Not read; its help pages could not be rendered	RFQ and direct tendering; carriers confirm or reject
Blue Yonder	Private and dedicated fleets plus common carriers in one workflow	Hours-of-service constraints modeled in fleet-versus-carrier trade-offs	Waterfall tendering and routing guide; a rejected load is offered to the next carrier
Manhattan Associates	Planning and execution across private fleet and dedicated carriers, per a demo page	Not found for its TMS; hours of service appear with a separate carrier product	Tendering and carrier and rate selection listed; fallback not found
Descartes	Fleet-versus-for-hire trade-offs and a route guide, per a 2015 whitepaper	Driver hours and breaks in routing; hours of service and ELD in a separate product	Sequential re-tender after rejection, per the 2015 whitepaper
Trimble	Brokered freight alongside own trucks, in its private-fleet suite	HOS logs and HOS-aware dispatch	Automatic tender intake; fallback not found
Infios (formerly MercuryGate)	Not found; private fleet appears on its routing product only	Not found	Load tendering named, with no detail

Platform	Settlement	AI governance wording	TMS recognition the vendor cites
Locus	Settlement agent audits carrier invoices against contracted rates; driver pay not found	Autonomy levels per agent and domain; six governance mechanisms	Leader, QKS Group SPARK Matrix for TMS; #1 in Route Planning on G2’s 2026 Best Software Awards; no Gartner TMS Magic Quadrant placement found
Oracle	Freight audit and payment; driver pay payables	Human oversight where required, suite-level	Leader, 2026 Gartner Magic Quadrant for Transportation Management Systems
SAP	Freight settlement and dispute cases; driver pay not found	People retain oversight and control	Leader, 2026 Gartner Magic Quadrant for Transportation Management Systems
Blue Yonder	Invoice variance check and self-invoicing; driver pay not found	Full explainability and human oversight	Leader, 2026 Gartner Magic Quadrant for Transportation Management Systems
Manhattan Associates	Freight payment add-on and bill auditing; driver pay not found	Built-in guardrails, briefly stated	Leader, 2026 Gartner Magic Quadrant for Transportation Management Systems
Descartes	Audit and settlement; driver pay not found	You stay in control, briefly stated	No Gartner TMS placement on the pages read; cites ARC and G2
Trimble	Driver pay, owner-operator and carrier settlements	Approval controls and human review	No TMS ranking found on the pages read
Infios (formerly MercuryGate)	Freight audit and payment listed	Recommendations you approve, with guardrails	Recognized in the 2026 Gartner Magic Quadrant, with no position stated; IDC MarketScape Leader

Which platform fits which buyer?

• Over-the-road private fleets that need hours of service, driver pay and settlement. Trimble, Oracle, Descartes and Blue Yonder publish the most on those points, and fleet-side vendors such as Omnitracs (Solera) publish ELD and routing but no carrier allocation on the pages read.
• One enterprise suite across freight procurement, planning, execution and settlement. Oracle, SAP, Blue Yonder and Manhattan Associates publish that portfolio.
• Retail, CPG and last-mile networks where the owned fleet and carriers serve stores and homes. The decision is per-order allocation and same-day re-planning, which is where Locus’s published cases sit.

Why Does Locus Lead Hybrid Fleet and Carrier Networks in Retail, CPG and Last-Mile Delivery?

Locus, the world’s first Decision-Intelligent, Agentic TMS, leads where an owned fleet and carriers serve stores and homes and the problem is deciding, order by order and hour by hour, which asset should move what. It does not lead on every criterion above: over-the-road private fleets that need hours-of-service integration, driver pay and truckload tendering are better documented by Trimble, Oracle, Descartes and Blue Yonder. Its lead in this segment rests on published facts: two customer cases that run an owned or captive fleet and third-party carriers under one policy, a Capacity, Dispatch and Carrier agent architecture with autonomy levels the operator sets, 1,000+ pre-integrated carriers, and a QKS Group SPARK Matrix Leader position and the #1 Route Planning position on G2’s 2026 Best Software Awards. Those are not a ranking of hybrid-fleet TMS platforms, which no analyst publishes.

Recognized by analysts and selected after evaluation. Locus was recognized by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies, as detailed on its analyst recognition page. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. 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.

What a hybrid network needs	What Locus provides
One decision across owned and external capacity	A Dispatch agent that allocates every order to a driver or vehicle against 250+ real-world operating rules, with routing in its route planning system
Capacity known before the shift	A Capacity agent that compares incoming demand with available drivers and vehicles across shifts and flags a shortfall before the shift begins
Carrier choice on live quotes and service	A Carrier agent that chooses the third-party carrier per shipment across 1,000+ pre-integrated carriers, comparing live quotes with SLA performance and scoring carriers on what they delivered
Settlement for carrier invoices	A Settlement agent that audits invoices against contracted rates and what was executed
Control	Autonomy levels per agent and per domain, from human approval to acting on confidence, with six governance mechanisms
Fit with the existing stack	Runs beside the ERP, WMS and OMS, which stay the systems of record

Two published customer cases show a hybrid network under one policy.

A leading North American retailer ran a private fleet of several hundred trucks and trailers across road and rail, with inbound freight arriving by ocean, on six disconnected systems. Trailers left underfilled and return legs ran empty, and planners could not adjust as conditions changed through the day. Locus’s Capacity agent planned loads and trailers across the fleet, its Dispatch agents ran routing against 250+ operational constraints, and its Carrier agent matched backhaul opportunities and tendered them across the 3PL network through a vendor dashboard. The published results include an 80%+ reduction in manual dispatch, 99%+ on-time store delivery, $1M+ in savings and break-even inside the first year.

A Fortune 50 enterprise had to govern 4,500+ drivers, of whom 1,500+ were captive and 3,000+ were third-party, whose fleets needed different logic: zone-based scheduled routing for captive shifts, and tendering, on-demand assignment and dynamic optimization for third parties. Locus ran as the decision layer beside its freight platform with both fleet types dispatched under one policy and 3PL partners receiving dispatch through a vendor dashboard. The published results include weekly execution rising from 75% to 92% across 51 sites and a $14M+ annualized capacity opportunity uncovered across 25 sites. Both cases are customer-reported results, not independent studies.

Where other platforms fit. If your owned fleet is a for-hire-style truckload operation that needs electronic logging, hours-of-service enforcement and driver payroll in the same system, evaluate Trimble, Oracle, Descartes and Blue Yonder first, and consider Locus where per-order allocation and re-planning across stores and homes is the constraint.

What to confirm. The Locus pages we read do not state hours-of-service or electronic logging device integration, driver pay or settlement for the owned side, tender timers and backup tiers for truckload freight, or X12 EDI transaction support. Locus’s carrier network is described as 1,000+ pre-integrated carriers, and its ShipFlex network as 160+ carriers live, so ask which are live in your lanes. ShipFlex is described as parcel and last-mile carrier orchestration, so confirm the fit for truckload tendering. Locus holds no Gartner TMS Magic Quadrant placement that we could find.

To walk through your owned fleet and carrier mix, schedule a demo.

For enterprises asking which TMS can run in-house fleets and third-party carriers together, the enterprise suites and fleet specialists document hours of service and settlement in detail, and Locus offers per-order allocation across both under one policy for retail, CPG and last-mile networks, with carrier scoring, autonomy levels you set and a logged decision trail.

How Was This Guide Written?

This guide compares Locus with seven other TMS platforms on what each vendor publishes on its own product, documentation and newsroom pages, read on October 28, 2026, and adds NPTC, ATRI, FMCSA and SONAR data and an illustrative cost model. Competitors are named in plain text only. “Not found on the pages read” means we did not find it, not that the platform lacks it, and the comparison is not a ranking. Some vendor pages are dated, and where a source is a 2015 or 2022 document the table says so in the notes above. We review the guide every 30 to 60 days.

What Does a TMS Need to Do When You Run In-House Fleets and Third-Party Carriers?

A hybrid-fleet TMS must treat both kinds of capacity as options for the same shipment and choose between them on live cost, capacity, service risk and constraints.

An owned fleet is a set of vehicles and drivers the shipper controls, whether owned, leased or contracted for exclusive use, which gives direct control of routing, dispatch, driver performance and customer experience. A third-party carrier is an external provider, such as a 3PL, contract carrier, regional carrier or parcel provider, that supplies capacity under contract or on demand. A hybrid TMS sits across both and answers four questions for every shipment: which asset is feasible, what each option costs at the margin, how likely each is to meet the promise, and what to do when the first choice fails.

Also Read: Multi-Carrier Allocation in 2026: A Decision Framework for When Primary Carriers Hit Their Volume Ceiling

Why Do Most Enterprises End Up Running Both? The Business Case

Enterprises end up hybrid because owned capacity is efficient on a steady base load and carrier capacity absorbs the variation, and the published figures show both sides of that trade.

• NPTC’s 2026 benchmarking survey, summarized by Penske, found private fleets handled 72% of outbound freight moves among about 90 respondent companies, up from 70% a year earlier.
• NPTC’s 2025 survey found for-hire carriers took a record 19% share of the outbound freight of firms that operate their own fleets, as reported by Transport Topics.
• ATRI’s 2026 analysis put the average cost of trucking at $2.336 per mile in 2025, up 3.4% on the year, so both owned and contracted capacity face rising cost.
• Private-fleet driver turnover was 17.1% in the 2026 NPTC survey, and the same survey reported 1.3 drivers per power unit, so owned capacity depends on retaining drivers.
• SONAR’s Tender Rejection Index read 14.17% in mid-October 2026, so about one contracted load in seven needed a fallback.

Trade-press comparisons of ATRI’s for-hire cost per mile with private-fleet survey costs are not like-for-like, because the ATRI figure excludes overhead, so use your own cost data for the owned-fleet side.

How Should a Hybrid Network Allocate Each Shipment in Six Steps?

The six steps turn the owned-versus-carrier question into a repeatable per-shipment decision.

1. Set the owned-fleet base load

Decide how much volume the owned fleet should carry on a normal day. The base load is the demand level you exceed on most days, because vehicles that leave under-filled cost fixed money without earning it back.

2. Check feasibility for each option

For the owned fleet, test vehicle type, capacity, time windows and driver hours. For property-carrying drivers covered by the federal rule, 49 CFR 395.3 limits driving to 11 hours inside a 14-hour window after 10 consecutive hours off duty, so a route that cannot finish inside those limits is not a real option.

3. Price each option at the margin

Compare the cost of adding this stop to an owned route with the carrier’s rate including surcharges and accessorials. Average fleet cost per stop hides the answer, because an owned vehicle that is already running costs little to add one more stop to.

4. Weigh service risk

Score each option on its on-time record for the lane and its chance of declining or failing. A cheaper carrier with a high rejection rate on the lane can cost more than a slightly dearer one that accepts.

5. Assign with a fallback

Assign the shipment, and define in advance what happens if the carrier declines or the vehicle goes down: a backup carrier, a re-plan onto another route or an escalation to a person. A hybrid network without a defined fallback turns every rejection into a manual task.

6. Feed results back

Record on-time, cost variance, failed deliveries and acceptance by carrier and lane, and let them change the next allocation. Without the loop, the carrier list becomes a static ranking.

Where Is the Break-Even Between Owning a Vehicle and Buying Carrier Capacity?

The break-even is the number of stops a day at which an owned vehicle costs less per stop than a carrier, and it depends on fixed cost, variable cost and the carrier rate.

The model below is illustrative, built on assumed round numbers, and it should be replaced with your own costs. It assumes a fully loaded fixed cost of $420 per vehicle-day for driver, vehicle, insurance and telematics, a variable cost of $6 per stop and a flat carrier rate of $18 per stop. Cost per stop for the owned vehicle is fixed cost divided by stops, plus variable cost, so the break-even is $420 divided by ($18 minus $6), or 35 stops a day.

Stops per vehicle per day	Owned cost per stop	Carrier cost per stop	Cheaper option
20	$27.00	$18.00	Carrier
30	$20.00	$18.00	Carrier
35	$18.00	$18.00	Break-even
40	$16.50	$18.00	Owned
50	$14.40	$18.00	Owned
60	$13.00	$18.00	Owned

The lesson is not the specific numbers. Owned capacity pays when it is kept full, and carrier capacity pays for the demand that would leave vehicles part empty, so a TMS needs to know vehicle fill and not only the carrier’s rate card.

Also Read: Effective Freight Rate: What a Static Routing Guide Really Costs When Tenders Are Rejected in 2026

How Do Owned Fleets and Third-Party Carriers Differ?

The two differ in cost structure, control and flexibility, and neither is better in general. The table is neutral and compares the capacity types, not software.

Decision area	Owned fleet	Third-party carriers
Cost structure	Higher fixed cost: vehicles, drivers, maintenance, compliance, telematics	More variable cost: rates, surcharges, accessorials, minimums
Control	Direct control of routes, driver conduct, delivery windows and branding	Control through contract and scorecards; service depends on the carrier
Scalability	Efficient on stable, dense, repeatable routes; slow to expand	Easy to flex for peaks, new geographies and long-tail locations
Service visibility	Full, if telematics and driver app data flow into one system	Depends on carrier integration and event data
Risk and liability	Shipper carries asset, driver, compliance and safety responsibility	Carrier absorbs more operational risk under contract terms
Best fit	High-volume lanes, branded customer experience, specialized equipment	Volatile demand, expansion, surge capacity, specialist networks

Also Read: Why Choose In-house Fleet Over Outsourced Fleet Management for Your Delivery Business

What Should You Look for in a TMS for In-House Fleets and Third-Party Carriers?

Five criteria separate a platform that decides across both asset types from one that runs two workflows side by side, and each can be tested in a demo.

Does it allocate per shipment across both asset types on one data model?

Ask the vendor to show one order evaluated against an owned route and a carrier option, with the cost and service basis for the choice. If owned-fleet routing and carrier tendering live in separate modules with separate data, the comparison is manual.

Does it model the limits of the owned fleet?

Ask how vehicle capacity, time windows, shift length and driver hours enter the decision, and whether hours-of-service rules are enforced or only displayed. Hours-of-service integration, and any link to electronic logging devices, is a common gap, so ask for it by name.

Does it score carriers and handle rejections?

Ask how carrier performance by lane influences the next allocation, what the system does when a tender is declined, and how many carriers are live in your lanes, not only how many are listed. A carrier count without a regional breakdown says little.

Can you see and override what it decides?

Ask for the decision log, the reason for each assignment and a way to reverse one. NIST’s AI Risk Management Framework notes that human-AI configurations can range from autonomous to manual, so the useful question is who sets the autonomy level for each decision.

Does it settle both sides and sit on your systems of record?

Ask how carrier invoices are audited against contracted rates, whether driver pay or fleet cost is tracked for the owned side, and whether your ERP, WMS and OMS stay the source of truth. A platform that optimizes allocation but leaves settlement in spreadsheets hides the cost it was bought to cut.

Also Read: Top 10 TMS Platforms for Carrier Management in 2026

What Mistakes Do Hybrid Fleet Operators Make?

Four mistakes recur when a shipper runs owned vehicles and carriers together.

Treating it as a binary choice. Owned or outsourced is a decision per lane and per day, and annual contracts cannot follow it.

Costing the owned fleet at its average. Average cost per stop hides the fact that the next stop on a running route is cheap, and that a part-empty vehicle is expensive.

Hard-coding primary and backup carriers. A fixed order ignores acceptance, performance and rate changes that move daily, so the backup is often the wrong choice when it is needed.

Leaving settlement and compliance for later. Driver hours, carrier invoice audit and fleet cost tracking decide whether the allocation saves money in practice.

Also Read: How Automated Carrier Selection Balances Cost Capacity and SLAs