MenuNerds

Restaurant POS & Management System
MenuNerds is a restaurant operations platform that combines public ordering, customer self-service, and role-based workflows for restaurant teams.
MenuNerds

It connects guest ordering with internal execution across waiter, kitchen, reception, store admin, franchise admin, and system admin roles.

Want to see it live in Australian venues instead of on a feature list? Read the build: MenuNerds case study.

Key features

Public ordering flow for menu browsing, cart, checkout, and confirmation
Customer account with order history, favorites, profile, and notifications
Waiter workflow with table grid, order list/detail, and order creation
Kitchen display system for preparation and order status handling
Reception and cashier workflow for payment and counter operations
Store-admin controls for products, orders, inventory, promotions, and delivery
Franchise-admin controls for multi-store setup, staffing, and revenue oversight
Finance reports, payment tracking, and audit log review
Supplier and staff management workflows
System settings and multi-role access control
Restaurant operations support for single-store and chain deployments
Role-focused navigation for customer, waiter, kitchen, reception, admin, and franchise teams

Use cases

Single Restaurants

Run ordering, table service, kitchen, and cashier operations in one system.

Restaurant Chains

Manage multi-store performance with franchise-level visibility.

Role-Based Teams

Give each role a focused workflow from service to administration.

The restaurant public home page, leading guests straight into the menu, takeaway ordering and table booking from one place.
The full digital menu grouped by course, with photos, prices and dietary tags, so guests can browse everything before ordering.
The menu a guest sees after scanning the QR code at their table, letting them add dishes to a round without waiting for a waiter.
The round a seated guest has built, with quantities and notes, reviewed one last time before it is sent to the waiter for approval.
Takeaway checkout, where the guest confirms the order summary, the contact details and the pickup time before paying.
The card payment step for a takeaway order, showing the amount due beside the order reference being paid.
A live status page for a placed order, showing which stage it has reached and when it will be ready for collection.
The table booking form, where a guest picks a date, time and party size and leaves the details the floor team needs.
The floor map used on the point of sale, showing every table, whether it is occupied and which orders are still open.
The waiter order screen, with the full dish grid on one side and the running bill for the table on the other.
Orders sent from guest phones waiting for a waiter to check and accept them before they reach the kitchen.
The kitchen docket for one order, laid out for the pass with each line, its options and any special preparation notes.
The sold-out board, where staff mark dishes unavailable so they disappear from the online menu and the till at once.
Every order across the counter, phone and online channels in one list, with its table, status, total and payment state.
The screen for closing an order and taking payment, splitting the amount due across cash, card and other tender types.
The takeaway collection queue, listing each waiting order with its collection time, total and whether it is already paid.
The reservations book, listing every booking with its party size, sitting time, status and whether it came in online or by phone.
The menu management table, where each dish is given a category, till label, price, dietary attributes and availability.
The table register, defining the seats and area of each table and giving it the QR code guests scan to order from their seat.
The daily sales report, breaking takings down by ordering channel and by payment method with tax shown separately.
Staff account management, listing each role, two-factor status and last sign-in so who can do what is kept under control.
The audit log, recording who changed what and when across the whole system, with the value before and after each change.

Tech stack

  • Drupal 11
  • PHP 8.3
  • Bootstrap 5
  • SCSS
  • jQuery
  • MySQL

Product guides

See it working before you commit

We build a working prototype first, so you decide against something real.

Start a project
See what it costs