Talking about digitalisation in the dismantling business rarely means new software. It means that facts which arise anyway — which vehicle came in, what was removed, where it is, what it cost — are not captured three times by hand and forgotten once. The rest follows almost by itself.
Why the timing is good
Three developments are converging, and all three reward businesses with clean data:
- Parts buying is online. Workshops and end customers search by numbers and filters. What is not held as structured data does not exist for that search — see IAM: the independent aftermarket and where dismantlers sit in it.
- Reuse is gaining regulatory weight. The European reform of end-of-life vehicle law puts components more firmly at the centre than pure tonnage — see EU ELV Regulation 2026/1738: timeline and impact on businesses.
- Record-keeping duties are growing. What has to be documented anyway can use the same data basis as sales — see The German end-of-life vehicle ordinance: duties for owners and dismantlers.
Put differently: the effort for clean data increasingly arises regardless. The only question is whether it comes on top of daily work or is absorbed into it.
The sequence that pays
Digitalisation projects rarely fail on technology and almost always on sequence. This one works:
| Step | What it brings | Effort |
|---|---|---|
| A vehicle file per VIN | Every later entry has an anchor | Low |
| Resolve vehicle data automatically | No typing of year, engine, gearbox | Low, per request |
| Photos at removal instead of notes | Numbers do not get lost | Low |
| Cross-check OE numbers by machine | Search hits and fewer returns | Medium, per request |
| Keep stock once, publish many times | One record, several channels | Medium |
| Interface to the ERP system | No more duplicate capture | Higher, one-off |
What changes measurably
- More parts sold from the same vehicle. Not because more is removed, but because more can be found.
- Fewer returns. Evidenced fitment instead of „should fit“.
- Shorter handling time per enquiry. The number is in the system, not in a colleague's head.
- Better purchasing decisions. With every part attached to a vehicle, revenue per model line becomes calculable.
- Calmer audits. The vehicle file is the audit file.
Why it fails in practice
- Started too big. A whole system that does nothing useful for a year does not survive daily reality.
- Capture in the wrong place. Recording only back in the office means the vehicle link is already lost.
- Two truths. Maintain the stock list and the marketplace separately and they diverge within weeks.
- Contracts that do not fit the volume. An annual contract for data services needed twenty times a month does not pay — and then goes unused.
What data cannot do
One honest note at the end: no data service knows whether a control unit needs coding after fitting, whether a wing has a dent, or whether a previous owner fitted something that does not belong to the vehicle. Those judgements stay with the business. What data delivers is the assignment — and the honesty to show a gap as a gap rather than filling it plausibly. A guessed value in a part record is worse than an empty field, because it looks like a measurement.
Frequently asked
Where do I start if I can only take one step?
With the vehicle file per VIN. It is the anchor everything later hangs off, and it costs almost nothing.
Does it pay off for a small yard?
Especially there, because a small business feels every return and every minute of searching directly. What matters is a contractually agreed billing model that fits the business and its volume.
Do I need a new ERP system for this?
Not necessarily. Most of the benefit comes from capturing in the right place. An interface pays only once volume makes duplicate capture expensive — see Connecting an API: when it pays off for dismantlers.
How long before it shows?
The effect on findability and returns shows within weeks. Statements about purchasing decisions need a few months of data history.