Hotel OS

One system for the whole hotel: reservations on a drag-and-drop calendar, guest folios, a restaurant POS, a QR guest portal per room, accounting, stock, spa and gym, online booking and a channel manager — each hotel isolated as its own tenant, with role-based access from owner to housekeeping.

The Problem

Small and mid-size hotels run on a patchwork: one tool for reservations, another for the restaurant, a spreadsheet for stock and paper for housekeeping. Nothing talks to anything, and the folio is rebuilt by hand at checkout.

The Solution

A single multi-tenant SaaS where every module writes to the same guest and room record. Tenant isolation is enforced in the database with row-level security, and financial history is append-only.

What I Built

• →Front desk with a drag-to-move reservation calendar
• →Restaurant POS charging straight to the room folio
• →QR guest portal per room
• →Accounting, stock, spa/gym and reports
• →Public online booking and a channel manager
• →Eight roles from owner to housekeeping, enforced with row-level security

Highlights

• →Ten modules, one tenant-isolated database
• →Payments are never deleted — only reversed
• →Installable as an app (PWA)

Outcome

• →Live demo with a seeded sample hotel at hotel-management.mehditerzi.com
• →Runs on Supabase with real auth and persistent sessions, also as an installed app