01
Work orders
Diagnosis, estimate, approvals, photos, documents and completed work all stay on one job.
- Diagnosis complete
- Estimate sent to customer
Demo view · sample data
From booking, diagnosis, estimating and cost approval to completed work, documents and history. Everyone works with current information.
A work order holds the customer, the vehicle, the slot, the paperwork and the team's communication in one place.
01
Diagnosis, estimate, approvals, photos, documents and completed work all stay on one job.
Demo view · sample data
02
Earlier repairs, documents and recommendations are already there at the next visit.
Demo view · sample data
03
Appointments, bays and team responsibility in a single view.
Demo view · sample data
04
Automation carries the repetitive steps and the messaging. Diagnosis and cost stay with a person.
Demo view · sample data
05
Current figures on work orders and workshop throughput, with no export to a spreadsheet.
Demo view · sample data
06
Agreed data and services wired into a specific stage of the job - access granted case by case.
Demo view · sample data
07
A photo of the registration document fills in the vehicle record - no retyping the VIN and plate by hand. What was read is always shown for confirmation before it is saved.
Demo view · sample data
The work order, the vehicle history and the current status are available from the shop floor, the front desk and a phone - without switching systems.
The same shared process, a different view of it - every role sees exactly what it needs for its own work.
RepairCore Cloud can help organize context, documents, communication and next steps. Decisions about diagnosis, repair scope, cost approval and responsibility remain with authorized people: service advisors, technicians, fleet managers or operators.

System suggestion
Order brake pads - Demo Vehicle
Confirmed by the advisor
RepairCore Cloud grows out of real vehicle service operations - combining service experience, eCarService locations, FleetPoint’s fleet needs, the current ECS Cloud foundation and a future partner network into one operational standard.
| Typical fragmented software | RepairCore Cloud |
|---|---|
| Assumptions about what software should look like | Real service workflows |
| Scattered tools and data | One shared workflow |
| Open, unscoped integration access | Scoped, auditable integrations |
| Automation without oversight | Diagnosis and cost decisions stay with people |
Whether you run a workshop, manage a fleet, build a service network or integrate as a partner - we start with one process and grow the engagement at your pace. The subscription comes from the public price list; add-ons and individual rollouts are agreed separately.
Putting customer and vehicle handling in order first, then further processes in the same environment.
Vehicle coordination, statuses, cost decisions, documents and reporting.
Multiple locations on one service standard, with shared data and workflows.
A controlled integration scope, roles, audit and the operator’s decision on access.
Damage report, documentation, estimate, insurer decision and settlement in one process.
One vehicle-service process, developed out of real operating experience at ECS Cloud, eCarService and FleetPoint. Below is what it covers today - stated plainly, without a maturity-stage split.
Work orders, calendar, documents, customer approvals, full vehicle history and a reconstructable decision trail - one service process from intake to handover.
Vehicle statuses, downtime, cost, decisions and B2B communication for fleet managers.
The current SaaS platform we are evolving RepairCore Cloud out of for further organisations.
Online booking, the customer panel and fleet service coordination at the same company’s live locations.
Partners, locations and a shared data standard for a service network - built on a history of 500+ service relationships going back to 1998, and rolled out to further partners after verification and consent.
Controlled, auditable access to selected data and integrations, granted individually to technical partners after verification and an agreed scope.
The damage process from report through documentation and estimate to an insurer decision and settlement - running today in production with an insurance partner.
A separate, developing area for customer payments to the workshop - independent of RepairCore’s subscription billing and rolled out in stages for selected channels.
A plan and its price cover the scope described for each module above. Items in pilot or in development are sold only to the extent they actually work today - they do not determine the base subscription price.
The Claims module takes a damage report through documentation, an estimate and an insurer decision all the way to settlement - in the same system as the rest of vehicle service. It runs today in production with an insurance partner.
Claims by stage
CLAIM-DEMO-01
Parking damage · DEMO-PL-12
CLAIM-DEMO-04
Collision · DEMO-PL-24
CLAIM-DEMO-07
Estimate with the insurer
CLAIM-DEMO-09
Inspection booked
CLAIM-DEMO-03
Vehicle collected by customer
CLAIM-DEMO-02
Invoice issued
CLAIM-DEMO-07 · DEMO-PL-12
Photo documentation
Set of 14 photos · shop floor
Repair estimate
Sent to the insurer
Insurer decision
Response due in 3 days
Parts order
After the insurer decision
Demo view · sample data
A short walkthrough against your processes: what can be joined up, what can be simplified, and what is better left alone.