RepairCore Cloud

One workflow for the entire vehicle service journey

From booking, diagnosis, estimating and cost approval to completed work, documents and history. Everyone works with current information.

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.

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

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.

Automation supports the team, but it does not replace human decisions.

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.

A workshop team member reviewing data on a tablet

System suggestion

Order brake pads - Demo Vehicle

Confirmed by the advisor

  • Automatic notifications
  • Preparing customer information
  • Data-analysis support
  • Automatic actions after a status change
  • Summaries

Why RepairCore Cloud isn’t another generic system

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 softwareRepairCore Cloud
Assumptions about what software should look likeReal service workflows
Scattered tools and dataOne shared workflow
Open, unscoped integration accessScoped, auditable integrations
Automation without oversightDiagnosis and cost decisions stay with people

A path shaped around your organisation.

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.

Workshop

Plan from the price list

Putting customer and vehicle handling in order first, then further processes in the same environment.

Fleet

FLEETPRO or individual offer

Vehicle coordination, statuses, cost decisions, documents and reporting.

Service network

Individual rollout

Multiple locations on one service standard, with shared data and workflows.

Partner API

Individual integration

A controlled integration scope, roles, audit and the operator’s decision on access.

Claims

Individually with the insurer

Damage report, documentation, estimate, insurer decision and settlement in one process.

What RepairCore Cloud covers.

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.

RepairCore Workshop

Work orders, calendar, documents, customer approvals, full vehicle history and a reconstructable decision trail - one service process from intake to handover.

RepairCore Fleet

Vehicle statuses, downtime, cost, decisions and B2B communication for fleet managers.

ECS Cloud

The current SaaS platform we are evolving RepairCore Cloud out of for further organisations.

eCarService and FleetPoint

Online booking, the customer panel and fleet service coordination at the same company’s live locations.

RepairCore Network

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.

RepairCore Partner API

Controlled, auditable access to selected data and integrations, granted individually to technical partners after verification and an agreed scope.

RepairCore Claims

The damage process from report through documentation and estimate to an insurer decision and settlement - running today in production with an insurance partner.

End-customer payments

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 process - from report to settlement.

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.

RepairCore
Claims

Claims board

Claims by stage

Reported4
  • CLAIM-DEMO-01

    Parking damage · DEMO-PL-12

  • CLAIM-DEMO-04

    Collision · DEMO-PL-24

In estimation2
  • CLAIM-DEMO-07

    Estimate with the insurer

  • CLAIM-DEMO-09

    Inspection booked

Settled9
  • CLAIM-DEMO-03

    Vehicle collected by customer

  • CLAIM-DEMO-02

    Invoice issued

Recent events

CLAIM-DEMO-07 · DEMO-PL-12

  • Photo documentation

    Set of 14 photos · shop floor

    Complete
  • Repair estimate

    Sent to the insurer

    In estimation
  • Insurer decision

    Response due in 3 days

    Awaiting
  • Parts order

    After the insurer decision

    Scheduled

Demo view · sample data

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.