What does a TMS do for a freight forwarder?

Start with the duty, not the software.

FIATA describes freight forwarding and logistic services as services of any kind relating to the carriage, consolidation, storage, handling, packing or distribution of goods, plus the advisory work around them, including customs and fiscal matters, insurance, and collecting payment or documents. FIATA also says the forwarder must scrupulously ensure the accurate and timely production of documentation.

That is the reason a TMS exists. Months later, somebody has to say what was agreed, what moved, what it cost and what was issued. A transportation management system is where a forwarder keeps that answer.

In a forwarding business a TMS usually holds seven things:

• 01the job or shipment file, with the parties, the route and the mode
• 02the booking and the carrier reference against it
• 03the documents issued for the job, such as a house bill or a delivery order
• 04the milestones the shipment has passed
• 05the cost lines from carriers and agents, and the charge lines to the customer
• 06the invoice, the credit note and what is still outstanding
• 07the trail of who changed what, and when

No two products cover those seven the same way. Some stop at operations and hand the accounts to a finance package. Some carry customs and warehousing too and are sold as a freight forwarding ERP. Write down which of the seven must live in one place.

Products differ, so treat what follows as a list to test rather than a verdict. Ask your own supplier to show each line.

A system of record is organised around an object that already exists. A job. A booking. An invoice. Most of a forwarder's day happens before that object exists, or in the gap between two of them.

• Reading an enquiry that arrives as loose text, a forwarded thread or a photo of a packing list.
• Working out what is missing from it and asking for it.
• Sending one lane to six agents, then chasing the four who did not reply.
• Deciding what to charge this customer, on this lane, this week.
• Answering “where is my cargo?” on the customer’s own thread.
• Checking a carrier bill line by line before it is booked.
• Carrying a file from pricing to operations to accounts without anything being retyped.

A TMS can hold the result of every one of those. It is not usually the thing that does them. That is why a forwarder can buy a capable TMS, configure it properly, and still find the team living in the inbox a year later.

Two boundaries that are boundaries by design

The first is statutory filing. It usually happens in a national channel rather than in a forwarder's own software. US Customs and Border Protection describes ACE as the United States single window, one access point connecting CBP, partner government agencies and the business community. Other countries run their own equivalents. Establish what your TMS hands to that channel, and what a person still keys in twice.

The second is the statutory books, which many forwarders keep in a separate finance system. Neither boundary is a fault. Both are things to confirm in writing.

Follow one job from the first enquiry to the closed file. The steps below are the record. Under each one there is a person doing the work that produces it.

Three things about that line are worth noticing.

The record starts late

The system really begins at the quote or the job. The enquiry, the rate sourcing and the agent chasing happen before a job exists, and many forwarders never record them. That is why a lost quote is invisible. There is no object to count.

Every arrow is a hand-off

Pricing to operations. Operations to documentation. Documentation to accounts. The record moves cleanly. The email thread, the customer's question and the reason a rate was chosen do not. They stay in somebody's mailbox, and the next desk asks again.

A milestone feed is not an answer

DCSA publishes its Track and Trace standard because status data is often exchanged inconsistently, with delays or not at all. It covers milestones including load and discharge, gate in and gate out, transhipment, and pick-up and drop-off. Even a clean feed leaves a person to read the customer's question and write the reply.

Ask for that line drawn with one of your own jobs on it. The sample job never has a missing document or a disputed charge.

Not every forwarder needs one yet, and not every forwarder needs the same shape.

Signals that you need one

• You cannot say what a job cost without opening three files.
• Two people hold different versions of the same shipment.
• Documents come from a template that somebody edits by hand.
• An auditor or a customer asked for history you could not produce quickly.
• Invoices go out late because the charges are assembled at month end.
• You are opening a second office or a second service line.

Signals that you do not need one yet

• One or two people see every shipment and the volume is small.
• The business is a single lane with a single carrier.
• The pain is answering enquiries, not finding records.
• You cannot yet describe how a job should be numbered, approved and closed.

The last one matters more than volume. A TMS records a process. If the process is not agreed, the system will faithfully record the disagreement.

Use the same questions with every supplier, and ask for evidence rather than agreement. The third column is what a good answer looks like.

Two of those rows are not really about the TMS. They decide whether a new system of record will change your team's day. If the mailbox stays open all day either way, the record was never your constraint.

Do not accept a feature list instead of this conversation. Two products can both say “document management” while one issues a negotiable transport document and the other stores an attachment.

What to take into the demonstration

• One closed job from last month, with every document attached.
• One job that went wrong, and the trail that explains what happened.
• The carrier invoice you disputed, and what you did about it.
• The email thread that started the messiest shipment of the quarter.

A demonstration that survives the messy thread is worth more than one that shows a perfect job.

A logo grid is not a connection. Ask what moves, in which direction, on what trigger, with whose credentials, and what happens when it fails.

The shortcut is to ask which published standard a connection follows, because a standard is something you can read without the supplier in the room.

• DCSA publishes common data models, communication protocols and operational processes for container shipping, covering Booking, Bill of Lading, Verified Gross Mass, vessel schedules and Track and Trace. Its stated aim is digital interoperability between carriers, ports, terminals, shippers and forwarders.
• DCSA Track and Trace uses interoperable data models, standardised definitions and APIs, so one connection can serve several carriers.
• IATA ONE Record is a standard for data sharing that creates a single record view of the shipment, and IATA describes it as going beyond EDI and messaging technologies.
• The IATA Multilateral e-AWB Agreement lets a party sign once with IATA and then work electronically with every other party to it.
• FIATA's secured paperless Bill of Lading is issued through a forwarder's everyday tools, and FIATA offers software providers a free API to connect to it.

None of that tells you a product is good. It tells you the connection has a definition, so you can test it and have it supported by somebody other than the person who sold it to you.

Then ask the awkward question. When the connection is down, or the carrier is not on a standard, who does the work by hand, and does anything tell them to?

Most forwarders reach this question after the TMS is running well and the team is still buried. The records are clean. The day is still spent in the mailbox.

Judge the new layer on the work, not on its screens.

Keep your TMS for the records. FreighAI runs the work around them. FreighAI is an AI-first freight operations platform that can run standalone or work alongside an existing TMS or ERP. It does not require a forced replacement.

FreighAI, as one example of such a layer, describes its own job this way: Every email your company receives is read, understood and turned into a task for the right person, with the answer already drafted. Your team approves. Nobody lives in the inbox any more.

FreighAI pulls your rate cards, checks the carrier, looks up the customer’s history, reads the shipment status, and talks to your TMS or accounting system.

Whatever you add above the record, three things should stay where they are.

• 01The system of record. The job, the documents, the costs and the audit trail belong in one place, and it should stay the place you show an auditor or a customer.
• 02The approval. A reply can commit margin, carrier capacity, payment terms or a relationship. Your team approves. They do not compose, forward, file or chase. The reply goes out in their name.
• 03The boundary. Statutory filing, statutory books, warehouse and fleet management stay in the systems that own them today.

Chasing, tracking checks, quote expiry and follow-ups run on their own. Nobody has to remember. We scope the first workflow, integration requirements and implementation plan with your team.

Put the same two questions from the table to any supplier of a layer above your TMS. Whether the mailbox still has to be opened, and what runs by itself.