> ## Documentation Index
> Fetch the complete documentation index at: https://docs.gridbeds.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Restaurants

> Setting up a restaurant: settings, opening hours, the menu with options and availability, tables with QR codes, and inventory.

The **Restaurant** group in the menu has **Restaurants** and **Inventory**. Restaurants are part of your subscription's Restaurants module; without it, the page says "Restaurants isn't included in your plan".

Orders, the kitchen and settling are in [Orders and kitchen](/en/restaurants/orders); delivery platforms in [Deliveries](/en/restaurants/deliveries).

## Which restaurants you see

The **Restaurants** list follows the property switcher in the sidebar: it shows the restaurants of the properties chosen there. A standalone restaurant (one with no property) appears only under **All properties**, and only to members with access to every property. When the choice is why the list is empty, the page says "No restaurant at the properties shown". The restaurant filter of the stock locations in **Inventory** offers the same restaurants.

On a restaurant's page, the button next to its name (**Switch restaurant**) opens a searchable list of the restaurants in the same choice, to move to another without going back to the list.

## Who can do what

In **Settings → Roles & Permissions**, the **Restaurants** and **Restaurant operations** categories:

| Right | What it allows |
| - | - |
| **Restaurants** — **View** | See the restaurants and their orders. |
| **Restaurants** — **Manage** | Everything: the restaurant, menu, settings, tables, delivery platforms, plus running the service and settling. |
| **Run the service (orders, reservations, tables)** | New orders and moving them along, the kitchen display, pausing, table reservations, QR codes. |
| **Mark menu items unavailable** | Item availability only. |
| **Settle orders (payment, charge to room, invoice)** | Settling, charging to a room and issuing an invoice at the customer's request. |
| **Hand over invoices at the till (own sales, same day)** | Printing, downloading and emailing the invoice of a sale you settled, on the day it was issued. A manager (**Restaurants** — **Manage**) does it for any sale. |

By default only **Owner** and **Admin** have restaurant rights; the other built-in roles have none. For waiters and cooks, create a role of your own with the right to run the service (and, if they take payments, the right to settle). Cancelling or rejecting an order also needs the finance right to cancel orders.

## Add a restaurant

**Restaurants** → **Add Restaurant**. The wizard has the steps **Basic Info**, **Location**, **Settings** and **Reservations**, then **Create Restaurant**. Under **Location**, the suggested addresses — like those in a property's form — are written in the language you use the app in ("Bucharest" in English, "București" in Romanian); what you save stays exactly as the field shows it. The restaurant starts as a **Draft**; the list filters by Draft, Active and Archived.

To activate it (**Activate**, in the restaurant's header) you need **At least one active menu** and **At least one day with operating hours**.

<Warning>
  Deleting a restaurant permanently deletes its menus, orders and reservations too.
</Warning>

The restaurant's page has the tabs **Overview**, **Orders**, **Reservations**, **Delivery**, **Tables**, **Settings** and **Payments** (the restaurant's Stripe account, for online payment).

### Settings

The **Settings** tab has, in order:

* **What you sell**: **Take table reservations**, **Take online orders**, **Deliver**, **Let guests collect**, **Serve at the table** ("Off: a scanned table QR can no longer place an order."), the preparation time, the minimum order, the **Missed-order alert** and **Let guests pay by card on the website**;
* **Opening hours**: open or closed each day, the times and a break;
* reservations;
* **The restaurant**: details, location, logo and cover;
* **Configuration**: currency, timezone, colour and **Default VAT category** ("Applied to untagged menu lines. Empty means the country's standard rate.").

**Missed-order alert** sets how long a new order may wait for someone to accept or reject it before it turns **URGENT** on the kitchen display and the staff who receive **Restaurant orders** get a phone alert: between 1 and 30 minutes, 5 by default, with quick picks of 2, 3, 5, 10 and 15. A pre-order counts from its preparation window, not from when it was placed. The alert only escalates: no order is ever rejected automatically. Under it, **Who is alerted** says how many people that is and links to **Notification settings**. When a connected delivery platform rejects unaccepted orders sooner (Wolt after 3 minutes) and that channel does not accept orders automatically, a warning asks you to set the alert below the platform's limit or turn on auto-accept for it.

