01
Work orders
Diagnosis, estimate, approvals, photos, documents and completed work all stay on one job.
- Diagnosis complete
- Estimate sent to customer
The workshop, the fleet and the service network work from the same vehicle record — not from six separate systems.
For workshops, service networks and fleets

Open work orders
18
+4 this week
Vehicles on site
7
no change
Estimates with customer
5
−1 since yesterday
Average repair time
2.4 days
−0.3 days MoM
Work orders opened and closed over the last 12 months
The front desk, the shop floor and the customer see the same record
RO-1042
Illustrative view · example data
01
Booking
02
Work order
03
Estimate
04
Approval
05
Documents
06
Communication
07
History
Today one job lives in a phone call, a spreadsheet, a calendar, a note, a separate CRM and a messenger — each of them knows only a fragment of it. In RepairCore Cloud that same job is one work order in one system.
Without RepairCore · six places
Nothing joins up on its own. What was agreed has to be retyped between tools, and every customer question starts with someone checking where the current version is.
With RepairCore Cloud · one system
Everything that used to sit in six places
RO-1042
Illustrative view · example data
The workshop, the fleet and the customer look at the same state of the job — nothing retyped, nobody asking who has it now.
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.
02
Earlier repairs, documents and recommendations are already there at the next visit.
03
Appointments, bays and team responsibility in a single view.
04
Automation carries the repetitive steps and the messaging. Diagnosis and cost stay with a person.
05
Current figures on work orders and workshop throughput, with no export to a spreadsheet.
06
Agreed data and services wired into a specific stage of the job — access granted case by case.
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.
Earlier repairs, documents, recommendations and status — there at every next visit, with no digging through binders or separate systems.
Active work order
VIN_DEMO_7841 · DEMO-PL-12
Illustrative view · example data

01
Bookings, work orders, the day plan, documents and customer contact in one process.

02
New locations on one shared service standard, with process visibility across the network.

03
Vehicle status, cost approvals, documents and service history without phoning round the workshops.

04
Agreed data and services wired into a chosen stage of the job, within a controlled scope.
Module register
RepairCore Cloud is one process made of several modules. Some of them already run inside ECS Cloud, some are still being built — here is where each one actually stands.
Module
Covers
Status
Work orders, calendar, documents, customer approvals and vehicle history in one service process.
Active foundation
Vehicle statuses, downtime, cost, decisions and B2B communication for fleet managers.
Active foundation
Partners, locations, requalification status and a shared data standard for a service network.
In preparation
Damage report, documentation, estimate, decision, repair and settlement in one process.
Planned
Controlled, auditable access to selected data and integrations, granted case by case.
In preparation
Start with the tools you need today. Extend RepairCore with more features, data and integrations when they are actually needed.
Prices are net per organisation, billed monthly. Add-ons and usage are billed separately from the subscription.
See the full price list
In the trade since
1998
RepairCore Cloud is being built out of real automotive experience: work with service shops, the eCarService locations, fleets, partners and workshop relationships built since 1998.
That is why what we design is not only an application but a way of working: from the first customer contact, through the vehicle and the work order, to documents, decisions, statuses and service history.
Ecosystem register
RepairCore Cloud is the technology layer for a whole vehicle-service ecosystem. Part of it runs in production today, part of it is still being built — here is where each piece actually stands.
Component
Scope
State
The current SaaS platform, being evolved towards RepairCore Cloud.
Running
A network of workshops and partners working to one data and process standard.
In preparation
Controlled access to selected data and processes, granted case by case.
In preparation
A short walkthrough against your processes: what can be joined up, what can be simplified, and what is better left alone.