000%
Ali Saad / Creative systems practiceSignal acquired
DestinationDestination
Destination / Destination11 / route handoff

All projectsW—08 / 11

RestaurantOperations

White-label restaurant operations platform unifying table service, realtime kitchen tickets, staff roles, manual settlement, analytics, menu management, and EN/DE workflows.

Open Reference Deployment
Restaurant Operations platform project cover
OverviewThe buildOutcome

Overview

Role
Product Architect & Full-Stack Developer
Client
Independent Product
Year
2026

Restaurant Operations Platform is a reusable internal system for restaurant teams, designed to replace fragmented table, order, kitchen, and management workflows with one secure workspace.

Waiters open tables with guest counts, add multiple rounds with quantities and item notes, and follow live order states. Kitchen staff receive independently timed tickets in realtime, update preparation stages without refresh buttons, and notify the assigned waiter when a round is ready. Owners and managers manage menus, media, staff access, restaurant settings, order history, and operational analytics.

The product is configuration-driven for white-label deployment across restaurant customers. Supabase provides PostgreSQL, authentication, authorized realtime updates, tenant-scoped storage, and row-level security; Next.js provides the responsive installable staff application. Prices are entered as final amounts, while cash and external card-terminal payments are recorded manually. The platform deliberately does not collect card data or attempt to replace payment terminals, printers, or cash drawers.

The challenge +

The original codebase was a customer-facing AI ordering prototype split across multiple applications. The central challenge was transforming it into a dependable staff-only restaurant system without carrying the prototype's confusing navigation, unsafe assumptions, or customer-ordering scope into production.

The operational model had to support one open table across multiple kitchen rounds, immutable sent items, editable unsent additions, realtime state changes, accurate timers, waiter handovers, manual settlement, and historically correct staff attribution. At the same time, the mobile workflow needed to remain fast enough for waiters while tablet and desktop layouts gave kitchen and management teams sufficient information density.

Security and reusability were treated as product requirements: tenant and location scope are derived from verified membership, privileged operations stay server-side, PostgreSQL row-level security provides defense in depth, and customer branding and onboarding are configuration-driven.

Thebuild

01

Table-First Service Workflow

Waiters open tables with a guest count, add dishes through a category-first mobile menu, attach optional notes, and continue adding new rounds throughout the same table visit without losing the original order history.

Guest counts, live timers, notes, and multiple kitchen rounds

02

Realtime Kitchen Display

Each submitted round becomes an independently timed kitchen ticket. Authorized realtime updates keep kitchen and waiter screens synchronized, while sound alerts announce new tickets and ready-for-pickup states.

Independent ticket timing with sound and ready notifications

03

Role-Aware Staff Access

Individual staff identities, server-side authorization, PostgreSQL row-level security, and tenant-scoped membership protect operational data. Important order, payment, menu, and staff actions preserve the acting employee for audit and analytics.

Owner, manager, waiter, cashier, and kitchen responsibilities

More details (3)
04

White-Label Menu & Settings

Restaurant identity and operations are configuration rather than a source-code fork. Owners manage bilingual categories and items, availability, images, locations, floors, tables, capacity, currency, language, and brand colors.

Branding, currency, language, locations, floors, tables, and media

05

Audited Settlement & Analytics

Staff can record whole-order settlement by cash or an external card terminal without storing cardholder data. Management views cover order history, void reasons, staff attribution, popular items, sales patterns, and busy or quiet periods.

Cash or external card records with waiter attribution

06

Repeatable Customer Deployment

A maintained codebase, ordered Supabase migrations, database policy tests, restaurant provisioning, bilingual menu import, PWA configuration, and a Vercel deployment guide support repeatable customer environments.

Versioned migrations, provisioning scripts, and deployment runbook

Outcome

The project now has a live reference deployment that combines floor service, multi-round ordering, a dedicated kitchen display, menu administration, staff access, manual settlement, order history, and management analytics in one responsive PWA.

Realtime operation was verified across two devices, while English and German interfaces cover the critical staff workflows. The repository includes versioned database migrations, pgTAP authorization tests, restaurant provisioning, bilingual menu import, and step-by-step Supabase and Vercel deployment guidance.

The result is a production-oriented white-label foundation that can be configured for separate restaurant customers without creating a custom code fork for each deployment.

Languages
English + German
Realtime
Verified across two devices
Operations
Floor, kitchen, payments, history, and analytics
Delivery
Repeatable Supabase + Vercel deployment
Application
Installable online-only PWA
Team
Solo product build
Next projectW—09 / 11

Aside

View project
Aside
Have something worth building?Start a project
aliihsaad1@gmail.com
InstagramLinkedInGitHubFacebook
© 2026 Ali Saad