Software package

QR menu package

Printable per-table QR codes that open a light, fast menu for the hour and the location, with allergen and dietary filters, an optional order-to-table flow with a kitchen ticket screen, call-waiter and bill request buttons and analytics on what diners look at, ready to set up around your tables.

Custom build Concept demo

Get a quote for this package

Who it is for

Built for

A good fit

Restaurants, bars, pubs, hotel outlets and food halls that want a menu which is always current and, where wanted, takes the order at the table without a marketplace taking a cut. It suits managers who edit menus several times a week, waiting staff who would rather answer a call-waiter button than scan the room, kitchens that want tickets on a screen in the order they should be cooked, and venues with areas that serve different menus at different hours.

Not the right fit

It is not for takeaways that need delivery zones and drivers, which belong to the online ordering package, nor for venues that mainly need table reservations, which the restaurant booking package handles. It does not replace the till, and it does not try to manage stock or recipes.

The operational problem it solves

How it runs, step by step

Half past eleven.

The duty manager checks the menu schedule: the brunch version is live on all codes until two, the bar snacks version takes over on the terrace at the same time, and dinner switches on everywhere at five.
A table of four scans the code on table nine and gets a two-second page with today's brunch, no app, no download.
One diner taps the filter for gluten and the list shrinks to what the kitchen has tagged, with a line asking her to tell staff about any allergy.
They order from their phones: the basket is tied to table nine, the ticket appears on the kitchen screen with the table number, and each item moves from received to preparing to served as the kitchen taps it.

At one the chef marks the shakshuka sold out on the kitchen screen; it greys out on every phone within the minute and nobody is told "we have run out" after ordering.

Table three presses call waiter and a floor tablet shows which table and how long they have been waiting.
Table nine presses request bill, pays at the table through the connected card provider, and the tab closes without anyone fetching a card machine.
At the end of the day the manager sees that the terrace snacks menu is barely read after seven, that the burger is viewed three times more often than it is ordered, and that most call-waiter requests come from the corner tables that are hard to see from the pass.

Features

What the package does

The package ships as modules that follow the diner's path: the menu and version schedule, the codes and the diner-side page, the ordering and kitchen ticket layer, and the floor tools and analytics. Each module below lists what it does; the comparison table shows which package variant includes it.

Content and editorial

Menu editor with allergen tagsBuild sections, items, prices and images, and record allergen and dietary tags against each item.
Per-table QR codesGenerate a code per table and location, with printable sheets, so each scan opens the menu being served at that spot.
Light diner pages with filtersDiners get a fast, image-light page with allergen and dietary filters, and no app to download.
Menus in additional languagesOffer the menu in further languages for visitors who need them.

Scheduling

Scheduled menu versionsSwitch between brunch, dinner or terrace menus by time of day, day of week and location without editing anything live.

Messaging and notifications

Call-waiter and bill requestsDiners press a button to call a waiter or ask for the bill, and a floor tablet shows which table is waiting.

Reporting and insights

Views per item and menu versionSee which items and which menu versions are being read, so you can judge what to promote or drop.
Multi-venue managementManage menus and codes for several venues from one account.

Payments and policies

Order-to-table with kitchen ticketsDiners order from their phones to their table, and the kitchen screen shows tickets with item status from received to served.
Pay at table and running tabsDiners settle the tab at the table through a connected card provider, so nobody fetches a card machine.

Roles and permissions

Who does what

Venue manager
- Create menus, sections, items, prices and allergen and dietary tags
- Schedule menu versions by time of day, day of week and location
- Generate and print QR sheets per table and location
- See views per item, orders, call-waiter and bill request patterns
Waiter
- See call-waiter and bill requests by table on a floor tablet
- Open, amend and close a table's tab
- Add items to a table's order on the diner's behalf
- Mark a request as handled
Kitchen
- See tickets by table in cooking order on a screen
- Move items through received, preparing and served
- Mark an item sold out so it greys out on every phone
- See which tables are still waiting on part of an order
Diner
- Scan a table code and read the menu that is being served now
- Filter or highlight items by recorded allergen and dietary tags
- Order to the table and watch item status, where ordering is switched on
- Call a waiter, request the bill and pay at the table

