Fleet Tour Planning and a Driver App That Closed the Gap from a Day to Minutes
Tours were planned weekly, drivers logged deliveries on paper, and the office coordinated by phone. A Flutter driver app wired into ERP tour planning moved the team from weekly planning to daily tracking.
- Service
- Software Solutions
- Industry
- Transportation & Logistics
- Region
- Germany
- Engagement
- Lab-type ODC (dedicated team)
Outcomes
- Weekly planning → daily tracking
- Record lag: a day → minutes
- Paper logs eliminated
Stack
Odoo · Flutter · Python · GitHub Actions · PostgreSQL
Written byOriental Nippon Team
A German B2B supply-chain vendor runs its own fleet of delivery trucks. Tours were planned by hand once a week. After a truck left the yard, the office knew very little until the driver phoned in or came back at the end of the day.
Returns were handled on paper and typed in later, so every downstream process ran a day behind.
The problem
- Weekly planning, daily improvisation. Mid-week changes were handled by phone.
- No live view. Dispatchers could not see tour progress or failed deliveries.
- Paper records. Deliveries, exceptions and B2B returns were written down and re-keyed.
- No trail. Office-to-driver coordination left no record.
| Before | After | |
|---|---|---|
| Planning cadence | Weekly | Tracked daily |
| Driver records | Paper, re-keyed | Mobile app, live |
| Work done to work recorded | ~1 day | Minutes |
| Returns | Paper slips | Captured in the app |
What we built
A driver app
Built in Flutter and connected to Odoo: the day's tour, delivery confirmation, exception capture and B2B returns, designed for a truck cab, not a desk.
Tour planning in the ERP
Vehicles, drivers and routes alongside orders.
A live feedback loop
What the driver records updates the plan and the operational record immediately.
An app release pipeline
GitHub Actions, so releases are routine.
What happens during a tour, now that the office can see it:
Technology and the role it played
| Technology | Role in this project |
|---|---|
| Odoo | Tour planning with vehicles, drivers, routes and orders |
| Flutter | The driver app for phones in the cab |
| Python | Integration between app and ERP |
| GitHub Actions | Automated app build and release |
| PostgreSQL | Operational data |
How we delivered it
We rode along with the process before designing anything. Offline use and glove-friendly controls became requirements after watching real drivers.
- Map the process. Planning, dispatch and returns, with the team.
- Foundation. Environments, source control and an automated app release pipeline.
- Planning side first. So the app had something to connect to.
- Driver app. Tested by real drivers on real routes.
- Pilot depot. One depot, one full week.
- Roll out. Depot by depot.
01Discovery
2 wks
Planning, dispatch and returns mapped with the team
02Foundation
2 wks
Environments, CI/CD pipeline, app distribution
03Tour planning
3–4 wks
Vehicles, drivers, routes and orders in one place
04Driver app
5–7 wks
Tour view, delivery confirmation, exceptions, returns
05Pilot depot
2 wks
One depot, one full week, real drivers
06Roll-out
ongoing
Depot by depot
Risks and how we handled them
| Risk | How we handled it |
|---|---|
| An app drivers won't use | Designed from ride-alongs, with offline and glove-friendly controls |
| App with nothing to connect to | Planning side built first |
| Rollout problems across depots | One depot piloted for a full week first |
Outcome
The team moved from planning the fleet once a week to tracking it every day, and the gap between work done and work recorded closed from a day to minutes.
The client describes delivery operations as significantly more efficient. That is their assessment of their own business, and we report it as theirs.
What the client keeps
- App source in their own repository and developer accounts
- Planning configuration
- The build and release pipeline
- Integration documentation
Sources and further reading
- Flutter documentation, Google
- GitHub Actions documentation, GitHub
- Odoo 17 documentation, Odoo
Facing something similar? This is the kind of work our Software Engineering & Cloud team delivers every day. Talk to us about your stack.
