Skip to content
Anzma modulePart of Operations

Restaurant table software and kitchen display system: tables, KDS, delivery and recipes

The order goes from the table to the right kitchen station on its screen, then to the bill and stock, with table reservations, delivery and a recipe for every dish.

Last updated: 8 min readBe the first to rate this page
Restaurant table software and kitchen display system: tables, KDS, delivery and recipes

In short

Anzma’s restaurant module is the table and kitchen layer for restaurants: a live floor plan, table orders, kitchen display (KDS) screens, delivery, table reservations, recipes and dish costing. This page goes deep on those features; the full picture of running a restaurant is on the restaurant page. It works on top of Anzma’s POS, and every settled bill becomes an ordinary sales invoice.

Who is it for?

  • Restaurants with dining rooms
  • Cafes
  • Fast-food outlets
  • Catering kitchens
  • Floor and kitchen managers
  • Restaurant owners
Order types
Dine-in, takeaway, delivery, drive-thru
Kitchen
Stations, KDS screens, an expo screen and 80 mm printing
Bills
Split by items, equally or by seat; merge bills
Recipes
Ingredients leave the kitchen warehouse when paid
Delivery
A delivery board with your own drivers, no third-party delivery apps
Builds on
The POS and products

What you get, at a glance

  • Live floor plan

    Draw areas and tables by drag and drop and see each table’s state (free, occupied, reserved, needs cleaning, bill printed) with a timer.

  • KDS screens by station

    Every item reaches its station (grill, cold, drinks) on a screen with a colour-coded timer, and the cook bumps it with one tap.

  • Modifiers, combos and menus

    Required or optional modifier groups with minimum and maximum picks, combo meals with choices, time windows and an 86 switch for sold-out items.

  • Split and merge bills

    Split a check by items, equally or by seat, merge bills, move a table or items, and add a service charge and tips.

  • Reservations and waitlist

    Reserve a table by party size with an optional deposit, and keep a waitlist for walk-ins without a booking.

  • Recipe and dish cost

    Link a dish to its ingredients, deduct them from the kitchen warehouse on payment, and compare theoretical and actual food cost.

Inside the product

The tillIllustrative screen of the POS this module runs on, not real restaurant data.
On this page
Section 01

What does the restaurant module add to the POS?

It adds what a restaurant needs and a shop does not: tables with a state, an open order that takes items in rounds, a kitchen that receives what the guest ordered on a screen, a bill that can be split between people, and a recipe that deducts ingredients. It runs on top of the POS and depends on products, so menu items are ordinary products with their prices, stock and reports in one place.

This page goes deep on those features alone. If you want the full picture of running a restaurant, including purchasing, staff and accounting, the restaurant management software page explains it, and this module appears there as part of a bundle.

The module belongs to Anzma’s operations management software line and is available on every plan, with no specific plan required.

Section 02

How does an order travel from the table to the kitchen?

An order travels from the table to the bill in six stops, and the system records each step with its time and who did it.

  1. 1

    Open the order at the table

    The server picks the table on the map and enters covers, so the table turns occupied and its timer starts. The order type can be dine-in, takeaway, delivery or drive-thru.

  2. 2

    Add items in rounds

    The server adds items with modifiers, guest notes and a seat number, and every item carries a course: starter, main, dessert or drink.

  3. 3

    Send to the kitchen

    On send the system creates one ticket per station according to each item’s station. You can fire one course and hold the others until the guest asks.

  4. 4

    Prepare

    The ticket appears on the station screen with a timer that changes colour when late. The cook bumps it when done and can recall it if it was a mistake. An expo screen gathers one order’s items from all stations.

  5. 5

    Serve

    The supervisor confirms the course was served. An 80 mm ticket can be printed instead of, or next to, the screen.

  6. 6

    Bill and payment

    The check is printed and the table becomes bill printed. The bill is settled with the usual payment methods and produces an ordinary sale; the table goes to needs cleaning, then free, depending on a setting.

Section 03

How do the floor plan and table management work?

The floor plan is a drawing of your restaurant: areas such as indoor and terrace, and tables with numbers, seats and shapes that you place by drag and drop where they really are. Open Live tables and every table shows its colour (free, occupied, reserved, needs cleaning or bill printed) and how long it has been in that state, so the floor manager sees where turnover is slow.

For a large party you merge tables with one tap so they act as one, and split them after the guests leave. You can transfer an order to another table, move chosen items to a different order, or merge two orders. Every transfer, and every item removed after sending, is logged with its reason and who did it, and voiding after sending can require a special permission if you turn that on in settings.

