The problem
Customers arrive with a vehicle class and a date range in mind. If the site shows a fleet but cannot connect it to dates, every enquiry becomes a phone call to check availability — and every phone call outside working hours is a booking that goes elsewhere.
The operational problem sits behind that: whoever runs the counter needs to see enquiries, vehicles and dates in one place, and they are not going to use a system that requires training.
What I built
A fleet catalogue in PHP and MySQL where each vehicle is a record with its own specification, rate and photographs, so the fleet can change without touching the site.
A date-aware enquiry flow that captures vehicle, dates and customer details together, so a request arrives complete rather than as "is anything available next week".
An admin view designed around the daily task — see today, see the week, see one vehicle — rather than around the database structure underneath it.
Decisions worth explaining
The build stayed on PHP and MySQL on standard shared hosting, because that is what the business can renew and manage independently. Building on a stack the client cannot afford to keep is a way of guaranteeing the site dies in eighteen months.
Enquiry rather than instant payment was the right model here. In this market the operator confirms vehicle condition and documentation before committing, and forcing prepayment into a process that genuinely has a verification step creates refunds rather than bookings.
Want something like this?
If you are looking at this because you need the same thing built, send me the brief. You will get a reply within one business day and a fixed-scope quote before anything starts.