How to Build Trucking and Freight Management Software

A freight broker dispatching 50 loads per day must verify that every carrier has active FMCSA operating authority and valid insurance before assigning them a load. A broker who dispatches a load to a carrier with revoked authority is liable for any cargo loss or accident. The FMCSA SAFER database is public, but checking it manually for 50 carriers per day isn't a process. It's an accident waiting to happen. Trucking and freight management software automates that check and every workflow surrounding it, from load creation to carrier payout.

What trucking and freight management software does

Freight management software coordinates the full lifecycle of a load, from shipper request to carrier settlement.

The American Trucking Associations' 2023 Trucking Activity Report shows the trucking industry generated $940 billion in revenue in 2022 and moves roughly 72% of all freight in the United States by tonnage. The operational complexity of managing that volume -- thousands of loads, hundreds of carriers, multiple compliance requirements -- is exactly what purpose-built TMS software exists to solve.

Load board management covers load creation with origin, destination, commodity, weight, mileage, and rate. Each load moves through a status state machine: available, assigned, in transit, delivered, billed, paid, with timestamps at every transition. Carrier database management stores carrier records with MC number, DOT number, legal name, insurance expiry date, authority status pulled from FMCSA, and a carrier packet completion flag. Carrier assignment and rate confirmation generates a PDF rate confirmation from the load record and sends it to the carrier for digital signature before pickup.

Document management handles five document types per load: rate confirmation, Bill of Lading (BOL), proof of delivery (POD), carrier invoice, and carrier onboarding packet. Driver and truck dispatch tracks the assigned driver and truck for each load with GPS position updates during transit. Freight billing calculates the shipper invoice from line-haul rate, fuel surcharge (calculated from the current DOE weekly diesel average), and accessorial charges. Driver and carrier pay settlement handles per-mile, per-load, or percentage-based pay calculations. A load status customer portal lets shippers check their load status without calling the dispatcher. Revenue and lane analytics show load volume, revenue, and margin by lane, carrier, and time period.

MVP vs. full platform

An MVP covers the core brokerage workflow. You need load management, carrier database with FMCSA verification, load assignment with rate confirmation, document management (rate confirmation, BOL, POD, carrier packet), and freight billing. That gives a freight broker everything needed to manage 20-100 loads per day with documented compliance and proper billing.

A full platform adds three high-value extensions. ELD integration pulls driver Hours of Service data directly from electronic logging devices, giving dispatchers real-time visibility into which drivers have remaining available hours before DOT limits are hit. Load board integration with DAT and Truckstop lets dispatchers source carrier capacity from spot market boards directly inside the TMS. Accounts receivable with factoring integration connects to freight factoring companies. Many brokers sell invoices at a discount for immediate cash rather than waiting 30-60 days for shipper payment. Multi-division management supports brokers with separate operating divisions or asset-based carriers with mixed fleet types under one TMS.

Core architecture

Four data models carry the system.

The load record stores shipper, origin, destination, commodity, weight, miles, rate, assigned carrier, assigned driver, and status. The status state machine moves through available, assigned, in transit, delivered, billed, and paid. Each transition is logged with timestamp and user.

The carrier record stores MC number, DOT number, legal name, insurance expiry date, authority status, and a carrier_packet_complete boolean. Authority status is pulled from the FMCSA SAFER API on carrier onboarding and re-checked weekly by a cron job. If a carrier's authority lapses, the record updates to inactive and the carrier becomes ineligible for assignment until the status resolves.

The rate confirmation is a PDF document auto-generated from the load record. It contains load details, rate, payment terms, and carrier signature block. Generation happens via Puppeteer on demand. Carriers receive it via email with a DocuSign link for digital signature. The signed document stores back against the load record in S3.

Fuel surcharge calculates from the current DOE weekly retail diesel average, fetched from the Energy Information Administration API every Monday morning. The system stores the active diesel price and looks up the applicable surcharge percentage from the configured fuel surcharge table when generating any invoice. Surcharge = miles x per-mile rate x surcharge percentage. The DOE diesel average for the week of load pickup applies, not today's price.

Owner and driver settlement records aggregate all loads in a pay period, apply the configured pay method (per-mile, per-load, or percentage), deduct any advances or chargebacks, and produce a net settlement amount for ACH disbursement.

The hardest technical challenge

FMCSA carrier compliance automation.

Under 49 CFR 387.9, carriers hauling general freight must hold minimum $750,000 in liability insurance. Carriers hauling household goods must hold $300,000. The broker is responsible for verifying this before dispatch. A broker who knowingly dispatches a load to an unqualified carrier can face joint liability for cargo loss, accidents, and shipper damages.

