BOOKING
Book a scooter
Rider qualification, then the full total, then payment. You see everything you are agreeing to before you pay anything.
The booking flow below is the specification Revura needs, laid out as a design reference. It is not a working form and it does not take payment. Which parts the existing plugin can deliver is settled by the WordPress audit. The brief bars replacing the booking plugin without approval and bars forcing booking functionality into Elementor HTML widgets, so anything the plugin cannot do gets documented as a limitation and an alternative proposed – not bodged in.
The booking flow
Seven steps. The easy one is first, and payment comes only after you have seen the total and the terms.
Check date availability
Done on the availability page. No commitment.
Confirm rider eligibility
Experience, licence, age and weight, against the published requirements.
Pickup or delivery
Port Zante, or an address for delivery, with the fee shown.
Review the total price
Rental, fees, deposit and terms, in full, before payment.
Pay the booking amount
Only the booking amount now. The balance is settled at pickup.
Upload documents
Licence and ID, where the flow requires them, over a secure upload.
Receive confirmation
Written confirmation with pickup instructions and what to bring.
Reminders before the day
A reminder of what to bring, and the licence step if it applies.
What the booking must capture
The specification the booking plugin is measured against. Anything it cannot capture becomes a documented limitation with a proposed alternative, per brief section 27.
The rental
- Rental date
- Pickup time
- Return time
- Rental duration
- Which scooter, by individual inventory
- Pickup or delivery, and the address
The rider
- Rider age
- Licence country
- Licence type and class
- Years of riding experience
- Date last ridden
- Passenger, yes or no
- Combined weight
- Cruise ship, or accommodation
The commitment
- Document upload
- Terms acceptance
- Digital signature
- Payment
- Booking deposit
- Security deposit handling
- Confirmation and reminders
- Cancellation handling
- Availability blocking across following dates
Before you pay, you see this
A worked summary, not a total with “fees may apply” underneath. This is the design the booking plugin’s checkout is styled to match.
Booking summary
| Scooter | make, model, year |
| Dates | Example – your selected dates |
| Rental | rental price |
| Delivery | delivery fee |
| Additional approved rider | fee |
| Tax | tax |
| Total rental cost | total |
| Due now, to book | due now |
| Due at pickup | due at pickup |
| Security deposit at pickup | deposit |
Document upload
Where the flow asks for a licence or ID, that upload has to be handled properly. The build requirements:
- File types restricted and validated
- Uploads not publicly reachable by URL
- Access limited to who needs it
- Retention limited - documents deleted once the rental is closed
- Storage location and access documented
- Never sent to analytics or advertising platforms
BUILD NOTE - REMOVE BEFORE LAUNCH
Booking outcome pages
Every outcome needs a real page. These are built and linked so nothing dead-ends.
Booking confirmed
What to bring, where to go, what happens next.
Booking failed
The date went while you were filling the form.
Payment failed
Card declined, and how to recover the booking.
Enquiry received
Confirmation after a WPForms submission.