An AI lot agent automates order entry by reading the shipment email and its documents, extracting the 20-odd fields an ocean import lot needs, and creating a complete TMS record, charge lines included, that a person then reviews. At the US import forwarder running the agent in production, lot creation went from about 30 minutes of reading and keying per shipment to seconds of agent work plus a short human review, across 25+ jobs a week. The fields come from 4 different documents, the bill of lading, the house bill, the commercial invoice, and the pre-alert, and the agent reads them the way an operator does, by meaning rather than position. The agent sends a review email that shows every field, and when it cannot match a party or two documents disagree, it stops and asks a person.
Nobody grows up wanting to do order entry. It is the work that fills the gaps between the real work: a booking lands, and before anyone can do anything useful with it, a shipment record has to exist in the TMS. Parties, ports, vessel and voyage, containers, commodity, charges. Twenty-odd fields for an ocean import, pulled from four different documents, typed in by hand, on every single job (the lot is the TMS job record that holds them). It is the most repeated task in the back office and the one that requires the least thought, which is a strange combination, and exactly the combination a machine is good at.
An AI lot agent reads those four documents and creates the record in seconds. Then it sends a review email so a person can check every field. That is order entry automation, and of all the things people claim AI can do for freight, this is one of the few it actually does.
We already built an ISF agent for the 10+2 filing. The lot agent is the same idea pointed at a different job. This post is about that job, order entry, and about where the person stays firmly in charge.
The problem is not the fields. It is that they are scattered.
A lot is just the shipment record, and the fields it needs are not a secret. Importer and consignee. Shipper and seller. Origin and destination. Vessel and voyage. Container numbers and sizes. Commodity and code. House and master bills. The charge lines. An ocean import runs about twenty of them. A domestic move is a different set, same idea.
But not one of them lives in the same place. The booking confirmation has the vessel and voyage. The origin agent’s worksheet has the parties and the stuffing location. The bill of lading has the containers and the bill numbers. The packing list and the invoice carry the commodity and the values. So a person opens all of them, hunts down each field, and keys it in. At the US import forwarder we work with, that ran about 30 minutes a lot.
What makes it costly is not the difficulty. It is the repetition, the clock, and the fact that a consignee whose name is spelled three ways across three documents, or a container number off by one digit on a Friday afternoon, turns into someone else’s problem next week. This is boring work that punishes a lapse in attention, which is the worst kind.
What the lot agent does with the pile
Think of it as the colleague who can read four documents at once and never gets bored halfway through the invoice.
Someone forwards the shipment email to the agent. It reads the body and every attachment, the worksheet, the bill of lading, the packing list, the invoice, and pulls the fields for the lot. It matches the parties against records you have built before, so the consignee spelled three ways collapses to the one you actually use. It creates the lot in your TMS and sends a review email that shows every field.
On a normal shipment that read-and-build pass takes seconds. A heavy one, ten attachments deep with origin and compliance certificates, takes longer, because the reading is the work and there is simply more of it. Set that against about 30 minutes of manual keying and the pass is effectively free, and it happens before anyone has opened the file.
It reads with a vision-capable model, so the format does not matter. An Excel worksheet, a scanned PDF of a bill of lading, an invoice with the numbers buried in an attached sheet, all read the same way. It works off labels, not positions, so one origin agent’s worksheet and another’s both resolve without anyone building a template for each layout.
Side by side, the two ways of building a lot look like this.
| Building a lot by hand | Building a lot with the agent |
|---|---|
| Open four documents and hunt down each field | Reads the email and every attachment in one pass |
| Key twenty-odd fields into the TMS | Creates the lot and sends a review email with every field |
| About 30 minutes per lot | Seconds, then a short human review |
| Retype consignee names and container numbers | Resolves parties against lots you have built before |
| Learn each origin agent’s layout | Reads by label, any layout, ocean or domestic |
Why it works for a forwarder it has never seen
The agent is not wired to one company’s setup. Three things keep it portable.
It lives between the inbox and the TMS. It does not replace your TMS and it will not ask you to migrate onto anything. TIO works through an adapter built for your TMS. Adapters run in production for two TMS platforms. Another TMS needs its own adapter first. Your TMS stays the system of record.
It works from your own records, not from a template. It matches parties against the lots you have already built. A first-timer gets flagged for a closer look. When your team corrects an agent, the correction becomes a rule for your operation. It is a rule, not model training.
It does not care about the lane. Ocean import and domestic trucking are different records with different fields, and the agent handles both from the same inbox. It reads the lane off the documents instead of asking you to pick one.
Two agents, one honest pattern
The lot agent and the ISF agent are the same move applied twice. Read the email and the documents. Pull the fields and check them. Flag whatever is uncertain. Hand a person the result. The ISF agent never files: it prepares a draft and a person on your team reviews and files it. The lot agent creates the lot and sends a review email that shows every field. Both take away the assembly, which is where the hours go, and leave the judgment, which is where they belong.
That is the version of AI a forwarder can actually put to work this quarter. Not a system that runs the business. A handful of narrow agents, each one taking a single high-volume, low-judgment job off the desk. Order entry is the highest-volume of the lot, which is why it is the first one worth handing over.
The same job, at a 3PL or a logistics desk
None of this is unique to forwarders. A 3PL spinning up shipment records from customer emails, a logistics team keying orders off inbound paperwork, a broker building entries from origin docs: it is all the same shape. Structured data, scattered across attachments, assembled into a record by hand. Wherever an order or shipment record gets built from an inbound email, the same job exists. The documents change and the destination system changes, and each destination needs its own adapter. The read, resolve, and review flow does not.
A person reviews every lot
To be clear about the part that matters: the human does not leave order entry. The agent creates the lot and sends a review email that shows every field. A party it cannot match, or two documents that disagree, go to a person. The reviewer checks the fields that count and fixes anything wrong.
That split should make sense to anyone who has done the work. The machine does the reading and the typing. The person still makes the calls that carry weight. What goes away is the keying. What stays is the judgment, which was the point all along.
Putting one on your desk
A first agent starts as a scoped pilot on your own documents. We need a mail rule that copies mail to the agent, sample documents, and a TMS login. The adapter and your rules for the job take the time. You keep your current process running next to it until the lots on your regular consignees stop needing corrections, and then you stop double-entering.
If order entry is quietly eating your team’s week, book a short demo and bring a few of your own shipment emails. We will run them live and show you the lot it creates for review, on your documents, in seconds.
TIO is an AI agent workforce for freight forwarders and 3PLs: named agents that quote freight, create lots and delivery orders, and reconcile charges from the inbox your team already uses. Meet the agents.
Frequently asked questions
What is order entry automation for freight forwarders?
Order entry is the work of creating a shipment record, often called a lot or a job, in the TMS: the parties, the ports, the vessel and voyage, the containers, the commodity, and the charges. Automating it means an AI agent reads the inbound shipment email and its attachments, extracts those fields, resolves the parties against records you have filed before, and creates the lot in your TMS, charge lines included. It sends a review email that shows every field. A party it cannot match, or two documents that disagree, go to a person.
What AI agents can a freight forwarder use today?
The useful ones are task-specific and email-native. An ISF agent reads the origin worksheet and house bill and prepares the 10+2 filing for a person to review and submit. A lot agent, or order-entry agent, reads the booking and pre-alert documents and creates the TMS lot, then sends a review email. Both follow the same pattern: the agent reads the email and documents, extracts and validates the fields, and flags what is uncertain. The ISF agent hands a person a draft to file. The lot agent sends the lot for review. A person makes every call that carries liability. This is where AI is genuinely useful in freight right now: the high-volume, low-judgment data assembly, not the judgment itself.
Does an AI lot agent create the TMS record automatically?
Yes, once the adapter for your TMS is in place. The agent creates the lot in your TMS, charge lines included, and sends a review email that shows every field. A party it cannot match, or two documents that disagree, go to a person. The point is not to remove the person. It is to remove the keying that happens before the person's judgment is even needed.
Does order entry automation work with my TMS, and does it work for a 3PL?
The agent needs a tested adapter for each TMS before it can create records. TIO has production adapters for two TMS platforms; another platform must be scoped and connected before use. The same order-entry burden exists for 3PLs and logistics teams that create shipment or order records from inbound email. The agent uses your own documents and operating rules, not a generic template.
