Route list import
Import and standardise route lists, picking lists and related files.
Back to NOPA
Logistics
E-route
Follow routes from preparation, handover and driver feedback to closing. You can see where the delivery is and what deviations require action.
Route list and route planning
Preparation and dispatch
Digital handover
Offline feed, proof and audit
NOPA X in practice
From the route calendar to individual stops
Actual NOPA X interface with demonstration data. Screenshots are in Hungarian.
View the daily route calendar
Operating model
A logistics process in which the status comes from the system
Daily preparation, handover, driver updates and customer service resolution share one event history.
Preparation
Track daily product requirements, item readiness and shortages before handing over a route.
Dispatch and digital handover
Record the items being handed over, confirm acceptance or explain discrepancies. The history of handovers and any cancellations is retained.
Driver feedback
The proprietary Android application shows the routes, stops and items assigned to the driver, and then transmits field feedback.
Import
data is received
Preparation
route is ready
Dispatch
handover starts
Driver feedback
field events
Closing
delivery note and audit
Current capabilities
Critical points in daily operations can be managed as independent, auditable processes
Review preparation, handover and field events. Both the current status and the steps leading to it remain visible.
Unified digital handover workspace
Routes awaiting handover, the selected route, and returning routes can be tracked in one workspace. Date filtering, aggregated product quantities, an immutable snapshot, verified acceptance or reasoned discrepancy, proof, revocation, and event history support operations.
Saved event history
Past package, stop and handover events are retained so discrepancies can be investigated later.
Operational route planning
Opening hours data, time zones, modifiable stop order and driver allocation support the dispatcher's daily work.
E-route Android app
The fieldwork is connected to the central E-route process with its own Android client
Drivers see their assigned daily tasks. Data synchronisation and repeatable uploads support work with changing network conditions.
Daily work assigned
Only eligible routes, stops and items are displayed to the field user.
Offline use
Data transfer and synchronisation designed for offline use support work with limited connectivity.
Handover evidence and events
Photo, GPS metadata, stop and item events, and returns can be returned to the audited process.
A management perspective
A shared view of deliveries and customer cases
Operational management
It becomes visible which route is in which condition, where the preparation or handover was stuck, and what happened in the field.
Customer service
The team does not work from separate lists and telephone inquiries, but from the delivery status, delivery note and audit trail.
CTO / IT manager
A product line built on API contracts, tenant isolation, permission scopes and controlled background processes.
Technical details
Data connections and operational details
Before implementation, we agree on the features available in the chosen version, the integrations needed and any custom development.
View technical details
Route package data model
package, stop, item, route and customer master connections
Workflow and status management
preparation, digital transfer, server-confirmed running status, return and closing
Delivery note and PDF
preview, generation, download and optional invoice integration
Audit and status history
append-only packet, stop, prepare and transfer events, proofs and user actions
Route-list normalization
CSV recognition, handling of Central European character encoding and product code alias layer
Driver / offline feed
active routes, offline package payload, picklist, stop work and delta sync
Proof and field events
stop/item events, returns, proof upload, processing status and GPS metadata
Master data and planning
customer master, addresses, business hours, drivers, groups, route assignment and sequence change
Product dimension management
create and update product dimensions in master data management
NOPA X fleet module
company vehicle records, effective-dated user assignments, and business trip start and close with odometer readings
Tenant rights
versioned authorization catalog, roles, direct user exceptions, and audited server-side decisions
NOPA X platform
The data model and contracts of E-route are transferred to the new Go base
During the transition, E-route is rebuilt not simply as an interface, but as API contract, workflow state machine, feed contract and testable normalizer.
Protected API contracts
Separate E-route and driver-feed endpoints use generated clients, scope boundaries, a standard error model, and server-side enforcement.
Explainable permissions
Alongside tenant roles and direct user overrides, effective permissions and their origin are explainable, with optimistic locking and an audit trail.
Contract testability
Anonymized route bundle and feed JSON samples provide the basis so that the Go implementation does not follow the current operation out of guesswork.
Next step