TechnologyLive client site

Restaurant OMS

A multi-tenant restaurant order system: guests scan a QR, the kitchen sees the ticket the same second, and the owner sees the money by closing time.

Most restaurant tech sells a tablet. This sells the loop — order to kitchen to payment to report — with every tenant isolated behind one deployment.

BlackPearl product — multi-tenant SaaS

Open the live site
resutantordermanagement-system-gj3r.onrender.com/?restaurantId=mayur-s-delight

Live and clickable — use the nav inside it, or open it in its own tab ↗

Multi
Tenant
Realtime
Kitchen display
UPI
Settlement

Design system

Restaurant OMS

Its own system

restaurant-oms design system — extracted from the frontend/ codebase this product runs on

Values below are read out of the system’s own stylesheet at runtime, not copied into this page.

Palette

What moves

  • —Guest scans a table QR and orders without installing anything
  • —Dishes drift across the hero — hover one to open it, click to order
  • —Orders stream to the kitchen display over sockets, no refresh
  • —UPI and Razorpay settle the bill before the guest stands up
  • —Owner dashboard exports the day to PDF, Excel or a deck
  • —Every restaurant is a tenant — one deployment, isolated data

Built with

React 19TypeScriptNode + ExpressMongoDBSocket.IORazorpay

Suits

Restaurant · SaaS · Payments

Want this one, for you?

Nothing here is reskinned. Restaurant OMS sets the tone; the type, palette, grid and copy get rebuilt against your brand.

Start with Restaurant OMS