Working examples · nothing hidden

A polished result is not proof.

Before you trust an automation workflow, inspect what went in, what should come out and which decision still belongs to a person.

The usual demo

You see a perfect screen, but not the source files, expected values or failure boundary behind it.

A reproducible case

Every LogisticsAI example names its synthetic inputs, exact expected result and human review boundary.

Open case files

Start with the evidence your team recognises.

These are working synthetic fixtures, not customer stories. Open the related product page to see how the same evidence moves through the controlled workflow.

01_DEMO_Vergunning_Uitzonderlijk_Vervoer.pdf
02_DEMO_Inkomende_Email_Vergunningsaanvraag.pdf
03_DEMO_Technische_Fiche_Voertuigcombinatie.pdf

Interactive demo

Permit pack → source-cited transport facts

Combine a permit, incoming request and vehicle sheet into a structured record with page references and review cues.

Synthetic case file

Expected result

Reference: DEMO-MOW-UV-2026-0042
Width: 3.15 m
Mass: 54,000 kg
Conditions: 3

Decision kept with a person

The original permit remains authoritative. Route, escort and validity wording require human confirmation.

Open interactive permit demo

1 clean CMR + 1 incomplete POD
2 exception documents
1 ambiguous + 1 unmatched document

Six-document cohort

CMR and POD evidence → routed delivery outcomes

Run clean, incomplete, damaged, short, ambiguous and unmatched delivery documents through the same validation boundary.

Synthetic case file

Expected result

Documents: 6 PDFs
Confirmed: 1
Needs review: 3
Unmatched: 1

Decision kept with a person

Damage, shortage and matching ambiguity are routed for review; the system makes no identity or liability conclusion.

Inspect delivery checks

01_order_request_en.md
02_delivery_details_nl.md
03_equipment_details_de.md

Multilingual fixture

Three messages → one transport-order draft

Merge an English request, Dutch delivery details and German equipment requirements into one evidence-linked order object.

Synthetic case file

Expected result

Parties: 3
Stops: 2
Validation: complete · pass
Reference: QA-ORD-17001

Decision kept with a person

The fixture may create a draft only. Carrier choice, rate acceptance and external TMS handoff remain disabled.

Inspect order intake

Cases 04—06

Three more exact fixtures.

Billing, status and emissions use the same rule: visible inputs, pinned outputs and no hidden authority.

Deterministic rule fixture

Gate evidence → reviewable waiting-charge candidate

Extract a waiting interval, check file readiness and apply a transparent free-time, unit and cap rule before invoicing.

Elapsed: 135 min
Billable: 105 min

The calculated amount is a candidate, never an approved charge. Source evidence and a reviewer decision are required.

Inspect billing readiness

Three-language fixture

Verified delay → EN, NL and DE message drafts

Turn one controlled operational event into localised customer communication while preserving the exact facts behind every draft.

Location: Aachen, DE
Delay: 90 min

Every draft requires approval before sending. Automatic delivery and real recipient domains are disabled in the fixture.

Inspect status updates

Calculation oracle

Three shipment rows → traceable emissions totals

Import a canonical CSV and compare every shipment and aggregate against the version-locked calculation oracle.

Shipments: 3
WTW CO₂e: 596 kg

The fixture proves calculation consistency, not certification or regulatory compliance. Methodology and source data remain reviewable.

Inspect emissions reporting

YOUR WORK / NEXT

Do these files look different from yours?

Send a representative description of the manual handoff. We will define what can be tested, what must remain controlled and which evidence would prove the result.

Scope my workflow