A guest scans the code on their table, browses your own branded menu and orders. It lands on your board and on the kitchen or bar screen the moment they press send — no app to download, no account to make.
Your own Stripe account Your data, isolated VAT-inclusive prices
1× Ftira Maltija
1× Beef Burger
2× Kinnie
For your guests
A guest points a camera at the table and is ordering. Nothing to download, no account to make, no waiting to be noticed.
The phone's own camera opens your menu — your name, your colours, your photographs. A collection counter works the same way; guests are called by number instead of by table.
Add-ons, things left out, a note for the kitchen. All fourteen allergens from Annex II sit on every item, and an allergy note is lifted onto the ticket rather than buried in a list.
Received, accepted, preparing, ready. The guest follows the same states your staff do, on their own phone, without refreshing anything.
Each code carries the venue, the area and the service point, and it is signed. Change one digit and it stops verifying — a photocopied or edited code lands on a page asking the guest to scan the real one instead of quietly ordering against somebody else's table.
Reissue a code the moment a sticker walks off, and the old one stops working the same second. Download each as PNG or SVG for whatever you print on.
Every service point's code downloads as a PNG or an SVG, and what it goes on is yours — a folded tent, a sticker where a card would not last, a card at a counter. Each point carries its own code, so an order arrives knowing where it came from without a guest typing a table number or a member of staff asking.
Scan to see the menu and order
Stands where the guest is already looking, and folds flat when the table is turned.
Scan to see the menu and order
TABLE 07
For a bar top, a bench or a rail — anywhere a folded card would not last the week.
For a kiosk or a hatch, where guests are called by number instead of by table.
For your team
New orders arrive with a chime and no refresh. If the connection drops, the board keeps working on a timer and says so on screen rather than going quiet and letting you find out later.
Food to the kitchen, drinks to the bar, routed by the category you put the item in. Each station bumps its own ticket and can see what the other is still working on.
Categories, add-ons, photographs, serving windows, and quantities that flip to sold out at zero.
Thermal tickets at the station that needs them. The screen stays the source of truth, so a printer out of paper never costs you an order.
Download each code as PNG or SVG, and reissue one the moment a sticker walks off a table.
Owner, manager, waiter, kitchen, bar. A role decides which screens somebody sees and what they may do — refunding is a permission rather than a hidden button, so the answer is the same through the API as on the screen.
Every word this platform shows can be changed for your venue alone, in either language, on the guest menu and on your staff screens. Anything you leave alone quietly falls back to ours.
The money
Charges are made directly on the venue's connected account. The money is yours from the moment it is held — it never passes through a balance belonging to anybody else, and there is a test in the suite that fails the build if a code path is ever added that could route it elsewhere.
Take cards at the table, or take the money at the counter and mark it paid. Reject an order and the hold is released; nothing was ever taken.
Emailed on payout day, at no extra cost.
Built for Malta
VAT is contained in the price you enter, never added at checkout. The guest pays exactly the number they were shown, and the receipt reconciles to it to the cent.
On only if you switch it on, at a percentage you set, and shown to the guest as its own line before they order rather than discovered at the end.
The guest menu wears your name and your colour. OrderTap QR stays out of it, apart from one optional line in the footer that is yours to remove.
Maltese has four plural forms where English has two, and the difference shows on anything that counts orders or tickets. It is handled rather than papered over by adding an s.
It is yours
Nothing in it depends on a service belonging to whoever built it, and there is a test in the suite that fails the build if that ever stops being true.