# Floor, kitchen, menu extras and day close for a restaurant

> Run table bills and kitchen tickets, maintain menu extras and recipes, record wastage, match imported aggregator payouts and install a switched-off guest win-back ladder.

Canonical page: https://finocket.com/help/restaurant-floor-kitchen-and-menu
Last updated: 2026-10-18
Area: Modules & features

Run table service, maintain the menu and review the day's stock losses and payouts.

> Restaurant pack and workspace setup
>
> These screens belong to the restaurant pack. Each needs a setup step on the workspace; until then, treat it as not available in this workspace yet, not as no data. For example, the floor says **Table bills are not available in this workspace yet.**, the kitchen says **The kitchen queue is not available in this workspace yet.**, and menu extras says **Modifier groups are not available in this workspace yet.** A failed read also does not mean an empty list: follow the screen's error message. The restaurant pack is switched off until your workspace owner switches it on.

> Who can do what, and what to have ready
>
> A shop admin is anyone whose role lets them both bill and manage stock; the owner, an admin and a store manager usually can, depending on the permissions set for them. Shop admins change the floor, the menu extras, the table QR, recipes and the review QR, and give the reason when a line is voided or comped. A cashier can bill and send to the kitchen but sees these setup screens read-only. Add your dishes first (a new item with its **Course** and **Veg / non-veg**, or **Import a menu** below): extras, combos, recipes and sold-out marks all work on dishes that already exist.

## Floor and bills

1. Lay out the tables

   Open **/restaurant/floor**, headed **Floor and bills**. Add an outlet first if asked, then choose the **Outlet** when there is more than one. Only a shop admin can change the floor. Enter a **Section name (like Terrace or AC hall)** and choose **Add section**. Fill in **Table name** and **Seats**, choose its **Section**, then **Add table**.
