If a car is missing, submit the details here. The request will feed the admin queue so the model profile can be created properly with weak points, mileage logic, images and buyer checks.
Why requests matter
Duewise becomes more useful as the database grows in the direction real users need. Unsupported vehicle requests help prioritise makes, models, engines and common faults.
The registration or model was not matched to an existing Duewise profile.
The model exists, but the exact engine, trim, generation or year range needs adding.
The vehicle profile exists, but it does not yet have enough known faults or buyer checks.
The vehicle is supported, but needs a proper model image or visual profile.
Vehicle request form
Send the details needed to review missing or incomplete vehicle coverage.
A request with make, model and engine is much more useful than just “my car is missing”.
Registration, if available.
Make and model.
Engine size and fuel type.
Year or generation.
Mileage.
Advert price.
Advert text.
Any known issue you want Duewise to include.
In the final admin system, repeated requests should be grouped by make/model/engine. The most searched unsupported vehicles should be added first.
A model should only become public once the profile has enough useful data: weak points, maintenance evidence, buyer checks, mileage logic and image support.
Admin workflow
Vehicle requests help prioritise the makes, models and engines that need stronger coverage.
The user sends vehicle details and why the model is needed.
The request appears in the admin unsupported vehicle queue.
Admin adds make, model, engine, years, image, faults and maintenance rules.
Future searches can generate a better report for that model.
If the model is already in the database, the check flow should take you straight to a buyer report.