01
Work orders
Diagnosis, estimate, approvals, photos, documents and completed work all stay on one job.
RepairCoreWork order RO-1042
- Diagnosis complete
- Estimate sent to customer
Demo view · sample data
The whole vehicle service.
One workflow.
The automotive workshop, the fleet and the service network work from the same vehicle record: VIN, booking, repair order, estimate, approvals, documents, repair status and history.
For automotive workshops, service networks and fleets
RepairCore
Dashboard
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
Workshop load
Work orders opened and closed over the last 12 months
Open work order
The front desk, the shop floor and the customer see the same record
Work order
RO-1042
- Vehicle
- Demo Vehicle · DEMO-PL-12
- VIN
- VIN_DEMO_7841
- Customer
- Customer 001 · Fleet A
- Received
- 12.03.2026 · 10:30
- DiagnosisComplete
- EstimateSent
- ApprovalAwaiting
- RepairScheduled
Demo view · sample data
- 1VIN
- 2Booking
- 3Repair order
- 4Estimate
- 5Approval
- 6Documents
- 7Repair status
- 8History
Six tools, or one system.
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
PhoneExcelCalendarNotesSeparate CRMMessages
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
RepairCore
Work orders
Open work order
Everything that used to sit in six places
RO-1042
- Customer
- Customer 001 · Fleet A
- Vehicle
- Demo Vehicle · DEMO-PL-12
- Slot
- 12.03.2026 · 10:30
- Scope
- Periodic inspection
- Documents
- Handover note, estimate, invoice
- Contact
- Thread with customer and fleet
Demo view · sample data
The workshop, the fleet and the customer look at the same state of the job - nothing retyped, nobody asking who has it now.
The information you need at every stage of the job.
A work order holds the customer, the vehicle, the slot, the paperwork and the team's communication in one place.
02
Customers and vehicles
Earlier repairs, documents and recommendations are already there at the next visit.
RepairCoreVehicles
- 01Demo sedan · Customer 001
- 02Demo SUV · Fleet A
Demo view · sample data
03
Work planning
Appointments, bays and team responsibility in a single view.
RepairCoreCalendar
Wed, 18 March09:00
Periodic inspection · bay 2
Demo view · sample data
04
Automation
Automation carries the repetitive steps and the messaging. Diagnosis and cost stay with a person.
RepairCoreAutomation
- To doInvoice
- In progressCustomer SMS
- DoneInspection
Demo view · sample data
05
Reports
Current figures on work orders and workshop throughput, with no export to a spreadsheet.
RepairCoreReports
156+18% MoM
Demo view · sample data
06
Integrations
Agreed data and services wired into a specific stage of the job - access granted case by case.
RepairCoreIntegrations
- Subscription billing
- Online payments - in development
Demo view · sample data
07
Scanning the vehicle registration document
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.
RepairCoreAdd vehicle
- Document photo
- Vehicle data read
- Checked at the front desk
- Saved to the record
Demo view · sample data
The data where the work actually happens.
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 vehicle's whole history in one place.
Earlier repairs, documents, recommendations and status - there at every next visit, with no digging through binders or separate systems.
RepairCore
Vehicles
Active work order
Demo Vehicle · Customer 001
VIN_DEMO_7841 · DEMO-PL-12
Service history
- 12.03.2026 - Oil change
- 02.11.2025 - Periodic inspection
- 18.06.2025 - Air conditioning repair
Documents and recommendations
- Handover note
- Invoice RO-1042
- Recommendation: brake pads in approx. 5,000 km
Demo view · sample data
Shared information for the workshop, the network, the fleet and partners.
01
Repair workshop
Bookings, work orders, the day plan, documents and customer contact in one process.
02
Service network
New locations on one shared service standard, with process visibility across the network.
03
Fleet
Vehicle status, cost approvals, documents and service history without phoning round the workshops.
04
Automotive partner
Agreed data and services wired into a chosen stage of the job, within a controlled scope.
Explore RepairCore by use case
Common starting points - pick the one closest to your problem.
RepairCore, module by module.
Module register
RepairCore Cloud is one process made of several modules, developed out of the real ECS Cloud platform. Here is the scope of each one.
RepairCore Workshop
Work orders, calendar, documents, customer approvals, full vehicle history and a reconstructable decision trail in one service process.
RepairCore Fleet
Vehicle statuses, downtime, cost, decisions and B2B communication for fleet managers.
RepairCore Network
Partners, locations and a shared data standard for a service network - built on a history of 500+ service relationships and rolled out to further partners after verification and consent.
RepairCore Claims
Damage report, documentation, estimate, insurer decision and settlement in one process, running today in production with an insurance partner.
RepairCore Partner API
Controlled, auditable access to selected data and integrations, granted individually to technical partners after verification and consent.
A plan that matches where your organisation is today.
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 listThis is not a software project. It is practice since 1998.
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 the same company’s whole vehicle-service ecosystem. Here is the scope of each element.
ECS Cloud
The current SaaS platform, being actively evolved towards RepairCore Cloud.
RepairCore Network
A network of workshops and partners working to one data and process standard, built on a history of relationships going back to 1998.
Partner API
Controlled access to selected data and processes, granted individually to technical partners after verification and consent.
The network does not start from zero. It now gets a digital standard.
RepairCore Network is being developed as a requalification program for service relationships built since 1998. Historical datasets include service centers, authorized-service capabilities, multi-brand workshops, body shops, paint shops and claims-handling partners in Poland. The current status of each partner requires renewed verification, contact, consent and confirmation of cooperation scope.
500+
Historical service records for requalification
16
Provinces in the historical relationship base
118
Records from the earlier eCar structure
Historical data. Current partner status requires renewed verification, contact, consent and confirmation of cooperation scope.
Historical data used in the requalification program is verified before publication. Public partner presentation requires up-to-date data, confirmed cooperation scope and publication consent. Entities contacted as part of relationship updates may request data updates or opt out from further contact.
Province register
- Wielkopolskie68
- Mazowieckie62
- Śląskie58
- Podkarpackie45
- Małopolskie38
- Dolnośląskie35
- Warmińsko-mazurskie29
- Zachodniopomorskie29
- Kujawsko-pomorskie25
- Łódzkie23
- Pomorskie21
- Lubelskie17
- Lubuskie16
- Opolskie16
- Podlaskie13
- Świętokrzyskie10
Competency categories
- Mechanical service
- Diagnostics
- Authorized or specialist competence
- Multi-brand service
- Body & paint
- Claims handling
- Fleet service
- Regional partner
Partner requalification process
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.