Solutions
Zabuno is one product for places that serve food and drink, from a single cafe to a business with several branches. There is no separate edition per kind of venue: what differs between them is the menu you write and the hours you keep.
Software sold by sector is usually the same software
Most of this industry's websites carry one page per venue type, and behind eleven pages sits one product with the noun swapped. The owner of a bakery reads a page written for a bakery and buys something that was never built for one.
The cost lands later, when the promised difference turns out not to exist and the setting that was implied cannot be found.
One product, and the differences named honestly
Zabuno knows one kind of business and says so in its own code. A cafe and a fine dining room get the same menu editor, the same codes on the table and the same reports.
The real differences are still real, and they are handled by things that already exist: several menus that hand over by the hour, prices set per branch, opening hours per day, and ordering that a kitchen switches on when it is ready.
How one product fits different rooms
- One kind of business, on purpose The product recognises food and drink businesses and nothing else. A distinction that does not change behaviour is not written into the data.
- Breakfast, lunch and the late menu A branch can hold several menus that take over from each other by the hour, in that branch's own time zone. This is what a cafe and a bar actually need from each other.
- The room decides the codes Codes are made per table or per area, so a twelve-table dining room and a counter with one code are the same product used differently.
- Ordering only where a kitchen is watching Sending an order from the table is switched on per branch and starts switched off, because a quiet counter should never receive an order nobody is looking at.
- Your language and your money The business sets the language its menu is written in and the currency it charges, and the guest page follows both.
What every venue gets, whatever it is called
- A menu the guest opens in their own browser
- A code on the table, a page that opens without an app, and a menu you can correct in the middle of service.
- A published version, not a live document
- Guests read a version you published. Editing the draft during service does not change what somebody is reading at that moment.
- As many branches as the business has
- One account holds one brand and any number of branches, each with its own menus, prices and hours.
- Photographs sized for a phone on a bad connection
- Upload the picture your phone took; the guest gets a small copy made for the size it is shown at.
- What guests looked at, and what they searched for in vain
- Counts of scans, opens, dish views and searches that found nothing - the demand a paper menu can never show you.
- Orders from the table, where it makes sense
- Guests can build a basket and send it to the kitchen in branches where the owner has switched that on.
- A team with real roles
- Managers, editors and a kitchen role that sees allergens and what has sold out rather than the whole business.
What you need
| A business and at least one branch | A brand with a name, and one branch with an address and a time zone. A single-site cafe is a business with one branch. |
|---|---|
| A menu you are willing to publish | Dishes with names and prices in your currency. Publishing is a deliberate act, not an autosave. |
| A way to put the code in front of the guest | A printed card on the table, a sticker, or a code by the counter. Zabuno makes the printable sheet; the paper is yours. |
| No plan, to begin | Writing the menu, publishing it and printing codes work without paying. Plans open the reports, the branding and the team. |
What it is not
- Not a till and not a point of sale Zabuno does not take payment from a guest, does not print a bill and does not know what your day took.
- No booking, no delivery, no loyalty There is no table reservation, no delivery or courier integration and no points card. These are not switched off; they are absent.
- No sector mode and no ready-made menu There is no cafe setting, no bakery template and no starter menu to import for your kind of venue. Your menu is yours to write.
- No customer stories or figures on this page You will not read a percentage here about faster service or a bigger bill. No such measurement exists, and quoting one would be inventing it.
- Nothing about money in the reports The reports count attention, not turnover. A venue that needs revenue reporting needs it from somewhere else.
Questions owners ask
Is there a version for cafes?
No, and that is the honest answer rather than a shortcoming. A cafe uses the same product; what makes it a cafe is the menu it writes and the hours it keeps.
Does it work for a bar with a late menu?
Yes. A branch can run several menus that hand over by the hour in its own time zone, so the late list appears on its own.
Can it replace my till?
No. Zabuno shows the menu and can carry an order to the kitchen. It does not take payment and does not report your takings.
I have one small place. Is this too much?
A single site is a business with one branch, and the base journey costs nothing. The parts built for several branches simply stay out of your way.
Do you have a menu template for my kind of venue?
No. There is no ready-made menu to import for a sector.
See what it costs, and what it does not
The plans, what each opens, and the part that never needed one.
See the plans