Every 15 minutes
Clock-in times of the current day, from midday into the late evening. One View shows the hours building up while the shift is on.
Kiosa reads schedule, clock-in times, contracts and absences from gastromatic and calculates working hours and labor costs per location and day from them. Together with the revenue from the POS, this gives groups with several locations their labor cost ratio every morning, instead of only with the monthly financial statement (BWA).
Kiosa is independent software and not part of gastromatic. The connection is strictly read-only, and gastromatic stays your staffing system.
01 // DATA FROM GASTROMATIC
gastromatic cleanly separates plan, clock-in time and confirmed actual time. Kiosa takes over all three so it can show where extra hours appear between planning and payroll.
| Data type | What exactly | What it is used for in Kiosa |
|---|---|---|
| Employees | Name, personnel number, start date, end date, location | Headcount per location, assignment of all times |
| Contracts | Weekly or monthly hours, wage type, wage group | Labor cost per hour, for fixed salaries from salary and contract hours |
| Schedule | Planned shifts with work area | Planned hours and planned costs per day and area |
| Clock-in times | Clock in, clock out, breaks | Current day: who is in, how many hours are running |
| Actual times | Confirmed working times | Actual hours and actual labor costs, the basis of the labor cost ratio |
| Absences | Holiday, sickness and other categories, paid or unpaid | Absence overview, absences per location |
| Leave entitlement, balance adjustments | Target values and correction postings | Working time accounts and remaining leave, calculated by Kiosa |
02 // CADENCE
Clock-in times of the current day, from midday into the late evening. One View shows the hours building up while the shift is on.
Employees and contracts, the schedule from seven days back to fourteen days ahead, clock-in times of the last seven days and confirmed actual times of the last 30 days. That way, later corrections in gastromatic come through automatically.
Absences: every week over the last 13 months, the entire history at the start of the month. So a sick day entered late is still recorded correctly after the fact.
03 // CONNECTION
You create an interface in gastromatic and give Kiosa the client ID and client secret. The locations usually map themselves.
Under Settings → Administration → API, create an access via "+ Interface", for example named "Kiosa". gastromatic then shows you the client ID and client secret.
Enter the client ID and client secret in the "Scheduling access" step. Token and base address are prefilled, and Kiosa stores the credentials encrypted.
Kiosa maps the gastromatic locations to Kiosa locations by name. Anything that is not clear-cut, we map by hand. On request we load past periods.
You compare hours and costs for a period with your gastromatic report. If it matches, the reconciliation keeps running on its cycle.
What you need: a gastromatic access with the right to create API interfaces, and up-to-date contract data so that the costs per hour are correct. For the labor cost ratio you also need a connected POS. How long onboarding takes depends on access and data quality.
04 // USE CASES
Kiosa was created at Mama Trattoria, ten restaurants in Hamburg that run their staffing with gastromatic. These are the questions it was built for there.
Kiosa calculates the actual labor costs from gastromatic against revenue every day and shows the ratio per location in One View. If it goes off track at one site, you see it the next morning, not in four weeks. Background in the article Labor cost ratio in restaurants.
Planned shifts against clocked and confirmed times, per location and work area. You see where people regularly work longer than planned, and whether revenue supports those hours.
From contracts, actual times, balance adjustments and leave entitlement, Kiosa calculates working time accounts per employee. The AI Partner answers "Who has more than 20 overtime hours at the Nord location?" directly from these numbers.
05 // STAFFING + POS
gastromatic knows who worked when. The POS knows what was sold. Kiosa brings both together, with OktoPOS or Hypersoft.
Net revenue per location and daypart divided by the hours worked. The comparison between sites shows where the team is deployed efficiently.
Kiosa calculates a revenue forecast from the POS history. Next to it sit the planned hours from gastromatic, so under- or overstaffing stands out before the day starts. More in the article Planning staffing by revenue.
Revenue from the POS, labor costs from gastromatic and, on request, cost of goods from the Inventory module produce a daily result per location.
06 // FREQUENTLY ASKED QUESTIONS
No. Kiosa is independent software. It connects gastromatic through the official API with an access you create yourself, and only reads. Your schedule, your time tracking and your payroll preparation stay in gastromatic.
No. Kiosa writes nothing back to gastromatic and does not need a second schedule. If you also want to plan in Kiosa against the revenue forecast, you can book the Scheduling module; it is not required for the analysis.
Clock-in times arrive every 15 minutes during the day. Every night Kiosa reconciles employees, contracts, the schedule from seven days back to fourteen days ahead and the confirmed actual times of the last 30 days. Absences are reconciled weekly over 13 months and monthly in full.
Nothing extra. Connecting your POS and staffing system is included in One View: €99 per location per month, net, no setup fee, 12-month minimum term. There is no surcharge per connected system.
07 // READ MORE
In the demo call we show you One View with real staffing and revenue numbers and go through the gastromatic interface together.
Book a demo call