QR menu software and contactless ordering source code
QR menu software replaces a printed restaurant menu with a page a guest opens by scanning a code at the table — and, in the versions worth paying for, lets that guest order and pay without waiting for a server, while the kitchen sees the ticket instantly.
Written by ZoopCoder, who build and sell one of the packages described below — that bias is declared in full further down this page.
Quick answers
How much does QR menu software cost?
Off-the-shelf source code runs about $30 to $250; hosted services charge each restaurant roughly $15 to $70 a month. If you plan to sell the service to restaurants rather than use it in your own, you need a multi-tenant codebase — the $30 listings almost never are.
What is the difference between a QR menu and QR ordering?
A QR menu displays items. QR ordering takes the order. The second needs a cart, modifiers, a table identity, a live ticket screen for the kitchen and an order lifecycle — roughly five times the software, and the reason restaurants renew.
Do guests need to install an app?
No, and any product that asks them to should be rejected. The whole value of a QR menu is that scanning opens a web page instantly. A Progressive Web App is the right shape here; an install prompt kills conversion at the table.
The one decision that matters: single restaurant or multi-tenant SaaS
Decide this first, because it is the difference between a tool and a business. A single-restaurant QR menu serves one venue: one menu, one payment account, one admin login. A multi-tenant platform hosts many restaurants inside one deployment, each with their own menus, tables, staff, branding, plan limits and billing — which is what you need if the plan is to charge restaurants a monthly fee. Both are listed as “QR menu software” and priced within a hundred dollars of each other.
| Model | What it runs | Money flow | Where it breaks |
|---|---|---|---|
| Single restaurant | One venue you own, possibly several outlets | All order revenue is yours; one gateway account | Onboarding a second business means a second deployment |
| Multi-tenant SaaS | Many independent restaurants on one install | Monthly subscription per restaurant, plus optional per-order fee | Tenant isolation and plan-limit enforcement — the parts cheap scripts fake with a dropdown |
| Hosted service (rented) | Someone else’s platform, your logo | You pay per venue per month, forever | You cannot resell it, and your restaurants are their customers |
A quick test on any demo: create two restaurants, give each a menu item with the same name, then open one restaurant’s public menu. If you can see the other tenant’s item, its images, or its order list — or if the plan limits are only enforced in the admin UI and not on the API — the multi-tenancy is cosmetic.
What a complete QR ordering package must include
These are the pieces a restaurant will notice missing within the first busy service. Menus are easy; the table-to-kitchen loop is where these products succeed or get uninstalled.
- Per-table QR codes that carry the table identity, so an order arrives labelled — not one code for the whole venue
- A menu model that survives real kitchens: categories, variants, required and optional modifier groups, combos, per-item availability and a one-tap “86 this item” toggle
- Cart and order lifecycle with real states (placed, accepted, preparing, ready, served, cancelled) and a running tab per table
- A live kitchen or counter display that updates without a refresh, plus an audible new-order alert
- Both payment paths: pay now at the table, and pay at the counter — most venues need the second on day one
- Multi-outlet and multi-language menus, with per-outlet pricing and hours
- Waiter-call and water-request buttons, which are the features guests actually use most
- Printable QR assets: table tents, stickers and a PDF at print resolution, generated from the admin
- If multi-tenant: subscription plans, trial handling, dunning, and a tenant signup flow that does not need you
- Full unobfuscated source, install docs, and a demo where you can scan a code with your own phone and place a real order
What QR menu software actually costs
This category has the lowest licence prices in ready-made SaaS and the highest ratio of incomplete products, because a menu page is easy to demo and an ordering loop is not.
| Route | Typical cost | What you get | Time to live |
|---|---|---|---|
| Marketplace script (regular licence) | $29–$69 | Usually a single-restaurant digital menu; resale not permitted | Days — then the ordering loop is yours to build |
| Marketplace script (extended licence) | $150–$600 | Resale rights; multi-tenancy still often absent | Weeks |
| Direct vendor, multi-tenant platform | $99–$299 | Tenant isolation, plan billing and kitchen display included | About a day to deploy |
| Hosted service, per venue | $15–$70 per restaurant per month | Nothing to run, nothing to own | Same afternoon |
Running costs nobody quotes you: printing — laminated table tents cost more than the software in year one, and you will reprint when a menu URL changes, which is an argument for codes that point at a stable ID rather than a slug; image hosting and CDN, because food photography is heavy and guests load it on patchy restaurant wifi; and payment gateway fees on every table payment, which at a small average order value can be a painful percentage. Budget for a real device in the kitchen too: a tablet that stays awake and loud is part of the product.
Where to buy, and what each source is good for
| Source | Best for | Watch out for |
|---|---|---|
| General code marketplaces | Low prices and lots of visual choice | “QR menu” listings that are a PDF viewer behind a QR generator; single-tenant code sold to people planning a SaaS |
| WordPress plugins | A single venue that already has a WordPress site | Kitchen display and live order push are usually absent or polled |
| Open source | Menu display and QR generation, which are genuinely solved | Almost nothing open source handles multi-tenant billing for restaurants |
| Direct from the developer | Running this as a subscription business across many venues | Ask specifically how tenant data is isolated and how plan limits are enforced on the API, not in the UI |
Declared bias: what we sell
We are ZoopCoder. We build and sell MenuCraft — a multi-tenant QR menu and contactless-ordering platform with per-table codes, live order routing to the kitchen, modifiers and combos, multi-outlet menus and subscription billing for the restaurants you onboard — as source code from $149, with no recurring fee to us. So read this page knowing we are a vendor in the category we just described. Everything above is what we would check if we were buying rather than selling, including the parts that do not favour us: if your requirements are genuinely unusual a custom build beats every package here, and if you want zero operational responsibility a hosted service is simpler than any source code.
If you want a working example to measure against
The MenuCraft demo runs the full stack, so you can use it as a yardstick for anything else you are evaluating — including the tests described on this page.
If you are comparing against hosted tools
The economics flip based on scale and headcount. These pages lay out the arithmetic against the hosted platforms most buyers weigh up.
Frequently asked questions
How do QR code menus work in a restaurant?
Each table carries a printed code encoding a URL with that table's identity. A guest scans it with the phone camera, the menu opens in the browser with no app install, and in an ordering-capable system the guest adds items to a cart and confirms. The order arrives on a kitchen or counter screen already labelled with the table number, and the guest either pays in the browser or settles at the counter.
Is a QR menu cheaper than printing menus?
Usually yes after the first few months, but not immediately, because you still print the table codes. The real saving is that changing a price or removing a sold-out dish costs nothing and takes seconds, instead of a reprint. For venues that change their menu often, the payback is fast; for a fixed menu it is mostly about ordering speed rather than print cost.
Can I sell QR menu software to restaurants as a SaaS?
Only if the codebase is genuinely multi-tenant and the licence permits it. You need per-restaurant data isolation, plan limits enforced server-side, subscription billing with trials and dunning, and a self-serve signup flow. Most inexpensive marketplace scripts are single-tenant and their regular licence explicitly forbids operating the software as a service for other people.
Do QR menus need internet in the restaurant?
The guest needs data or wifi, which is the main practical failure mode, so offer guest wifi and keep the menu page light. Design the fallback deliberately: a menu that loads in a couple of seconds on a weak mobile connection beats a beautiful one that stalls, and a small printed backup menu behind the counter costs nothing to keep.
What is the difference between QR menu software and a POS?
A QR menu takes the guest's order; a POS runs the restaurant's money and inventory. They overlap at the ticket. Small venues often run QR ordering alone and settle at the counter, while larger ones want the order pushed into an existing POS. If integration matters, check for a documented API or webhook before buying, because retrofitting one is the single most expensive change in this category.
How many restaurants do I need for a QR menu SaaS to be viable?
At $25 a venue per month, roughly forty paying restaurants covers a modest full-time income, and around a hundred and fifty makes it a real business. The constraint is never the software after launch; it is local sales and onboarding, because each venue needs its menu entered and its codes printed before it sees any value.
Get a quote or a guided demo
Tell us your use case and we'll send pricing, a live demo walkthrough and licensing options for QR menu software and contactless ordering source code. Usually a reply within one business day (IST).