If you have purchased the "Order Monitor" module, the POS runs an additional web server that you can access from any device on the same network using a standard browser. Simply enter the fixed IP address of the POS with port 48888 in the browser's address bar to access the order monitor.
Example: http://192.168.1.105:48888
Info: The configuration of monitor profiles (order steps, article groups, grid settings) is done in the bessa Manager under Order Monitors in Location Management.
Advancing Order Steps
To update the step of an order or an individual article, simply tap on the ticket or article. A bar appears for a few seconds. If you tapped by mistake, you can tap again within this time to cancel the change. Once the time elapses, the order or article advances to the next processing step.
Tip: The short delay serves as a safety mechanism, allowing accidental taps to be quickly corrected. It has nothing to do with the Delayed Display, which deliberately brings an article onto the board later.
Recovering a ticket
Once the delay has elapsed and the ticket has left the board, it is not lost: the Recent button in the navigation bar opens Recently processed bons — the tickets that left this monitor most recently.
The list shows what was advanced within the last five minutes, at most the ten most recent tickets.
-
Tapping the ticket brings the whole ticket back.
-
Tapping a single item brings only that item back.
In both cases it goes back exactly one step — the ticket or item reappears on the board and can be worked again. Recovered tickets drop out of the list, and the list refreshes along as soon as something changes on the board. Refresh reloads it by hand, Close takes you back to the board.
The list is specific to this monitor. A ticket only appears while it sits at the step immediately after this monitor — once it has moved on, this view will not bring it back. And recovering a whole ticket concerns only this monitor's articles: whatever another station has already advanced does not resurface here.
Two corrections for two moments: the short delay on tapping corrects immediately, before anything happens. Recent corrects afterwards, once the ticket is already gone. Whoever is searching in the kitchen is almost always after the second case.
With nothing to recover it reads No recently processed bons. If the list cannot be loaded, the monitor reports Could not load bons — check the connection to the Sales Point in that case.
Automatic Updates
The monitor display updates automatically whenever something changes – for example, when a new order is placed, an article is cancelled, or a ticket is modified on another order monitor. Manual refreshing or reloading of the page is not required.
Synchronisation via Preparation Time
As soon as articles have a preparation time set, the order monitor staggers their display so they finish at roughly the same time. The synchronisation group depends on the setup:
-
Articles assigned to a course: Synchronisation per course — all articles of the same course finish together.
-
Articles without a course, or no courses configured at all: Synchronisation per ticket — all course-less articles of a ticket finish together. If no courses are configured at all, every article on the ticket falls into the same group.
How It Works
Within each synchronisation group, the order monitor identifies the article with the longest preparation time and aligns the remaining articles to this target completion. Articles with shorter preparation times appear later, so the kitchen starts them exactly when they are needed for simultaneous completion.
Example
A synchronisation group (a course, or a ticket without courses) contains three articles with preparation times of 300 s, 120 s and 60 s. The order monitor displays:
-
Second 0: article with 300 s
-
Second 180: article with 120 s
-
Second 240: article with 60 s
All three articles are then finished simultaneously at second 300.
Maximum Preparation Time per Course
If a single article exceeds the Max. preparation time configured on the course, it is displayed immediately instead of pushing the rest of the course's articles artificially backwards. This caps the guest's overall waiting time.
For ticket-level synchronisation (articles without a course) this cap does not exist — Max. preparation time is a course property only.
Special Cases
-
Articles without a preparation time in a group with staggered articles are displayed immediately — staggering is not possible without a target time.
-
Course without Max. preparation time: Synchronisation runs without an upper bound; even very long articles are staggered.
-
Only one article in the group, or no article with a preparation time: Display is unchanged — immediately after posting.
-
Interaction with course request: When course request is enabled, the per-course staggering starts only with the manual release of the course via the course heading in the cart — not on posting. Articles without a course are still staggered immediately on the ticket level.
Checking Preparation Times
How long the articles actually take is shown by the Processing time/Time and Processing time/Day reports in bessa Manager. They analyse only articles that were set to "done" on the Order Monitor and compare the measured duration with the stored target value. If the target value deviates permanently, it can be corrected directly in the report row — see Check and Correct Preparation Times.
Delayed Display
Some dishes should not go into the kitchen straight away: the soup is poured and served while the schnitzel next to it should only start ten minutes on. For that, an article carries a delay in seconds, and the order monitor shows it that much later.
The decisive point: the order has long been booked. The delay shifts the display on the board only — not the booking, not the ticket, not the billing.
Delay and preparation time
Both values steer the same moment of display, but in opposite directions:
|
|
Delay |
|
|---|---|---|
|
Purpose |
A course finishes together |
A single article starts later |
|
Effect |
pulls an article forward |
holds an article back |
|
Reference |
relative to the longest article in the group |
absolute, from booking |
If both sit on the same article, the delay is added on top of what the preparation time works out. An article never appears before its own order — preparation time cannot pull it into the past, and the delay applies after that.
Assigning a delay ad hoc
If the delay should not always apply, it sits on an article option rather than on the dish. The business creates options such as "+10 min" and "+20 min" once; the service attaches them to the dish while booking.
-
An option's delay applies to the line it is attached to.
-
If several options carrying a delay are attached to the same line, the largest one applies. They do not add up.
-
A delay on the dish itself and one on an option are not added up either — here, too, the larger value wins.
Effect on the course
Courses run one after another. A delayed article therefore keeps the course it belongs to in the kitchen for correspondingly longer — the next course only follows once this one is through. That is intended: a dish that starts ten minutes later is finished ten minutes later.
A ticket that is not on the board yet accrues no waiting time either. The colouring by time to priority (yellow) and time to rush (red) only starts counting once the ticket actually appears — otherwise a deliberately delayed dish would show up red at once.
The delay is configured in bessa Manager on the article in the Configuration section — see Articles.
Locking Articles
Articles can be temporarily locked on the monitor, for example when ingredients are running out or the work station is overloaded.
If "Lock for Today" is selected, the article will be automatically unlocked at midnight.
Important: Locked articles can no longer be booked at the POS or terminals.
To unlock articles early, or to release permanently locked articles, go to the monitor settings via the clock (top right) and remove the article from the article list.
Monitor Settings
To access the order monitor settings, tap the clock in the top right corner. To exit the settings, tap the house icon in the top right corner.
The following settings are available:
Monitor
Selected Monitor – If you have purchased multiple licenses, several monitor profiles are available, for example a kitchen and a bar monitor, which can be switched here.
Selected Printer – Here you can select a print group on which completed tickets or articles should be printed. This setting applies to the whole monitor and takes effect whenever the order step in question has no printing group of its own — see Which Printing Group Applies.
Times – Times help you visually identify tickets that have been waiting too long. Define the desired times for when a ticket should receive priority status (yellow) and when it is considered delayed (red).
Columns / Rows – Define how many rows and columns are available for tickets on a page.
Text – Adjust the font size on the monitor to suit your needs.
Visibility – Define which information should be displayed on this monitor. "Tickets" shows all individual tickets, and "Aggregation" shows all articles in a summarized list. A combination of both is also possible.
Article Groups
Select all article groups that should be displayed on this monitor. Each article group can also be assigned its own color for easier distinction.
Articles
All currently locked articles are listed here. To unlock an article, simply remove it from this list.
Status
Select all relevant processing steps that should be displayed on this monitor.
Every selected step additionally carries a Printing Group field. It determines which printing group this monitor prints on when an order moves into this step. Two stations working the same step can therefore each print on their own printer.
-
As long as you select nothing, the field reads General setting (name of the printing group) — the monitor takes over whatever is configured for this order step in general. If nothing is configured there, the text reads General setting (no printing group).
-
Pick a printing group and it applies to this monitor and this step only.
-
The topmost entry in the list — the same General setting (…) text — hands the step back to the general setting.
The field can only be edited while the step is selected for this monitor. Deselect the step and the field becomes inactive as well.
The same assignment can also be made in bessa Manager, in the "Order Steps" tab of the monitor profile — see Order Monitors. Both routes write the same entry.
Which Printing Group Applies
When printing, the Sales Point looks for a printing group in this order and takes the first one that is set:
-
The printing group of this monitor for this order step — the field from the Status section, or the "Order Steps" tab in bessa Manager.
-
The printing group of the order step — configured on the step itself in bessa Manager and therefore valid for every monitor without an entry of its own.
-
The printing group of the monitor — the Selected Printer field.
If none of the three levels carries a printing group, nothing is printed.
An existing setup keeps printing unchanged. No per-step entries are created for monitors that already existed before the update. Without such an entry, level 2 applies and then level 3 — exactly the resolution that was in place before 6.1.0.
Example: kitchen and bar both work the step In Preparation. The order step generally carries the printing group Kitchen. In the Status section the bar monitor sets the printing group Bar for this step. The result: the kitchen monitor keeps printing on Kitchen, the bar monitor on Bar — without anything changing in the general setting.
Frequently Asked Questions
Which devices can I use as an order monitor? Any device with a standard browser (e.g. Chrome, Firefox, Safari, Edge) that is on the same network as the POS. Common options include tablets, monitors with connected PCs, or smart TVs with built-in browsers.
Can I run multiple monitors simultaneously? Yes, provided you have the appropriate licenses. Each monitor can use its own profile with individual settings.
What happens during a network outage? Since the order monitor runs locally on the POS as a web server, you only need a functioning network connection between the POS and the monitor. An internet connection is not required.
Related Articles
-
Order Monitors – Configuration of monitor profiles in bessa Manager
-
Order Steps – Definition and management of order steps
-
Article Groups – Managing article groups
-
Printing Groups – Configuring printing groups