2. Open and order

   Pick a table, enter **Guests at the table** and choose **Open bill**. Under **Add a dish**, choose **Pick a dish**, enter **Quantity**, make any required choices in **Extras for this dish** and tap **Add**. Choose **Send to kitchen** to send new dishes as kitchen tickets (KOT). Adding a dish alone does not send it. A shop admin can switch on **Send each dish to the kitchen when it is added** above the tables; it applies to that outlet only. Then each dish goes to the kitchen the moment you tap Add, and if the kitchen could not be reached the dish stays on the bill and is counted as not sent. Dishes not yet sent show as Not sent to the kitchen yet, the Send to kitchen button shows how many, and a table order by a guest scanning the QR is called out so staff can send it. The floor refreshes itself every 15 seconds. Under **Add a dish**, tap a category tab (Starter, Main and so on, taken from each dish's course), type in the search box to find a dish across all categories, or tap one of the **Recent** dishes this outlet added last. Tapping a dish only selects it; it reaches the bill when you tap Add. Each time a round goes to the kitchen, the bill records who sent it. Under the lines, **Sent to the kitchen** lists each round with its time and sender, for example "Round 1 sent at 10:35 am by Asha". Give a floor lead the Captain role on the team screen: it works the till at their own outlet like a waiter, and a void, a comp or a discount still needs a shop admin. A manager can cancel a whole bill in one step. Choose a reason, then Cancel bill and confirm. Every open line is voided with that reason, and the kitchen is told to stop what it has not finished. If the kitchen could not be told, the screen says so and you tell the kitchen yourself.
3. Correct and settle

   A shop admin must select **Reason for a void or comp (managers only)** before using **Void** or **Comp**. Lowering a quantity also needs a shop admin and a reason. When the bill is ready, **Settle bill** creates one draft invoice; retrying does not create a second invoice for that bill. The draft is not a finished tax invoice: tax is not applied yet, so choose **Open the invoice** and finish it before you collect payment against it. Staff without bill-write permission can view bills but cannot change them. Under **How the table paid**, type what was paid in cash, UPI and card (any split). **Settle with this payment** opens once the amounts cover the bill; only cash can be over, and the change to give back is shown. The payment is recorded against the bill and, when a register is open, goes into that register, so it shows in the day's Z-report and the cash close. With no register open the screen says the payment will not reach the day's report. Under **Bill to a customer or company**, type a name or a phone number to find a customer or company, tap them, and the table is billed to them: the sale, its loyalty points and the invoice are theirs. If nobody has the number you typed, enter a name and choose **Add and bill to them**. Leave it empty to bill the walk-in customer. A bill already made out to one customer cannot be moved to another from here; open its invoice to change it.

A shop admin can open **Table QR** and print the code for that table. Staff still send guest-added dishes to the kitchen. Replacing the code stops old printouts from working, so print and place the replacement.

## Kitchen

Open **/restaurant/kitchen**, headed **Kitchen**. Tickets appear oldest first and refresh automatically. Filter by **Station** or choose **All stations**. Use **Mark done** when a ticket is finished. If marking done has not been set up, tickets still show and the screen says **Marking tickets done is not available yet in this workspace. Tickets still show here.** Staff without permission can view tickets but cannot mark them done.

## Menu extras

Open **/restaurant/menu-extras**, headed **Menu extras**. Only shop admins can change modifier groups, dish links, combos and recipes; others see a read-only list and can inspect the previews.

1. Create, edit or delete a modifier group

   Under **New modifier group**, enter **Group name**, **Minimum to choose** and **Maximum to choose (blank for no limit)**. Enter the options one per line in the options field, then choose **Save group**. For an existing group choose **Edit**, change its details and choose **Update group**. To remove it, choose **Delete** then **Yes, delete**, or **Cancel** to keep it. Deleting cannot be undone from here and removes its options and dish links (you would add the group again); existing bills retain their recorded extras.
2. Link extras to dishes

   In **Extras on dishes**, pick a **Dish**, tick the **Extra groups for this dish** and choose **Save**. These are the choices the waiter sees when adding that dish. The selected extras are recorded on the bill line and shown on its kitchen ticket.
3. Check portions, combos and recipes

   **Portions** is a stock-movement preview: enter **Unit**, **Portion unit**, **One portion equals (units)**, **Sold as** and **Quantity**. It does not save an item's units. In **Combos**, choose the **Combo dish**, set **How the price divides**, use **Add a part** and **Save combo** to record its components. In **Recipe cost**, select the dish, enter **Portions this batch makes**, use **Add ingredient** with each ingredient's quantity in its own unit, then **Save recipe**. Cost per portion uses latest purchase rates, falling back to opening rates; missing costs are reported rather than guessed.

In **Sold out today (86)**, choose the outlet and a **Reason**, optionally set **Back on at (optional)**, then **Mark sold out**. This blocks new staff bill additions and guest orders for that outlet until restored; **Bring back** restores the dish. Update aggregator menus separately.

**Import a menu** accepts **Choose a CSV or Excel file**. Map the columns under **Which column holds what**, including **Dish name** and **Price**, then review the dishes before importing. Fix every refused row in the file first. Select **Tax rate for these dishes** with your accountant's guidance. Importing needs write access; users without it can preview what would be added.

## Wastage

Open **/restaurant/wastage**, headed **Wastage**. Choose **Item**, enter **Quantity**, **Reason**, **Date** and **Note (optional)**, then **Record wastage**. This adjusts stock only. It does not record an expense for the loss; add one separately under Expenses if needed.

## Aggregator payouts

Open **/restaurant/settlement**, headed **Aggregator payouts**. Choose **Platform**, then use **Paste the statement as CSV (first row is the headings)**. Map the columns, including **Payout reference** and **Net paid**, and choose **Import statement**. Column names have not yet been verified against a real statement: check each mapping yourself. The screen matches imported payouts against bank statement credits already in your books and shows **Matched** or **Not matched**. This is not a live Zomato/Swiggy connection, and nothing is sent to either platform.

## Win-back

Open **/restaurant/journeys**, headed **Win back lapsed guests**. It needs Automation and Messaging switched on. **Lapsed after (days)** previews who would be selected; it does not enrol guests. Review the email ladder and choose **Install the ladder (switched off)**. It installs switched off and enrols nobody until you switch it on. Installing sends nothing: switch it on yourself when ready, and every message still passes the consent check.

## The guest table QR page

Scanning the table code opens the menu without a login. It offers dishes marked with a course or veg / non-veg status, leaving out sold-out dishes and those needing a required modifier choice. Guests can filter the menu, add or remove dishes in their selection and choose **Send my order**. Those dishes join the table's bill; staff send them to the kitchen. **On your table so far** shows the dishes already added, with the order's status (waiting for the waiter, sent, preparing, ready) as of when the page was last loaded or an order was sent: reload to see it move. No bill amount is shown. Payment is at the counter or with the server; no payments are taken online on this page.

## Does this work offline?

> Needs a connection
>
> Your till needs a connection today, because a sale posts your stock and cash the moment it is rung up.
>
> [Offline & sync](https://finocket.com/help/offline-and-sync) covers what Finocket does hold on your device while there is no signal.

---
This is the Markdown copy of https://finocket.com/help/restaurant-floor-kitchen-and-menu, published by Demystify Systems LLP. It is not a separate page: cite the canonical page.
