How to choose ELV software.

1. Start with your regulator

Your regulatory regime shapes the checklist. A UK ATF answers to the Environment Agency / SEPA / NRW / NIEA, files Certificates of Destruction to the DVLA, and operates under the End-of-Life Vehicles (Producer Responsibility) Regulations 2005. A Finnish dismantler answers to Traficom and the regional ELY centres under the Finnish implementation of EU ELV Directive 2000/53/EC. Score the platform against your regulator's actual documentary requirements, not against a generic compliance slide.

2. Mandatory capabilities

The capabilities below are non-negotiable for any platform claiming ELV coverage. Score each candidate explicitly.

• Depollution as a first-class workflow stage with role checks and signed certificates.
• Per-vehicle audit trail capturing operator, role, time, and value for every state transition.
• Material-stream capture by weight (fuel, oil, brake fluid, coolant, refrigerant, battery, airbags).
• Certificate of Destruction issuance and DVLA filing (UK) or equivalent registry update (FI).
• Per-VIN chain of custody from intake through final destruction.
• PDF document archive, indefinite retention, full export.
• GDPR-compliant customer and operator records.

3. Strongly preferred capabilities

Beyond the mandatory list, the capabilities below separate a passable platform from a strong one.

• Configurable dismantling state machine per yard.
• Multi-channel parts listing reconciled to a single ledger.
• Rules-engine pricing per part and per market.
• Hardware abstraction (Code-128, QR, ZPL printers, mobile capture).
• Public REST API with outbound webhooks.
• SSO / SAML for head-office staff lifecycle.
• Battery Passport readiness against the upcoming EU regime.

4. The scoring rubric

Use a 0–3 scale per capability. 0 = absent. 1 = present but bolted on. 2 = native and usable. 3 = native, audited, and demonstrated against your data shape. Weight mandatory rows at 3x and preferred rows at 1x. Score every candidate at the same level of granularity.

Decline to score against marketing slides. A demonstrated, audited, against-your-data score is worth more than a self-reported one. Most platforms will agree to a short pilot at this stage.

5. The five questions to ask in the demo

These are the questions that tend to separate strong ELV platforms from passable ones.

• Walk me through depollution against one of my real vehicles, end to end.
• Show me the audit trail for a CoD issued in the last week.
• Show me how you handle a part that's been dismantled but never binned.
• Show me how the same part lists in PrestaShop and the walk-in counter without double-selling.
• Show me the export I'd hand to my regulator at audit time.

6. Hardware compatibility — a one-day check

Most yards arrive with hardware they already own — Code-128 / QR scanners, ZPL-compatible label printers, mobile capture devices. The platform either reads that hardware or asks you to buy new. The right check is a one-day sandbox: take a scanner off the floor, point it at the candidate platform, and see if it produces a clean read on a Code-128 label. Take a label printer, send it a ZPL template, and see if the label comes out correctly. If either fails, the deployment will cost more than the platform fee will.

Hardware compatibility is the cheapest scoring row to evaluate and the most reliably under-scored in demos. Most candidate vendors will say their platform reads any HID scanner, and most actually do — but the demonstration is worth more than the claim, particularly for the printers and the older scanners.

7. Integration shape, by stage

Score integration shape against the stage you most depend on. Yards with significant PrestaShop revenue weight the sell-stage integration depth heavily. Yards with significant insurer-write-off intake weight the acquire-stage integration with auction systems and insurer feeds. Yards running large EV traction batteries weight the report-stage Battery Passport readiness highly. Yards with corporate parent ERPs weight the report-stage CSV export and REST API integration.

The integration directory on a candidate platform should list every connector with its direction of flow, sync cadence, authentication mechanism, and setup time estimate. A platform with vague language on these dimensions is hiding something. Ask for the specifics in writing, with the relevant stage flagged.

8. Total cost of ownership

Platform fees are the visible cost; implementation, integration, and migration are the rest. Ask the candidate for an itemised quote covering configuration, channel integration, data migration, staff training, and the cost of the regulator-facing reporting you specifically need. A platform that quotes a low platform fee but a long professional-services tail is not cheaper than one that quotes higher platform with bundled professional services.

Watch for the hidden costs the demo does not surface. Custom integrations that the platform implies are part of the quote but are actually bespoke builds priced per project. Migration tooling that the platform implies is available but is in practice a manual import done by professional services. Training time for staff that the platform implies is short but in practice takes weeks for a multi-yard team. These costs are real and they need to be itemised in the quote.

Annual platform fees scale with the operating shape. Single-yard fees are sized for one site. Multi-yard fees scale with yard count and integration depth. Aggregator Enterprise fees are typically negotiated against the network size and the integration scope. Ask explicitly which tier matches your operating shape and what the upgrade triggers are inside the platform's pricing.