Does Hanno replace our TMS?

No. Hanno works around the TMS you already use. It reads the email, documents and messages a shipment arrives in, assembles them into one source-linked record, and hands over a checked result. It is not a transport management system and does not replace your customs broker or your responsible operator.

Does the AI decide whether a shipment is ready?

No. An AI model reads documents and extracts values; deterministic, versioned rules decide readiness. The same confirmed inputs always produce the same verdict. Every audited decision records how it was reached, so a rule firing and an AI model reading a document are distinguishable in the record.

Can Hanno email our customers without us seeing it first?

No. Every outbound message requires a person to approve it. The approved wording is what is sent, and the approval is recorded in an append-only audit trail.

How accurate is the extraction?

Hanno does not publish a field-level accuracy figure, because it does not yet have one measured on real customer documents. What is measured is the layer that decides whether an extracted value is actually supported by the source cited for it: on a 100-shipment evaluation corpus, 770 correct values were accepted with none wrongly rejected, and 1,827 deliberately corrupted values were all rejected. That corpus is synthetic and Gulf-focused, so it is a floor rather than a general accuracy claim.

What happens if a document says one thing and another says something different?

The conflict stays visible until an accountable person resolves it. Hanno does not silently pick a value. A gross weight of 1,840 kg on the invoice and 1,790 kg on the packing list is shown as a conflict with both sources, not averaged or guessed.

Does Hanno handle German and Arabic documents?

Yes. English, German and Arabic, including European decimal notation such as 22.500,00, Anglo-American notation such as 22,500.00, Arabic-Indic digits, and month names in English, German and French. Arabic and English have equal standing in the product rather than one being translated after the fact.

How do we start, and how long does it take?

By replaying 10 to 20 shipments you have already completed, so you can judge the output against work whose answer you already know. No TMS integration is required for that first check. Integration comes only after the evidence is credible.

Is Hanno certified, and where is data hosted?

Hanno holds no formal security certification yet and does not claim one. Certifications will be published only once completed and independently supportable. Data handling, storage location, retention, access roles, model usage and subprocessors are agreed in writing with each design partner before any customer information is connected.

HANNO BUYER GUIDE / EUROPEAN FORWARDERSEMAIL → VERIFIED RECORD → TMS

Email-to-TMS automation should remove rekeying—not remove control.

A practical evaluation framework for freight forwarders turning transport orders, attachments and later amendments into verified shipment records.

Replay 10–20 completed orders ↗

The workflow a production system must close

Capture the complete order

Keep the email body, attachments, sender, timestamps and thread together. An attachment-only parser loses instructions that exist only in the message.

Identify before creating

Search customer references, booking numbers, parties, route, dates and prior messages before creating a record. Ambiguous matches belong in a review queue—not in the wrong shipment.

Extract with evidence

Every critical value should open to the source document, page and excerpt. Low-confidence values remain review items and must not silently become operational facts.

Apply deterministic checks

Customer, lane, mode and commodity rules decide what is missing or contradictory. AI models can read and draft; they should not decide release readiness.

Handle revisions as changes

A later email is not a new order by default. Link it, show what changed, identify affected checks and preserve the previous value in the audit history.

Approve the TMS handoff

Map the verified record to the customer’s TMS fields, preview the write and keep the external identifier. Retries must be idempotent so the same order cannot create duplicates.

What Hanno can prove before integration

Hanno’s Shipment Readiness Agent can assemble completed orders, source-link facts, expose conflicts and replay the readiness workflow without writing to your TMS. A live TMS write path is configured and validated per design partner; Hanno does not claim a universal plug-and-play connector today.

Email-to-TMS automation should remove rekeying—not remove control.

The workflow a production system must close

Capture the complete order

Identify before creating

Extract with evidence

Apply deterministic checks

Handle revisions as changes

Approve the TMS handoff

What Hanno can prove before integration

Questions to ask every vendor

Matching

Corrections

Revisions

TMS control

Auditability

Measurement

A low-risk evaluation

Choose one recurring order type

Replay completed shipments

Compare against known outcomes

Integrate only after the evidence is credible