CarrierTool
Integrations

Customer EDI, LTL carrier APIs, load boards, and enterprise connectivity — built into the operating system.

CarrierTool connects customer systems, LTL networks, load marketplaces, accounting platforms, documents, and enterprise applications to the same transportation workflow instead of pushing operations into separate bolt-on tools.

Connectivity

Integration-native transportation operations.

CarrierTool is designed to be the integration hub for the transportation operation. Customer EDI, enterprise APIs, LTL carrier APIs, load boards, documents, accounting systems, and workflow events all feed the same Transportation OS rather than forcing users to operate a different product for every connection.

Customer EDI & Enterprise Data Exchange

CarrierTool includes native customer integration patterns for EDI and structured enterprise data exchange so orders, tenders, shipment updates, acknowledgments, invoices, and related transportation messages can move directly between CarrierTool and customer systems.

✓ Customer EDI
✓ Trading-partner mappings
✓ Order and tender intake
✓ Shipment status messages
✓ Invoice and acknowledgment flows
✓ API and webhook alternatives

LTL Carrier API Network

CarrierTool is plumbed for direct LTL carrier API connectivity. Carrier connections are activated with the applicable carrier account and API credentials so rating, service options, tendering, tracking, and shipment documentation can remain inside the CarrierTool workflow.

✓ LTL rating
✓ Service-level options
✓ Tender / booking
✓ Tracking and status
✓ BOL / label workflows
✓ Carrier credential activation

Load Board Connectivity

Post and source truckload freight from CarrierTool through supported load-board connections instead of re-keying the same load into separate marketplace screens.

✓ Multi-board posting
✓ Load updates
✓ Carrier sourcing
✓ Posting status
✓ Marketplace credentials
✓ Operational workflow integration

Secure APIs & Webhooks

Tenant-scoped APIs and event-driven integration allow customers and partners to securely exchange shipment, customer, carrier, document, billing, and reporting data with CarrierTool.

✓ Tenant API keys
✓ Permission-scoped access
✓ Import and export endpoints
✓ Webhooks
✓ Workflow events
✓ Audit history

Accounting & Financial Systems

Financial integration patterns support invoice export, customer synchronization, carrier settlements, payment status, and transportation financial reporting workflows.

✓ Invoice export
✓ Carrier payables
✓ Customer receivables
✓ Payment status
✓ Revenue and margin data
✓ Financial synchronization

Document & Evidence Automation

CarrierTool connects operational records directly to FreightIQ™ document and evidence workflows for PODs, BOLs, carrier packets, invoices, receipts, compliance records, and driver-submitted evidence.

✓ POD and BOL processing
✓ Evidence verification
✓ Carrier packets
✓ Billing packets
✓ Document matching
✓ Exception workflows
LTL Carrier Connectivity

Connect CarrierTool directly to major LTL networks.

The LTL integration layer is built into CarrierTool. Individual carrier connections are activated with the customer's applicable carrier account and API credentials. Major U.S. and North American LTL networks include:

FedEx Freight logo
Old Dominion Freight Line logo
Estes Express Lines logo
XPO logo
R+L Carriers logo
TForce Freight
Saia logo
ABF Freight
Central Transport logo
Southeastern Freight Lines logo

Carrier names and trademarks belong to their respective owners. Listing a carrier indicates CarrierTool integration capability / connectivity target and does not imply endorsement or partnership.

Load Board Connectivity

Post freight without leaving the operating workflow.

CarrierTool's load-board integration layer supports marketplace connectivity so brokers can post and update freight from the load itself using their marketplace accounts and credentials.

DAT One
Truckstop
123Loadboard
Trucker Path
Direct Freight

Marketplace names and trademarks belong to their respective owners. Availability of a specific connection depends on the marketplace account, API access, and credentials supplied for the tenant.