Please write in your response:
Briefly describe the proposed stack.
Show 1–2 examples of similar projects.
Propose deadlines and budget for this specification.
Indicate whether there will be support for bugs after launch (1–2 months).
Development of a website for a bus carrier with online ticket purchasing and seat selection (to be done like the type/analog of eclub.com) with our branding and color scheme
It is necessary to develop a small but reliably functioning website, where passengers can:
choose the desired direction,
see available/occupied seats on the bus,
make a reservation and pay for the ticket online,
receive discounts / bonuses / cashback through a simple loyalty program.
Important:
Make a maximally simple in implementation and cost option (MVP),
but ensure that everything works stably in real combat (minimum bugs in payments and reservations).
The website in spirit and logic is a simplified analog of the website eclub com, but not an aggregator, rather one carrier and 4 directions
Detailed specification for the website:
1. Routes
Support for 4 directions is needed:
Odesa → Bukovel
Bukovel → Odesa
Kyiv → Bukovel
Bukovel → Kyiv
The ability to add/remove directions in the future.
2. User functionality
Main page:
Brief information about the company + advantages (comfort, safety, etc.).
Search form for routes:
Direction (from/to),
Date,
Number of passengers,
Button "Find a route".
Block with popular directions (route cards).
Links to social networks.
List of routes (search results):
List of routes by selected direction and date.
For each route: departure/arrival time, price, availability of seats.
Button "buy a ticket".
Calculation of the total for selected tickets.
Order processing:
List of selected seats, total amount.
Passenger(s) data: first name, last name, phone, email.
Promo code field (for discount).
Display:
base price,
discount from promo code (if any),
cashback that will be credited,
total to pay.
Checkbox agreeing to the rules.
Button "Pay".
Payment:
Mini-cabinet (simplified):
Authorization by email + code/link.
Order history: route, date, seats, amount, status.
Display of current cashback balance.
3. Loyalty program
Cashback: fixed % of the ticket price (for example, 5%).
Cashback accumulates in the cabinet balance.
With a new purchase, the client can use cashback as part of the payment.
Promo codes: fixed amount or %, validity period.
4. Admin panel
A simple but functional admin panel:
Management of routes and schedule of routes (date/time, price, bus, status).
Management of buses and seating plan.
Viewing orders:
filter by date/route,
payment status,
passengers, seats.
Management of promo codes and basic % cashback.
Viewing clients and their cashback balance.
Editing texts of main pages (about the company, rules, contacts).
5. Technical requirements
Responsive design (mobile priority).
Stack — at the discretion of the performer (CMS or framework), the main thing:
Protection against double selling of one seat during simultaneous bookings.
The ability to add a second language in the future (UA/EN), currently can start with one (UA).