## The restaurant and its property

A restaurant belongs to a property or is standalone. That decides three things: who sees it (the members with access to its property; a standalone one, only members with access to every property), whose rooms its bills can be charged to (only its property's guests; a standalone one's, any guest of the organization), and whether a room charge goes through — the bill must be in the folio's currency.

You change the link in two places, both for members with **Restaurants** — **Manage**:

* on the property's page, the **Restaurants** tab: its restaurants, **Unlink** on each, and below them **Choose a restaurant** (standalone or another property's) and **Link to this property**;
* in the restaurant's **Settings**, the **Property** card (**Belongs to**), where the sidebar's **Link to a property** also lands.

Before the change, a confirmation says what changes: who sees it, whose rooms its bills go to, the property it leaves, and the currency. If the restaurant sells in another currency than the property's folios, the confirmation offers to switch it to the property's; menu prices keep their amounts, so check them afterwards. A member restricted to some properties can move a restaurant only between their own properties, and cannot make it standalone.

## The menu

On **Overview**, the **Menu Management** card → **Open Editor**. On the left is the tree of menus → categories → items (**Add Menu**, **Add Category**, quick add, duplicate, sort A-Z, **Export menu (CSV)**); on the right, the chosen item.

A **menu** has a name, a description, **Active** and a period (**Available From** / **Available Until**). An **item** has the tabs:

* **Basic Info** — name, description, **Price**, compare-at price, prep time, calories, available, featured;
* **Translations** — the name and description in other languages;
* **Dietary** — vegetarian, vegan, gluten-free, spicy, and the allergens (required for any dish sold unpackaged);
* **Sizes** — the guest picks exactly one size; the base size carries the item's price;
* **Options** — shared option groups (**New option group**: required or not, how many choices, each option with its price difference), attached to the item with **Attach group**;
* **Availability**.

An item that has run out for now: **Mark unavailable**, or **Snooze** it for an hour, the rest of the day or until a time you choose. If you use inventory, an item whose ingredient has run out in the kitchen becomes "out of stock" on its own.

<Note>
  **Coming soon:**

  * time windows per item (breakfast only 07:00–11:00, say): the **Availability** tab shows them but does not save them yet. Meanwhile, make a separate menu with its own period, or mark the items unavailable.
  * a VAT category per item: today only the restaurant's default category can be set. If you sell items at different rates (food and alcohol), contact support.
</Note>

## Tables and the QR code

**Tables** tab → **Add table**: number, minimum and maximum seats, **Zone** (free text, Terrace for example — zones become filters) and available. An unavailable table is hidden from seating and QR ordering. A table with an open order shows **Active order**; it frees up when the order is completed under **Orders** — settling the bill alone does not free it.

**Download QR** gives the table's code: "Guests scan this to order straight from the table." The code leads to the restaurant's menu on [your website](/en/websites), so the restaurant needs a published website. The orders appear under **Orders**.

<Note>
  There is no floor plan: zones are only labels on tables.
</Note>

## Inventory

**Inventory** (a separate module of your subscription; the **Restaurant inventory** right) keeps the restaurant's stock:

| Section | What it holds |
| - | - |
| **Catalog** | Stock items, locations, recipes, suppliers, price lists |
| **Purchasing** | Purchase orders, reorder, goods receipts, supplier invoices, price variances |
| **Stock** | Stock levels, par levels, transfers, requisitions, ledger |
| **Counts & reports** | Stocktakes, variance, dead stock, valuation |

The link to the restaurant is optional: if a menu item has a recipe and the restaurant has a kitchen stock location, the ingredients come off stock when the order goes to preparing, and come back if it is cancelled.

On a phone, restaurants and inventory open in the browser: the staff app has no restaurant screens, only the notification for orders nobody answered.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.