Addresses and delivery contents arrive together.
Receive tasks from a connected source. Each stop keeps its address and associated delivery data.
Ready for routing
LAST-MILE DELIVERY PLATFORM
Less friction.
More deliveries.
From an address list to a completed route. R/ENGINE brings planning, navigation and delivery data together in one smartphone workflow.
Any cargo. By bike, by car or on foot.
ADDRESSES BECOME A ROUTE
01
INPUTDelivery data
ROUTE ENGINEOne connected workflow
DELIVERYAll the way to each stop
Data → sequence → movement → completion
PROVEN IN REAL DELIVERY
A difference measured on the route.
−39%
less time on the delivery route
3:17≈ 2:00
up to−50%
in individual shifts
03
transport profiles
Live
GPS navigation
On an active courier route, delivery time fell from 3 h 17 min to around 2 h. Up to 50% was observed in individual shifts. Results depend on the area, delivery workload and operating conditions.
ONE ROUTE. FIVE STEPS.
From the first address
to the final delivery.
The courier no longer has to piece together a map, an address list and separate notes. The next step is already in front of them.
The sequence follows the road network.
The engine calculates an efficient stop order for the selected mode: driving, cycling or walking.
Tasks become a route
Navigation follows the courier.
GPS, heading, distance and voice guidance help the courier reach the next stop. After a deviation, the path updates to the same destination.
The next address stays in context
See where to go and what to deliver.
The address and delivery contents stay available during navigation. Information belongs to the current stop, without searching through another list.
Address + cargo + distance
Progress moves with the route.
Controlled automatic completion checks arrival near the stop and confirmed departure. The workflow then advances to the next delivery.
Current stop → next stop
BEYOND ROUTE PLANNING
The entire workflow.
In one engine.
Stop optimization
An efficient delivery sequence instead of choosing each next address manually.
Navigation in motion
Live GPS, a heading-aware map and voice guidance.
Delivery context
The address, delivery contents and remaining distance stay together.
Automatic progression
Arrival and confirmed departure help complete stops in sequence.
Live rerouting
After a deviation, the path updates from the current position to the active stop.
Continue on another device
The session and working route support switching between compatible devices.
AN OPERATIONAL SHIFT
Fewer manual steps.
More clarity on the route.
BEFORE
A fragmented process
- A static district map
- A separate address list
- Manually chosen stop order
- Reliance on knowing the area
WITH R/ENGINE
One R/ENGINE workflow
- Navigation from the current position
- Address and cargo in one stop
- A calculated stop sequence
- A clear next step for the courier
ONE ENGINE. DIFFERENT CARGO.
Deliveries change.
The workflow stays.
R/ENGINE works with stops and delivery data. Cargo defines the context, while the route remains one connected workflow.
ParcelsDocumentsPrint & mediaGroceriesSpare partsRetail goodsInternal logistics
ROUTING FOR THE WAY YOU MOVE
On wheels.
Or on foot.
Stop order and paths are calculated for the selected transport profile.
A cycling profile for everyday delivery.
GET INTO THE WORKFLOW
Local knowledge helps.
The workflow should
stand on its own.
A new employee opens the route, follows navigation and sees what to deliver. Less information to memorize; more available at the moment of action.
BUILT TO CONNECT
Your delivery data.
One working flow.
Your existing back office remains the task source. R/ENGINE turns addresses and delivery data into a working courier route.
01 / SOURCE
Task source
ERP · TMS · API
02 / ENGINER/ENGINE
Integration & routing
03 / DELIVERY
Courier Web App
GPS · Navigation
API import is already used in real operations. Connecting a specific ERP, TMS or custom source is scoped during implementation.
TECHNICAL FOUNDATION
REST API · OSRM · VROOM · Live GPS · TTS
IMPLEMENTATION IN YOUR OPERATION
Start with one
real delivery route.
Understand the operation
Task source, cargo, transport and current bottlenecks.
Connect the data
Scope the import of addresses and information for every stop.
Validate on the route
Compare time, usability and delivery quality on your own route.
Before implementation
Does the courier need to install an app?
The courier interface runs as a Mobile Web App on a compatible smartphone. GPS navigation requires location permission and network access.
Is the product only for newspaper delivery?
No. The workflow is built around stops and associated data. Parcels, documents, print, retail goods and spare parts use the same delivery process.
What works in the product today?
Task import, stop optimization, three routing profiles, GPS navigation, voice guidance, rerouting, delivery data, progress and switching devices. A dispatcher dashboard and fleet analytics are outside the current courier product.
How do we connect our existing system?
First, we review your task source and data structure. Then we scope integration, deployment and a route trial. Compatibility with a specific system is assessed individually.
What does implementation cost?
Cost depends on integration, deployment environment and required changes. Share how your delivery operation works so implementation scope and pricing can be defined.
MAKE DELIVERY FLOW
Put your route
to work.
Tell us about your delivery operation. Let’s discuss how R/ENGINE can fit your existing workflow.