Driver app
Let drivers handle trip-linked tasks, documents, and events on mobile — online and offline.
ViaNexis
Features and modules
Detailed capabilities from the driver app to documents and audit.
Features and modules
Company / Admin control
Let transport companies manage trips, users, permissions, and workflows from one portal.
Digital CMR & documents
Trip-linked documents — CMR, delivery note, invoice, vehicle and driver papers — managed in a structured way.
Important
Digital documents do not automatically carry legal probative force. Acceptance varies by country and customer.
Completed trip package
Summarise completed-trip evidence in an exportable package.
Important
The package supports documentation; it does not replace the company's legal assessment or authority proceedings.
Messaging & notifications
Trip-linked communication and alerts for important driver events.
Important
Notifications do not claim every event arrives instantly.
Pallet & packaging exchange
Record pallet and packaging exchanges per stop with quantities, shortage, damage, and dispute.
Important
PDF evidence section is not fully ready in all cases. Recording supports dispute documentation but does not decide disputes.
ADR / border support
Quick helper information for ADR and border/customs context — alongside verification of official sources.
Important
ADR and tunnel data are helper information. The app does not replace legislation, training, the company's DG officer, or authority decisions.
Truck map foundation
Fleet and trip overview on map — operational orientation.
Important
The map does not guarantee compliance with legal restrictions or permits.
Multilingual operation
Multilingual teams on one platform.
Important
Machine or AI translation is assistive; human review is required. The original document remains primary.
Audit & support access
Traceable log; controlled support access for troubleshooting.
Important
The audit log is not automatic legal proof.
Enterprise integrations
Connect ViaNexis to your existing systems
ViaNexis is built for provider-neutral integration with external transport and enterprise systems. ViaNexis can connect to external systems, and approved external systems can connect to ViaNexis through APIs, webhooks and connector architecture.
Companies do not necessarily need to replace their current TMS or ERP to adopt ViaNexis. ViaNexis can be introduced alongside existing systems through integration.
External systems
ViaNexis Integration Layer
ViaNexis operations
Two-way connectivity
External systems → ViaNexis
Approved systems can send trips, stops, assignments and operational data into ViaNexis where the external interface supports it.
ViaNexis → External systems
ViaNexis can return execution status, delays and document metadata such as final CMR or POD events to connected systems where supported.
What this enables
Provider-neutral architecture
Designed so integrations follow a shared pattern instead of one-off core changes for each provider.
API and webhook connectivity
Structured exchange through Partner API and event webhooks for approved partners.
Two-way data exchange
Inbound operational data and outbound status or document events can be phased over time.
Sandbox technical onboarding
Validate mappings and flows in a controlled sandbox before go-live.
Controlled connector certification
Production rollout follows review and approval — not anonymous self-service activation.
Keep your core systems
Use ViaNexis for driver operations and evidence without forcing an all-or-nothing TMS replacement.
Example flows
TMS
A TMS can send trip, stop and assignment data into ViaNexis. ViaNexis can return execution status, delay signals and final CMR / POD metadata where the TMS interface supports it.
Telematics
A telematics provider can supply GPS, odometer or fuel-related transport data into ViaNexis according to the available interface.
Partner API / webhooks
An approved enterprise application can connect through Partner API or webhooks to exchange agreed operational events with ViaNexis.
Relevant system categories
ViaNexis uses a provider-neutral integration architecture. New documented API-based providers normally need provider-specific configuration, mapping and adapter work — not a redesign of ViaNexis core.
Partner API and webhook-based integration options are available for approved integrations.
Approved technical partners can validate integrations in a sandbox environment before production rollout. Production access remains manually approved.
Responsible use — important notices
ADR — responsible use
ADR and tunnel data are helper information. Official sources, tables, and current local rules must always be verified. ViaNexis does not replace legislation, ADR training, the company's dangerous-goods officer, or authority decisions.
AI, OCR & translation
AI summarisation, OCR, and automatic translation are assistive tools. Human review is required. The original document and message remain primary. Not legal advice and not certified translation.
eFTI & authority sharing
ViaNexis is not a certified eFTI platform. It does not promise authority acceptance in every country. eFTI-ready foundation means technical preparedness — not a certificate or licence.