A role-aware hotel operations platform bringing rooms, tasks, requests, attendance, manuals, meals, notifications and team communication into one system.
Zerrenpach
01 / Overview
One internal system for a hotel's daily operation
Zerrenpach is a mountain hotel and resort in Látky, Slovakia. Running it means coordinating people who never sit at the same desk: reception, kitchen, housekeeping, maintenance and management, each on their own shifts and each needing different information.
Working full-stack as part of the BeCode team, I helped design and build the internal platform that carries that coordination: rooms, tasks and requisitions, attendance, meals, manuals, notifications and team chat in one role-aware system.
02 / Challenge
A hotel cannot be run from WhatsApp groups
Before the platform, operational communication lived in WhatsApp groups. A request raised in a message thread has no owner, no state and no history: whether it was seen, taken or finished depended on somebody remembering to reply.
The replacement had to respect how differently each position works. An owner needs oversight of everything, a shift manager needs their operation, the kitchen needs meals and its own tasks, and housekeeping needs to see the rooms for today, each without wading through everyone else's noise.
03 / Approach
Roles decide what each person sees
Every employee signs into the same application and gets a different view of it. Roles carry permission sets, individual users can be granted overrides, and rooms, tasks and manuals are visible only to the positions they concern. Tasks cover one-off jobs, staff requisitions and recurring templates, each with a state instead of a message thread. Attendance is recorded as arrivals and departures in the same system, meals and manuals live alongside, and the built-in chat (direct and group, with presence) runs on Supabase Realtime, the same platform that provides authentication and file storage behind the NestJS and Next.js application. The system is internal to the hotel's operation, so this case study stays general: no client data, and the only interface shown is the public sign-in screen.
04 / Results
The operations moved out of message threads
The platform has been in daily operation since 2024. Requests that used to be WhatsApp messages are now tasks with an owner and a state, attendance is recorded where the work happens, and every position sees its own slice of the same system.
Since 2024
In daily operation
The hotel's staff coordinate their shifts, tasks and communication inside the platform rather than across message threads.
12
Operational modules
Rooms, tasks, requisitions, attendance, meals, manuals, documents, notifications and chat share one data model and one sign-in.
05
Role levels, one application
Owner, operations manager, administration, kitchen and custom staff positions each get their own view, with per-user permission overrides when a role is not enough.
