ScanCar guides
Used Car OBD2 Scan Before Buying: A UK Checklist
ScanCar editorial team · Updated 19 November 2026
A pre-purchase OBD2 read can flag an engine issue worth investigating. Get the seller's permission, use read-only menus and treat the result as one part of the vehicle check. A clean engine-code screen does not prove a car is sound, safe or ready for an MOT.
Do the checks in this order
- Use the GOV.UK used-vehicle checklist to match the seller's details to DVLA records and look for safety recalls. Compare mileage and past notices against the official MOT history. An engine scan cannot do either job.
- With permission and the vehicle safely parked, record the dashboard warnings, whether the reader connected, any shown engine codes and their statuses, and the visible emissions readiness results. Do not clear the seller's codes or change any settings.
- Ask the seller about specific observations. Keep photographs or a written summary with permission, without publishing registration or vehicle identifiers.
Turn the result into a buying decision
| Result | Useful next step |
|---|---|
| No codes shown and supported monitors report ready | Continue the history and condition checks; the scan did not cover accident damage, wear or every controller. |
| No codes shown, several supported monitors incomplete | Ask about a recent repair, battery disconnection or reset. This is a reason to seek evidence, not proof that the seller concealed a fault. |
| Warning, code or failed connection | Record the exact result and ask for an independent inspection before committing. A non-connection is not a clean scan. |
Use a vehicle inspection if the price or risk makes a guess expensive, especially if a safety-system warning is present. See what a garage diagnostic check adds beyond a home code read to decide what to request.