Definition
A transportation management system is the software a freight forwarder uses as the system of record for shipments: lots, parties, documents, charges, and status. Common platforms include CargoWise, Magaya, Descartes, and GoFreight.
Why it matters
The TMS is authoritative but it does not read email. Someone has to move the data from the inbox into the TMS by hand, which is the bottleneck TIO removes.
What a freight forwarder TMS actually manages
A freight forwarder's TMS is the system of record for every shipment: the lot or job record, the parties (shipper, consignee, agents, broker), the document set, the charges (AP and AR), and the status at each point in the lifecycle. Most forwarder TMS platforms are organized around the mode of transport, with separate job types for ocean import, ocean export, air, and domestic. Each job type has its own field set, document requirements, and billing structure. The TMS does not tell the forwarder what to do — it records what the forwarder has done.
How CargoWise, Magaya, and GoFreight differ
CargoWise (WiseTech Global) is the dominant platform for mid-to-large forwarders globally. It has deep customs integration via ABI, handles multi-modal and multi-currency operations, and runs a built-in accounting module. As of December 2025, WiseTech moved most customers to per-transaction pricing under the CargoWise Value Pack (CVP), which significantly increased costs for smaller operations. Magaya is popular with small and mid-size U.S. forwarders for its lower cost and ease of use. GoFreight is designed for newer, smaller operations and has a simpler interface. Descartes is common in customs brokerage operations with its licensed ABI connection.
The gap no TMS fills
Every TMS has the same structural limitation: it stores data, but it does not acquire data. A booking confirmation, a pre-alert, an arrival notice, an LFD notification — all of these arrive in an email inbox. None of them arrive in the TMS. A person reads each email, opens the TMS, finds the correct lot, and types in the data. At 50 to 200 jobs per month, this manual inbox-to-TMS step consumes more back-office hours than any other single activity in a forwarder's operation. The TMS vendors have not solved this because it is an email ingestion and extraction problem, not a TMS architecture problem.
TIO is TMS-agnostic. It writes approved data to your TMS via API and reads lot state back. No rip-and-replace.
Learn more →