Fleet tracking
Fleet records live in the platform in place of paper, in the same system as routes and invoices.
Logistics software case study
A logistics platform that took four days a month out of invoicing.
A logistics company tracked its fleet on paper, planned routes from memory and spent four days a month matching invoices by hand. We put all of it into one platform, connected to the ERP (enterprise resource planning) system it already had.
- Fleet, routes and invoices in one platform
- The existing ERP stayed in place
- Route planning no longer rests on one person
- React
- ERP integration
- Logistics
In brief
- The client
- A logistics company. Its fleet tracking, route planning and invoicing all ran without software, next to an existing ERP.
- The problem
- Paper fleet logs, routes planned from one person's memory, and four days of manual invoice reconciliation every month.
- The result
- One platform for all three, connected to the ERP. The client reports 35% lower operating cost and four days of manual reconciliation removed each month.
The challenge
Paper logs, routes from memory and invoices matched by hand.
Three core processes ran without software. Building the platform turned out to be the smaller part of the job.
- Fleet tracking. Kept in paper logs.
- Route planning. Depended on one person's knowledge.
- Invoicing. Four days of manual reconciliation every month.
- The existing ERP. No documentation, and the new platform had to work with it rather than replace it.
Software for the work, and less riding on one person
The obvious need was software for work that had none. The less obvious one was risk. When route planning lives in one person's head, the business slows down whenever that person is away.
Why the ERP stayed
Replacing an ERP to fix invoicing would have been a far bigger project than the problem. So the platform works with the system already there. That meant integrating with an ERP nobody had documented.
What we built
One platform for fleet, routes and invoices.
The three processes went digital and connected to the ERP, instead of competing with it.
Route optimization
Route optimization, where the software suggests efficient routes, is built into the platform. Planning no longer sits with one person.
Invoice matching
Invoices are matched automatically against the existing ERP, in place of four days a month of reconciliation by hand.
All three sit in a single React platform. React is a widely used toolkit for building web applications.
The impact
Lower operating cost and a shorter month-end.
Fleet tracking, route planning and invoicing now run in one system, connected to the ERP the company already used. The figures are the client's own, as reported to us.
- 35%
- lower operating cost
- 4 days
- of manual reconciliation removed each month
- One platform
- for fleet, routes and invoices, so route planning no longer depends on one person being in the building
What made it work
The integration took longer than the platform.
That is normal when nobody has documented the system you have to connect to.
- Why it takes longer. An undocumented system has to be learned by watching what it actually does. Nobody can say in advance how long that will take.
- What we do about it. We scope integrations separately from the build. A fixed price on a system nobody can describe is a guess, and we would rather say so than hide the guess inside a quote.
Related services
Facing something similar?
Pick the problem closest to yours to see the service behind this project.
- We run core work on paper, spreadsheets or systems that don't share data.Web and custom software
- New software has to work with a system nobody documented.API development and integration
- We want a rough price before we talk to anyone.Cost estimate
More case studies: the hotel management platform, the smart home monitoring dashboard, the travel booking and itinerary app and the AI recruitment platform. Or see every case study.
Let's talk
Stuck with a system nobody documented?
Tell us what you run today and what the new work has to connect to. We scope the integration on its own first, so the build estimate isn't a guess. We reply within one working day.