How to Automate Shipment Creation From Pre-Alert Emails

A pre-alert looks like an email with a few attachments.

For an ocean import operator, it can mean the beginning of an entire shipment workflow.

The operator opens the message, checks the documents, identifies the master bill and house bill, copies shipment details into the freight management system, uploads the files, adds the container, starts tracking, notes what is missing, and follows up with the overseas agent.

None of these steps is especially complicated. The problem is how often they repeat.

When a team receives pre-alerts throughout the day, manual shipment creation becomes a steady stream of data entry and checking. It also delays downstream work because tracking, document preparation, and exception monitoring cannot begin until the shipment record is ready.

AI can connect the pre-alert directly to the work that follows. It can read the email and attachments, extract the shipment information, check for an existing record, prepare or create the shipment, save the documents, start tracking, and bring missing or conflicting information to the operator.

The operator remains in control. The difference is that the operator begins with prepared work instead of an untouched email.

What does it mean to automate shipment creation from a pre-alert?

Automated shipment creation is the process of turning the information in a pre-alert email and its attachments into a structured shipment record with the appropriate documents and next actions.

A complete workflow may include:

• Identifying the email as a pre-alert
• Reading the email body and attached freight documents
• Extracting shipment, routing, container, and party information
• Checking whether the shipment already exists
• Creating a new record or updating the correct existing record
• Saving and organizing the attachments
• Starting container or bill tracking
• Identifying missing, inconsistent, or low-confidence information
• Sending the prepared work to an operator for review when required

This is different from simply summarizing the email. A summary helps someone read faster. Shipment creation automation helps complete the operational work.

Why pre-alert processing creates so much manual work

A pre-alert is rarely a single standardized document.

One overseas agent may place the shipment details in the email body. Another may attach a master bill, several house bills, a commercial invoice, a packing list, a booking confirmation, and a spreadsheet. Naming conventions, layouts, reference numbers, and levels of completeness vary by agent, customer, trade lane, and shipment.

The operator must turn those different inputs into one consistent record.

That usually requires several kinds of work:

• Interpretation: determining what was sent and which documents belong together
• Extraction: locating the correct shipment fields across the email and attachments
• Matching: checking whether the shipment or bill is already in the system
• Validation: comparing details across documents and identifying conflicts
• Entry: creating the shipment, parties, routing, containers, and references
• Organization: saving the attachments under the correct record
• Follow-up: asking for missing information and monitoring the next milestone

Traditional automation works best when the input is already structured. Pre-alerts are difficult because the information is useful but arrives in inconsistent forms.

AI is valuable here because it can interpret unstructured messages and documents before applying the forwarder's validation and workflow rules.

What information can be extracted from a pre-alert?

The exact fields depend on the company's FMS, workflow, and shipment type. For an ocean import shipment, common information may include:

• Master bill number
• House bill number
• Booking or shipment reference
• Container number and container type
• Carrier or steamship line
• Vessel and voyage
• Port of loading
• Port of discharge
• Place of receipt and final destination
• Estimated departure and arrival dates
• Shipper, consignee, and notify party
• Package count, weight, measurement, and cargo description
• Incoterms or delivery instructions when provided
• Attached bills of lading, commercial invoices, packing lists, and other documents

Extraction is only the first step. The information must also be placed in the correct fields, associated with the correct shipment, and checked against other available information.

For example, a container number may appear in both the email body and the master bill. If the two values do not match, the system should not silently choose one. It should show the conflict and ask for review.

How AI can automate the workflow

1. Identify the pre-alert

The workflow begins when a message reaches the connected operational inbox.

AI can examine the sender, subject line, body, thread history, attachments, and shipment references to determine whether the message is a new pre-alert, a revision to an existing pre-alert, or another type of operational email.

This distinction matters. A revised document should not automatically create a second shipment.

2. Read the email and attachments together

Important shipment information is often divided across several files.

The house bill may contain party and cargo details. The master bill may contain the carrier routing and container information. The email body may explain a special instruction or identify a document that will follow later.

The system should treat the email and attachments as one operational package, while preserving the source of each extracted value.

3. Match the information to existing records

Before creating anything, the workflow should search for an existing shipment using reliable identifiers such as the master bill, house bill, container number, booking reference, customer reference, or a combination of fields.

If a match is found, the new information may belong to an existing record. If no match is found and the required fields are present, the system can prepare or create a new shipment.

Duplicate prevention is a core part of automation. Faster data entry is not useful if it creates duplicate shipments that operators must clean up later.

4. Validate the shipment data

A reliable workflow applies operational rules before information is written into the FMS.

Validation may include:

• Checking the format of bill and container numbers
• Confirming that required fields are present
• Comparing values found in different attachments
• Checking that port and carrier information are consistent
• Identifying a date that appears out of sequence
• Flagging multiple possible matches
• Showing low-confidence fields for operator review

The objective is not to force every email through an automatic path. It is to complete the clear, repetitive work and surface the uncertain parts.

5. Create or update the shipment in the FMS

Once the data passes the required checks, AI can map it to the correct fields in the existing freight management system.

Depending on the workflow and approval settings, the system may create the shipment automatically, prepare a draft record for operator approval, or update an existing shipment with new information.

The FMS remains the system of record. AI reduces the manual work required to move information from the inbox into that system.

