Product overview
Zabuno is one web product for places that serve food and drink: you write a menu, publish it, print a code for each table, and guests read the menu in their own browser. Photos, reports, ordering from the table, branding and a team are parts of the same account, not separate products.
Nine features on a poster, and no map
A restaurant owner comparing menu software reads long lists of features and cannot tell which ones exist, which are switched on by a plan, and which are a sentence about the future. The list is the same length whether the product is finished or not.
The cost of guessing wrong is paid at the table: a feature the owner assumed was there is discovered to be missing during service, when there is no time to change anything.
One product, described part by part
This page is the map. Each part of Zabuno has its own page, and each of those pages says what the part does today, what it needs and what it does not do, with every claim tied to the product itself.
The base journey is the same for everybody and costs nothing: an account, a business, a branch, a menu, a published version, a printed code. Plans add capability on top of that chain; they never switch the chain off.
The journey, in order
- Create an account and a business Register with an email address, then describe your business with its name, language, currency and time zone.
- Add a branch A branch has an address and its own clock. A single restaurant is a business with one branch; a chain adds more under the same account.
- Write the menu Categories, dishes, prices, photos and declared allergens go into a draft that guests cannot see.
- Publish a version Publishing freezes a numbered snapshot. Guests always read a published version, and an earlier one can be restored.
- Print a code for each table Generate a code per table, export it as a card, a poster or a sheet to cut up, and change what it points at later without reprinting.
- Guests scan The code opens the menu in the browser already on the phone. No app, no account, and the page is readable without scripts.
The parts, and where each one is explained
- QR menu
- The page guests read: photo, description, price, declared allergens and sold-out state of every dish, at a permanent address that fits on a card.
- Menu management
- Categories, dishes, prices and stock, edited in a draft and released as numbered versions, with a record of who changed what.
- Tables and QR codes
- A code per table, read back by a decoder before it becomes a file, printed as vector cards, and pointed elsewhere without reprinting.
- Design and branding
- A logo, a primary and a secondary colour, frozen into each publication so a published menu never changes under a guest.
- Images and media
- Photos are scanned, resized once and served small; the original is kept so the copies can be made again.
- Languages and currency
- The guest page is in Turkish or English by the guest's choice, dish names stay in yours, and prices follow the decimals of your currency.
- Multiple branches
- Any number of branches under one business, each with its own menus, prices, codes and opening hours.
- Analytics
- Scans, menu opens, dish views, searches that found nothing and orders sent, counted by the server and turned into a menu report.
- Zabuno AI
- A photo of a printed menu becomes a draft you approve, a dish gets a first draft of a description, and dishes typed twice are found.
- Ordering from the table
- Where the owner switches it on, guests build a basket and send it to a kitchen screen; the table is read from the code, never typed.
- A team with roles
- Editors, managers and a kitchen role that marks allergens and sold-out dishes and sees nothing else, invited by the owner.
- Ratings from the table
- A guest who scanned a code can rate a dish, and the owner can reply.
What you need
| A phone or a computer with a browser | The owner's side is a web application too. There is nothing to install for you or for your guests. |
|---|---|
| An email address you can read | Registration is confirmed by email before the account can be used. |
| A printer, or a print shop | Zabuno makes the printable files; the paper on the table is yours. |
| No plan, to begin | Registering, building, publishing and printing are on the free plan. Paid plans open bulk code generation, reports, branding, the team and ordering. |
What Zabuno is not
- Not a till and not a payment system Guests do not pay through Zabuno, and nothing here prints a bill or reports your takings.
- No reservations, delivery or loyalty There is no table booking, no courier or delivery integration and no points card.
- No third-party integrations Nothing connects to a point-of-sale system, an accounting package or a food marketplace. Your menu leaves as a spreadsheet file and comes back the same way.
- No app in a store There is no iPhone or Android app for you or your guests; both sides are web pages.
- Dish names are written once The interface around the menu speaks two languages; the dishes are written in yours and are not translated.
- One brand per account An account holds one business with many branches, not several businesses.
- No sector editions There is no cafe version, bakery version or hotel version. The product recognises one kind of business: places that serve food and drink.
Questions owners ask first
Do I have to buy a plan before I can try it?
No. The chain from account to printed code works without a plan. Plans add capability on top.
Do guests install anything?
No. The code opens a web page in the browser already on the phone.
Is Zabuno a point-of-sale system?
No. It shows the menu and can carry an order to the kitchen. It does not take payment and does not know your takings.
Which part should I read first?
The QR menu page, because that is what your guests see. Menu management is where you spend your own time.
Does it work with my current software?
Not through an integration; there is none today. The menu can be exported and imported as a spreadsheet file.
See what each plan adds
The free plan covers the chain above. Paid plans add on top of it.
See the plans