An independent garage sells almost nothing that resembles what a dealership sells. It sells workshop time, fitted parts and avoided downtime. Yet when it grows (a second site, the acquisition of a body shop, fleet contracts), its owner ends up facing the same question as distribution groups: keep the garage software, move to an ERP, or stack the two?
This article is written for owners and finance directors of multi-site garages, repair groups and body shops with 10 to 150 employees. It does not cover new and used vehicle sales: for franchised dealers, read our guide to ERP vs DMS for car dealerships. Here, the angle is independent repair.
Why a Repair Workshop Is Not a Dealership
A Business Model Built on Time Sold
At a dealership, margin is made on the vehicle, the financing and the related services. In an independent workshop, it comes from three levers: labour billed, margin on parts, and the utilisation rate of lifts and paint booths. A technician hour that is not sold is lost forever, unlike a stock of parts that can still be sold next month.
That changes the central object of the information system. For a dealership DMS, it is the vehicle sold. For a workshop, it is the repair order (RO, or job card), which brings together the vehicle, the customer, the estimate, the time spent, the parts used and the invoice.
Vehicle Downtime as a Constraint
A vehicle sitting in the car park waiting for a part or an insurer’s approval blocks a bay and a customer. The software must therefore track not only costs but also statuses: awaiting estimate, awaiting approval, awaiting parts, in progress, ready for collection. A general-purpose ERP cannot do this without heavy configuration, and a spreadsheet stops working as soon as three sites run in parallel.
No Manufacturer to Connect To
A franchised dealer has to speak its manufacturer’s language. The independent repairer relies on multi-brand parts catalogues, standard labour times and third-party technical data. The integration challenge is therefore different: it concerns parts suppliers, insurers and accounting, not a manufacturer portal.
The Business Cycle: From Estimate to Warranty
Estimate, Repair Order and Time Clocking
The standard cycle runs as follows:
- Vehicle check-in and file opening (registration, mileage, history).
- Estimate, with labour and parts pricing.
- Customer approval and opening of the RO.
- Parts reservation or ordering.
- Clocking: each technician records hours by RO and by operation.
- Quality control and RO closure.
- Invoicing, collection and warranty follow-up.
Time clocking is the decisive link. Without it, you cannot tell sold hours from hours actually spent, so you cannot calculate productivity or the real profitability of each repair. Many general-purpose ERPs can record time against a project, but cannot reconcile a standard labour time with the time actually spent on a vehicle.
Body Shops and Insurance Assessment
The body shop adds a step: the estimate is often checked by an insurance assessor. The file goes through an estimate, an assessment, possibly a counter-proposal, then an agreement. Extra work discovered during strip-down triggers a supplementary estimate. The system must therefore:
- keep successive versions of the estimate and their approval status;
- distinguish approved lines from disputed ones;
- track paint, panel-beating and preparation times separately, since they differ in productivity and consumables;
- manage paint consumables, which are hard to attach to a specific RO.
Insurer Billing and Direct Settlement
Part of the activity is billed not to the driver but to the insurer, through direct settlement or within approved repair networks. The software then has to handle split invoicing: the excess (deductible) to the customer, the balance to the insurer, sometimes with discount terms and payment delays specific to each insurer. This is a cash-flow issue as much as a billing one: a finance director who does not track insurer receivables by file quickly discovers discrepancies. Exact terms depend on each network’s contracts, so check them before fixing the target.
Three Architectures Compared
There is no single right answer. In practice, three architectures are found.
| Criterion | Repair DMS only | General-purpose ERP + workshop connector | Integrated sector suite |
|---|---|---|---|
| Workshop coverage (RO, clocking, statuses) | Very good, native | Average, depends on the connector | Very good, native |
| Insurer and body shop flows | Depends on the vendor | Rarely native | Often present, to be verified |
| Accounting and consolidation | Limited, export to accounting software | Strong | Average to good depending on the suite |
| Accounting integration | Interface to maintain | Native | Native or integrated |
| Multi-site and inter-company recharging | Basic, sometimes one database per site | Strong | Variable |
| Implementation cost | Low | High (configuration and integration) | Medium |
| Main risk | Functional ceiling reached at 5 or 6 sites | Workshop poorly served, low technician adoption | Dependence on a niche vendor |
Repair DMS Only
This is the natural choice for a single garage or a few sites. The DMS knows the RO, clocking, parts catalogues and workshop invoicing. It simply exports entries to accounting software. Its ceiling appears with growth: consolidation across entities, detailed analytics, group cash management.
General-Purpose ERP with a Workshop Connector
The ERP is kept for finance, purchasing and inventory, and a workshop module or application is plugged in for the RO. On paper the architecture is powerful, but it moves the difficulty to the interface: who is the master of items, customers, vehicles and stock? If the workshop has to key data twice, technicians and front-desk staff will bypass the tool. Integration cost is often underestimated, as in most projects covered in our guide to choosing an ERP.
Integrated Sector Suite
Some vendors offer a suite designed for repair, with workshop, parts, accounting and reporting in a single product. The benefit is data consistency. The risk is dependence on a niche player: check its longevity, the frequency of its updates and its ability to keep up with regulatory changes. Only shortlist a vendor on the basis of references you can verify with customers of a size comparable to yours.
Spare Parts: The Second Margin Engine
Catalogues and Supplier Orders
Estimating speed depends on the quality of access to parts catalogues. A good tool should offer search by registration number, compare availability and prices across several wholesalers, and turn an approved estimate into purchase orders. Manual entry of part references is the first source of errors: wrong part ordered, a return, a vehicle held one more day.
Stock, Obsolescence and Returns
A workshop’s stock is paradoxical: few parts sit on the shelf by design, yet consumables, common wear parts and unprocessed returns pile up. Set rules:
- a minimum stock limited to fast-moving parts and consumables;
- a part ordered for an RO is attached to that RO, not to general stock;
- supplier returns are recorded within a maximum delay, otherwise the credit note is lost;
- unused parts are reviewed monthly to detect obsolescence.
Handling supplier returns and warranties follows the same mechanism as described in our article on ERP for warranty management, returns and after-sales claims.
Workshop Profitability Indicators
Four indicators are enough to run a workshop. They can only be calculated properly if clocking is reliable.
- Productivity rate: hours billed divided by hours clocked. It measures a technician’s ability to work within the standard time.
- Efficiency (utilisation) rate: hours clocked divided by hours present. It reveals idle time, waiting for parts and poorly managed breaks.
- Average value per RO: average revenue per repair order, split between labour and parts.
- Margin per RO: labour and parts billed minus the cost of time and parts consumed.
A gap between productivity and efficiency leads to two different diagnoses: low productivity points to a skills or labour-time problem, low efficiency to an organisational one (scheduling, reception, parts supply). A tool that does not separate them cannot help you fix the workshop.
Reference thresholds vary by trade (mechanics, body work, tyres) and by network. Compare yourself first with your own history by site, then with benchmarks published by your trade association, rather than a figure found at random.
Multi-Site Groups
Consolidation and Analytics
Once the group has several legal entities, the finance director needs consolidation, analytics by site and by activity (mechanics, body work, parts) and group-wide cash tracking. This is typically where a repair DMS alone hits its limit, and the reason ERP enters the discussion.
Inter-Site Stock and Recharging
A part ordered for site A but available at site B must be transferable without re-keying, with clear internal recharging. Without rules, each site inflates its stock as a precaution. Decide before the project whether sites are cost centres or profit centres: recharging depends on it.
E-Invoicing: A Deadline to Build In
The French e-invoicing reform requires, according to the calendar published by Cegid (in French), the ability to receive electronic invoices for all VAT-registered businesses from 1 September 2026, with issuing mandatory on the same date for large companies and mid-caps, then on 1 September 2027 for SMEs and micro-businesses. For a repairer operating in France, this touches the whole chain: parts invoices received from wholesalers, invoices issued to fleets, insurers and companies, and transaction data reporting. Other European countries are following similar paths (Germany, Belgium, Poland and others), so groups with sites abroad should plan for it too. Ask each vendor for its status with respect to certified platforms and the real availability date, not a sales promise. Our guide to choosing a French e-invoicing platform covers this point in detail.
Recommendation by Profile
Single Garage or Two Sites
A repair DMS covers the essentials. Check the quality of the accounting export and access to parts catalogues. An ERP would be oversized and costly to get adopted.
Group of 3 to 10 Sites
This is the trade-off zone. If the group is a single entity with simple reporting, a multi-site DMS is enough. Once there are several companies, inter-company recharging and a need for consolidation, two options hold up: an integrated sector suite or an ERP with a well-interfaced workshop system. In the latter case, designate a master system for each data set before signing.
Industrial Body Shop
The activity rests on insurer flows, workstation management (panel work, paint) and consumables. Prioritise native coverage of these points, then accounting. A general-purpose ERP will not make up for a poorly equipped workshop.
Common Selection Mistakes
- Choosing on the strength of the accounting module demo, when the risk lies in the workshop.
- Leaving technicians out of testing: clocking fails if it is a pain to use.
- Underestimating data migration (vehicle history, customers, stock).
- Not defining a master system for items and customers in a two-tool architecture.
- Not asking for a reference from a customer of comparable size and activity.
- Leaving the e-invoicing deadline until the end of the project.
Going Further
Before launching a tender, structure your workshop, parts, insurer and accounting criteria with our ERP evaluation grid. If your business also includes vehicle or equipment rental, read our ERP comparison for equipment rental.