Cloud TMS platforms are the workhorse for a large segment of U.S. freight forwarders running ocean import operations. There’s a reasonable chance your TMS is what you’re filing ISFs through right now.
A cloud TMS does a lot. But there are parts of the ISF workflow it doesn’t automate, and for small teams, those gaps are where most of the manual labor lives. This post covers what a cloud TMS handles natively, where you’re still doing manual work, and what TIO does about it.
What does my TMS handle for ISF?
A full cloud TMS covers lot management, filing (ISF and entry), AES for exports, billing, and reporting. For ISF specifically, most platforms provide:
- A structured data entry screen for the 10 ISF fields
- Direct CBP filing via the ABI network; you fill in the fields, the TMS submits to CBP
- Acknowledgment tracking: the TMS reads CBP’s response and updates the lot status
- Rollover handling: when a vessel rolls, you update the ETD and refile
That’s solid functionality. Your TMS screen is authoritative. It’s the filing system of record.
What does my TMS not do?
Your TMS doesn’t read your email. It doesn’t extract data from a booking confirmation PDF. It doesn’t look at a packing list and map shipper name to the Seller field.
Every time a new booking arrives, someone on your team has to:
- Open the email from the overseas agent or shipper
- Identify the carrier, vessel, ETD, container number
- Open the commercial invoice and packing list PDF
- Identify manufacturer, seller, HTS code, country of origin
- Open the TMS, create a new lot
- Type each field in
For a clean, well-formatted booking with standard factory documents, that’s 20 to 30 minutes. For a messy email with attachments in Chinese, three follow-up emails to the factory, and an HTS code that doesn’t match the commodity description, it’s 60 to 90 minutes.
Multiply by 80 lots a month. That’s 27 to 120 hours of manual data entry. For a 3-person back office, that’s not a small number.
Where do ISF errors happen?
The most common ISF error on manual entry isn’t laziness. It’s document ambiguity.
HTS code errors happen when the factory writes a vague commodity description (“household goods,” “plastic parts,” “hardware”) and the filer has to interpret it. The TMS doesn’t help with this; the filer picks the code.
Manufacturer vs. seller confusion happens because Chinese factories often sell through trading companies. The seller on the invoice is the trading company. The manufacturer is the factory. They’re different entities, different addresses, and the ISF requires both. The TMS has fields for both. Filling them correctly requires reading the documents carefully, something that’s easy to shortcut under time pressure.
Copy-paste transpositions: a digit flipped in the HTS code, a city name pasted into the wrong field, are hard to catch when you’re working through 15 lots before 5 PM.
Most TMS platforms validate fields against CBP’s formatting rules (field lengths, code formats) but they don’t validate the semantics. If you put the trading company name in the Manufacturer field, the TMS accepts it.
What does TIO add to my TMS?
TIO is the operating layer that sits between your email inbox and your TMS. When a booking email arrives, TIO reads it and its attachments, extracts the job fields, and presents them to your team for review. After review and approval, TIO creates the lot in your TMS via API; the team doesn’t need to open the TMS for initial lot creation at all.
For each field, TIO shows:
- The extracted value
- The confidence score
- The source text in the document where it came from
Low-confidence fields are flagged. The operator can correct any field before approving. Nothing goes to the TMS without human sign-off.
What this means in practice:
- Email arrives from Shanghai at 9 PM
- TIO extracts fields immediately
- Operator reviews in the morning: 8 minutes instead of 45
- TMS lot is created via API, lot number stored in TIO audit log
- CBP deadline is tracked from intake
The filer is still in the loop. That’s not a limitation. It’s the design. ISF filing is regulated and the filer of record carries liability. TIO reduces the labor without removing the human judgment.
How does TIO integrate with my TMS?
TIO integrates with your TMS via API at arm’s length. No TMS partnership or additional TMS licensing required. TIO posts the ISF data to your TMS using the standard API, reads the lot number back, and polls for CBP status. Your team doesn’t need to change anything about how your TMS is configured.
This also means TIO works with your existing setup. If you’re already using a cloud TMS and have a licensed broker on your filing account, TIO connects to that arrangement without requiring you to change your broker relationship or move to a new TMS.
What is TIO not?
TIO is not a replacement for your TMS. Your lots still live there. Your team still files through it. CBP still receives submissions via your TMS’s ABI connection.
TIO is the AI operating system that sits between your inbox and your TMS. It handles intake, extraction, job organization, and review workflow so the 45-minute manual process becomes a 10-minute review. As the job matures, TIO adds a natural-language query interface so any team member can ask about lot status, email history, or invoice data without opening your TMS screens.
For a timed walkthrough of the manual email-to-TMS steps this replaces, see How Much Time Are You Spending Moving Data from Emails into Your TMS?. For a full breakdown of what the inbox-to-TMS layer covers, see the solution page.
Ready to see it work on a real booking email? Book a 15-minute demo.
Frequently asked questions
Does my TMS automate ISF filing?
Most cloud TMS platforms provide a structured data entry screen and direct CBP submission via the ABI network. They do not read your email or extract data from booking confirmations and commercial invoices. That extraction step is still manual.
Where does manual ISF work actually happen?
The manual work is in the intake step: opening the booking email, reading the commercial invoice and packing list, identifying manufacturer vs. seller, finding the HTS code, and typing each field into your TMS. The TMS submits to CBP; the ops team does all the data gathering before that.
What causes ISF errors on manual entry?
The most common errors are HTS code misclassification from vague commodity descriptions, manufacturer vs. seller confusion on Chinese factory shipments, and copy-paste transpositions. Most TMS platforms validate field format but not field semantics.
How does TIO fit into an existing TMS workflow?
TIO sits between your email inbox and your TMS. It reads each inbound booking email and attachment, extracts the ISF fields, and presents a pre-filled review to your team. After review and approval, TIO writes the lot to your TMS via API. Your team still files through your existing TMS. Nothing changes about your CBP connection or filer relationship.