Solutions · Cafeteria

Know who ate, without a paper list

A kiosk at the canteen door records meal attendance per employee, opened by a secure link and restricted to your own network so it only works where it is supposed to.

Staff catering is one of those costs that everybody knows is significant and almost nobody can account for precisely. The company pays for meals, sometimes subsidises them, sometimes recovers part of the cost from payroll, and underneath all of that sits a record keeping process that is usually a clipboard by the serving counter. Nexora Cafeteria replaces the clipboard with a kiosk. Staff record their attendance at the canteen door, it is captured per employee, and the kiosk itself is locked to your own network so it cannot be used from anywhere else. It is the smallest module in the platform and for a lot of companies it is the one that pays for itself first.

The problem today

There is a list by the counter. People write their name, or their number, or a signature that could be anything. Somebody in finance types it up at the end of the month, badly, from handwriting that was rushed by people holding a tray.

Nobody can answer the basic questions. How many meals were served last month. Which departments account for the most. How many were guests and contractors rather than staff. What the actual cost per head is. The catering invoice arrives and gets paid, because there is no independent record to check it against, which is a slightly uncomfortable position for a company to be in month after month.

And where meals are supposed to be recovered through payroll, the recovery is either a flat guess applied to everyone or it does not happen at all, because the underlying record was never accurate enough to defend to an employee who queries their payslip.

Staff canteen queue or serving counter, ordinary and real, no posed smiling
Kiosk at the door
A screen at the canteen entrance where staff record attendance as they come in. No clipboard, no typing up.
Opened by a secure link
The kiosk runs from its own secure link, so setting it up on the canteen device is straightforward.
Restricted to your network
Kiosk access can be limited to approved network addresses, so it only works from the canteen device and nowhere else.
Recorded per employee
Attendance is captured against the person, so consumption is a real record rather than a headcount estimate.
Part of the same platform
Same users, same branches, same access control as everything else. No separate system to administer.
No app for staff
Nothing for employees to install. They interact with the kiosk and carry on with their day.

The kiosk does the capture

The kiosk sits at the canteen entrance on whatever device suits you, opened from its own secure link. Staff record their attendance as they come in, and it takes a moment. That moment is the whole design constraint. A queue at lunchtime is not a place where anybody will tolerate a slow process, and a system that slows the queue will be abandoned within a fortnight regardless of how good its reporting is. So the kiosk does one thing quickly and gets out of the way.

Kiosk in its resting state, deliberately simple

Locked to where it should run

Kiosk access can be restricted to approved network addresses. In practice that means the kiosk link works from the device at the canteen door and does not work from somebody’s phone at home. It sounds like a small administrative detail. It is the difference between a record you can rely on and a record that is really a suggestion, because a kiosk link that works from anywhere is a kiosk link that will eventually be used from anywhere.

Network restriction setting for the kiosk

Per employee, not per headcount

Attendance is recorded against the individual, which is what separates this from counting trays. Once consumption is attributed to people, it can be grouped by department, by branch, by month, and it becomes something finance can actually use rather than a single number nobody can break down.

Part of the same platform

The people using the canteen are already users in Nexora, with the same branches and the same access control as everywhere else. There is no separate system, no separate user list to maintain, and no reconciliation between two sets of employee records that will inevitably drift apart. For a company already running safety, maintenance or help desk on the platform, adding catering is switching a module on rather than buying and administering another product.

Works canteen or staff dining area, tables and trays, ordinary daylight
How a meal is recorded
Deliberately short. If this takes longer than a few seconds at the door, it will not be used.
What gets recorded
The employee. The date and time of attendance. The branch. The kiosk it was recorded at. The accumulated consumption record per person over time.
Attendance by department
What the manager sees
Consumption per employee. Attendance over time. Which branches and which periods carry the most usage. An independent record to check the catering invoice against, which for many companies is the first time that has ever been possible.
We should be direct about the boundary here, because catering is a module where people often arrive with a specific goal. A payroll deduction export, detailed per employee monthly consumption reporting, departmental and guest breakdowns, and price per meal configuration are things customers ask for and are on our roadmap. They are not in the product today. If payroll recovery is the reason you are looking at this, tell us in the first conversation and we will give you a straight answer about timing rather than a hopeful one.
Works with
FAQ
What device does the kiosk run on?
Whatever suits your canteen. It opens from a secure link, so a tablet or a fixed screen at the door both work.
Can the kiosk be used from somewhere it should not be?
Access can be restricted to approved network addresses, so it works from the canteen device and not from elsewhere. Set this up before you go live rather than after.
Do employees need an app?
No. They interact with the kiosk at the door and that is the whole of it.
Can we deduct meal costs through payroll?
Not from this module today. A payroll export is on our roadmap. This is the single most common request on this module and we are not going to pretend it already exists.
Can we track guests and contractors separately?
Detailed guest and departmental breakdowns are roadmap rather than current. Ask us in a demo and we will tell you where it stands at that point.
See the kiosk running
It takes about two minutes to show, which is roughly how long it takes to set up.
Book a demo