Sultan Palace
A hotel management platform for a beach resort in Zanzibar, covering guest booking and payment, front desk, food and bar orders, inventory and invoicing.
git clone git@github.com:the-client/sultan-palace.git
Cloning into 'sultan-palace'...
fatal: could not read from remote repository.
The code stays at the hotel. Only the kitchen tickets get printed.
hint: the code is private, the product isn't. It's running live at sultanpalacehotelznz.com ↗
- Role
- Team Lead and Full-Stack Engineer
- Tools
- Next.js · React · TypeScript
- Type
- Hotel Management
- Year
- 2025 to 2026

01 · Overview
Leading a full hotel platform build
I led the build of a hotel management platform for a beach resort in Zanzibar, Tanzania. It has three parts: a public website where guests book and pay, a staff back office for front desk, housekeeping, food and bar, inventory and finance, and print services running on PCs inside the hotel.
I worked directly with the client and hotel staff to turn their daily work into features, and guided two interns through the build. I designed the website and the payment flow, built food and bar ordering, KOT and BOT printing, billing, invoicing and menu management, and designed the inventory module and reviewed the interns' code for it.

02 · Problem statement
A system the hotel owns
The hotel ran on a separate hotel software package and took online bookings only through third-party booking sites. There was no hotel website where guests could book and pay the hotel directly.
The goal was one system of its own: guests book and pay on the hotel's site, and front desk, waiters, kitchen, bar and managers all work from the same live data, with food and bar orders going straight to printers in the kitchen and bars.
- Direct online booking
- Order ticket routing
- One shared system
03 · Architecture
Shared Firestore, local print services
The guest website and the staff back office are one Next.js app on Vercel, backed by Firestore. Anything that needs a secret runs on the server: creating and verifying DPO payments, sending email through Zoho, rendering receipt PDFs into Firebase Storage, and the nightly audit behind a protected cron route. Firebase Auth handles staff logins and Cloud Messaging sends push notifications.
The kitchen and bar printers sit on the hotel's local network, where the cloud can't reach them. Two small Node services run on hotel PCs under PM2: they watch Firestore for orders that need printing, print them on thermal printers and write the result back.
04 · Food and bar
Separate menus, flows and printers
Food and bar are split into separate menus, order flows and printer routes, so a waiter's order lands as the right ticket in the restaurant, kitchen or bar. The kitchen board checks each dish against inventory and flags missing ingredients before anyone starts cooking.
Receipts are rendered as PDFs on the server and stored in Firebase Storage, so every screen and every email shows the same receipt.
- KOT and BOT
- Inventory checks
- Server-side receipts

05 · Build
Printing every order exactly once
The hardest part was getting orders from a web app onto a kitchen printer without losing any or printing any twice. A browser can't reach a printer on the hotel network, and staff also needed reprints and separate restaurant, kitchen and bar tickets.
I made Firestore the print queue. Each service locks an order while it prints and marks it printed inside a transaction only after the printer confirms, so failed prints retry and a second copy of the service can't print the same order again. Order and receipt numbers come from a transaction on a shared counter, so they stay unique across devices.
- Firestore print queue
- Transactional locks
- Retry on failure

06 · Project results
In daily use at the resort
Front desk, waiters, kitchen and bar staff and managers use the website and back office every day. Guests now book and pay the hotel directly, and every food and bar order reaches its printer once. The platform spans 73 staff screens, 27 guest-facing pages and 2 on-site print services.
- Staff back-office screens
- 73
- Guest-facing pages
- 27
- Ticket printers, one queue
- 3
What shipped
- Built KOT and BOT printing that sends each food and bar order to the right thermal printer exactly once, with staff reprints.
- Designed and integrated DPO Pay card payments for direct room bookings, with token creation and verification on the server.
- Split food and bar into separate menus, order flows and printer routes for the restaurant, kitchen and bars.
- Moved receipt PDFs to the server and stored them in Firebase Storage, so every screen and email uses the same receipt.
- Led two interns and gathered requirements directly from the client and hotel staff in Tanzania.
