Entity

Carrier Profile

The master record of a carrier — authority credentials, insurance, equipment types, lane preferences, capacity, historical performance metrics, and tender acceptance patterns that define carrier capabilities.

Last updated: February 2026Data current as of: February 2026

Why This Object Matters for AI

AI carrier matching and performance prediction require a comprehensive carrier profile to score carriers against shipment requirements; tender optimization depends on knowing which carriers accept which loads.

Freight Operations & Transportation Management Capacity Profile

Typical CMC levels for freight operations & transportation management in Logistics organizations.

Formality
L2
Capture
L2
Structure
L2
Accessibility
L2
Maintenance
L2
Integration
L2

CMC Dimension Scenarios

What each CMC level looks like specifically for Carrier Profile. Baseline level is highlighted.

L0

Carrier knowledge lives in the freight broker's head. The ops manager knows which carriers are reliable on the Chicago-Dallas lane and which ones lose cargo, but none of this is written down. When a new dispatcher starts, they spend months learning which carriers to trust through trial and error.

None — AI cannot score, rank, or match carriers to shipments because no carrier profile record exists in any system.

Create a carrier database with at least the basics — SCAC code, MC number, insurance status, equipment types, and primary lanes served.

L1

A spreadsheet lists carriers by name with their MC numbers and phone contacts. Some entries have notes like 'good for reefer' or 'slow to pay claims,' but the information is inconsistent — some carriers have detailed performance notes, most just have a name and number. Insurance certificates are in a shared folder somewhere.

AI could read the carrier list to match names to loads, but cannot reliably score carrier fitness because profile fields are inconsistent and incomplete. Insurance and authority verification require manual lookups in FMCSA SAFER.

Implement a carrier management system with enforced fields — authority status, insurance expiration dates, equipment capabilities, lane preferences, and a standardized performance rating — for every active carrier.

L2Current Baseline

All active carriers have profiles in the TMS with standard fields — SCAC, MC number, insurance status and expiration, equipment types, hazmat certification, and primary lanes. Carrier reps update the profile when onboarding a new carrier. But performance metrics (on-time percentage, damage rate, tender acceptance) live in a separate report, not in the carrier profile itself.

AI can match carriers to shipments based on static qualifications (equipment, lanes, insurance) but cannot assess carrier quality because performance metrics aren't part of the searchable carrier profile. Carrier ranking requires manually cross-referencing two different systems.

Integrate historical shipment performance metrics — on-time delivery rate, damage claim rate, tender acceptance rate, and average transit time by lane — directly into the carrier profile record.

L3

Carrier profiles are comprehensive and connected — each profile links authority credentials, insurance records, equipment capabilities, lane coverage, and calculated performance metrics (on-time %, damage rate, tender acceptance rate by lane). A planner can query 'show me all reefer-certified carriers on the ATL-DAL lane with on-time delivery above 95%' and get a trustworthy ranked list.

AI can perform intelligent carrier matching — scoring carriers against shipment requirements using qualification, performance, and cost criteria. Automated tender waterfall strategies are reliable because carrier profiles reflect actual historical performance.

Add real-time carrier capacity and pricing signals to the profile — current truck availability, spot rate willingness, and load board presence — so the carrier profile reflects not just who the carrier is but what they can do right now.

L4

Carrier profiles are schema-driven entities with formal relationships to every relevant object — rate agreements, shipment history, compliance records, equipment manifests, and real-time capacity signals. Each data element carries its source and freshness timestamp. An AI agent can query 'what is Carrier X's current capacity on the DAL-CHI lane and their 90-day on-time record?' and receive a structured, verified answer.

AI can autonomously manage carrier relationships — selecting optimal carriers for each load, predicting tender acceptance probability, negotiating spot rates, and dynamically adjusting the carrier waterfall based on real-time market conditions.

Implement continuous carrier profile updates where performance metrics, capacity signals, and compliance status stream in real-time from carrier APIs, load boards, and regulatory databases without manual refresh cycles.

L5

Carrier profiles are living entities that auto-update continuously — every delivered shipment recalculates performance scores, every FMCSA inspection updates the safety record, every load board posting updates capacity availability, and every market transaction refreshes pricing signals. The carrier profile is a real-time digital twin of the carrier's current capabilities and performance.

Fully autonomous carrier management. AI agents evaluate, select, negotiate, and monitor carriers in real-time using continuously current profiles. The carrier profile is a living market intelligence feed, not a static reference record.

Ceiling of the CMC framework for this dimension.

Capabilities That Depend on Carrier Profile

Other Objects in Freight Operations & Transportation Management

Related business objects in the same function area.

Shipment Record

Entity

The core transactional record of a freight movement — origin, destination, pickup/delivery times, carrier, equipment type, commodity, weight, cube, and status milestones that define what moves where and when.

Route Plan

Entity

The planned path from origin to destination including waypoints, stops, estimated transit times, fuel stops, and rest breaks that guide driver execution and serve as baseline for deviation detection.

Rate Agreement

Entity

The contracted or quoted rate structure by lane, mode, and accessorial — base rates, fuel surcharges, accessorial schedules, and volume commitments that determine the cost of freight movements.

Load

Entity

The physical cargo configuration on a truck or container — what's loaded, how it's positioned, weight distribution, and fill percentage that determines capacity utilization and consolidation opportunity.

Delivery Appointment

Entity

The scheduled arrival window at a destination facility — dock door assignment, expected arrival time, loading/unloading duration, and detention rules that coordinate freight-facility handoffs.

Freight Invoice

Entity

The carrier's bill for transportation services — line items, rates, accessorials, fuel surcharges, and supporting documentation that must reconcile against shipment records and rate agreements.

Carbon Emission Record

Entity

The calculated CO2 emissions for a shipment or route — emissions by mode, distance, fuel type, and load factor that enable sustainability tracking and optimization decisions.

Lane

Entity

An origin-destination corridor that defines a repeating traffic pattern — geography, typical volumes, seasonal variations, and carrier coverage that structures network planning and rate negotiations.

What Can Your Organization Deploy?

Enter your context profile or request an assessment to see which capabilities your infrastructure supports.