Freight broker load board vs TMS: what runs the operational day
Why broker desks need a live load board alongside Aljex or another TMS, what each system should own, and how to stop re-keying shipper spreadsheets into both.
A TMS is the broker's system of record for settlements, carriers, compliance and accounting. A live load board is where the operational day happens, from morning shipper emails to posting and carrier calls to booking. SmartLoads runs the board side, with imports from email and Google Sheets, Truckstop and DAT posting, AI answering for missed carrier calls and confirmations from the broker's Outlook, while the TMS stays the ledger.
Freight brokerages run on two clocks. The operational day runs on the load board: what came in this morning, what's posted, who called about it and what's booked. The financial day runs in the transportation management system (TMS): settlements, carrier records, compliance and invoices.
Most broker software tries to be one or the other. The trouble starts when a desk tries to make the TMS do the morning's work.
What a TMS is good at
A TMS such as Aljex is built to be the system of record:
- carrier onboarding, insurance and compliance
- rate confirmations, invoicing and settlements
- accounting, commissions and reporting
It's where a load needs to end up. It isn't where brokers want to fight a stack of shipper emails, PDF attachments and Google Sheets at 7:30 in the morning. Some TMSs have no bulk export at all, which forces brokers to key loads in one at a time before they can post them anywhere.
What the operational day needs
The morning looks different. A broker desk needs:
- Every shipper's loads in one place, whatever format they arrived in, without retyping
- A board that stays current as shippers re-send sheets and change rates during the day
- Posting to Truckstop and DAT without building an upload file by hand
- Carrier calls answered, including the ones that roll to overflow at peak
- Booking and confirmation that reach the customer from the broker's own mailbox
How the two fit together
SmartLoads runs the operational layer and leaves the TMS as the ledger:
| Job | Where it lives |
|---|---|
| Shipper intake (email, Excel, PDF, Google Sheets) | SmartLoads |
| Live load board, deduplicated | SmartLoads |
| Truckstop posting (API) and DAT upload file | SmartLoads |
| AI answering for missed carrier calls, carrier leads | SmartLoads |
| Booking and customer confirmation email from Outlook | SmartLoads |
| Carrier records, settlements, invoicing, accounting | Your TMS |
At SmartLoads' first agency customer, a broker agency on Aljex, the board has structured 38,321 load postings from 16 automated shipper feeds since May 21, 2026, and Truckstop posting runs through the API. The TMS still does what it's good at.
Connecting them
The two sides don't need to be manually synced. SmartLoads imports Aljex report exports (the Big 500 CSV), matches Aljex invoices back to covered loads, and shows every field in Aljex's order when a load is covered so entering it takes seconds. For any other system, the SmartLoads Partner API lets a TMS read loads, carrier leads and load paperwork, and get webhooks when loads are booked.
Frequently asked questions
Do we still need a TMS if we use SmartLoads?
Yes. SmartLoads doesn't do carrier settlements, invoicing or accounting. It runs the part of the day before and around booking.
Does SmartLoads work with TMSs other than Aljex?
Yes. Intake and posting don't depend on the TMS, and the Partner API lets any TMS connect to SmartLoads.