Availability logic
Stay dates, occupancy, room status, private-room capacity, active dorm beds, overlaps, and temporary holds shape what can be requested.
Manu Startup House needed a better way to manage a hospitality workflow spread across spreadsheets, team conversations, and Reseliva. I designed and built the product end to end—from UX and interface design to frontend, backend, data services, and integrations.
The core challenge was not simply collecting a reservation. It was connecting direct booking requests, room and bed availability, reservation states, assignments, guest records, and externally sourced reservations in one operational workflow.
I owned the project from end to end: product and workflow discovery, UX and interface design, frontend development, backend and API work, Firebase data services, booking logic, and the external reservation synchronization layer.
Stay dates, occupancy, room status, private-room capacity, active dorm beds, overlaps, and temporary holds shape what can be requested.
Guests submit a booking request; staff can assign, confirm, update, cancel, or check out the reservation.
List, board, and calendar views connect reservations with room and bed management, guest records, and daily operations.
Start with how reservations are coordinated before the product exists.
Bring the availability rules out of manual work and into the system.
Give administrators a practical way to manage booking operations.
The project turned a workflow spread across spreadsheets, chats, and Reseliva into a shared product for booking requests, availability, reservation operations, assignments, guest records, and supporting hospitality work. No unverified performance metric is used.
The application covers reservation list, board, and calendar views; room and bed inventory; guest profiles; assignment workflows; payment-status tracking; and supporting operational areas such as tasks, shifts, inventory, finance, volunteers, and events.
Even if it's rough. Especially if it's rough.