Best carrier TMS for Intermodal operations

About intermodal TMS shopping

Intermodal / drayage TMS is the operation type where the gap between "supports it" and "actually does it" is largest. Drayage carriers operate against external systems built decades ago: port terminal operating systems (TOS), eModal appointments, Class-I rail track-and-trace APIs, chassis-pool membership systems (PoolStat, etc.). A real drayage TMS connects to those natively. A general-purpose FTL TMS calls a container "a load with a number" and lets the dispatcher manage the rest manually.

The traps: per-diem on chassis ($25–$40/day per chassis after free time runs out), last-free-day on containers (demurrage to the steamship line if the container doesn't move), chassis pool membership (you're paying to use chassis you don't own). Manual tracking on whiteboards leads to invoices the carrier can't recover.

Our intermodal picks

The 3 must-haves for intermodal

1. Port / rail appointment integration (eModal, Rail Inc / Class-I rail APIs). Native API integration to surface and book port appointments without re-keying.
2. Container + chassis number tracking with per-diem / last-free-day / demurrage tables. The TMS must track each container's clock from gate-out to gate-in, surface impending demurrage, and produce billing evidence for chargeable detention.
3. Multi-leg / rail-move "master order" structure with chassis-pool and lift-charge accounting. A single shipment can involve drayage to rail, rail line-haul, drayage from rail to consignee. The TMS must structure it as one shipment with multiple legs, not three disconnected loads.

Wrong choices for drayage-primary carriers

• Rose Rocket. The vendor markets a drayage use-case page, but a Software Advice review explicitly notes "no sensible straightforward way to track both chassis and container numbers within a shipment." Source. Weak for true drayage.
• Truckbase, Tailwind, ITS Dispatch. No intermodal / eModal / chassis features surfaced on vendor pages. Positioned for FTL/small-fleet — wrong fit for drayage-primary carriers.
• AscendTMS. Minor intermodal touches (container # + last-free-day on docs) but no eModal or chassis-pool integration surfaced. Unverified as drayage-specialty.
• Alvys. The op_tag includes "intermodal" and tracking integrates with telematics for container visibility. Defensible at asset-based intermodal trucking, but no eModal / chassis-pool / per-diem specifics surfaced. Pressure-test in demo if drayage is >50% of your operation.

What to pressure-test in a demo

• eModal appointment booking. Walk through booking a port appointment from inside the TMS — does it round-trip with eModal or is it a "log into eModal in another tab" handoff?
• Per-diem clock on chassis. Show how the TMS tracks chassis check-out, free-time, and per-diem accrual. When does the alert fire?
• Last-free-day on containers. Same for the container side — demurrage to the steamship line.
• Chassis-pool membership accounting. If you're in a chassis pool, the bill at month-end includes per-day chassis charges. The TMS should produce reconciliation evidence per chassis ID.
• Multi-leg shipment structure. Drayage → rail → drayage. One shipment, three legs, three sets of moves. Show the data model.
• Lift-charge accounting. Each lift at port or rail incurs a charge. The TMS should attribute it to the right shipment for cost accounting.
• Driver app for container/chassis number capture. Drivers should be able to update container and chassis numbers from the cab without paper handoffs.

---

Sources