From eCarService to FleetPoint and RepairCore — one vehicle service process.
RepairCore Cloud is not a project detached from the workshop floor. It grows out of a real vehicle service process where three levels of the market meet: the workshop, the corporate customer and the technology.
The first level: eCarService
This is where a car actually arrives at a workshop. The customer reports a problem, books an appointment, the vehicle is received, diagnosed, repaired and handed back. This is where you see what really happens on the shop floor:
- Conversations with the customer
- Symptoms
- Incomplete information
- Parts delays
- Scope changes
- Cost approvals
- The need for good documentation
The second level: FleetPoint
For companies and fleets, the problem doesn't end with a single repair. A company needs one point of contact, status information, cost control, claims handling, replacement cars and reporting.
A company car needs to get back to work as fast as possible, and the person responsible for the fleet needs to know what's happening.
The third level: RepairCore Cloud
This is the digital layer meant to bring order to the whole process: from the initial report, through VIN, vehicle data, qualification, the work order, parts, approval, communication, all the way to the report and repair history.
Confirmed at Frankfurt
Automechanika Frankfurt 2026 confirmed that the market is moving in this same direction. At the centre of attention were the areas that a workshop's daily work needs to tie into one process:
- Data
- AI
- Digitalisation
- Diagnostics
- Parts
- Connected systems
- ADAS
- New aftermarket service models
One process, made to scale
That is why RepairCore Cloud should not be seen as just "workshop software". It is a platform built for workshops, service networks and fleet models that need repeatability, data and control over the process.
eCarService shows that the process works in the physical world. FleetPoint shows how it can be sold to companies and fleets. RepairCore Cloud is meant to make that process scalable.
Let’s look at it in your own workshop.
A short walkthrough against your processes: what can be joined up, what can be simplified, and what is better left alone.