Every car that pulls onto your forecourt,
understood.
Type of vehicle, time on bay, plate read against DVLA. ICE cars in EV bays. EVs that finished charging twenty minutes ago and still haven't moved. Cloned plates trying to drive off without paying. All from the cameras you already have on the forecourt.
Four things that pay for the camera in a fortnight.
Make, model, body type, fuel.
Saloon, SUV, van, lorry — and one level deeper where the visual signal allows: make, model, fuel type (petrol, diesel, EV, plug-in hybrid). Useful for fleet attribution, segmenting forecourt traffic by customer type, and the rules that follow (see ICEing).
An ICE car in an EV bay is an alert.
Petrol or diesel cars parked in EV charging bays block paying EV customers. We detect the vehicle, classify the fuel type, check whether the bay is an EV-only bay, and flag in seconds. The forecourt operator decides whether to escort, ticket, or call the recovery contract.
Integrate with the charger; alert when charging ends.
Hook into the charge point's API to know exactly when a session ended. The CCTV continues watching the bay; if the EV is still there ten or twenty minutes after the session closed, the operations team gets a ping with the plate and the timer. Most networks charge an idle fee — this lets you actually enforce it.
Drive-offs and cloned plates, caught at the bay.
Plate OCR is cross-referenced against DVLA / DVSA records. Vehicles whose make / model / colour don't match the registered plate are flagged as likely cloned — the kiosk can request prepayment before the pump unlocks. Genuine fleet vehicles get the smooth experience; the suspicious ones don't get free fuel.
Two integrations, one camera.
Forecourt analytics works on its own — but most operators get the most value when we wire two existing systems into the detection stream:
OCPP or vendor API.
We poll the charger's session state — start, end, kWh, fault codes. The platform knows the moment a session ends, so the overstay timer starts at exactly the right second. Compatible with most major charge networks and OCPP 1.6 / 2.0.1.
Plate against record, in seconds.
Each plate read goes via the DVLA Vehicle Enquiry API for make / model / colour / tax / MOT, and against DVSA records where the deployment requires it. Mismatches trigger a kiosk-side prepayment request before the pump unlocks. Used for fleet attribution, never for identification of individual drivers.
What you receive, row by row.
Plates, not faces.
Number plates are processed against DVLA / DVSA records for vehicle attribution — they are never used to identify the driver. Faces in the camera feed are anonymised in RAM before any clip is persisted. The deployment runs under a UK-GDPR-compliant data-processing agreement that names DVLA and DVSA as the only third parties the plate is shared with.
First detection on day one. No financial commitment for two weeks.
If we can't reach the accuracy you agreed within two weeks, you pay nothing — and we remove anything we installed.