AI Operators · Use cases

Document automation

Automate logistics document processing and TMS data entry from emails and PDFs. Extract shipment fields, validate documents and write approved data to your TMS.

Discuss document automation

Your SOPs. Your systems. Your team in control.

Starts with
Shipment documents received through agreed operational channels.
Works with
Document types, shipment context, field mappings, comparison rules and your connected TMS.
Completes with
Approved data entered into the operational workflow, or a document exception ready for review.

The operational opportunity

Process the document. Validate the data. Complete the operational entry.

Logistics document processing connects incoming emails and PDFs to accurate operational records. It includes document classification, shipment-data extraction, validation and automated TMS data entry—not just OCR or comparing two files.

Shipflow’s Document Operator classifies files, extracts shipment data, checks it against customer rules and compares related documents when needed. It enters validated data into your TMS and sends unclear or conflicting information to your team with the source documents attached.

Use the same approach across Ocean, Air and Road: identify the shipment, validate the source data and complete the system entry. Document types, field mappings and review rules are tailored to each operation.

Your team defines the source of truth, destination fields and approval rules once, before launch. The operator applies them to every document.

Document to TMS · Worked example

See what changes in the shipment record.

A revised Shipping Instruction arrives by email. The AI Operator matches the existing shipment, checks each field and prepares the TMS update. A changed package count needs review before this revision can proceed.

Illustrative workflow using fictional shipment data.

Incoming email + PDFSF-DEMO-1042
Customer instruction

Revised shipping instructions

“Please use the attached revision: 120 cartons, gross weight 2.4 metric tonnes. The route remains Shanghai to Rotterdam.”

shipping-instructions-v2.pdfPage 1 · Cargo detailsRevision 2 · Supersedes v1

Scroll across to compare all columns →

Field review before the TMS update
TMS destinationPDF · page 1Current TMS valueProposed action
Shipment referenceSF-DEMO-1042SF-DEMO-1042Match existing shipment
Port of loadingShanghaiShanghaiKeep existing value
Port of dischargeRotterdamRotterdamKeep existing value
Package count120 cartons100 cartonsReview 100 → 120
Gross weight2.4 metric tonnesNot enteredNormalize to 2,400 kg

The destination labels are illustrative. Field names, units and source-priority rules are mapped to your TMS during setup.

Review before writing

100 cartons → 120 cartons

The reviewer receives the old value, proposed value and source page together. In this example, the package-count change holds the revision until approval.

After approval

120 cartons · 2,400 kg

Recheck the record, apply the approved revision and verify the saved values. Retain the source version and review decision with the task.

When the input is not ready

  • Multiple matching shipments: ask the team to resolve the record match.
  • Unreadable or conflicting values: show the exact field and request clarification.
  • Duplicate file or uncertain write: check the existing record before processing again.

Complete when: the correct shipment contains the approved values and the system update is verified. Carrier submission is a separate workflow.

See how Shipflow reads and writes CargoWise data through eAdaptor

Workflow coverage

Process documents. Compare the right fields. Complete the data entry.

Configure the Document Operator around the job each document needs—not a single extraction template applied to every file.

Document processing

Collect documents from agreed channels, identify the document type and shipment, read the relevant content and manage revised versions.

Comparison and validation

Check required fields against related documents, TMS records and customer rules. Surface only the differences or omissions that require action.

TMS data entry and follow-through

Enter approved data into the shipment record and move the workflow to its next step.

Representative document types

  • Master Bill of Lading (MBL)
  • House Bill of Lading (HBL)
  • Shipping Order
  • Shipping Instructions
  • Pre-alert
  • Commercial Invoice
  • Packing List
  • Arrival Notice

How it works

From incoming file to usable operational data.

  1. Collect and identify the document

    Bring files from the agreed inbox, portal or workflow into one process. Classify the document type, match it to the shipment and distinguish the current version from superseded or duplicate copies.

  2. Extract and normalize the required data

    Read the fields the operational workflow needs, such as parties, references, routing, cargo, equipment, dates and document-specific values. Normalize the information to the formats expected by your TMS and SOP.

  3. Validate the document in context

    Check fields, formats and business rules against shipment records. Treat a document as ready only after it passes validation.

  4. Compare related documents when required

    Apply relationship-aware checks across documents such as MBLs and HBLs, Shipping Orders and Shipping Instructions, or commercial invoices and packing lists. Define which values should correspond, which can legitimately differ and which discrepancies require action.

  5. Enter approved data or route the exception

    Write validated values to the TMS. If information is missing, unclear or conflicting, send the source file and exact fields needing review to the responsible person.

Human control

Automate the routine. Keep judgment with your team.

