What MenuNerds Restaurant stands for
Order in the browser
Guests browse dishes, order takeaway, send a table round or request a booking without creating an account.
Keep service connected
Waiters approve guest rounds and prepare browser-printed kitchen dockets from the same order record.
Review the day’s activity
Managers maintain menu prices, record payments and use sales and GST reports with the day-close workflow.
One system from the table to the till
MenuNerds Restaurant is MenuNerds, WeebPal’s restaurant ordering product, set up for one venue: the website and menu, takeaway ordering, ordering at the table by QR code, a POS for the floor, kitchen dockets and tax invoices, bookings, gift cards and the reports of the day, in one Drupal system.
It is shown on Chuan Chuan & Sizzle, a sample Sichuan skewer hotpot and charcoal BBQ restaurant, so you can walk through every role before anything is signed. Screens on this page are recorded views of that demonstration site; their dishes, accounts and other visible records are sample content.
View full sizeFunctions that connect the restaurant
The guest menu, floor service and management tools support different parts of the same working day.
- MenuDishes and optionsPhotos, categories, dietary filters, prices and kitchen notes
- QROrdering at the tableGuests send a round; a waiter approves or rejects it
- POSFloor serviceTables, service status, rounds and a shared order record
- PickupTakeaway ordersOnline and counter orders with collection details
- PrintDockets and billsBrowser printing for kitchen rounds and tax invoices
- PayPayment recordsCounter tenders, split payments and gift-card redemption
- ReviewReports and day closeSales, GST, payments, bookings and CSV exports
- ManageVenue settingsOpening hours, menu, tables, staff and recorded changes
Chuan Chuan & Sizzle, its address, ABN and staff are sample content, and its dish and story photos are AI-generated. Screens show this demonstration venue and its sample content.
Built for a restaurant that runs its own floor
This edition runs one restaurant on one site. For a group with several stores, start from the standard MenuNerds page.
A restaurant replacing its cash register
Talk about your restaurantOrders on a tablet POS, a docket for the kitchen and a tax invoice at the counter, with the menu and prices changed by the manager.
A venue with table service
Read guideEvery table gets its own QR code. Guests send rounds from their phones, and a waiter approves each one before it reaches the kitchen.
A kitchen with a busy takeaway counter
Prepare a venue for day-to-day useGuests order online, choose a collection time and pay by card or at the counter; the takeaway queue helps staff organise preparation and collection.
An agency whose client runs restaurants
Partner programmeWe deploy and adapt it together with you, under your name, and your client receives the running system and its source code.
From the table’s QR code to a closed bill
Guest rounds move through waiter approval, kitchen preparation and payment, with the same order retaining the table’s service history.
Scan the table’s QR code
The poster on the table opens Order at your table, with the table number and no sign-in.
Choose dishes
The same menu, with search and categories; options such as Spice Level and Pot Type, and a note for the kitchen.
Send to waiter
Review your order shows every line and the total; the guest changes or removes lines, then sends the round.
The waiter approves
Guest orders to approve lists the round; the waiter approves it, or rejects it with a reason.
The kitchen docket
The approved round goes to the kitchen; the waiter prints its 80 mm docket from the table’s ticket.
Another round
More dishes from the table become a new round on the same order, with a docket marked NEW ITEMS.
The bill
Bill preview, then Print bill: a tax invoice with the ABN, GST included and a receipt number.
Take payment
A manager takes EFTPOS, cash, other or a gift card, split across several payments if needed.
The table is free
Paid in full, the order is archived with its history and the table shows Free on the floor map.
The floor, the kitchen and the takeaway counter
Waiters work from the POS floor map, on a tablet or a computer. They open a table, send each round to the kitchen, approve what guests send from their phones and keep the takeaway counter moving.
- The floor map: every table with its seats, zone and status, filtered by Waiting approval, In service, Bill printed or Free
- Rounds sent to the kitchen, each with an 80 mm docket of only the new dishes
- Guest orders to approve, with Approve or Reject and a reason
- The Sold out board: hide a dish from the public menu and lock it on the POS; restore it manually or through the first scheduled check after Sydney midnight, with checks every three hours
- Counter and phone takeaway, the takeaway queue and Pause online ordering
View full sizeMenu, prices and the numbers of the day
Managers change the menu and prices themselves, set the hours and the rules for ordering and booking, close table bills and the day, and read the reports.
- Dishes with price, photo, category, bill and kitchen labels, dietary flags and option groups
- Price changes logged; orders already placed keep the price they were sold at
- Opening hours, ordering and booking rules, gift cards and promotions
- Close and take payment, split payments, voids, reopen within 24 hours and refund records
- Eight reports with CSV export, then Close the day
View full sizeStaff, settings and a record of who did what
Administrators look after the staff accounts and the restaurant’s settings, and can switch to a staff member’s account to see the system exactly as that person does.
- Staff accounts with one role each, a set-up email and an alert when a privileged role is given
- Restaurant profile, ABN, GST, receipt header and footer
- Payment, print and feature-flag settings in Drupal’s own administration
- An audit log of price changes, voids, reopens, refunds, QR rotations and role changes
- Switch user, filtered by role, with every switch and switch back logged
View full size
Live demo
Each demo is a working copy of MenuNerds with sample data, open for you to try.
Connect the order, the floor and the day’s review
Compare common counter tasks with the connected guest, waiter and manager tools in this edition.
| A counter-based workflow | MenuNerds Restaurant | |
|---|---|---|
| Taking an order | Staff enter the guest’s choices at the counter | Guests order online or by table QR; staff also enter orders on the POS |
| Informing the kitchen | Staff pass the order to the kitchen | Kitchen dockets group dishes, options and notes by round |
| Maintaining the menu | Prices and menu records need separate attention | Managers maintain dishes, options and prices in the same system |
| Recording payment | The card terminal and the order book are separate | Staff record counter tenders; configured online payment serves takeaway |
| Following table service | Staff track rounds and the bill during service | The floor map, guest approvals, rounds and bill share one order |
| Reviewing the day | Staff collate totals from service records | Sales, GST and payment reports support the day-close review |
What stays in the product, and what is yours
A deployment has a core and a layer of your own. The core is MenuNerds as it runs on the sample site; venue content and settings are maintained separately from shared application code. Custom development needs an agreed extension and update plan. Chuan Chuan & Sizzle is such a layer: it runs the same code as the other sample restaurants and differs only in its data, photos and settings.
A MenuNerds Restaurant deployment Venue content and settings sit alongside the shared application
Your systems The payment provider (Stripe today), the email service, your printers and any accounting integration agreed for your deployment
Integrations built for you
Your layer Restaurant profile and brand, menu and photos, tables and QR posters, opening hours, ordering and booking rules, website pages and the receipt footer
Kept apart from the core
Product core MenuNerds: ordering, table QR, POS, dockets and invoices, payments, bookings, gift cards, promotions, reports and staff
In this edition
- Website, menu, takeaway ordering and ordering at the table by QR code
- POS floor map, guest approvals, Sold out board and takeaway queue
- Kitchen dockets and tax invoices on 80 mm paper, from the browser
- Payments by tender, split payments, voids, reopen and refund records
- Bookings, gift cards, promotions, eight reports and the day close
- Staff accounts, authorised Switch user, audit records and configured TOTP support
Built for your deployment, when you need it
- A kitchen display screen in place of printed dockets
- A card machine linked to the bill
- Delivery, and orders from delivery products
- Loyalty, and customer accounts with an order history
- Several venues, with a view across them
- Stock, recipes and staff rosters
Prepare a venue for day-to-day use
Preparation combines venue content, staff responsibilities and environment checks before the team begins service.
From the sample site to your own
- Review the venue Walk through how guests, the floor and the takeaway counter currently work. Define the operating needs
- Prepare the menu Check dishes, prices, dietary labels, options and kitchen labels. Agree the menu content
- Set service rules Prepare opening hours, tables, collection slots and booking capacity. Check the venue settings
- Prepare the team Create staff accounts with the required roles and practise the relevant guides. Confirm responsibilities
- Check the environment Validate payment, email and browser-printing arrangements for the deployment. Review integrations
- Rehearse and hand over Walk through agreed service scenarios and confirm the scope before going live. Keep the operating guide
How the working parts fit together
These conditions help a venue plan its service workflow and deployment.
- Guest access Ordering and booking start without a customer account; private follow-up pages use time-limited signed links.
- Staff responsibilities Waiters handle floor and counter service; managers maintain the menu, close table bills and review reports. The demonstration has TOTP support configured, but account setup is currently unavailable and no role is required to use it.
- Prices on existing orders Order lines retain the price, dish label and options captured when the order was placed.
- Kitchen and payment hardware Dockets and bills use browser printing. Staff record EFTPOS from a separate card terminal.
- Online payment setup Takeaway and gift-card payment require a configured provider and successful payment confirmation.
- Refund handling Refund entries record the adjustment. Returning money through a payment provider is handled separately.
Everyday situations the team can practise
A guest scans the table’s QR code, selects dishes and options, and sends a round. The waiter reviews it before sending it to the kitchen.
Table serviceGuest and waiterA restaurant use case A waiter enters a counter order with collection details. Staff record the available tender and follow the order through the appropriate service steps.
Takeaway counterWaiter and managerA restaurant use case A manager changes tomorrow’s menu and opening rules, checks the day’s reports and records the cash count when the day can be closed.
Daily managementManagerA restaurant use case
Questions about MenuNerds Restaurant
Do guests need an account or an app?
No. Guests order takeaway, order at the table from its QR code, book a table and buy gift cards in the browser, without an account. What a guest opens afterwards, such as the order confirmation or the card payment page, comes from a signed link that expires: 48 hours for a takeaway order, 30 minutes for the payment page.
Can we change prices and the menu ourselves?
Yes. A manager adds, edits, archives and republishes dishes, each with a price, photo, category, labels for the bill and the kitchen docket, gluten-free and vegetarian flags and option groups. Every price change is logged, and orders already placed keep the price they were sold at.
What does the kitchen receive?
A kitchen docket for each round, on 80 mm paper: the table or takeaway, the round number, the time it was sent, the waiter, and each dish by its kitchen label with its options and notes, without prices. A later round on the same order is marked NEW ITEMS and lists only the new dishes. Dockets print through the browser’s print dialog; this edition has no kitchen display screen.
What does the tax invoice show?
The restaurant’s name and ABN, the words TAX INVOICE, the date, a receipt number, the table, the number of guests and who served them, the dishes, the subtotal, GST included, the total and how it was paid. Receipt numbers run by business date, in order, with no repeats or gaps. Have your accountant check the layout against your obligations before you go live.
Can we use a payment provider other than Stripe?
Online card payment, for takeaway and gift cards, goes through a hosted payment page behind a provider interface, and Stripe is the provider today. Moving to another provider needs a new adapter and renaming the fields and routes that still carry Stripe’s name; the fit report specifies and prices it. At the counter, staff take EFTPOS on your own card machine, or cash, and record the tender, so that part depends on no provider.
Can guests book a table?
Yes. Available booking times, capacity, party limits and advance booking follow the configured venue rules. Eligible requests are confirmed automatically when auto-confirmation is enabled; other requests need manager review. The restaurant reserves a time slot, not a particular table. Guests can cancel through their signed link before the configured cut-off. The demonstration site currently allows bookings outside normal opening hours.
Can the menu be in Chinese or another language?
The interface is in English. On the sample site each dish and category name carries English and Chinese in one label, such as “Charcoal Meat Skewers | 炭火鲜肉烤串”, so guests read both. A second interface language is not in this edition; it can be built for your deployment.
Where are orders and records kept?
On the system you choose to run it on: your own servers or cloud account, or hosting we operate for you. Each deployment is a system of its own, so orders, payments, bookings, gift cards and reports stay in your own database.
A guide for every role
Step by step, with screens of the sample site.
