Technology & integration

Options for use

With the open source eCMR solution, the Open Logistics Foundation deliberately opts for a modular architecture: companies can either operate a complete eCMR instance or integrate individual components into existing systems.

Use of the complete eCMR instance (Deployable System)

This variant provides a fully operational eCMR implementation that can be used in production, including:

• eCMR process implementation
• Service for execution in a productive environment, including interfaces for integration of IT systems, such as TMS/ERP
• The basis is the eCMR data model, the eCMR API, and the eSEAL implementation
• A backend and a frontend

The instance can be adapted to a company’s own IT infrastructure, UI/UX design, and/or internal processes. The public API must not be changed, as this could affect compatibility with other eCMR instances.

Modular use of individual components

Alternatively, individual components from the OLF-eCMR Toolbox can be used independently and integrated into existing systems. This variant:

• Defines the structure of the eCMR (data model) and the interfaces (API) for processing and exchanging eCMRs between transport partners
• Requires that the API is implemented
• Requires that advanced electronic seals are supported for integration capability with other eCMR instances. The eCMR eSEAL implementation can be used for this purpose.

This version can be used to extend existing IT systems, such as eCMR platforms, with interfaces that are compatible with the open source eCMR / the full instance variant.

Integration into existing company applications

The eCMR reference implementation can be seamlessly integrated into existing applications. Companies that have already developed their own driver apps or transport solutions can integrate the eCMR functionality directly via the API.
Integration typically takes place via:

• REST-based API calls
• Embedded eCMR workflows into existing UI structures
• The use of eSEAL components for the legally compliant protection of documents
• Standardised data models for interoperability

This does not create a parallel system, but instead an extension of existing software landscapes.

View and download components now: Go to the Repository5

Preparing the system landscape

Companies can implement the components and instance internally or commission suitable service providers to do so. In all cases, it must be ensured that the necessary technical prerequisites are met.

Structured preparation of the system landscape significantly contributes to the smooth integration and stable production operation.

Important aspects include:

• Support for containerised environments based on Docker
• Authentication and access concepts based on OAuth 2.0 (e.g., via Keycloak or Active Directory)
• Use of relational SQL databanks such as PostgreSQL or Microsoft SQL Server
• Integration capability with existing TMS and ERP systems
• Provision of external API access for the secure exchange of eCMR documents with transport partners
• Configuration of the eSEAL, including the set-up of an own certificate and key pair to activate the sealing functionality

Use cases

The open eCMR solution is suitable for all standardised transport processes in international road freight transport.

Typical use cases include:

• Proof of Delivery (PoD) – Digital confirmation of receipt of goods by the consignee, including timestamp and condition documentation.
• Cabotage inspections – Proof of transport operations within a country as part of international transport.
• Digital freight communication – Exchange of transport documents between companies without breaks in the digital workflow.
• Cross-company transport processes – Collaboration between multiple logistics partners along a transport chain.

Technological foundations

The open eCMR solution is based on a modern, service-oriented software architecture that ensures scalability, interoperability, and extensibility.

Cross-cutting technologies

• Microservices architecture
• API-first architecture (REST/Json), public API + internal Integration (TMS/ERP)
• Event-driven communication
• OpenAPI – API specification and documentation
• Docker – Containerization and deployment

Backend

• Spring Boot – Framework for REST services and business logic
• Java – Core backend programming language
• Maven – Dependency and build management for Java projects

Frontend

• Angular – Core Framework
• TypeScript – Core frontend programming language
• npm – Package and dependency management