Section 04

What is a kitchen display screen (KDS) and how is it tied to stations?

A kitchen display system shows the cook what to prepare, instead of a paper slip that gets lost. In Anzma you define kitchen stations (grill, cold, fryer, drinks), tie each menu item to its station, and register a screen for each device that opens the screen page in a browser and is paired to it with a token. You do not need special hardware; any screen with a browser will do.

A ticket shows the order’s items, modifiers, notes, course and table, with a timer that changes colour after two limits you set in minutes: warning, then late. All-day counts show how much of each item remains across tickets. A ticket is bumped with one tap and can be recalled, and an expo screen is there for whoever assembles dishes before they leave.

  • One ticket per station carrying only that station’s items.
  • A colour-coded timer with warning and late limits in minutes.
  • Recall a ticket that was bumped by mistake.
  • An expo screen that gathers the whole order before serving.
  • An 80 mm ticket as a fallback or companion.
Section 06

How are bills split and how are service charge and tips handled?

A table’s bill splits three ways: by items, so each person carries what they ate, equally into a number of parts you choose, or by seat, which collects what was entered against each seat. Bills can be merged and split again. Each bill is paid with the usual POS payment methods and produces one sales invoice, so there is no parallel money trail for the restaurant.

You set a service charge as a percentage (whether it is taxable and whether it applies to dine-in only), a minimum charge, and tip presets. Tips can be treated as a liability to staff or as revenue, according to your policy. Discounts, voids and comps need permissions, and a dedicated report shows who voided what.

Section 07

Does it handle table reservations and delivery?

Yes. A table reservation is stored with a default duration and party size, the system suggests suitable tables, the table turns reserved ahead of the time, and a deposit can be taken that is applied to the bill when they sit. Walk-ins without a booking join a waitlist and are seated from it when a table frees up. On arrival you press seat and the order opens at the table.

Delivery is a board that tracks orders from new to preparing, ready, out for delivery and then delivered or failed, with a driver assigned from your employees, dispatch and delivery times recorded, and a delivery fee you set. The module does not connect to third-party delivery apps; delivery orders are entered by your staff or taken by phone.

Section 08

How is dish cost calculated from a recipe?

A dish’s cost is the sum of its ingredients at the warehouse’s average cost. You link each dish to a recipe: a light recipe inside the module is enough, or a bill of materials from the manufacturing module if it is switched on, so sub-assemblies are exploded down to raw items. When a bill is paid the ingredients leave the kitchen warehouse, their effect is posted to cost of sales, and everything comes back if the invoice is cancelled.

The food-cost report compares theoretical cost from recipes with actual consumption from stock counts, which exposes cooking waste or missing ingredients. The example is illustrative, with made-up numbers, for a chicken meal.

Example: cost of a grilled chicken dish from its recipe (illustrative numbers)
IngredientQuantityCost
Chicken0.35 kg28
Rice0.15 kg3
Vegetables and sauceportion5
Packaging and spicesportion4
Dish cost40
Selling price 120: cost ratio33%
Section 09

What does a kitchen screen change compared with paper tickets?

A paper ticket is printed in the kitchen, where it gets lost, wet or ignored, and nobody knows how long an order has waited unless they ask. A screen turns all of that into data: each ticket has an entry and finish time, each station has an average time, and each order has someone responsible for serving it. Printing stays available as a fallback when a screen fails or for a station that prefers paper.

This does not replace the kitchen team with technology; it cuts the shouting between floor and kitchen. When a server adds a late item or a guest drops a dish, the change reaches the same screen instead of relying on a verbal message. The table summarises the difference.

Paper tickets vs a kitchen display screen (KDS)
AspectPaper ticketKDS screen
Order arrivalWhen printed and hungAt the moment of sending, on the station screen
Tracking delayBy looking and askingA colour timer with two limits you set
Change after sendingVerbal messageShown on the ticket itself
Performance measurementNoneTime per station and item in a report
Recall a ticketReprintRecall with one tap
Several stationsPaper copies for eachOne ticket per station with its own items only
Section 10

Which settings and permissions control the restaurant?

In restaurant settings you set the service charge and whether it is taxable, a minimum charge, the tip policy and presets, the kitchen warehouse that ingredients are deducted from, the warning and late limits on the screens, the default reservation length and deposit, the delivery fee, opening hours, and whether a table returns to needs cleaning after payment.

