Ticket Booking System with Google Sheets & Apps Script | React Seat Reservation System 2025 | E12

A booking system where the customer picks the actual seat off a map, pays from a wallet balance, and prints the ticket — for buses and for events, on the same build, running on Google Sheets.

Choosing a seat, not a quantity

Pick a date within that service's booking window and the seat map loads for it: taken seats marked, free seats selectable. Choose several at once, record each passenger's gender against their seat, add a contact number, and confirm. The layout comes from the seat settings — total seats with rows and columns — so a fifty-two-seat coach and a hundred-seat hall are configuration, not code.

The wallet is the payment layer

Booking requires balance, which sidesteps integrating a payment gateway while keeping the money side real. A user tops up by choosing one of your payment methods, entering the amount and the transaction ID from their bank, and submitting a request. The admin approves or declines it, and the balance updates immediately with an email and a notification. Users can also transfer balance to one another by email address — the recipient is verified and named before the transfer goes.

What the admin runs

Events and buses are managed with a price, description, image, and the start and end dates that define when tickets can be sold. Seat settings sit alongside. Payment methods carry their own instructions and an active status. Users are managed with balance adjustment, every booking is visible and filterable by booking ID, and top-up requests queue for review.

Settings and the record

Currency symbol, currency name, app name and support email are settings rather than code. Bookings produce a printable ticket and a confirmation email, and notifications cover payment approved, balance received and transfer successful. Two roles: users see their own bookings and balance, the admin sees everything.