You turn shipment emails into TMS entries automatically by putting a read-and-match layer between the ops inbox and the TMS, so no one retypes the email. The layer copies each email from a mail rule, classifies it (pre-alert, booking confirmation, arrival notice), ties it to the right job by its master bill, house bill or container number, reads the fields in the body and attachments, and writes the result through a TMS adapter. Anything the rules cannot decide goes to a person, and the agent does not guess. The work it replaces is large: a single pre-alert takes 14 manual steps and 8 to 30 minutes, and a 100-job ocean import operation spends roughly 35 to 53 hours a month on this loop (illustrative, from ops team feedback). The TMS stays the system of record, and your team stops retyping into it.
Most ops managers know how many jobs they run a month. Very few know how many hours their team spends moving those jobs’ emails into the TMS, because nobody has timed it per step.
How do you automate the inbox-to-TMS loop?
You automate it in 5 steps, and the person stays on every decision the rules cannot make.
- Copy the mail. A mail rule copies the shared ops inbox to the agent. Nothing changes for the team; they keep working in the same inbox.
- Classify the email. The agent decides what kind of email it is, such as a pre-alert, a booking confirmation, an arrival or release notice, or a trucking message, and sets aside mail that is not about a shipment.
- Match it to the job. It ties the email to an open job using the master bill, house bill or container number, then a booking reference it has learned from earlier mail. No match, or a number that fits two jobs, goes to a person.
- Read the fields. It reads the body and every attachment and fills the job’s fields. A party it cannot match to your TMS party list, or a value it cannot settle, goes to a person.
- Write through the adapter. It writes the fields into the TMS record through an adapter built for that TMS. Each write step has its own on/off switch: it runs within your rules, goes for review, or waits for a person’s reply.
Here is what that looks like on one illustrative pre-alert (values changed):
| Field | Where it was found | What the agent did |
|---|---|---|
| Master bill ABCD1234567 | House bill, page 1, labelled “M/BL No.” | Matched the open job |
| House bill HB-55012 | Email subject and house bill | Matched the same job |
| Container ABCU7654321, 40HC | Equipment list, page 2 | Filled the container line |
| Vessel and voyage | Master bill header | Filled, ETA filled from the agent’s email |
| Shipper name | House bill | Sent to a person: no exact match in the TMS party list |
4 of the 5 rows needed no one. The fifth needed one decision from a person: which existing party in the TMS is this shipper.
What is the inbox-to-TMS loop?
The inbox-to-TMS loop is the gap between a shipment email arriving in your ops inbox and the corresponding TMS record being updated with the data inside that email.
Every ocean import job generates a sequence of inbound emails from parties you do not control: booking confirmations from carriers, pre-alerts from overseas agents, arrival notices, LFD assertions, and trucking coordination messages. Each one contains structured fields that belong in the TMS. None of them land there automatically. A person bridges that gap.
The loop exists in every lane: ocean import, ocean export, air, domestic trucking. The document names change. The steps do not.
For a detailed map of which email types appear at which job stage, see The Freight Forwarder Email Infrastructure Problem.
Every manual step on a single pre-alert
A pre-alert is the highest-cost email type in the ocean import inbox. It arrives from the overseas agent before the shipment, carries the most fields, and often includes multi-page PDF attachments that require scanning, not just reading.
Here is every step a person takes to process one pre-alert into a TMS lot, from the moment the email lands:
-
Notice the email. In a shared ops inbox, this is not instant. The email arrives at some point during the workday. If the ops person is mid-task, it may sit for 15 to 45 minutes before someone opens it.
-
Read the subject line and sender. Identify: is this a pre-alert or something else? What shipment is this likely for?
-
Open the body. Read the agent’s message for context, reference numbers, and any notes about the shipment.
-
Open the attachment. A pre-alert typically has 2 to 5 attached documents: the house B/L, master B/L, commercial invoice, packing list, sometimes a packing certificate or fumigation certificate. Open each.
-
Locate the MBL and HBL. The master bill of lading number and house bill of lading number are the primary identifiers. They may appear on different documents, under different label names (“Master Reference,” “M/BL No.,” or just “Reference” depending on the agent’s format).
-
Extract vessel and voyage details. Read: vessel name, voyage number, ETD (estimated time of departure from origin), ETA (estimated time of arrival at destination). These appear on the B/L but the format varies by carrier and origin.
-
Extract container and seal numbers. These usually appear on a second page of the B/L or on a separate equipment list. If there are multiple containers, each line requires reading.
-
Extract party details. Shipper name and address, consignee name and address, notify party. Each value must be read and verified against the booking record already in the TMS.
-
Cross-check the commercial invoice. Does the shipper on the invoice match the shipper on the B/L? Does the commodity description match? Does the declared value look correct? Discrepancies here require a follow-up email before proceeding.
-
Open the TMS in a separate window. Navigate to the ocean import module. Search for the correct lot by MBL, reference number, or customer name. Locate and open the job record.
-
Key each field individually. MBL number, HBL number, vessel, voyage, ETD, ETA, container number, seal number, container type, commodity, package count, weight, shipper, consignee, notify party, freight charges. Each field is a separate input. Typos in reference numbers create reconciliation problems later.
-
Verify the ISF status. If ISF has not been filed yet, this is the moment to confirm the field list is complete. Missing manufacturer or HTS code triggers a follow-up before the ISF can be submitted.
-
Save the record. The lot is now updated with the pre-alert data.
-
File or archive the email. Move the pre-alert to a job folder or archive for reference. If this step is skipped, the inbox becomes a search problem the next time someone needs to find the original document.
That is 14 steps. On a clean pre-alert from a well-organized agent, this takes 8 to 12 minutes. On a messy one, 20 to 30 minutes. Both are routine. For a detailed breakdown of the full pre-alert workflow including ISF implications, see Pre-Alert to TMS Lot: The Ocean Import Workflow.
What each email type costs in minutes
Pre-alerts are not the only email type requiring TMS updates. Every job milestone sends at least one email. Here is the manual time per type, labeled as illustrative figures based on ops team feedback from active forwarding operations:
| Email type | Key fields to extract | Manual time per email |
|---|---|---|
| Pre-alert | MBL, HBL, vessel/voyage, ETD/ETA, container, parties | 8 to 12 min (clean) / 20 to 30 min (messy) |
| Booking confirmation | Booking number, vessel, ETD, port of loading, container type | 5 to 8 min |
| Arrival notice | Container available date, terminal, charges confirmed, free time start | 5 to 10 min |
| LFD notice | Container number, last free day date, detention rate | 3 to 5 min |
| Trucking coordination | Pickup appointment, chassis, driver, release number | 5 to 8 min |
At 100 ocean import jobs per month with 3 to 4 emails per job requiring TMS updates, that is 300 to 400 emails per month. At an average of 7 to 8 minutes per email (illustrative), the total is 35 to 53 hours per month. Per ops staff member. On data entry before any actual freight decisions happen.
The manual workflow vs an AI-assisted workflow
The distinction between these two paths is not about the judgment calls; those stay with the ops team regardless. The distinction is about the preparation work that happens before the judgment call.
Manual workflow: An email arrives. Someone on the team opens it, reads it, identifies the shipment, opens the TMS, finds the lot, and keys in each field. 14 steps, 8 to 30 minutes depending on document quality.
TIO-assisted workflow: TIO reads the inbound email the moment it arrives. It identifies which shipment the email belongs to using reference numbers, vessel details, and sender patterns. It extracts each field from the body and attachments, flags the ones it is unsure of, and pre-fills the TMS record. Your ops person starts from a pre-filled record instead of a blank one. Where the action is set for review, they verify the extracted fields and correct anything flagged as low confidence. Other actions run inside your rules.
The 14-step manual sequence becomes a short review of the pre-filled fields. The judgment is still there. The typing is not.
What this compounds to at volume
The time cost scales linearly with job volume. At 50 jobs per month it is a nuisance. At 100 it starts to constrain throughput. At 150 it becomes the ceiling that forces a hire.
At $35 to $50 per hour in fully loaded ops staff cost (illustrative range, varies by market), 40 hours per month of data entry runs between $1,400 and $2,000 per month. Per ops person. The work is not skilled. It is necessary and accurate, but it requires no judgment. The labor cost of doing it manually is not justified by what the task actually is.
For the broader case on reducing back-office hours without adding headcount, see Cut Freight Forwarder Back-Office Hours in 2026.
What to measure before deciding
The most useful number to have before evaluating any inbox automation tool is your actual per-email processing time. Not an estimate. A timed sample.
Pick one day. Have someone on the ops team log the time they start and finish processing each inbound shipment email. Count the steps. Note the email type and whether the documents were clean or required follow-up.
After one day you have: emails processed, minutes per email by type, and a rough monthly projection. That number, set against your current ops cost, is the right input for any build-vs-buy decision.
A freight forwarder AI software layer that closes the inbox-to-TMS gap does not require switching TMS platforms or retraining your team. It adds the extraction and preparation layer on top of what you already have. Each action is configured to run within your rules, go for review, or wait for a person’s reply. The 14 manual steps become a short review.
Request a demo to see TIO run a real pre-alert through the inbox-to-TMS workflow end to end.
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
How do I turn shipment emails into TMS entries automatically?
Put a read-and-match layer between the ops inbox and the TMS. It does 5 things on every email: copies it from a mail rule, classifies the email type, ties it to the right job by master bill, house bill or container number, reads each field from the body and attachments, and writes the fields through a TMS adapter. Each write step has its own on/off switch, and anything the rules cannot decide goes to a person, and the agent does not guess. The 14 manual steps of a pre-alert become 1 short check.
How many manual steps does it take to process one pre-alert email into a TMS record?
A clean pre-alert with complete documents takes 12 to 14 distinct steps: locating the email, opening attachments, reading the B/L for each field, cross-checking against the commercial invoice, opening the TMS, finding the correct lot, and keying each field individually before saving. On a clean email from a well-organized agent, this takes 8 to 12 minutes. On a messy one, with mismatched values, non-English attachments, or a missing field, it takes 20 to 30 minutes. Both are routine.
What is the inbox-to-TMS loop in freight forwarding?
The inbox-to-TMS loop is the gap between a shipment email arriving and the matching TMS record being updated with the data inside it. Every booking confirmation, pre-alert, arrival notice, and trucking coordination email contains structured fields that belong in the TMS. None of them arrive in a structured format, and none land in the TMS automatically. A person bridges that gap: reading, extracting, and keying. An ocean import job sends 3 to 4 of these emails through the loop, so 100 jobs a month means 300 to 400 trips across it by hand.
How much time per month does a 100-shipment operation spend on email data entry?
An operation running 100 ocean import jobs per month generates roughly 300 to 400 inbound emails requiring TMS updates across the job lifecycle (booking confirmations, pre-alerts, arrival notices, LFD and trucking coordination). At an average of 7 to 8 minutes per email (illustrative, based on ops team feedback from active forwarding operations), that is 35 to 53 hours per month in email data entry before any actual freight decisions get made. This estimate does not include the time to triage unread emails or handle exceptions.
Does TIO need access to my TMS to automate email data entry?
TIO does not replace your TMS. Its agents can read inbound documents and prepare records, but each TMS needs a tested adapter before an agent can write to it. TIO has production adapters for 2 TMS platforms. Any other platform must be scoped first. Each write step has its own switch: it runs within your rules, goes for review, or waits for a person's reply.