Example screen

Concept demo

Concept demo of a QR menu kitchen ticket screen listing tables, items with received, preparing and served statuses and a sold-out control.

The kitchen ticket screen during a lunch service: tickets by table in cooking order, each item with its status, a sold-out control on the shakshuka and a count of tables still waiting on part of an order.

Scope and options

What is included and what is extra

In the base package

Menu editor with sections, items, prices, images and allergen and dietary tags
Menu versions scheduled by time of day, day of week and location
Per-table and per-location QR codes with printable sheets
Image-light diner pages with allergen and dietary filters
Call-waiter and bill request buttons with a floor tablet view
Views per item and per menu version

Common add-ons

Order-to-table with kitchen ticket screen and item status
Pay at table and running tabs through a connected card provider
Menus in additional languages
Multi-venue management under one account

Needs custom work

Two-way connection to a specific till or kitchen printer
Hotel room charging checked against a property management system
Food-hall split tickets and per-kitchen settlement

See the custom development service

Ownership, maintenance and pricing

After the build

Deployment and ownership

The package runs on your own hosting or on hosting we manage; the kitchen and floor views are any browser on a tablet or screen, and diners need no app. You own the code and your data in either case. Menus, order history and analytics can be exported at any time in standard formats, and nothing in the package stops you moving it to another provider.

Maintenance

Maintenance is optional and scoped separately. When taken, it covers security updates, monitoring of the diner pages, the kitchen screen and payment callbacks, backups, and a monthly window for small changes such as a new location or a seasonal menu schedule. Anything larger is quoted as a change request against the original scope.

Pricing model

Priced per proposal.

Sold as a one-off setup and customisation with optional monthly maintenance and hosting as separate recurring lines; there is no commission on orders taken through it. The setup figure depends on the number of venues, locations and tables, how many menu versions are scheduled, whether ordering and payment are switched on, the payment provider and any till connection. Each line is itemised in the proposal so recurring costs are never hidden in the setup.

Software package

Custom build Concept demo

Variants

Business Software : quote for this variant

Menu editor with sections, items, prices, images and allergen and dietary tags
Menu versions scheduled by time of day, day of week and location
Per-table and per-location QR codes with printable sheets
Image-light diner pages with allergen and dietary filters

Priced per proposal. A written proposal is the only binding figure.

Get a quote for this package Prefer a fully custom build?

FAQ

Frequently asked questions

Does the diner need to install anything?

No. The code opens a web page built to load quickly on a phone with poor signal. Images are optional and compressed, and the page works without them.

Can the same table show a different menu at lunch and dinner?

Yes. Menu versions are scheduled by time of day, day of week and location, so the code on a table never changes but what it opens does.

How does the kitchen know a dish has run out?

The kitchen marks it sold out on the ticket screen, or the manager does in the editor, and it greys out on every diner's phone within the minute. It comes back when switched on again.

How are allergens handled?

The venue records allergen and dietary tags per item and diners filter by them, with a prompt to tell staff about any allergy. The package displays what the venue has recorded; keeping that accurate is the venue's responsibility and no compliance claim is made.

Can we start view-only and add ordering later?

Yes. Ordering, tickets and pay-at-table are add-ons that switch on against the same menu and codes, so nothing is reprinted.

Is this a finished product I can see running?

Not yet. The readiness badge shows the real state: the package is a custom build assembled from our menu, ordering and payment modules for each venue, and the screen on this page is a labelled concept demo rather than a live client system. Anything beyond the listed options is scoped as custom QR menu development.

Get a quote for QR menu package

Tell us about your locations, the people who will use it and the add-ons you need. We reply with a clear, competitive proposal.