Hi all, hope you don't mind a newbie coming in asking questions! I will come back with thanks/answers to any follow-ups :-)
After hanging onto my last car for ages I'm now looking to buy a Mazda 3 Sport and have found a tasty looking one for sale at a reputable franchise dealer, with number plate SR11GYS. This checks out on the DVLA vehicle check, MOT history and an HPI check: all match the actual car details as seen in the advert photos etc.
But if you put that reg number into any of the insurance comparison sites, or direct on most insurers' websites, or e.g. on tyre supplier websites, they come up with the wrong model - they seem to think it is a Mazda CX-7 instead. Some of them let you enter the details manually for a quote, but then won't actually supply. I got an email reply from DayInsure saying that because their computer could not match the car plate, they could not insure at all.
However, after a bit more digging I found the plate is recognised correctly by DirectLine, and they gave a decent quote. It also comes up OK with e.g. Green Flag for breakdown and AutoCarParts.
I've informed the selling dealer and asked them if they can do anything - no reply as yet - and also asked various of the sites that it came up wrong on to ask whoever provides their data to correct it in line with the (correct) data the DVLA has. Credit to DayInsure who were the only ones to reply and say they'd make the request, but couldn't guarantee if/when it would get fixed...
Given all of the above, would you go ahead and buy? Car seems basically legit according to DVLA (I phoned them to double check and they could see nothing wrong). But if no insurer recognises it I could be tied into Direct Line...
Anyone know which database is messed up exactly, and who to contact to get it amended? What's the chances of being able to get this error fixed?
Thanks in advance for any advice!
Cheers
Pete
EDIT - sorry forgot to mention that the HPI check included a number plate change alert as follows:
but the chap at the DVLA said that was so long ago that no way should the change not have reached all relevant databases.
Edited by bikepete on 11/07/2018 at 09:48
|