Skip to content
Restaurant POS · Multi-tenant

Restaurant Operations & POS Platform

A multi-tenant restaurant platform: an installable POS on the floor, a kitchen display that updates as orders change, and a NestJS backend holding the order state machine behind both.

DevelopmentEcomLabs ProductPOS
Overview

A restaurant floor is the hardest place to run a web application: the connection drops, the same order is touched by four people, and nobody has time to reload. The platform is built for that — the POS is an installable web app with an offline queue, the floor plan and kitchen display stay in sync over websockets with a Redis adapter, and an order moves through an explicit state machine rather than through whichever screen wrote last. Tenancy is row-scoped on PostgreSQL, so one deployment serves several restaurants and their branches. An Android wrapper puts the same application on a tablet.

This EcomLabs product is in active development; a public URL is not yet available.

What EcomLabs did

  • Built the monorepo — a Next.js progressive web app, a NestJS API and an Android wrapper sharing one database package.
  • Implemented the order state machine and the kitchen display that reacts to it in real time.
  • Scoped tenancy by row on PostgreSQL so one deployment serves several restaurants and branches.
  • Built the floor plan, the catalogue, inventory movements and the daily sales reports.

Capabilities

  • Point of sale with an offline queue and PIN login.
  • Kitchen display driven by an explicit order state machine.
  • Floor plan with live table states.
  • Multi-tenant, multi-branch on one deployment.
  • Catalogue, inventory movements and daily sales reports.
  • Installable web app plus an Android wrapper for tablets.

Stack

  • Next.js
  • NestJS
  • TypeScript
  • Prisma
  • PostgreSQL
  • Redis
  • Socket.IO
  • PWA
  • Kotlin
  • Railway
Related work

Related work

Let's build

Have a project in mind?

Tell us your goals and current setup — we'll come back with a clear, honest plan.