The platform
QR menus are a commodity — a dozen tools will make you one this afternoon. What is not a commodity is a system that knows the shape of your venue, keeps the same guest the same person across visits, and can close a door. That is what the rest of this page is about.
The room, not the menu
Brand → venue → floor → terrace → room → table → cabana → sunbed. Every node can carry its own signed QR, and a code knows where it is.
That is why a beach club can price a sunbed differently from a table, why a hotel can put a different code in every room, and why "which table is asking?" has an answer without anybody typing a number.
Most QR tools model a menu. This models the room the menu is in.
Codes that outlive the furniture
Delete table 5 and the code on table 5 does not 404. It resolves to the room, then the floor, then the venue — the guest always lands on a menu.
Reprinting a hundred laminated cards because somebody rearranged a terrace is a real cost, and this is the feature that removes it.
Print once. Rearrange as often as you like.
Guests, not sessions
A guest can have a SilverQR account and be recognised at every venue on the platform — their visits, their requests, their own dashboard.
For you that means a standing: rate a guest, flag a no-show, ban one from a venue or from the whole group. Private to your workspace, never shown to the guest, never shared with another workspace, and never sold.
Below enterprise, almost nothing in this category has a guest identity at all.
Doors that close
Flip a venue to protected and its mini-site goes dark to the public. Three ways in: the printed QR is the key, the QR plus a venue passcode, or a named guest whitelisted by email.
Everyone else is redirected away as though it did not exist — no login page, no "access denied", nothing to enumerate. Members’ lounges, private villas, conference floors, staff canteens.
Pro. Turning it on is gated; a venue that lapses stays protected.
Orders without a payment
Guests build an order from the menu they scanned and send it to your board, tagged to their table, priced from your own catalog.
SilverQR takes no payment, holds no card details and is not a party to the sale. You are paid exactly as you are today.
That is a decision, not a gap. Staying out of payments is why there is no commission, no per-order fee, no PCI scope on your side of the line, and a free plan worth using.
Pro. €12 a venue, whether that venue takes four orders a night or four hundred.
Where the data lives
The application, the database and every uploaded photo are on servers in Germany. Guest recognition is off by default on every venue and asks the guest before it stores anything.
There is a signed Data Processing Agreement, endpoints a guest can use to see or erase what is held, and a documented balancing test for the guest-standing feature rather than a paragraph hoping nobody asks.
For a hotel group’s procurement team this is the whole conversation.
Before you choose anything
Including us. We have deliberately not put a table of competitors here — their prices and features change without telling us, and a comparison that goes stale is a comparison that misleads. These are the questions the answers actually turn on.
A thousand per venue here, alongside 500 areas and tables, 1,000 menu items and 50 staff accounts — ceilings against abuse, not a tier, and raised on request. Ask, because "free plan" in this category often means ten codes.
Here it resolves up the tree to the room, floor or venue. Ask, because the usual answer is a 404 and a reprint.
No, at any volume — we never touch the money, so there is nothing to take a cut of. Ask, because order-and-pay is usually priced per order or as a percentage.
Yes, across all eight languages, and an undeclared item says so rather than looking empty. Ask, because this one is a legal obligation for the venue rather than a feature.
Germany, and there is a DPA naming everyone. Ask, because a lot of this category is hosted in the United States and answers this with a support ticket.
The stack is a Docker Compose file — Postgres, Redis, one API, static sites. Ask, because almost nothing in this category can be self-hosted at all.
Nothing is deleted. The venues you have keep serving guests, the attribution line comes back, and you cannot add more. Ask, because "your data" and "your page stays up" are different promises.
Map the spaces, build the menu, print the sheets. If the rest of the platform is useful to you, it is €12 a venue a month — and if it is not, the free one does not expire.