Skip to content
Case Study Hellmann Worldwide Logistics

How Hellmann Automated Their 4PL Control Tower with AI

How Hellmann Worldwide Logistics automated their 4PL control tower operations with AI — achieving 60% processing time reduction, 50% AI cost reduction, and zero manual TMS entry.

60% Processing time reduction

Client Overview

About Hellmann Worldwide Logistics

Hellmann Worldwide Logistics is a global freight forwarder headquartered in Osnabrück, Germany, with 500+ offices across 170+ countries and more than 13,000 employees. Hellmann operates sea freight, air freight, road, and rail services worldwide, handling millions of shipments annually. Their 4PL control tower function manages complex multi-modal supply chains for enterprise clients, requiring high-volume, accurate document processing as the operational foundation.

The Challenge

What They Were Dealing With

Hellmann's 4PL control tower operations received daily document bundles from suppliers — commercial invoices, airway bills, packing lists, customs compliance forms — often packaged as PDFs of 200–300 pages per batch. Two operators each spent 2–3 hours per morning manually downloading, splitting, reading, and re-keying data into spreadsheets before it could be entered into CargoWise. The manual process followed a rigid sequence: download email attachments, split multi-hundred-page PDFs into individual documents, identify document type, extract relevant fields, enter data into spreadsheets, and finally re-key everything into CargoWise. New suppliers required 1–3 weeks of engineering effort to map their document formats into the existing workflow. During peak season, document processing backlogs regularly exceeded 24+ hours, delaying downstream operations and creating compliance risk. The entire process lacked any audit trail — there was no systematic record of what was processed, when, or by whom, making error investigation and compliance reporting extremely difficult.

What We Built

The System

1

Email monitoring agent — monitors the ops inbox, detects supplier document emails, auto-downloads attachments

2

AI document filter — lightweight classifier removes irrelevant pages (cover sheets, blank pages, duplicates), reducing AI processing costs by 50%

3

Extraction engine — LangGraph-orchestrated AI pipeline extracts structured fields from invoices, AWBs, packing lists, and compliance documents

4

Validation layer — extracted data checked against business rules before any data moves downstream

5

CargoWise XML push — validated data formatted as CargoWise-compatible XML and pushed directly into TMS via API

6

Excel report generation — formatted compliance reports auto-generated for the ops team

7

Self-learning supplier onboarding — new supplier formats mapped automatically with no engineering effort

System Architecture

How It All Connects

1

Email Inbox monitoring via IMAP/Microsoft 365 connector

2

Email Monitor Agent — detects supplier document emails, auto-downloads attachments

3

PDF Splitter — separates multi-hundred-page PDFs into individual documents

4

AI Document Filter — lightweight classifier removes irrelevant pages (cover sheets, blanks, duplicates), reducing AI processing costs by 50%

5

Extraction Engine — LangGraph-orchestrated pipeline combining Azure Document Intelligence, custom OCR, and GPT-4o for structured field extraction

6

Validation Layer — extracted data checked against Hellmann business rules (required fields, value ranges, supplier whitelist, cross-document consistency)

7

CargoWise XML Push — validated data formatted as CW1-compliant XML and pushed via eHub API

8

Excel Report Generator — formatted compliance reports auto-generated for ops team records

9

Ops Dashboard — real-time processing status, confidence scores, and exception queue

Results

Measurable Impact

60%

Processing time reduction

2–3 hour manual morning workflow reduced to under 30 minutes of exception review

50%

AI cost reduction via smart filtering

Pre-filtering removes ~50% of pages before LLM extraction, halving token consumption

0

Manual TMS data entry

All validated data pushed directly via CargoWise eHub XML — ops team never opens CargoWise for routine document data

≈0%

Failure rate on 300-page batches

Stress-tested on production batches of 300+ pages with no dropped or partially processed documents

Key Learnings

What We Learned

  • Self-learning supplier onboarding eliminated the engineering backlog entirely — new suppliers mapped automatically without developer intervention

  • Pre-filtering was the highest-ROI single feature — removing irrelevant pages before LLM extraction cut AI costs by 50%, which was not obvious during the design phase

  • The parallel run period (4 weeks of automated and manual processing side-by-side) was essential for building ops team confidence and catching edge cases

  • Confidence scoring at field level (not document level) was the right granularity for human review — operators review specific uncertain fields, not entire documents

Tech Stack: PythonLangGraphAzure Document Intelligencen8nCargoWise APIOpenAI GPT-4oCustom OCR

Want Results Like These?

Book a free audit. We'll map your operations and show you what's possible.