TMS automation that fills the system you already pay for

What is TMS automation?

TMS automation is software that reads the documents arriving in a freight inbox and writes their fields into the transport management system a company already runs. It does the keying that a dispatcher, an account manager or an accounts-receivable clerk would otherwise do between calls. The documents are the familiar ones: rate confirmations, bills of lading, proofs of delivery, carrier invoices. The system is whichever one you already pay for.

The phrase gets used loosely for anything that touches a TMS, including route optimization and load matching. This page means the narrow thing: moving information from documents into the system without a person retyping it. The broader picture is in logistics automation.

Why is a TMS still empty when you are paying for it?

Because a TMS records what someone types, and nobody is paid to type. Typing is the work that loses to the next phone call. A load number gets entered because the load cannot move without it. A time at the dock, a note about a damaged pallet, or the scanned proof of delivery does not stop anything that day, so it stays in an email thread, a driver text or a folder on someone’s laptop, and the system holds a skeleton of the shipment instead of the shipment.

This is why buying a better TMS does not close the gap. The new system will be as empty as the old one for the same reason, plus a few months in which both are partly filled. The gap sits in the labour, and the labour is the thing the software is waiting on. Where the missing fields are facts that no document ever held, reading will not help either; that is covered under freight document automation.

What gets written into the TMS, and by which route?

The agent writes the fields of each document into the record they belong to, by whichever route your system accepts: an import, an API, or the same screens a person would fill. We do not claim an integration with any named product. What a system exposes depends on the plan, the version, and what the vendor has chosen to switch on, and two customers of one product can differ. So the route is found by looking at your installation, and the table sets out what each one means in practice.

Whatever the route, the first thing to settle is what happens to the original page. A written field with no link to its source is a number that someone will eventually doubt and cannot check.

What does the record have to hold?

At minimum, the transaction details that a broker is required to keep for three years, which is the line between a database and a file. 49 CFR 371.3 requires a broker to keep a record of each transaction, and it names what goes in it: the consignor’s name and address, the originating carrier’s name, address and registration number, the bill of lading or freight bill number, the compensation the broker received and who paid it, any non-brokerage service performed, and the freight charges the broker collected with the date the carrier was paid. A TMS that was filled by hand holds this only for the loads where someone found the time.

The rule is a floor and not a design brief, but it changes how the question reads. A broker cannot treat a half-empty system as a convenience that might be tidied up later, because the entries are the record the regulation expects to exist. Automation that writes every load the same way produces that record as a by-product. On the carrier side, the invoice that follows has its own content requirements under 49 CFR 373.103, and a field written from the document that proves it is the one that survives a question.

What should you ask a TMS automation vendor before signing?

Ask what it writes, by which route, what it does with a document it cannot read, and what leaves with you if you cancel. The first two questions are easy to answer and tell you little, since every vendor will say it writes to your system. The third is the real one. A tool that stops at the first unreadable scan has moved the work to a queue that nobody owns, and a tool that guesses has hidden it. Ask to see a held item and the person it was routed to.

The fourth question is about leaving. If the values the agent wrote live in your system, they stay when it goes. If they live in the vendor’s own platform, with your TMS holding a copy, you have rented your own records. Also ask whether the page stays linked to each field, whether pricing is by document or by seat, and who answers when the writing route breaks after a TMS update, because it will.

Do you have to migrate to a new TMS?

No, and a project that starts by replacing the TMS usually does not finish. A migration means moving years of loads, customers, rates and carrier history, retraining every user, and running two systems while the old one winds down. It competes for the same few people who do the daily work, and it is the most common reason that back-office improvement is abandoned halfway. Automation does not need it and does not delay it.

If you do have a reason to move later, the work carries over. The documents are still the documents, the capture process still holds, and the agent points at a different place to write. If the current system is not the problem, the problem is the typing, and that is the part you can remove this quarter without touching the contract.