Every job needs to know exactly what the car is. Most portals make somebody type that out, and somebody types it wrong. RemapDash resolves the vehicle from a UK registration plate or a VIN at the moment of submission — make, model, engine, fuel, year — so the job arrives correct. Unlimited lookups, no daily cap, no per-query charge.
On the surface this is a convenience feature. Nobody enjoys typing "1.6 TDI CR 105bhp" into a form. But convenience is the least interesting thing about it, and the shops that understand why tend to be the ones with the best-run benches.
Consider what happens when vehicle data is typed by hand. A dealer submitting from a phone, in a workshop, mid-job, types what he thinks the car is. Sometimes that is the model on the tailgate rather than the engine variant. Sometimes it is the previous customer's car because the form was half-filled already. Sometimes it is "Golf 2.0" for a car that could be one of half a dozen quite different calibrations. Sometimes it is simply a typo.
You then do one of three things, and all three are expensive:
The third one is the genuinely costly outcome, because it is invisible today and expensive later. Which brings us to the part of this feature that nobody markets.
In the UK, the registration plate is the natural key. Everybody knows it, it is on every job sheet and every text message, and a dealer can read it off the car in two seconds without opening a door.
So the submission form starts there. The customer types the reg, and the make, model, engine, fuel type and year populate themselves. What was a form full of fields the customer would rather not fill in becomes a single box and a confirmation.
Two things follow, and the second matters more than the first:
It also changes the tone of the relationship. A dealer submitting to a portal that already knows the car feels like they are dealing with a professional operation. A dealer typing engine variants into a bare form feels like they are doing your admin for you. Over a year of jobs, that impression is worth more than most marketing.
This is worth stating plainly because the industry has trained people to expect otherwise. Reg lookups on RemapDash are not capped per day and not charged per query. Look up a hundred in an afternoon, look up the same car six times while a dealer works out what he is sending — it does not matter, and it does not generate a bill.
Competing platforms commonly limit lookups per day or charge per query, which produces the absurd situation where a tuner is rationing the single cheapest thing that makes their data accurate. A capped lookup is worse than no lookup, because the day you hit the cap is the day people start typing again — and your records go back to being guesses without anybody deciding that.
The reg plate is the fastest route in, but it is not always the right one, and it is not always available. VIN lookup covers the rest:
A VIN is the vehicle's own identity, stamped by the manufacturer, and it is the closest thing to ground truth available at intake. Where a plate gives you the registered vehicle, the VIN gives you the specific one.
The two are complementary rather than competing: the plate for speed on the majority of UK jobs, the VIN for certainty on the awkward ones. Used together they cover almost everything that walks through the door.
Pulling the threads together, because the individual benefits undersell the compound one:
Yes. RemapDash includes UK registration plate lookup at the point a customer submits a job — the customer types the reg and the make, model, engine, fuel type and year populate automatically. Lookups are unlimited, with no daily cap and no per-query charge, and are included in the flat monthly fee rather than sold as an add-on.
Yes. VIN lookup is included alongside reg plate lookup. It covers the cases a registration cannot: imports, personal plates, non-UK vehicles, and bench or boot jobs where the ECU is present but the car is not. The plate is the fastest route for most UK jobs; the VIN gives certainty on the awkward ones.
Not on RemapDash. Lookups are unlimited with no daily cap and no per-query cost. Competing platforms commonly cap lookups per day or charge per query, which leads to tuners rationing lookups and going back to typing vehicle data by hand — which is how job records become inaccurate.
Because a tuner's project library is only valuable if it is searchable, and it is only searchable if the vehicle, engine and ECU data on every past job is correct. Vehicle details typed by hand on a phone introduce errors that are invisible on the day and expensive years later, when the right past file cannot be found. Accurate intake data is also a precondition for library-based donor matching and automation to work at all.
Yes, significantly. A form full of vehicle fields becomes a single box: the customer types the registration and confirms. That lowers the friction of sending work, which in practice means more jobs submitted — and every field the customer does not have to type is a field they cannot get wrong.
That is what VIN lookup is for. Where a registration record is missing, unhelpful, or does not reflect the actual vehicle specification, the VIN identifies the specific vehicle as built. Both lookups are available on every job.
Unlimited reg and VIN lookup, automatic slave decode, native archive handling, WinOLS LUA bot, branded portal, mobile app and invoicing — £74.50/month for your first 6 months, then one flat £129/month. No per-file charges, no lookup caps, no contract.