Works with the TMS you already run.
TIO connects to your existing TMS and to your inbox, on Microsoft 365 or Google Workspace, through their APIs: CargoWise, Magaya, Descartes, GoFreight, or any system with a REST or SOAP endpoint. Your TMS stays the system of record; the agents read your inbox, do the prep and the entry, and a person approves the filings and records they draft.
Your TMS
Connects through the API you already have, including CargoWise, Magaya, Descartes, GoFreight, and any TMS with a REST or SOAP endpoint. No migration, no parallel system.
Your inbox
Work reaches the agents the way it always has, through Outlook or Gmail. No forwarding rules to set up, no new system for the team to learn.
Your system of record
Approved records write back to your TMS. It stays the source of truth for billing, filing, and every other downstream process.
What happens between the email and the TMS record?
Nothing is ripped out and nothing is replaced. The loop is the same on every TMS: read, stage, approve, write.
1 · Read
A booking, worksheet, bill of lading, or delivery order lands in the inbox. The agent reads the message and its attachments and identifies the job it belongs to.
2 · Stage
It resolves the parties, references, and charges against what is already in your TMS and stages a finished record: the complete lot, the drafted ISF. Anything it cannot verify, it flags and asks instead of guessing.
3 · Approve
A person on your team reviews the staged record next to its source documents and approves it, or corrects it. Every correction becomes a rule the agent keeps.
4 · Write
Only after approval does TIO write through the TMS API. At the US import forwarder running this in production, that loop took lot creation from about 30 minutes to seconds across 25+ jobs a week.
Why a layer, not a switch?
Replacing a TMS is a year-long project with real failure risk, and most forwarders have years of jobs, rates, and habits in the one they run. TIO’s bet is the opposite: keep the system of record, remove the keying between the inbox and it. If you are weighing that trade, read whether to switch systems or add a layer, or see how it plays out lane by lane on ocean import.
Book a demoStraight answers on connecting.
Which TMS platforms does TIO work with?
TIO connects to the TMS a forwarder already runs through that system’s own API: CargoWise, Magaya, Descartes, GoFreight, and any TMS that exposes a REST or SOAP endpoint. The TMS stays the system of record for billing, filing, and every downstream process. TIO does not replace it and there is no migration.
How does the TMS integration actually work?
Read, stage, approve, write. The agents read what lands in the inbox, resolve it against the jobs and parties already in the TMS, and stage a finished record: the lot with charge lines, the drafted filing. A person on the team reviews and approves it, and only then does TIO write through the TMS API. The filings, quotes, and records the agents draft wait for a person.
What does connecting take?
API access to the TMS and the mailbox, and no change to how work arrives. Emails keep landing in the same Outlook or Gmail inbox the team already uses; there are no forwarding rules to build and no new system to learn. Connection runs in days, not weeks, and the first agent works real shipments from day one.
What if our TMS is not on the list?
If it has a REST or SOAP API, TIO can connect to it; the adapter pattern is the same read-stage-approve-write loop against a different endpoint. Tell us what you run on the demo call and we will scope it there.