The business starts with a menu that the operation knows.

A guest sees a menu, a table and a bill. Behind that lie agreements that determine who receives what.

Restaurant management brings that foundation into one place: what you sell, which tables there are, who has access, and which location it belongs to. A menu change is then visible in the order; a table belongs to the venue, not to a standalone screen.

  • ForIndependent businesses and groups
  • BasicMenu, tables, team, locations
  • ConnectsOrders, table layout, workforce
MenubeheerIllustratieve demo-interface
Dishes with category, price and image — the basis of every order. Demo environment.

One setup, three kinds of agreements.

Restaurant management is not a collection of settings. It is the place where you record what a venue sells, which tables exist, and who has access.

  1. 01

    Menu

    Categories, dishes, options, allergens and availability. A dish is not just text and price: it also determines which station a line goes to.

    Category · dish · option · allergen · availability

  2. 02

    Table service

    Tables, zones, and the status of the venue. Service opens a table, sees what is going on, and keeps the bill together. Moving a table does not mean the order starts over.

    Table · zone · status · bill

  3. 03

    Team and locations

    Roles, access, and the location someone works at. A group can manage multiple restaurants side by side without mixing up the daily environments.

    Role · access · location · environment

The menu determines more than the card.

A dish has a category, a preparation station and allergen information. That data is on the dish itself, not in a loose list next to the system.

This is how an order reaches the station that prepares the dish. The bar only receives the drink lines; the kitchen only the dishes. What is not available cannot be passed on as available.

The kitchen does not have to guess which dishes belong to a table. The pass sees the order and the status.

The location is the unit, not the exception.

An independent restaurant manages one restaurant environment. A group manages multiple environments and keeps the same foundation per location.

The central management layer coordinates environments and access. Daily operations remain per location. Reporting can place locations side by side with the same definitions.

View Reporting per location
Independent01

One menu, one business, one operation. The setup determines what the kitchen, bar and service see.

Group0N

Multiple locations with their own environment. The group coordinates access and rollout; the reporting compares.

The same foundation per location. No second truth for the group.

All locations and teams in one overview.

In the business environment, a group manages its locations from one place: name, address, team and access. Each location remains its own restaurant environment with its own menu, tables and roster.

Who works where and who holds which role can be found per location. This keeps the central layer clear without taking over daily operations.

Locations · team · roles · access

Business / LocationsBeheeromgeving · demo-gegevens
Locations, teams and roles per site in the management overview. Demo environment.

View Restaurant Management with your own menu and tables.

Tijdens een walkthrough beginnen we bij de inrichting die nu het meeste werk kost: het menu, de tafels of de vestigingen.