The FMCSA SAFER API provides authority status in real time. But it does not provide insurance certificate details. Those come from the carrier's insurance broker as PDF certificates of insurance. Build a two-layer compliance system.

Layer one is automated. On carrier onboarding, query the FMCSA SAFER API with the carrier's MC number or DOT number. The API returns authority type (broker, carrier, or both), current status (active, inactive, or revoked), safety rating, and out-of-service order status. Store these fields on the carrier record. Run a weekly cron job that re-checks every active carrier and updates their authority status. Carriers whose status changes from active to anything else get flagged immediately and removed from the eligible carrier pool.

Layer two is manual with automation assist. Staff upload the insurance certificate PDF on carrier onboarding and enter the expiry date. The system accepts the certificate and marks the insurance as current. A daily job checks every carrier's insurance expiry date. Carriers within 30 days of expiry appear on a carrier alert dashboard, sorted by load volume over the past 90 days. The busiest carriers with expiring insurance surface first.

Before any load assignment, a pre-dispatch validation runs three checks:

authority_status == 'ACTIVE'
insurance_expiry > today
carrier_packet_complete == true

All three must pass. A single failure blocks the assignment and displays the specific reason: "Authority status: INACTIVE as of 2026-04-15" or "Insurance expires in 12 days -- certificate renewal required." Dispatchers cannot override a failed compliance check without a manager approval workflow. The approval is logged on the load record with the approver's name, timestamp, and reason.

The carrier alert dashboard deserves its own screen. Sort by loads in the last 90 days descending. A carrier doing 200 loads per month with insurance expiring in 10 days is a higher operational risk than a carrier doing 2 loads per month. Surface the highest-volume risks first, not alphabetically.

"FMCSA compliance isn't a checkbox you visit once. Carrier authority and insurance status can change any day. The brokers who avoid liability are the ones who've automated daily monitoring, not the ones who verified once at onboarding." -- David Heller, VP of Safety at the Truckload Carriers Association, in a 2023 industry compliance briefing.

Build costs and timeline

An MVP takes 14-20 weeks and costs $140K-$240K. This covers load management, carrier database with FMCSA compliance, load assignment, document management, and freight billing. That's enough to run a 20-100 load per day brokerage with documented compliance.

A full platform with ELD integration, customer portal, load board connections, factoring integration, and multi-division support takes 24-32 weeks and costs $280K-$450K.

Post-launch infrastructure runs $2K-$5K per month: hosting, document storage, DocuSign API, email and SMS notifications.

Build vs. buy

Build custom when you dispatch 100+ loads per day and need compliance workflows that go beyond what off-the-shelf tools support, when you need direct factoring company integration without a middleware fee, or when you are an asset-based carrier with 50+ trucks whose per-truck SaaS fees are approaching $20K-$30K per month. The custom ROI case for asset carriers is straightforward: eliminate per-truck licensing, own your data, and add features without a support ticket.

Tech stack

Backend: Node.js with PostgreSQL. PostgreSQL handles the relational structure of loads, carriers, documents, and settlements without requiring a separate search engine for the query patterns involved.

Frontend: React for the dispatcher web application. The dispatch screen is the highest-traffic interface: load board, carrier assignment, status updates, and compliance alerts all live here.

FMCSA compliance: FMCSA SAFER System API for carrier authority and safety rating lookups. Query on onboarding, re-check weekly via cron.

Fuel surcharge: US Energy Information Administration (EIA) API for weekly retail diesel average. Fetched every Monday morning and stored as the active fuel surcharge base rate.

Document storage: AWS S3 for all documents: rate confirmations, BOLs, PODs, and carrier packets. S3 presigned URLs for secure carrier and shipper access without exposing bucket credentials.

PDF generation: Puppeteer for rate confirmation and BOL PDF generation from load record data. Templates are HTML/CSS rendered server-side.

Carrier signatures: DocuSign API for digital carrier rate confirmation signatures. Signed documents are stored back to S3 with the envelope ID for audit trail.

Notifications: SendGrid for load status emails to shippers and carriers. Twilio for SMS dispatch notifications to drivers on load assignment and pickup window reminders.

ELD integration (full platform): KeepTruckin (Motive) or Samsara API for driver Hours of Service data. Both expose REST APIs returning current HOS status per driver.

Load board integration (full platform): DAT API and Truckstop API for posting available loads and sourcing carrier capacity from spot market boards.