Every 15 minutes
The shifts of the current day with their time recordings, from midday into the late evening. Newly clocked-in employees appear in Kiosa shortly afterwards.
From ordio, Kiosa reads shifts with time tracking, the wage history per employee, absences and leave accounts. From these, Kiosa calculates labor costs per location and day, including staff on a monthly salary, and, together with POS revenue, the labor cost ratio, for groups with several locations in one view.
Kiosa is independent software and not a product of ordio. The connection uses the ordio API v3 with read permissions only.
01 // DATA FROM ORDIO
ordio keeps the wage history with hourly, daily and monthly wages. That keeps labor costs in Kiosa correct even when part of the team is on a fixed salary.
| Data type | What exactly | What it is used for in Kiosa |
|---|---|---|
| Locations | All locations of your ordio company | Mapping to Kiosa locations |
| Shifts | Planned shifts with work area, working time, hourly wage and time tracking | Planned vs. actual per location and area, running hours during the day |
| Wages | Wage history per employee: hourly, daily or monthly wage, weekly target hours | Labor cost per hour, for fixed salaries from salary and target hours |
| Employee master data | Name and basic data | Headcount per location |
| Absences, leave account | Holiday, sickness, remaining leave | Absence overview, remaining leave per employee |
| Reporting query | Totals from ordio reporting | Control total against the import in Kiosa |
02 // CADENCE
The shifts of the current day with their time recordings, from midday into the late evening. Newly clocked-in employees appear in Kiosa shortly afterwards.
A full reconciliation of the last few days with shifts, wages and absences. Anything deleted or moved in ordio is cleaned up in Kiosa as well.
The schedule from seven days back to fourteen days ahead. That puts the next two weeks side by side with the revenue forecast.
03 // CONNECTION
One API key and your company ID are enough. The only important thing is to choose the right scopes when creating it.
As administrator, create a key in the Developer Hub, for example named "Kiosa", and select exactly these scopes: branches:read, shifts:read, absences:read, employees.base_data:read, wages:read.
In the "Scheduling access" step, enter the API key and the ordio company ID. Kiosa stores the key encrypted and keeps track of the expiry date.
We map each ordio location to a Kiosa location. If one location runs several businesses, we separate them via the work areas. On request we load past months.
Hours and costs of a period are compared with ordio reporting. After that the reconciliation keeps running automatically.
What you need: administrator access to ordio, the company ID and up-to-date wages in ordio so that the costs per hour are correct. For the labor cost ratio you also need a connected POS. If a location is not mapped, Kiosa imports nothing for it, so no shift ends up at the wrong location.
04 // USE CASES
If you calculate labor costs from hourly wages only, you overlook the head chef and operations management. Kiosa uses the ordio wage history and converts fixed salaries to an hourly rate via the target hours. The labor costs per location in One View therefore include the whole team.
A bar and a café with separate POS systems but one ordio location? Kiosa assigns the shifts to the right business via the work area. Areas that should not be analysed stay out.
Leave accounts and absences from ordio show where remaining leave piles up and which week is thinly staffed. The AI Partner answers "Who still has more than ten days of remaining leave?" from this data.
05 // STAFFING + POS
With OktoPOS or Hypersoft as the POS, the ordio costs become a figure you steer by.
Labor costs from ordio divided by net revenue from the POS, per location and day. More on the metric in the article Labor cost ratio in restaurants.
The comparison across all sites shows where the team is overstaffed or stretched too thin relative to revenue.
Revenue, labor costs and, on request, cost of goods from the Inventory module produce a daily result per location, and the Morning Briefing summarises it in the morning.
06 // FREQUENTLY ASKED QUESTIONS
No. Kiosa is independent software that connects ordio through REST API v3. The API key contains read permissions only, and Kiosa writes nothing back to ordio. Scheduling and time tracking stay in ordio.
Exactly these five scopes: branches:read, shifts:read, absences:read, employees.base_data:read and wages:read. Scopes cannot be changed in ordio after creation. If one is missing, you create a new key.
ordio keys expire after 365 days at the latest. Kiosa records the expiry date so the key is renewed in time. You then create a new key in ordio with the same scopes and store it in Kiosa.
The shifts of the current day arrive every 15 minutes during the day. Every night Kiosa fully reconciles the last few days and reads the schedule from seven days back to fourteen days ahead.
It is included in One View: €99 per location per month, net, no setup fee and no surcharge for the connection, 12-month minimum term. What the further modules cost is listed under Pricing.
07 // READ MORE
In the demo call we show you One View with real numbers and go through the ordio key with the right scopes together.
Book a demo call