- Product overview
- Menu management
Menu management
Menu management is where you build the menu your guests read: categories, dishes, prices, photos and declared allergens. Nothing you type reaches a guest until you publish, and every publish is a numbered version you can go back to.
Editing is not the hard part
Changing a price is easy anywhere. The hard part is changing it without breaking the menu a guest is reading at that exact moment, and being able to say tomorrow who changed it and what it was before.
Most kitchens solve this by not editing at all. The menu drifts, and the correction is made out loud by whoever is carrying the plates.
Draft and published are two different things
You work on a draft. Guests read a published version. Between the two there is a deliberate step, so a half-finished breakfast menu is never on a table.
One state deliberately skips that step: marking a dish sold out takes effect immediately, because a dish that ran out has already run out and waiting for a publish would be waiting for nothing.
How it works
- Categories first Create, rename, delete and reorder categories. The order you set is the order the guest reads.
- Then the dishes A dish, its menu row and its allergens are written in one transaction, so a half-written dish never appears.
- Check it on a phone first A signed preview link shows the draft on a real phone and expires by itself, so a draft cannot leak by being forwarded.
- Publish a numbered version Publishing freezes a snapshot and gives it a version number. Guests read that snapshot.
- Go back if it was wrong Any earlier published version can be restored, so a bad publish is a minute of trouble instead of an evening of it.
What you can do
- Prices
- Set a dish price in your currency, stored as a whole number of minor units so rounding does not drift.
- Photos
- Attach a photo from the media library; the guest page serves the right size for the screen that asked for it.
- Declared allergens
- Mark the allergens you declare for a dish. They are shown to the guest as declarations, never as a guarantee.
- Sold out, immediately
- Mark one dish, or a whole list of dishes in one request, as sold out or back in stock. Guests see it on the next scan without a publish.
- Hide without deleting
- A dish can be taken off the published menu and kept in the catalogue, so a seasonal dish does not have to be typed again.
- Several menus, one place
- A location can hold more than one menu, and a menu can hand over to another at a set time of day, so breakfast and dinner live behind the same printed code.
- Publish at a chosen time
- A publish can be scheduled. It is carried out by the server on the minute, whether or not anyone is logged in.
- Import and export as CSV
- A whole menu can be brought in from a spreadsheet and taken back out as one, so the menu is never locked inside the product.
- Who changed the price
- Menu changes are written to an audit trail, so "why is the kebab 20 lira more" has an answer with a name and a time on it.
What you need
| An account and a location | One workspace and one location are enough to build and publish a menu. |
|---|---|
| A plan | Building, editing, publishing and restoring a menu are on the free plan. No part of this page is behind a paid plan. |
| One currency per menu | A menu is priced in the currency of its brand. Mixed currencies inside one menu are not supported. |
What it does not do
- No sizes or portions A dish has a single price. Small and large, or half and full, cannot be expressed as one dish today.
- No extras or option groups Paid additions such as extra cheese, or choices such as a sauce, are not part of a dish.
- No menu duplication A menu cannot be copied into a second one. A second menu is built, or brought in from a spreadsheet.
- Bulk work is limited to stock Sold-out marks can be changed for many dishes at once. Prices, visibility and deletion are changed one dish at a time.
- No tax lines A price is shown as the price. There is no separate tax field and the guest page makes no statement about tax.
Questions owners ask
Does my edit reach the guest straight away?
Only if it is a sold-out mark. Everything else waits for you to publish, so guests never read a half-finished menu.
Can I undo a bad publish?
Yes. Every publish is a numbered version and an earlier one can be restored.
Can I set the new prices tonight and have them start tomorrow?
Yes. Schedule the publish and the server carries it out at that time on its own.
Can breakfast and dinner share one printed code?
Yes. A location can hold several menus and one can hand over to another at a set time of day.
Can I get my menu out again?
Yes. The whole menu exports to a spreadsheet file, and one can be imported the same way.
Can I see who changed a price?
Yes. Menu changes are recorded with who made them and when.
Start with the free plan
Building, publishing and restoring a menu are not behind a paid plan.
See the plans