Every 15 minutes
The working hours of the current day, from midday into the late evening. During service you see how many hours are clocking up at each location.
From e2n, Kiosa reads the planned shifts per location, the recorded working hours with hourly wage and costs, and the absences. That gives businesses with several locations labor costs in euros, planned vs. actual and, together with POS revenue, the labor cost ratio, all in one overview.
Kiosa is independent software and not part of e2n. The connection runs through the e2n REST API and is strictly read-only.
01 // DATA FROM E2N
e2n attaches hourly wage and costs directly to shifts and working hours. Kiosa takes over these amounts instead of estimating them again.
| Data type | What exactly | What it is used for in Kiosa |
|---|---|---|
| Employees | Name, personnel number, work area, start date, end date, hourly wage | Headcount per location and area, wage history when it changes |
| Shifts | Planned shifts with area and costs | Planned hours and planned costs per day |
| Working hours | Clock in, clock out, break, duration, hourly wage, amount | Actual hours and actual labor costs, the basis of the labor cost ratio |
| Absences | Type, duration, factor and amount | Absence overview and cost of absences per location |
e2n keeps wages as hourly wages. The interface does not deliver monthly salaries or contract terms, so Kiosa works with the hourly wages and amounts from e2n.
02 // CADENCE
The working hours of the current day, from midday into the late evening. During service you see how many hours are clocking up at each location.
Employees, working hours and absences of the last seven days. Anything corrected later in e2n is right in Kiosa by the morning.
The shifts from seven days back to fourteen days ahead. That way Kiosa compares the coming two weeks with the revenue forecast in advance.
03 // CONNECTION
With e2n, each location has its own key. That suits groups well: you decide location by location what Kiosa may read.
e2n provides the x-api-key, once for you as a customer. If you do not have it yet, ask your e2n contact.
In each location under Administration → REST API, activate the bearer key with the blue switch and copy it. Only then is it valid.
In the "Scheduling access" step, enter the customer code and x-api-key, then map each location's bearer key to the matching Kiosa location, as many as you like via "+ Add location".
Kiosa takes over the last seven days and starts the reconciliation. Together we check hours and costs against e2n, after which everything runs on its cycle.
What you need: the e2n customer code, the x-api-key and administrator rights in every location to be connected. For the labor cost ratio you also need a connected POS. How long onboarding takes depends mainly on when the x-api-key is available.
04 // USE CASES
Because e2n already provides costs for planned shifts, Kiosa shows plan and actual side by side not only in hours but also in euros, per location and day. A week with too many overruns stands out before it shows up in payroll.
The work area from e2n is attached to every shift and every working time. In Kiosa you see whether kitchen or service at a location is over plan, and adjust exactly there.
Absences with duration and amount produce an overview of where sickness and holiday hit staffing. The AI Partner answers questions like "Which location had the most sick days in October?" with the numbers from e2n.
05 // STAFFING + POS
With OktoPOS or Hypersoft as the POS, Kiosa sets the e2n costs against net revenue of the same day and location.
Daily, per location and in comparison across all sites. How to read the ratio and which levers exist is covered in the article Labor cost ratio in restaurants.
Revenue per daypart from the POS next to the working hours from e2n: where does the evening shift start too early, where is a pair of hands missing at lunch?
The revenue forecast from the POS history sits next to the e2n shifts of the next two weeks. If you want to plan in Kiosa itself, add Scheduling.
06 // FREQUENTLY ASKED QUESTIONS
No. Kiosa is independent software that connects e2n through the REST API. The keys come from you and e2n, and Kiosa only reads with them. Your scheduling and time tracking stay in e2n.
Three things: your e2n customer code from the access path, the x-api-key that e2n issues once for you as a customer, and a bearer key per location from Administration → REST API, which you activate there with the switch.
The working hours of the current day arrive every 15 minutes during the day. Every night Kiosa reconciles the last seven days so that later corrections come through, and reads the shifts from seven days back to fourteen days ahead.
No surcharge. Connecting POS and staffing system is part of One View: €99 per location per month, net, no setup fee, 12-month minimum term. All modules are listed under Pricing.
On servers in Germany (Hetzner). The access keys are stored encrypted. Which service providers are involved in processing is governed by the data processing agreement.
07 // READ MORE
In the demo call we show you One View with real numbers and go through which e2n keys you need for your locations.
Book a demo call