As of 18 Nov 2026, the panel rates gastromatic 3/5 and Skello 3/5 in Employee Scheduling. Weighted by what each judge cares about, 5 of the 6 judges pick gastromatic and 0 pick Skello, 1 calls it a tie. gastromatic scores higher on 4 of 7 criteria (European sovereignty, Roster building & demand planning, Mobile self-service for deskless staff, plus 1 more). Skello scores higher on 2 of 7 criteria (Pricing transparency and Works council & employee data). Provenance — gastromatic: EU-Made, Germany; Skello: EU-Made, France. Ratings are the AI panel’s opinion, formed from public evidence: how scores are made.
The short answer
The table has gastromatic ahead on roster planning (7.5 vs 6.5; six lean gastromatic, none lean Skello), staff self service (6.3 vs 5.7; four lean gastromatic, two tie) and sovereignty (6.0 vs 3.0; six lean gastromatic). Its verdict credits till-data staffing modules and labour cost visible while planning; its attributes list data residency "EU only", against Skello's "unknown"; Skello's verdict reports no public information on where employee data is hosted, naming only Webflow, Inc. of San Francisco, for the website. Skello takes pricing transparency (5.3 vs 4.2; five lean Skello, one tie) and codetermination and privacy (5.2 vs 4.8; a three-to-one lean Skello, two ties). Payroll and integrations is level at 5.8, leaning two-to-one toward Skello's lock workflow; working time rules yields five ties. Weighted totals put gastromatic ahead for the shift manager, works council, frontline employee and skeptic; the payroll officer is level at 6.1; the operations-director row shows a placeholder.
Choose gastromatic if
You build rosters from till data and need labour cost visible while planning — roster planning means 7.5 vs 6.5, with six judges leaning gastromatic and none leaning Skello.
You require EU-only data residency — gastromatic's sovereignty attributes list data residency as "EU only", while Skello's lists "unknown".
Your staff rely on self-service scheduling — staff self service means 6.3 vs 5.7, four judges lean gastromatic, two tie.
Your shift managers are the primary users — their weighted total runs 6.4 for gastromatic against 5.5 for Skello.
You prefer a vendor under a German legal entity — gastromatic's sovereignty attributes list jurisdiction as "DE".
Choose Skello if
You weigh published prices heavily in the decision — pricing transparency means 5.3 vs 4.2, five judges lean Skello, one tie.
Your works council scores granular permissions highly — codetermination and privacy means 5.2 vs 4.8, a lean of three judges to one toward Skello with two ties.
Your payroll depends on weeks locked and immutable before transmission, with administrator-only unlocking — payroll and integrations is level at 5.8 on means but leans two judges to one toward Skello.
You need a vendor under a French legal entity — Skello's sovereignty attributes list jurisdiction as "FR".
Read this comparison as one judge. Each weighs the same scores by what they care about.
The Skeptic
Has read a great many pages saying the product "supports" the Arbeitszeitgesetz and wants to know whether it blocks a violation, warns about it, or merely exports it. Reads for which tier the time clock and the DATEV export sit in, how seasonal staff are counted per employee, and what the forecasting "AI" actually uses as input.
gastromatic
This judge's pick
Skello
Criterion by criterion
Roster building & demand planning
gastromatic
Staffing requirements sit on the shift cards, revenue-based planning is named as such with POS data flowing into the roster, and the automated planner is described as an algorithm trying combinations under rules, skills and fairness rather than sold as AI. Planned shifts are later compared with clocked hours and labour cost is held against contract and budget frames while planning, across locations planned centrally. I found no cross-location staff sharing as such and no explanation of which rule or demand figure drove an individual assignment.
Skello
Templates filterable by team, position or employee and duplicable over ten weeks, positions ranked primary and secondary, and a Smart Planner that proposes full schedules from constraint sets — favouring the lowest hourly rate and the lowest hour balances — are documented. Staffing forecasts are advertised as a higher-tier feature and a cash-register connection exists, but we found no public information naming the data source the forecast uses, showing labour cost against budget, or describing cross-location staff sharing. It does propose rosters and prices people by rate when it does; the forecast input stays behind the word AI.
Working-time law & collective agreements
gastromatic
The pages say labour law is 'automatisch mitgedacht', and what that concretely means is: conflicts displayed when statutory limits are exceeded, hints on rest times and working-time limits, checks of availability, absence and rules before publication, automatic break models per employee and work area, youth protection named as considered, and complex surcharge logics in the Professional tier. The 11-hour rest period and the 30/45-minute break minimums appear only in a legal guide that calls itself orientation. I found no statement whether an exceeded limit blocks publishing or merely lights up, no Minijob earnings-ceiling warning and no recorded, reasoned override.
Skello
The Smart Planner takes daily amplitude, weekly rest days and an overtime system as constraints and sets rules by default according to the collective agreement, and the pages promise regulatory alerts plus automated hour calculations accounting for legal specifics, with hour counters per employee. We found no public information naming a statute or a rest period in hours, stating whether a check blocks a violating shift or only warns, or covering earnings limits or youth protection. I credit the named rule inputs and per-employee hour tracking, not an unspecified alert.
Mobile self-service for deskless staff
gastromatic
Staff see their shifts, positions and changes in real time with push notifications and read receipts, manage preferred times, holiday requests and shift swaps in the app, and clock start, breaks and end by smartphone, tablet, terminal or browser, with the app working offline; GPS and photo verification at clock-in are explicitly optional. I found no evidence that swaps or open shifts are checked against qualifications or rest periods before approval, no multilingual interface beyond German, and no employee-side export of the data held about them.
Skello
The app on iOS and Android gives employees their published schedule, leave and availability requests, shift-transfer and replacement requests, and clock-in from the phone or tablet with a personal PIN and geolocation at each badge. We found no public information on notification of changes, on swaps checked against qualifications or rest before approval, on offline clock-in, or on languages beyond the captured French and English. Mid-level self-service, well evidenced as far as it goes.
Works council & employee data
gastromatic
Individual rights models for multiple planners sit in the Professional tier, GPS and photo verification at clock-in are opt-in, and the privacy policy documents employee data on AWS in Frankfurt with deletion 80 days after contract end, a seven-day cap on log files and an external data protection officer. I found no data processing agreement offered for the product itself — the GDPR pages are generic legal education — no audit log of who viewed or changed an individual's data, no configurable deletion periods, and no public information on documentation for works-council approval under section 87 of the BetrVG.
Skello
Permission granularity is genuinely documented: four default levels plus more, managers seeing only strictly lower levels, sensitive employee data of the scheduler role restrictable, and read-only access for external accountants and CFOs; the privacy policy states processor status under article 28, retention periods (six years for client data, three for user data) and that personal data is not sold. We found no public information on an audit log of who viewed an individual's data, on a data processing agreement, on whether the geolocation captured at clock-in can be switched off, or on documentation a works council would need.
Payroll handoff & integrations
gastromatic
Worked hours and absences go as export to payroll, with a release step in the hour evaluation before data passes on, and the Professional tier adds payroll interfaces, surcharges and exports for payroll and controlling — but no payroll system is ever named; on these pages I found no DATEV. Four HR tools are named over an open API, POS data feeds the planning, and payroll is also sold as a fully integrated in-house service with a personal clerk. The pages do not show wage types mapped per surcharge or public API documentation.
Skello
The lock step is real and documented: a week can be locked for payroll, a green padlock marks data immutability, the report locks red once payrolls are sent, and only the system administrator can unlock — with payroll variables calculated automatically into an exportable report, HR and payroll sync to the customer's tools, named time-clock and employee APIs, and partner accounting firms able to finalise payroll. We found no public information naming the payroll systems behind the integrations, on wage-type mapping per surcharge, on API documentation, or on handling retro corrections after the close. The mechanics are the strongest evidence on the evidence; the counterparties are invisible.
European sovereignty
gastromatic
The contracting entity is a German GmbH registered in Darmstadt and employee data sits on AWS in Frankfurt, with subprocessors enumerated in the privacy policy and standard contractual clauses named as the basis for Google and Zoom transfers. Two reservations: the revenue book and automated scheduling can store data with Google LLC, a US provider, as the primary storage option, and the policy reserves third-country processing under Articles 44 to 49 GDPR. I found no data processing agreement, no certification and no disclosure covering push notification services.
Skello
The contracting entity is named and European — Skello SAS of Paris, registered in the Paris trade and companies register — with a privacy policy, a DPO contact, and a stated preference for subcontractors located in the EU and EEA. The only hosting statement in the captures names Webflow, Inc. of San Francisco and sits in the legal notices, so it may describe the marketing site rather than the product; we found no public information on the product's hosting location, a published subprocessor list, or a data processing agreement. A named European entity plus silence on where employee data lives is exactly the middle case.
Pricing transparency
gastromatic
Two tiers carry public from-prices — 'ab 69,50 € /Monat' for Starter and 'ab 99,50 € /Monat' for Professional — with monthly billing stated, feature lists showing that the mobile time clock and payroll interfaces live in Professional, and Enterprise on request. The basis of the from-price is never stated, so a buyer cannot tell whether it counts employees or locations or how seasonal staff are billed, VAT treatment is not stated, and the add-ons — automated planning, documents and e-signature, payroll as a service — carry no prices. The calculators on offer estimate the cost of sloppy time tracking, not the invoice.
Skello
Two tiers carry public figures — "Dès 99€ /mois" and "Dès 129€ /mois" — with a 14-day cancellable trial, a stated 10% annual-commitment discount, and three priced add-ons: Service de paie "Dès 20€ /mois par employé", Recrutement "Dès 40€ /mois" and RH Expert "Dès 20€ /mois"; the pricing page helpfully places the geolocated clock-in and the automatic payroll-variable calculation in the lower tier. But the unit behind the tier prices is never stated — per employee or per establishment is not said — the large-plan tier is a quote for 200 to 10,000 employees, and we found no public information on how seasonal or inactive staff are counted, on minimum term, or on VAT. A buyer can read the shelf prices but cannot compute the annual invoice.
Sovereignty, side by side
Dimension
gastromatic
Skello
Legal entity
Incorporated in DE
Incorporated in FR
Hosting location
EU only
Not determined
Hosting options
Not determined
Not determined
Open source
Not determined
Not determined
Data processing agreement
Not determined
Not determined
Transfer impact assessment
Not determined
Not determined
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.
team scheduling · time and absence tracking · payroll management · admin and HR management · performance management · field teams app · electronic signature · scheduling assistant · time clock · activity management4
As of 18 Nov 2026, the panel rates both 3/5. Weighted by what each judge cares about, 5 of the 6 judges pick gastromatic and 0 pick Skello, 1 calls it a tie. Which one fits depends on the criteria that matter to you; the table on this page shows both side by side, and each judge’s reading has its own page. Both were scored by the same AI bench under the same rubric, from public evidence only, as the methodology describes.
Is gastromatic or Skello European?
gastromatic is European (EU-Made, Germany). Skello is European (EU-Made, France). Provenance is read from each company’s own legal pages: who builds it and who owns it.
Where do gastromatic and Skello store customer data?
Per the vendors’ own pages as captured — gastromatic: In the EU; pages mention Germany. Skello: its pages as captured do not say.