6. Save the documents and start the next work

Shipment creation should not be the end of the workflow.

After the record is ready, the system can save the source documents, add the container or bill reference to tracking, identify missing documents, prepare a reply to the agent, and schedule the next operational check.

This is where automation becomes more valuable than faster data entry. One incoming email can start several connected actions without requiring the operator to move between the inbox, FMS, document folders, and carrier portals.

7. Bring exceptions to the operator

Some pre-alerts will be complete and consistent. Others will contain missing references, conflicting dates, unreadable attachments, unexpected routing, or more than one possible shipment match.

The workflow should make those exceptions visible, explain what needs attention, and show the original source information.

Good automation does not hide uncertainty. It reduces routine work so the operator has more time to resolve the cases that require experience and judgment.

An example ocean import workflow

An overseas agent sends a pre-alert for an ocean import shipment. The email includes a master bill, two house bills, a commercial invoice, and a packing list.

Without automation, an operator may need to:

• Open the email and each attachment
• Search the FMS for the bill or booking reference
• Create the shipment and house bill records
• Enter the routing, parties, cargo, and container details
• Upload and organize the documents
• Check which required information is missing
• Visit a carrier portal and start tracking
• Reply to the overseas agent
• Set a reminder for the next milestone

With AI operations software, the email can initiate the workflow.

The system identifies the message as a pre-alert, reads the attachments, detects the master and house bill relationship, extracts the shipment details, checks for an existing record, prepares the shipment structure, saves the documents, starts tracking, and presents any missing or conflicting information to the operator.

The operator reviews the prepared work, corrects anything necessary, and approves the next step.

The same operational result is reached with fewer manual handoffs and an earlier start on tracking and exception monitoring.

What should remain under operator control?

Not every decision should be automatic.

A freight forwarder should be able to decide which actions can happen automatically and which require approval. Human review is especially important when:

• A required field is missing
• Two documents contain conflicting information
• The system finds more than one possible shipment match
• A new party or unusual instruction appears
• The shipment has a high operational or financial impact
• The action would send an external communication
• The workflow falls outside the company's approved rules

Operators should also be able to see what information was received, where each value came from, what the system prepared or changed, and who approved the action.

Automation should create clearer control, not less visibility.

How to start with a practical pilot

A forwarder does not need to automate every pre-alert workflow at once.

A focused pilot can begin with one high-volume, reasonably consistent workflow, such as ocean import pre-alerts from a small group of overseas agents.

A practical pilot should define:

• Which inboxes and email types are included
• Which shipment fields are required
• Which documents should be recognized and saved
• How existing shipments are matched
• Which validation rules must pass
• Which actions require operator approval
• What should happen when information is missing or uncertain
• Which downstream actions should start after shipment creation

The team can then measure the workflow itself:

• How much operator time is spent per pre-alert
• How many fields require manual correction
• How often duplicates or mismatches occur
• How quickly tracking begins after the email arrives
• How many exceptions require operator attention
• How consistently documents and shipment records are prepared

The purpose of the pilot is not to prove that AI can read an email. It is to prove that the complete shipment creation workflow becomes faster, more consistent, and easier to control.

From pre-alert to prepared shipment

Pre-alert processing is a strong starting point for freight operations automation because the input is frequent, the manual work is visible, and the downstream actions are clear.

The email contains the information needed to begin. The FMS provides the structure. Carrier data supports monitoring. The operator provides the judgment for exceptions and important decisions.

AI can connect those pieces.

Instead of asking an operator to rebuild the shipment by hand, the workflow can arrive prepared: the record created or updated, the documents organized, tracking started, and the unresolved questions clearly identified.

The pre-alert is still the starting point. It no longer has to be the beginning of another round of manual work.

Frequently asked questions

Can AI create a freight shipment from a pre-alert email?

Yes. When the email and attachments contain enough reliable information, AI can extract the shipment details, check for an existing record, and create or prepare a shipment in the connected FMS. Missing or conflicting information should be routed to an operator for review.

Can AI read multiple attachments in one pre-alert?

Yes. A workflow can read the email body and multiple attachments together, including bills of lading, commercial invoices, packing lists, booking documents, and spreadsheets. It should preserve the source of each extracted value and identify conflicts between documents.

How does automation avoid duplicate shipments?

Before creating a new record, the system should search existing shipments using identifiers such as master bill, house bill, container number, booking reference, and customer reference. Multiple or uncertain matches should require review instead of automatic creation.

Does automated shipment creation replace the FMS?

No. The FMS remains the system of record. AI operations software helps move information from emails and attachments into the correct shipment record and starts the connected work that follows.

Should every pre-alert be processed automatically?

Not necessarily. Complete, consistent pre-alerts may follow a highly automated path. Missing information, conflicting values, unusual instructions, or high-impact actions should be brought to an operator with the relevant context.

What is the best way to begin?

Start with a frequent pre-alert workflow that has clear required fields, known document types, and measurable manual effort. Define the validation and approval rules first, then expand after the team confirms that the prepared work is accurate and useful.

See how NavLogic turns pre-alerts into prepared shipment work

NavLogic connects to the inbox your team already uses. It reads operational emails and attachments, creates or updates shipments in the existing workflow, starts tracking, prepares the next actions, and brings exceptions to the operator for review. Your team keeps control of the operation.

Book a demo