- Product overview
- Menu management
- Prices
Prices
Every dish carries one price in the currency of your business. You change it in the draft, it reaches guests when you publish, a publish can be scheduled for a chosen minute, and every price change is recorded with who made it and when.
The price on the table is a promise
A guest orders at the price they read. If the card shows last month's number, the difference is argued at the till, and the argument is lost by whoever is standing there.
Changing prices on paper means a reprint, so prices are changed rarely and all at once, usually at the wrong moment of the evening.
Change in private, release on purpose
Prices are edited in a draft nobody at a table can see. When you publish, every guest who scans from then on reads the new price; the version they were already reading does not change under them.
A publish can be scheduled, so tonight's edits go live at six in the morning without anybody being awake for it.
How it works
- Type the price Enter a decimal amount. It is checked against the decimals of your currency and stored as a whole number of minor units, so nothing is rounded twice.
- It is checked against your currency A price in a currency other than the brand's is refused, not converted.
- Preview on a phone A signed, expiring preview link shows the draft with its new prices on a real phone before anyone else sees it.
- Publish, now or at a set time Publish immediately, or schedule the publish; the server carries it out on the minute, in the branch's time zone.
- Undo a mistake If the new prices were wrong, restore an earlier published version.
What it does
- Formatted by the currency, not by a habit
- Two decimals for lira and euros, none for yen, three for dinar. The decimal count comes from the currency itself.
- Written the way the guest reads numbers
- The separator between thousands and decimals follows the guest's interface language.
- No price rather than a wrong price
- A price that cannot be formatted is left out of the page instead of shown wrong.
- Prices frozen in every publication
- A published version carries its prices inside it. A price edited today does not change what yesterday's version shows.
- Who changed the kebab
- Every price change is written to the audit trail with the person and the time. A spreadsheet import that changes many prices is recorded as one summarised entry.
- All prices at once, through a spreadsheet
- Export the menu, change the price column, import it back. The import writes to the draft, never straight to the tables.
- Different prices per branch
- Menus belong to a branch, so a branch's prices are its own. The same dish can cost differently at two addresses.
- The guest can filter by price
- On the menu page a guest can narrow the list to a price range, when scripts run.
- Orders carry the server's price
- Where ordering is on, the price on an order line comes from the server, not from what the phone sent.
What you need
| A price above zero on every visible dish | Publishing refuses a visible dish with no price. |
|---|---|
| One currency on the business | The currency is set on the brand from the real list of currencies, and every menu of the business is priced in it. |
| Permission to manage the menu | Owners, managers and editors change prices. The kitchen role is refused on the price endpoint even if it tries. |
| No plan | Setting, changing, scheduling and restoring prices are on the free plan. |
What it does not do
- One price per dish No size prices, no portion prices, no option surcharges.
- No discounts, no happy hour There is no discount field, no time-based price and no promotional price. A cheaper afternoon list is a second menu that hands over by the hour.
- No tax line A price is the price. There is no separate tax amount, and the guest page says nothing about tax.
- No currency conversion Prices are shown in your currency only. A guest cannot switch them to another one.
- No bulk repricing in the panel Prices are changed one dish at a time in the panel. Changing many at once is done through the spreadsheet.
- No price history for the guest A guest sees the current published price only. Earlier prices are visible to you in the versions and the audit trail, not to them.
- No payment The price is read, not charged. Nobody pays through the menu.
Questions owners ask
When does a new price reach the tables?
When you publish. Until then it is in the draft only.
What happens to a guest who is reading the menu while I publish?
They keep reading the version they opened. The new price is read by the next scan.
Why does the price show two decimals for lira but none for yen?
Because the currency decides. The decimal count comes from the currency, not from a setting.
Can I add a happy hour price?
No. There is no time-based price. A cheaper afternoon list is a second menu that takes over by the hour.
Does an import from a spreadsheet change prices immediately?
No. It writes to the draft. Guests see the new prices after you publish.
What if I type a price with the wrong number of decimals?
It is refused with a message. The decimals must match your currency.
Prices are free to change
Setting, scheduling and restoring prices are on the free plan.
See the plans