Logistics
An international freight forwarder
Supplier invoices read by AI, approved by people and matched to shipments
- applications in one portal
- 4
- roles in the access-control model
- 7
Enterprise AI, at Codedesign, means AI systems that run in production inside a company's own processes: they read documents, answer questions and prepare work, then hand the result to your ERP, CRM or transport management system, with a person in control of the exceptions.
A pilot proves that a model can read an invoice. Production needs more: real data, a place to send the result, a rule for every exception, and someone who answers for it on Monday morning.
Without integration, AI produces text that someone copies by hand. Without validation, it produces errors nobody notices. Without monitoring, it degrades quietly. That is the part we build.
01
AI agents that receive supplier invoices, transport orders or delivery notes, check what each document is, extract the data and prepare it for approval.
02
Assistants that answer from your own procedures, contracts and manuals, cite the source and respect each person's permissions, using retrieval-augmented generation (RAG).
03
Agents that answer the phone for defined customer-service tasks and pass the request on, with a transcript of every call.
04
AI prepares; a person approves, corrects or rejects. Every decision is recorded.
05
Results reach the systems of record through their own interfaces, never by copy and paste. See systems integration.
06
Test sets built from your real documents, run before every release, and monitoring of accuracy, exceptions and cost in production.
07
Where it fits, we build on Evolus, our own AI platform; Evolus is a trademark of Codedesign SRL. Otherwise, we build on the model and infrastructure you choose.
01
We start from a process with a clear cost, such as invoices keyed by hand, and agree how success will be measured.
02
We gather real documents or conversations, the difficult ones included, and use them to test every version.
03
Validation, integration, permissions and the review screen are built with the AI step, not after it.
04
The system runs on real cases alongside the current process, and we review the results with the people who do the work.
05
In production we monitor accuracy, exceptions and cost, and release improvements in small, documented steps.
Data is processed in an EU region, access follows your roles, and every AI step is logged in an audit trail.
The model reads and suggests. Deterministic checks validate amounts, codes and master data before anything reaches your ERP.
When the system is unsure, a person sees the case, the reason and the source document, and decides.
We choose the model for each task and can replace it when a better or cheaper one appears. You can also bring your own.
For an international freight forwarder, an AI agent checks that each supplier PDF is really an invoice, then extracts the data for approval and import. Read the case study. For a European transport and logistics group, a pilot turns customer emails into transport orders. Read about the pilot.
Logistics
An international freight forwarder
Logistics
PilotA European transport and logistics group
A pilot proves that a model can do the task. Production proves that a company can rely on it every day. Between the two sit integration, validation, ownership and cost, and that is where many AI projects stop.
, 6 min read
Governance is what lets a company put AI into production without losing control of its data. What the GDPR and the EU AI Act ask of a company that uses AI, with the AI Act timeline as amended in July 2026.
, 7 min read
Enterprise AI is the use of AI models inside a company's own processes and systems, in production, with the controls a business needs: integration with the systems of record, validation of results, human review of exceptions, access control, an audit trail and monitoring. The model is one component; most of the work is around it.
Yes. The AI step prepares data outside the ERP; an integration layer validates it and writes it through the interfaces the ERP already offers, such as services, staging tables or import files. The ERP stays the system of record. Codedesign has built such integrations with Microsoft Dynamics NAV.
In the European Union. Codedesign keeps processing, storage and model deployments in an EU region, lists every processor that touches the data, and keeps an audit trail of each AI step.
It depends less on the model than on data access, integration and the rules for exceptions. The AI step is usually the first part to work; integration, validation, review and monitoring take longer, and they are what makes the system reliable.
It depends on the use. Back-office document automation is usually not high-risk, but chat and voice agents must tell people they are dealing with an AI, and systems used for recruitment or credit scoring are high-risk. Our guide to governance under GDPR and the AI Act sets out the dates.
Enterprise AI
Bring one real example, such as an invoice or an order email. We'll show you what a production system around it would look like.
Request a private meeting