Today
Container status arrives by e-mail, from several portals or over the phone. When free time ends is worked out in someone's head or in a spreadsheet. If it runs out unnoticed, demurrage and detention follow, and hardly anyone checks those invoices.
An example
Nordhanse has 85 import containers at the terminal in Hamburg, 62 of them 40 ft and 23 of them 20 ft. The agent flags six whose free time ends in two days with no truck booked. In one detention invoice it finds a public holiday that the contract excludes.
Your data, wherever it lives
Status messages arrive today by e-mail and from several carrier and terminal portals, bookings and trucking orders sit in the TMS, free-time terms in contracts as PDFs, deadlines in spreadsheets and invoices in the ERP. demi reads, understands and links them per container, with your rights. The AI spots every expiring free time early and recalculates every demurrage invoice, and dispatch and the team lead decide on pick-up and disputes.
Where the data lives today
- E-mails
- Web & portals
- PDFs
- Office files
- ERP
How demi solves it
Three layers in this order: connect the data first, then the rights, then the AI.
- 1 · ConnectData Layer
The case needs data from the TMS, e-mail, portals and ERP. demi replaces nothing and links bookings, bills of lading, status messages, free-time terms from the contracts, trucking orders and invoices; every container is one record with all its events in time order. demi only writes back after approval.
- 2 · PermitPermission Layer
Dispatchers see their shipments; customers see only their own containers. The team lead approves invoice disputes, and every dispute is recorded.
- 3 · ActIntelligence Layer
The agent computes free time exactly from contract terms and event times and warns in time. It recalculates demurrage and detention invoices against the terms and events and drafts the dispute with evidence.
How it runs
- 1
Status messages from e-mail, portals and the TMS come together on the container.
- 2
demi computes when free time at the terminal and for the equipment ends for each container.
- 3
Containers close to the deadline without a booked pickup go to dispatch as a warning.
- 4
Incoming demurrage and detention invoices are recalculated against contract and events.
- 5
Wrong invoices go to the team lead as a draft dispute.
What changes
Less demurrage and detention
One view per container
Wrong invoices disputed
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.
Your numbers
Result
+96 hfreed per year
Assumptions and calculation
demi merges messages from carrier, terminal and forwarder and warns before demurrage; you act.
15 min → 9 min per case
How we calculate
80 containers × 15 min × 40% × 1.0 (manual) × 12 months = 5,760 min = 96 h
Value per year, before demi costs
Freed per year+96 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
+$6,240
gained per year
96 h ÷ 1,760 h per role = 0.1 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 packageQuestions about this use case
Which status sources can demi read?
Messages from shipping lines and terminals by e-mail, portal or interface, plus the events in your TMS and updates from haulers. If two sources disagree, the agent shows both with timestamp and origin.
Can our customers see the status of their containers?
Yes, if you allow it. Each customer sees only their own containers with status, deadline and planned pickup. Internal notes and other customers' terms stay hidden.
Does demi check shipping line invoices?
Yes. The agent recalculates every demurrage and detention invoice from the free-time terms in your contract and the actual event times. If the amounts differ, it drafts the dispute with invoice, contract clause and timestamps, and the team lead sends it.
What if a status event is missing?
Then the agent does not carry on with an assumption. It flags the gap and asks the terminal or shipping line. The warning stays open until the event arrives.
