Skip to content
Warehouse, shipping & traceabilityWaste & RecyclingLogistics & Ports

Capture transport orders from e-mail

Address, weight and time window are taken from the e-mail and attachment, so you stop retyping.

Today

Transport orders arrive by e-mail, PDF and phone and are typed in again. A transposed digit in an address, a wrong weight or a missing time window means a wasted trip. At peak times the orders pile up in the inbox.

An example

A customer of Nordhanse sends a PDF with 12 container pickups at the terminal, a mix of 20 ft and 40 ft. The agent prepares 11 orders and holds them for approval. The twelfth has no time window, so a query goes to the customer.
Fictional company, typical workflow.

Your data, wherever it lives

Today transport orders arrive in the order inbox as e-mails, PDFs or spreadsheets, or as a note after a phone call, while customers, loading and unloading points, tariffs and time windows sit as master data in the ERP and TMS. demi reads, understands and links them per order and loading point, with your rights. The AI prepares each order in seconds instead of minutes of retyping, checks address, weight and time window and asks for what is missing, and the dispatcher approves.

Where the data lives today

  • E-mails
  • PDFs
  • Office files
  • Phone & voice
  • ERP
Data LayerOne view of everything, with your rights

How demi solves it

Three layers in this order: connect the data first, then the rights, then the AI.

  1. 1 · ConnectData Layer

    The case needs data from the order inbox, ERP and TMS. demi replaces nothing and checks every order against customers, loading and unloading points, tariffs and time windows from master data. demi prepares matching orders; results only go back after your approval.

  2. 2 · PermitPermission Layer

    Dispatchers see the orders of their branch. The dispatcher approves orders outside a customer's standing rules, and every order created is recorded.

  3. 3 · ActIntelligence Layer

    The agent reads the order data from text, PDF and spreadsheets, checks addresses, weights and time windows against the customer's fixed rules and copies values unchanged. Whatever is missing or does not fit, it asks about instead of filling in, each detail with its location.

How it runs

  1. 1

    The order arrives by e-mail, as a PDF or as a spreadsheet.

  2. 2

    demi reads every line and matches customer and loading points.

  3. 3

    The agent checks addresses, weights and time windows against master data.

  4. 4

    Matching orders are ready for approval; special cases go to dispatch.

  5. 5

    The agent asks the customer for any missing details.

What changes

  • No more retyping

  • Fewer wasted trips

  • Orders in the system faster

What does it bring you?

Check it with your own numbers

Every starting value is an assumption you can change. The calculation sits right below, step by step.

Assumption, editable

Your numbers

Result

+600 hfreed per year

Assumptions and calculation

demi reads orders from mail and attachments, adds master data and prepares them; you approve.

6 min → 3 min per case

How does it run today?

What is already digital saves less: the factor lowers the share demi brings.

How we calculate

1,000 transport orders × 6 min × 50% × 1.0 (manual) × 12 months = 36,000 min = 600 h

Value per year, before demi costs

Freed per year+600 h

Assumption: labor cost of $48.62 per hour in US manufacturing in June 2026 (BLS), plus workplace, IT and overhead.

= Value per year, before demi costs

+$39,000

gained per year

600 h ÷ 1,760 h per role = 0.3 full-time roles

An estimate, not a promise. The starting values are assumptions for an industrial company with 150 to 500 people.

Combine with more cases and get the package

Questions about this use case

Which formats can demi read?

E-mail text, PDF, scanned forms and spreadsheets, including many lines in one file. Each customer can keep their own format. For every order you see which part of the document each value came from.

How are errors caught?

Every address, weight and time window is checked against master data and the customer's rules before the order is created. If something does not fit, such as a weight above the permitted payload or an unknown loading point, the order is held. The agent never fills in on a guess.

Does it work with our transport system?

demi only writes back after approval; nothing is replaced. Dispatch keeps working in the screens it knows. Status and changes flow back so every query knows the current state.

What happens to orders outside the rules?

They go to the branch dispatcher with the reason, for example an unusually high weight, a new pickup address or a weekend date. The dispatcher confirms, changes or rejects. Only then is the order created.

See this case with your data

In the demo we show you the workflow on your own systems.

Your configurator

No use cases yet

Your configurator is still empty

Add a use case from any card or case page and see what it brings per year, with the calculation. Free, no sign-up, no commitment: try it out and change any number.

Browse use cases