A standard ocean import job runs through five to seven stages from the first booking email to the final invoice: rate and booking, pre-alert and document intake, ISF and customs entry, arrival and last-free-day management, drayage and pickup, delivery and POD, and invoice reconciliation. Across that 30-to-60-day lifecycle the job generates 30 to 60 inbound emails, each from a different sender in a different format, each carrying fields that belong in the TMS. The highest-cost stage is pre-alert processing: at 100 jobs per month it alone costs 13 to 20 hours per ops staff member. Most ops hours do not go to freight decisions. They go to reading email and retyping its contents into the TMS, stage after stage.
A freight forwarding job does not begin when cargo moves. It begins when an email arrives.
From that first inbound rate request to the delivery confirmation and final invoice reconciliation, a single ocean import job passes through five to seven distinct stages, each generating its own emails, each requiring its own TMS updates, each carrying its own deadlines. Understanding the full sequence is the prerequisite for understanding where ops hours go and where they can be recovered.
This post walks the complete lifecycle of a standard ocean import job. Each stage covers the emails it generates, the data fields it requires, and what goes wrong when any step is processed late.
Stage 1: Rate request and booking confirmation
The lifecycle starts with an inbound rate request from a shipper, importer, or overseas agent. The request contains the core shipment parameters: origin and destination ports, mode (ocean FCL or LCL, air), commodity description, weight and volume, incoterms, and cargo ready date.
This becomes the first record in the TMS: a rate inquiry or quote entry. The ops team prices the lane, responds with rates, and the back-and-forth that follows is the commercial foundation of the job.
When the rate is agreed and the booking is placed with the carrier, the booking confirmation arrives. It carries the most important identifiers in the job’s early life:
- Master Bill of Lading (MBL) number or booking reference
- Carrier name and SCAC code
- Vessel name and voyage number
- Estimated departure date (ETD) from port of loading
- Port of loading and port of discharge
These fields bind to the main TMS lot record. A booking confirmation that sits unprocessed for 24 hours means the lot has no vessel, no ETD, and no MBL — any downstream step that depends on those fields is blocked.
Data required at this stage: lane, mode, commodity, weight/volume, incoterms, cargo ready date, MBL, vessel, voyage, ETD, POL, POD.
Stage 2: Pre-alert and document intake
The pre-alert is the highest-data-density email in the ocean import lifecycle. It arrives from the overseas agent after the cargo is loaded and typically contains:
- HBL number (house bill of lading issued by the forwarding agent)
- MBL number confirmed
- Container number, container type, and seal number
- Shipper, consignee, and notify party names and addresses
- Commodity description, package count, gross weight
- Freight charges and charge breakdown
- ETA at destination port
- Attached documents: commercial invoice, packing list, certificate of origin, sometimes the draft bill of lading
Processing a pre-alert manually requires reading the email, opening multiple PDF attachments, identifying the relevant fields across formats that vary by agent and origin country, switching to the TMS, locating the correct lot, and typing each field in.
At 100 jobs per month with one pre-alert per job, that single email type costs 13 to 20 hours of ops time every month. For a detailed time-per-step breakdown, see How Much Time Are You Spending Moving Data from Emails into Your TMS?.
Data required at this stage: HBL, container number and type, seal number, all parties (shipper/consignee/notify), commodity, package count, weight, freight charges, ETA, all attached documents.
Stage 3: ISF filing and customs entry
Before the vessel departs the foreign port, the ISF must be submitted to CBP. Under 19 CFR Part 149, the Importer Security Filing is due no later than 24 hours before cargo is laden aboard the vessel. The ISF requires 10 fields from the importer, including seller, buyer, importer of record, consignee, manufacturer or supplier, ship-to party, country of origin, and HTS code.
The ops team’s job at this stage is data preparation: finding the manufacturer and seller entities in the commercial invoice, confirming the HTS classification, and pre-filling the ISF screen. The customs broker of record reviews every field and submits to CBP. No automated path bypasses that review. The filer of record carries CBP liability for every submission.
For how the data extraction step at this stage interacts with the TMS, see TMS Cloud ISF Automation: The Manual Gap.
After the vessel arrives, the customs entry (CBP Form 7501) follows. The entry covers the full dutiable value, HTS classifications, tariff rates, and any applicable duties. For most small forwarders, customs entries on ocean import are handled by a licensed broker outside the firm. The forwarder’s role is assembling and delivering the entry documents.
Data required at this stage: ISF 10 fields (seller, buyer, IOR, consignee, manufacturer, ship-to, country of origin, HTS, container stuffing location, consolidator), entry value, tariff classification evidence.
Stage 4: Arrival notice and last free day management
The arrival notice from the carrier or terminal confirms the vessel has arrived and the container is available for pickup. This starts the free-time clock: the terminal grants a defined number of free days before storage charges begin.
The last free day is the final date on which the container can be picked up without triggering detention charges. An LFD notice that sits unread in a shared inbox for 24 to 48 hours is a detention invoice waiting to be issued.
At this stage, the LFD date must be entered into the TMS and flagged as a deadline for trucking coordination. Jobs with imminent LFDs require immediate action. Jobs with comfortable windows can be processed in the normal queue. The distinction is invisible in a shared inbox with no triage layer.
Data required at this stage: container availability date, free time days, LFD date, terminal name and location, container release status.
Stage 5: Drayage coordination and pickup
Once the container is available and the customs release is confirmed, drayage must be arranged: carrier selection, chassis order, pickup appointment at the terminal, container release authorization.
This stage generates its own email chain: rate requests to drayage carriers, quote responses, pickup confirmations, driver assignments. Unlike most of the upstream stages, the drayage coordination loop is not driven by an overseas agent. It is driven by the ops team emailing carriers and tracking responses across what are often multiple concurrent jobs.
For how the email-based trucking rate management problem compounds at scale, see The Trucking Quote Gap Freight Software Ignores.
Data required at this stage: selected drayage carrier, quoted rate, chassis order number, pickup appointment date and time, driver name and contact, container release number.
Stage 6: Delivery confirmation and job close-out
Delivery confirmation arrives once the cargo reaches the consignee. Proof of delivery (POD) is the final document in the job file. The POD date and receiver confirmation close the operational portion of the lot in the TMS.
Final invoice reconciliation follows: comparing the carrier’s actual invoice against the charges agreed at booking, checking that surcharges were applied correctly, and verifying that any accessorial fees are documented before the invoice is approved for payment. This step surfaces the rate discrepancies and undisclosed surcharges that erode margin on individual jobs.
Document archiving closes the lot. All documents — commercial invoice, packing list, bill of lading, ISF acknowledgment, customs entry, POD — are linked to the TMS record before the job is marked complete.
Data required at this stage: POD date, consignee receiver name, final invoice amounts, any variance from quoted charges, document links.
The inbox-to-TMS gap across the full lifecycle
The six stages above describe a job that spans 30 to 60 days and generates 30 to 60 emails. Each email that touches a stage carries structured fields that belong in the TMS. None of it arrives there automatically.
The ops team is the bridge. They read each email, identify which job it belongs to, extract the relevant fields, open the TMS, find the lot, and type in the data. For a timed breakdown of every manual step in this process, see The Freight Forwarder Email Infrastructure Problem.
At 100 jobs per month with 3 to 4 emails per job requiring TMS updates, and 7 to 8 minutes per email, that is 35 to 50 hours per ops staff member per month on data transcription alone. Across a two-person team at 150 jobs per month, it is 50 to 75 combined hours every month before any actual freight decisions happen.
That ceiling is not a judgment ceiling. It is not a skills gap. It is a math problem: the team runs out of processing hours before it runs out of jobs to process.
Definition: the inbox-to-TMS loop
The inbox-to-TMS loop is the recurring manual cycle that runs throughout the freight forwarding job lifecycle. It consists of five steps that repeat for every inbound shipment email:
- Read the inbound email (and open any PDF attachments)
- Identify which job the email belongs to using reference numbers, vessel details, and sender patterns
- Extract the structured data fields relevant to this email type
- Open the TMS, locate the correct lot, and enter each extracted field
- File or archive the email
This cycle repeats hundreds of times per month for a small forwarder running 80 to 150 jobs. Systematizing this loop is the single highest-leverage change available to a small freight forwarding operation before it adds headcount.
What changes when the inbox-to-TMS layer exists
An AI layer that handles the inbox-to-TMS loop reads each inbound email on arrival, identifies the job it belongs to, extracts the relevant fields, and pre-fills the TMS record for the ops team to review. The team still approves every write. Nothing reaches the TMS without human sign-off.
What changes: the team opens a pre-filled record to verify rather than a blank record to populate. The 8-minute manual cycle on a pre-alert becomes a 2-minute review. Across a full month of jobs, the recovered hours are the capacity that lets the same team handle more volume without adding a dedicated data-entry person.
For how this works specifically at small forwarder scale, see What Small Freight Forwarders Actually Need from AI. For how the math looks across a team before and after the transcription step is removed, see Scaling a Freight Forwarding Operation Without Hiring.
The right architecture for the full lifecycle
The freight forwarding job lifecycle is already defined. The stages, the emails, the required data fields, the deadlines — none of these change. What varies across operations is how much of the movement between stages is manual transcription and how much is systematized.
The operations team is not the bottleneck. The data pipeline is. The team that builds an inbox-to-TMS layer between their email and their TMS converts their ops team from transcribers to reviewers and decision-makers. Every judgment call still goes through them. The prep work that consumes them before the call gets automated.
That is the shift that lets a small forwarding operation grow volume without the next hire being a direct consequence of data-entry throughput.
A live demo runs a real pre-alert through the full inbox-to-TMS workflow in about twenty minutes. For an overview of how TIO sits between your inbox and your TMS across every stage of the job lifecycle, see the freight forwarder AI solution page.
Frequently asked questions
How many stages does a freight forwarding job have?
A typical ocean import job has five to seven stages from booking to close-out: rate request and booking confirmation, pre-alert and document intake, ISF filing and customs entry, vessel arrival and LFD management, drayage and pickup, delivery and POD, and final invoice reconciliation. Each stage generates one to several emails containing structured data that needs to enter the TMS.
Where do most ops hours go in a freight forwarding job?
The highest-cost routine step in the ocean import lifecycle is pre-alert processing: reading the email, extracting the HBL, container number, vessel, ETD, ETA, shipper, consignee, and freight charges from the body and PDF attachments, and entering each field into the TMS lot. At 100 jobs per month, pre-alert processing alone costs 13 to 20 hours per ops staff member every month.
What is the inbox-to-TMS gap in freight forwarding?
The inbox-to-TMS gap is the manual step between receiving a shipment email and getting its data into the TMS. Every pre-alert, arrival notice, and booking confirmation contains structured fields that belong in the TMS record, but none of it arrives there automatically. A person reads each email, finds the relevant fields, opens the TMS, and types them in. At 100 jobs per month across a two-person ops team, this step alone costs 50 to 75 combined hours every month.
How long does an ocean import job lifecycle take?
A standard ocean import job from first booking email to final delivery runs 30 to 60 days depending on origin and routing. A transshipment from East Asia to the US West Coast might run 15 to 25 days. During that time the job generates 30 to 60 emails, each arriving from a different sender in a different format, each containing data that belongs in the TMS.