The situation
Restaurants across Qatar and the GCC often rely on expensive legacy POS terminals and static PDF menus. When customer orders surge during peak dinner hours, waiters get overwhelmed taking orders by hand, orders get delayed in the kitchen, and errors mount.
MenuHub was built to provide a modern, lightning-fast operating system for restaurants — from the customer scanning a QR code at their table to the chef preparing the meal in the kitchen.
What I built
- Customer QR Menu & Table Ordering: Instant multilingual (Arabic & English) web menu where diners browse, customize items, and order directly from their phone with no app download or sign-up needed.
- Offline-First Staff Point of Sale (POS): Dedicated POS interface for waiters and cashiers that continues working smoothly even during intermittent network drops, with immediate syncing upon reconnection.
- Kitchen Display System (KDS): Live order stream for cooks and kitchen staff with order timers, status updates, and priority tagging.
- Thermal Print Bridge: Integration with network receipt printers (
ESC/POS) to automatically fire order tickets to the bar and kitchen. - Multi-Tenant Architecture: Granular hierarchy allowing enterprise owners to manage multiple restaurant brands and branches with localized tax, currency, and role-based staff PIN security.
The tech stack
- Backend: FastAPI (Python), PostgreSQL, SQLAlchemy/SQLModel, WebSockets for sub-second live order dispatching.
- Frontend: React, TypeScript, Tailwind CSS, service workers for offline caching.
- Infrastructure: Docker Compose, Vercel frontend deployment, production PostgreSQL.
What this means for you
If you need a high-concurrency SaaS platform with real-time syncing, offline resilience, or hardware device integration (printers, scanners, card terminals), I can take it from architecture to production.