EFC Cloud is the workhorse TMS for a large segment of small U.S. freight forwarders. If you’re running ocean import operations with 20–200 lots a month, there’s a reasonable chance EFC is what you’re filing ISFs through.
EFC 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 EFC handles natively, where you’re still doing manual work, and what TIO does about it.
What EFC Cloud handles
EFC is a full TMS: lot management, filing (ISF and entry), AES for exports, billing, reporting. For ISF specifically, EFC provides:
- A structured data entry interface for the 10 ISF fields
- Direct CBP filing via the ABI network — you fill in the fields, EFC submits to CBP
- Acknowledgment tracking — EFC reads CBP’s response and updates the lot status
- Rollover handling — when a vessel rolls, you update the ETD in EFC and refile
That’s solid functionality. The EFC screen is authoritative — it’s the filing system of record.
What EFC does not do
EFC 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 Shanghai
- Identify the carrier, vessel, ETD, container number
- Open the commercial invoice and packing list PDF
- Identify manufacturer, seller, HTS code, country of origin
- Open EFC, create a new lot
- Type each field in
For a clean, well-formatted booking with standard factory documents, that’s 20–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–90 minutes.
Multiply by 80 lots a month. That’s 27–120 hours of manual data entry. For a 3-person back office, that’s not a small number.
Where 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. EFC 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. EFC 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.
EFC validates fields against CBP’s formatting rules (field lengths, code formats) but it doesn’t validate the semantics. If you put the trading company name in the Manufacturer field, EFC accepts it.
What TIO adds
TIO is the operating layer that sits between your email inbox and your TMS. When a booking email arrives from Shanghai, 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 EFC via API — the team doesn’t need to open EFC 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 broker can correct any field before approving. Nothing goes to EFC without human sign-off.
What this means in practice:
- Email arrives from Shanghai at 9 PM
- TIO extracts fields immediately
- Broker reviews in the morning — 8 minutes instead of 45
- EFC 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.
The EFC API
One thing worth noting: TIO integrates with EFC via API at arm’s length. No EFC partnership, no EFC licensing required. TIO posts the ISF data to EFC using the same API that other integrations use, reads the lot number back, and polls for CBP status. Your team doesn’t need to change anything about how EFC is configured.
This also means TIO works with your existing TMS. If you’re already using EFC Cloud and have a licensed broker on your filing account, TIO connects to that setup without requiring you to change your broker relationship or move to a new TMS.
What TIO is not
TIO is not a replacement for EFC. Your lots still live in EFC. Your team still files through EFC. CBP still receives submissions via EFC’s ABI connection.
TIO is the operating brain 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.
Ready to see it work on a real booking email? Book a 15-minute demo.