Your team sets the SOPs, system access and approval rules before launch. AI Operators act within those limits and escalate cases that need a decision.

Execute within agreed rules

  • Collect, classify and match documents from the agreed sources.
  • Extract and normalize the fields required by each document workflow.
  • Validate documents against shipment records and related files.
  • Enter approved data into the TMS and advance the workflow.

Escalate when needed

  • Required documents or fields are missing.
  • Source information is unclear or does not pass validation.
  • A discrepancy or revision falls outside the approved handling rules.
  • The authoritative source is unclear or multiple documents conflict.
  • A correction, submission or downstream action requires human approval.
Explore security and human control

Customer result

AI execution at Asia Shipping.

Less time spent on document comparison
97%+

Asia Shipping uses Shipflow AI Operators to automate document comparison, including MBL and HBL checks. The deployment reduces time spent on this task by 97%+. This is evidence for the comparison task, not a measured result for TMS data entry or all document processing.

This result relates to the customer workflow described. Results depend on workflow scope, input quality and deployment configuration.

“Prior to Shipflow, our operators had to manually compare data fields between MBL and HBL three to four times per shipment, which was extremely time-consuming. With Shipflow, this process is now fully automated by AI.”

Jack YeungIT Manager at Asia Shipping
Read the customer story

Getting started

Build around the way your operation works.

Choose the document workflow

Bring representative documents, including scans, attachments, revisions and difficult examples. Define whether the first workflow is processing, comparison, TMS data entry or a connected sequence, and agree what completed work means.

Map fields, relationships and sources of truth

Specify the data required from each document, how documents connect to shipments and one another, and which source takes precedence when values conflict. Identify the exact destination fields in the TMS.

Set validation and write controls

Define the checks, exception routes and approvals that apply before information is entered or an external action is taken. Confirm the supported input channels, file formats, system access and write-back permissions for the deployment.

Explore systems and integrations
Plan testing and rolloutHow document workflows are priced

Agree the baseline before the pilot.

Compare the same document types and validation rules before and after deployment. Report the sample size, time period, exclusions and review rate alongside the result.

Touchless completion
Eligible document tasks completed and verified without human intervention ÷ all eligible document tasks.
Manual effort
Human handling minutes per document, including review, corrections and rework.
Receipt-to-record time
Elapsed time from document receipt to verified TMS entry.
Data quality
Required field values found correct in a reviewed sample ÷ all required field values checked.

These are measurement definitions, not promised results.

Common questions

Before you put an AI Operator to work.

How is this different from OCR or data extraction?

Optical character recognition (OCR) converts an image into readable text. Extraction identifies useful fields. Shipflow connects those steps with validation, cross-document checks and actions in the operational workflow, subject to your rules and system access.

Can Shipflow compare MBLs and HBLs?

Yes. MBL/HBL comparison is part of the document-comparison deployment at Asia Shipping. The fields, document relationships and exception rules for another implementation are configured around that operation’s requirements.

Can Shipflow process documents and enter data into our TMS?

Yes. Shipflow reads documents, checks extracted fields against shipment context and writes approved values into the connected TMS. For CargoWise, the workflow can read and write through eAdaptor. Your team defines the document types, field mappings, access and approval rules before deployment.

Can we automate logistics data entry from emailed PDFs?

Yes. An email and PDF can start a document-processing workflow that matches the shipment, extracts the required fields, validates them and updates the TMS. Test the actual file formats and layouts used by your team, including scans, revisions and incomplete documents. Unreadable or conflicting information goes to review instead of being treated as valid data.

Which logistics documents can be included?

Workflows can be configured around documents such as MBLs, HBLs, Shipping Orders, Shipping Instructions, pre-alerts, commercial invoices, packing lists and arrival notices. Supported file formats, fields and actions are confirmed for the selected workflow and systems.

Does every difference mean a document is wrong?

No. Different document roles can lead to legitimate differences. During setup, your team defines which fields should correspond, which differences are expected and which require investigation. The operator applies those rules rather than treating every difference as an error.

How do revised documents and duplicate attachments get handled?

The workflow matches the file to the existing shipment, checks its version and compares it with the current record. A revised value follows your review rules. Duplicate files should not create a second shipment or repeat an update; an uncertain system response is reconciled before retrying.

Do we have to automate every document type at once?

No. Start with one repeatable document workflow and a clear validation standard. Expand to additional types after the team has reviewed the results and agreed the relevant rules, exceptions and system connections.

Start with one workflow

Start with the document processing or data-entry workflow your team keeps repeating.

Start with a free 15-minute AI consultation. Describe the document your team rekeys most often, the destination system and the checks it needs. We will map a first workflow around those requirements.

Discuss document automation