AI on your TMS / Aljex
Keep Aljex. Add the execution layer.
Same overlay model as McLeod and Tai. FreightScout layers on Aljex so you intake, cover, track, and work shippers without migrating order entry or settlements off Aljex.
Last updated 15 September 2026.
Hub: AI on your TMS. Comparison that quotes Aljex in its own words: FreightScout vs Aljex.
What stays versus what agents take
| You keep | FreightScout adds |
|---|---|
| Aljex as system of record | Load building off email, PDF, EDI |
| Existing users and settlements | Carrier booking to your max pay |
| Customer and lane files | AI check calls logged to the load |
| Floor judgment | Shipper outreach from your lane history |
Built for Aljex-shaped days
Tenders, routing guides, check calls, cover boards: if that is the day, agents were built for it. Win, price, move, bill, keep in one login. 146,539 loads under management on the product. Not a second TMS.
Questions people actually ask
Do I have to replace Aljex?
No. FreightScout sits on Aljex and reads it in place.
Is this a new system of record?
No. Aljex remains the record until you choose otherwise.
Can I start with one pain, check calls or load build?
Yes. Turn on the capability that hurts most first, supervised.
Where are McLeod and Tai?
AI on McLeod and AI on Tai live next to this page, under the same TMS hub.
Most freight software watches your business. FreightScout wins freight and then runs it.