HaulCortex isn't a generic logistics dashboard. Every module is designed around the specific workflows of a 3PL or freight broker running 50–500 loads per day on spot and contract lanes.
Five distinct processing stages, each auditable and configurable for your operation.
New loads enter via webhook from your TMS or EDI 204 message. Origin, destination, commodity, weight, and required equipment type are parsed in under 3 seconds.
The routing model evaluates 18 months of historical performance for that lane pair, current spot rates from DAT, and seasonal demand curves to calculate a margin probability score.
The carrier model cross-references your active network against FMCSA location data, ELD pings (where available via API), and historical acceptance rates per lane to rank the top 5 matches.
Your dispatcher sees the ranked list inside their existing TMS UI (via embedded widget) or in the HaulCortex web interface. One click initiates outreach with pre-filled rate and load details.
The lane model ingests your historical load data as a CSV export from your TMS and retrains on a nightly batch cycle. It learns your carrier relationships, your typical rate acceptance windows, and which lanes are chronically unprofitable before you realize it in month-end accounting.
The model outputs a carrier score between 0 and 100 for each active carrier on a given lane. Carriers above 70 get immediate outreach priority. Below 40 triggers a flag for your carrier relations team to investigate the relationship.
Aggregates real-time capacity signals from multiple sources: FMCSA active authority data, ELD last-ping locations (via MyCarrierTMS and Macropoint integrations), and carrier-reported available equipment from your broker portal.
The match algorithm weights proximity, lane history, equipment type availability, and your customizable carrier tiers. Carriers can be pinned to preferred status on specific lanes or flagged as do-not-use without requiring TMS configuration changes.
Integrates with DAT One and Truckstop API to pull current spot rate indices for each lane before outreach begins. The system calculates your rate position as a percentage above or below market and surfaces it in the dispatcher UI.
If a carrier quotes $2.85/mile on a lane where the current DAT average is $2.40/mile, the system flags the 18.8% premium automatically — no manual spreadsheet lookup required.
Runs nightly checks against FMCSA Safety Measurement System (SMS) data, insurance certificate expiration dates from RMIS or Carrier411, and authority status changes. Any carrier with a compliance event triggers an alert to your compliance coordinator.
Covers conditional rating changes, out-of-service orders, cargo insurance lapses, and authority revocations — before you tender them a load that creates liability exposure.
HaulCortex connects to your TMS via REST API or file-based EDI. Current certified integrations: McLeod PowerBroker (SOAP API), Turvo (REST), AscendTMS (REST), and 3Gtms. For custom TMS platforms, we provide a Python SDK with load event hooks and a webhook endpoint.
The integration layer runs as a sidecar service in your cloud environment (AWS/Azure) or in HaulCortex-managed infrastructure. Average TMS integration deployment: 3–5 business days.
Aggregates load-level P&L data from your TMS into a unified margin view by lane, by carrier, by dispatcher, and by customer. The dashboard calculates effective margin per mile including fuel surcharge, accessorials, and driver pay (where available via payroll feed).
Weekly digest emails surface the five best-performing lanes and five worst-performing lanes in your portfolio. Recommended rate floor adjustments are generated automatically based on 30-day rolling cost data.
Monitors active loads for deviation events: carrier goes dark on ELD for more than 4 hours, pickup arrival is 90+ minutes late, or delivery appointment is at risk based on current position. Exception alerts fire to the responsible dispatcher and optionally to the shipper's load tracking portal.
Alert thresholds are configurable per customer tier. High-priority shippers can receive sub-30-minute exception notifications; spot shippers get daily status summaries.
| Carrier score calculation | < 2.3 seconds per load |
| API response time (p95) | 47ms |
| Max concurrent loads processed | 1,200 / hour |
| Model retraining cycle | Nightly at 02:00 local |
| Historical data window | 18 months rolling |
| Data encryption (at rest) | AES-256 |
| Data encryption (in transit) | TLS 1.3 |
| Certifications | SOC 2 Type II (in progress) |
| Data residency | US-East, US-West |
| API authentication | OAuth 2.0 + API key |
Send us 90 days of load data. We run the analysis and return a lane-by-lane optimization report in 48 hours — at no cost.