Hotel operations / Project case study
HotelMotel
A Django backend organized into hotel, room, guest, booking, housekeeping, billing, and access-control applications.
01 / Context
The problem
Hotel operations need to connect reservations, guests, rooms, prices, and actual stays while controlling who may perform sensitive booking actions.
My role
I implemented hotel and room endpoints, booking creation, listing and detail APIs, and later expanded the booking lifecycle with confirmation, cancellation, check-in, checkout, no-show flows, hotel-context permissions, and automated tests.
02 / Engineering
Technical decisions
Booking, BookingRoom, and Stay are separate models. BookingRoom connects a reservation to rooms and nightly prices; Stay records actual check-in and check-out independently of planned dates.
Explicit permissions cover actions such as confirmation, cancellation, check-in, refunds, and price access. This provides finer authorization vocabulary than a single general editing permission.
Separate Django applications organize bookings, rooms, guests, billing, and housekeeping, giving each domain a clear place in the backend.
03 / Delivery
What the project delivers
The backend includes reservation and stay records, room associations, monetary fields, and booking-action permission definitions. These form the foundation for the hotel operations API.
Technical focus
A closer look at the implementation.
- Django REST API
- Booking and stay records
- Room and hotel services
- Role and permission models
Let’s talk about the work.
Interested in the technical decisions behind this project? Get in touch.
Start a conversation ↗