Permissions are detailed to suit a restaurant: managing the floor plan is separate from viewing it, switching off a sold-out item has its own permission, and voiding, comping, transferring, splitting and settling a bill are separate permissions, as are managing screens, delivery, reservations and reports. A server gets what they need and the rest stays with supervisors and managers.

Section 11

Which daily reports does the module give you?

The restaurant reports answer the floor and kitchen manager’s questions: sales by table, area, server, order type and hour; average check and covers; kitchen times from order to bump by station and item; voids and comps; food cost; and delivery performance. All can be exported for analysis.

Kitchen times show which station slows service, and hourly sales help set floor shifts. All of it flows into the financial reports because paid bills are real sales invoices.

Section 12

Which restaurants is it for and when is it not enough?

It suits any business serving food at tables or by delivery: restaurants, cafes, fast-food outlets, catering and bakeries with seating. For a shop that sells items without tables, the POS alone is enough.

In multi-branch restaurants each branch sets up its own floor and stations and their reports combine at company level. Costing recipes in a central kitchen that supplies branches needs manufacturing. Book an online meeting and we will show the module on your menu.

Frequently asked questions

What is a kitchen display system (KDS)?

A screen that shows each kitchen station the tickets it has to prepare, with a timer that changes colour when late, and the cook bumps each with a tap. In Anzma it runs in any browser once paired with a token, with an expo screen, all-day counts and 80 mm printing as a fallback.

How do orders reach the kitchen from the till?

When the server sends the order, the system creates one ticket per station according to each item’s station, and it appears instantly on that screen. You can fire one course, such as starters, and hold the rest; each ticket carries the table, modifiers and guest notes.

Does it support modifiers and combos?

Yes. Required or optional modifier groups with minimum and maximum picks and a price difference for each, combo meals with choice slots, time windows for menus like breakfast, and an 86 switch for sold-out items. A modifier can also add or remove a recipe ingredient.

How is dish cost calculated?

From the dish’s recipe: its ingredients at the warehouse’s average cost, with modifiers adjusting them. On payment the ingredients leave the kitchen warehouse and cost of sales is posted, and the food-cost report compares theoretical with actual consumption from stock counts.

Does it manage delivery and table reservations?

Yes: a delivery board from new to delivered with a driver from your staff and a delivery fee, and table reservations with party size, an optional deposit and a waitlist. It does not connect to third-party delivery apps, so those orders are entered by hand.

What is the difference between this module and restaurant management software?

This module is the part that handles tables, kitchen, delivery and recipes. Anzma’s full restaurant management software adds sales, purchasing, stock, HR and accounting around it. The restaurant page linked above explains the whole bundle.

Can a bill be split between several people?

Yes, three ways: by items, equally into parts, or by seat. Bills can be merged again, and each one is paid separately and issues its own sales invoice. Splitting requires a dedicated permission.

Does the restaurant module work offline?

No. The floor plan, kitchen screens and delivery board exchange data live, so they need an internet connection. The only offline feature is the standard POS terminal queueing plain sales, and it does not include these restaurant features.

Part of the product line

operations management software

What your company sells besides finished goods, from appointments to rented units, work orders and production, becomes an invoice and an entry automatically in one system.

All Operations modules

Rate this page

Did you find this useful? Your rating helps others.

No ratings yet.

Share this pageWhatsAppXLinkedInFacebook
Pricing

Clear plans that grow with you

Nearly every module in every plan; plans differ by limits.

Basic

For small businesses getting started

450EGP / mo

Billed 5,400 EGP yearly

Save 24%

Includes:

  • 3 users and one branch
  • 150 invoices per month
  • Every module your activity needs
  • 5GB storage
Book a meeting
Most popular

Advanced

For growing businesses with several branches and warehouses

790EGP / mo

Billed 9,480 EGP yearly

Save 20%

Everything in Basic, plus:

  • 7 users, 2 branches and 3 warehouses
  • 750 invoices per month
  • 2 POS devices
  • 15GB storage
Book a meeting

Comprehensive

Everything: unlimited invoices, manufacturing, custom domain and API

1,590EGP / mo

Billed 19,080 EGP yearly

Save 20%

Everything in Advanced, plus:

  • 15 users, 3 branches and 5 warehouses
  • Unlimited invoices
  • Manufacturing, custom domain and API
  • 30GB storage
Book a meeting

Enterprise

For enterprises: open limits, dedicated server and SLA

Custom

Everything in Comprehensive, plus:

  • Unlimited users, branches and warehouses
  • Dedicated server and SLA
  • Storage on demand
  • Account manager and tailored onboarding
Contact us