RezoPoint of sale built for a full dining room.
A real-time restaurant POS and operations platform — floor and table management, kitchen display, order flow and day-close reporting, on a modern TypeScript stack.
- Floor & kitchen sync
- Real-timeFloor & kitchen sync
- Rollback-safe deploys
- Zero-lossRollback-safe deploys
- Channel & outlet
- MultiChannel & outlet
What Rezo does
Rezo is a restaurant point-of-sale and operations platform built for venues where service moves fast: tables turning, orders splitting, the kitchen and the counter needing the same truth at the same moment. It replaces the till-plus-notebook arrangement most restaurants end the night with.
The system is organised around the floor. Staff see the room as it actually is — occupied, seated, awaiting food, ready to bill — and every action from taking an order to firing a course to splitting a cheque updates the kitchen and the cashier in real time. Menus carry modifiers, combos, timed availability and per-channel pricing, so dine-in, takeaway and delivery can run different rules off one catalogue.
Underneath, Rezo runs a TypeScript API against PostgreSQL with a React operations console, deployed behind a reverse proxy under process supervision. It is deployed with transactional migrations and a scripted cutover that rolls back cleanly on failure — because a POS that is down is a restaurant that is closed.
Built with
- TypeScript
- Node.js API
- React + Vite
- PostgreSQL
- PM2 + reverse proxy
- WebSockets
Built for
- Restaurants & cafés
- Cloud kitchens
- Quick service chains
- Bars & lounges
- Multi-outlet groups
What you get with Rezo
Floor and table management
Live room map with sections, table states, covers, merges and transfers. Servers see status at a glance instead of asking the kitchen.
Kitchen display & KOT routing
Orders route to the right station by item category, with course firing, prep timers and bump-back. Printed KOTs remain available for kitchens that want paper.
Billing that handles reality
Split by guest, by item or by amount, part payments across cash, card and UPI, discounts with reason codes, voids that require authorisation, and full reprint history.
Menu engineering
Modifiers, add-ons, combos, timed availability and per-channel pricing off a single catalogue, so nothing drifts between dine-in and delivery.
Day close that balances
Shift and session reporting, cash drawer declaration, variance tracking and a day-close that reconciles sales, payments and voids before the books move.
Operational visibility
Sales by hour, item and server; average cover; table turn time; and channel mix — reported from the live transaction data, not a nightly export.