Shiftbase
EU-Made Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Shiftbase B.V. · www.shiftbase.com
Compare with Staffomatic → Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Shiftbase at a glance
- Vendor
- Shiftbase B.V.
- Headquarters
- Incorporated in the Netherlands source, captured 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 22 Sep 2026
- Panel verdict
- The AI panel rates Shiftbase 3/5, the mean of 6 judges. Shiftbase, an employee-scheduling tool from Shiftbase B.V. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Shiftbase, an employee-scheduling tool from Shiftbase B.V. in Zoetermeer, lands mid-pack on this bench: persona-weighted totals run from 5.7 to 6.5. It is strongest at roster planning, where scores cluster at 7-8 — an auto-scheduler drafts a full week from availability, absences, contract hours and skills, publishes nothing automatically, explains each per-shift recommendation, and shows labour cost against expected turnover, with POS revenue flowing back into the plan. Staff self-service, payroll and integrations and pricing transparency follow, with three of four tiers publicly priced — Basic at '30 € / Monat' including 6 people, Premium at '75 € / Monat' including 12. The weak point is working time rules, scored 4-6, the widest range among the criteria: the spread reflects how judges weighed the shipped overtime and minijob configuration against a Compliance+ module marked coming soon, and we found no public information on rest-period or break checks. Codetermination and privacy and sovereignty trail on a password-gated subprocessor list and the privacy policy's stated unrestricted administrator access.
Speaks for it
- Auto-scheduler drafts a complete week from availability, approved absences, contract hours, skills and account rules, publishes nothing automatically, and per-shift recommendations come with a Why? explanation.
- POS revenue flows back into the plan and the draft summary shows total labour cost and labour cost as a share of expected turnover.
- Three of four tiers are publicly priced with per-employee maths — Free at '0 €' up to 15 people, Basic at '30 € / Monat' with 6 included and '4 €/Monat pro weitere Person', Premium at '75 € / Monat' with 12 included.
- Approved hours export DATEV-compatible with hour types, surcharges and absence types mapped per contract type, Personio connects directly over the API, and API documentation is public.
- Permissions are granular: four default groups plus custom ones, scoped per department, with employees limited to their own team's schedule and planners barred from viewing salaries.
Held against it
- Working-time enforcement ships only as configurable caps and surcharges — the Compliance+ module naming the Arbeitszeitgesetz is marked coming soon, and we found no public information on rest-period or break checks.
- The DATEV handoff is a CSV sent by e-mail that the user imports into DATEV payroll themselves, and leave balances are not processed.
- The current subprocessor list is retrievable only behind a password, and we found no legal basis stated for the US-headquartered subprocessors such as Customer.io and Mixpanel.
- The privacy policy states Shiftbase administrators have unrestricted access to all customer and personal data without permission, and we found no public information on an audit log of who viewed an individual's data.
- Enterprise is 'Auf Anfrage', the chat add-on is 't.b.d.', and the captured pages give different figures for the onboarding packages (150/325/575 € versus 175/350/600 €).
Best for
- You plan hospitality or retail shifts and want a reviewed, never-auto-published roster draft with labour-cost metrics before applying it.
- You prepare German payroll and need hour types, surcharges and absence types mapped per contract type into a DATEV-compatible export.
- You are a small team moving off spreadsheets: the Free tier covers up to 15 people, Basic is '30 € / Monat' with 6 included, and a 14-day trial runs without payment data.
- Your deskless staff live on their phones and need swaps, open-shift claiming, kiosk clock-in and push notifications in five interface languages.
Avoid if
- You need working-time law enforced in the plan today — ask the vendor: the public pages we read do not show it
- Your payroll requires a maintained DATEV connection with leave-balance sync and retro corrections rather than an e-mailed CSV.
- Your works council will scrutinise data access — the privacy policy states unrestricted administrator access without permission.
- You buy at enterprise scale and need a computable price up front — Enterprise is 'Auf Anfrage'.
The scores
| Criterion | Panel median |
|---|---|
| Roster building & demand planning | 4 of 5 |
| Working-time law & collective agreements | 2 of 5 |
| Mobile self-service for deskless staff | 3.5 of 5 |
| Works council & employee data | 2.5 of 5 |
| Payroll handoff & integrations | 3.5 of 5 |
| European sovereignty | 3 of 5 |
| Pricing transparency | 3.5 of 5 |
Roster building & demand planning
Show reasoningHide reasoning
How this is scored
How a plan gets built across locations, roles and qualifications — templates, staffing requirements, forecasting from sales or occupancy, and whether the product proposes a roster or only draws one.
0 — Not a rostering tool; shifts cannot be planned in the product (a time clock, HR file or messenger only).
3 — A weekly shift grid per location with shift templates and roles attached, and the roster published to staff.
5 — Shift templates with roles or qualifications on shifts, several locations or departments, and open shifts or coverage gaps shown while planning.
8 — Staffing requirements per shift and demand-based planning from a named data source (POS revenue, footfall, occupancy or bookings), automatic roster proposals the planner can accept or adjust, labour cost shown against budget while planning, and cross-location staff sharing.
10 — Planning closes the loop: forecast, proposed roster and actual hours compared in one place, the proposal explains which rule or demand figure drove each assignment, and the vendor documents the forecasting method rather than calling it AI.
The Shift Manager
Required shifts with minimum, exact or maximum staffing, POS revenue flowing back into the plan, and an AI-proposed draft the planner reviews and applies with nothing auto-published, plus labour cost, productivity and cost percentage shown on the proposal. The per-shift Why-explanations say why an employee is recommended, but the vendor calls the forecast AI rather than documenting a method and rules are account-wide rather than per department, so the loop stays open. 6 7 6 1 2
The Operations Director
Required shifts carry minimum, maximum or exact occupancy per department and team, POS revenue flows back into the plan, and the auto-scheduler proposes a complete draft with total labour cost and labour-cost percentage of expected turnover shown before I apply it — that is the demand-and-cost planning I look for. It stops short of the full loop: one department per draft, staff sharing documented only as a loaning function between teams, and the turnover forecast sold as AI without the forecasting method published, though per-shift recommendations do explain their reasoning. 6 7 6 1 2
The Payroll Officer
Required shifts with minimum, maximum and exact occupancy per department and team, POS revenue flowing back into the plan, and an auto-scheduler that proposes a complete schedule from contract hours, skills and rules, applied or discarded with total labour cost and labour-cost percentage shown on the draft, plus a loaning function across teams and per-shift recommendations that explain themselves with a Why button. It stays below the top because the forecast is sold as AI rather than a documented method, drafting covers one department at a time, and applying a proposal is all-or-nothing with no undo. 6 6 7 1 13 1
The Works Council Advocate
Required shifts with minimum, maximum or exact occupancy per department and team, a proposed complete schedule the planner reviews and applies, and till revenue flowing back into the plan put this genuinely at the demand-planning level, and the per-employee "Why?" explanations even show what drove each assignment. For co-determination I must flag that the optimiser offers a "Profit" mode that schedules lower-paid employees more often — that is a distribution of working hours, and no works agreement of mine would let it run unregulated. 6 7 6 1 1 2
The Frontline Employee
Required shifts can be set per team and department with minimum, maximum or exact staffing, and the auto-scheduler proposes a full week from availability, approved absences, contract hours, skills and the account's scheduling rules, which the planner reviews and applies or discards — never auto-published. POS revenue flows back into the schedule and a forecast step shows expected turnover, the draft summary shows total labour cost and labour cost as a share of expected turnover, and a Why? button explains each per-shift recommendation; a loaning function lets one person be scheduled across teams. It falls short of the top because the vendor brands the proposal as AI rather than documenting a forecasting method, and comparing forecast, proposal and actual hours in one place is not shown. 7 6 6 1 2
The Skeptic
The auto-scheduler is documented with unusual candour — required shifts, availability, absences, contract hours, overtime balances and skills as named inputs, three optimisation strategies, nothing published automatically, apply all-or-nothing — and required shifts with minimum, maximum and exact occupancy exist per department and team. But the documented inputs contain no revenue figure: POS revenue flows back so the plan "weiß, was die Schicht gebracht hat" and a permission-gated turnover forecast step exists, and I found no evidence the optimiser consumes either; labour-cost draft metrics and budget management sit on Premium, and cross-department staffing appears only as a loaning function across teams. The vendor also brands the feature "Shiftbase's AI" rather than publishing a forecasting method. 6 7 13 6 1 2
Working-time law & collective agreements
Show reasoningHide reasoning
How this is scored
Whether the roster knows the rules it is subject to — ArbZG rest periods and maximum hours, youth and maternity protection, Minijob earnings limits, Tarifvertrag and works-agreement rules, surcharges — and whether it enforces them, warns, or leaves them to the export.
0 — No working-time checks: the vendor states or shows that any shift can be planned without a rule check.
3 — Basic checks such as overtime, maximum-hours or break warnings shown to the planner.
5 — Named working-time checks — daily or weekly maximum hours, rest periods between shifts and breaks — shown to the planner before the roster is published, and contract hours or earnings limits tracked per employee.
8 — ArbZG named with the 11-hour rest period and daily maximum checked, the Minijob earnings ceiling warned about, whether a check blocks or only warns stated, and configurable rule sets per contract or employee group covering Tarifvertrag surcharges (night, Sunday, holiday), time accounts, youth-protection limits and works-agreement rules, with the planner's override of a violation recorded and reasoned.
10 — The rules are modelled as law, not as warnings: maintained rule sets for named collective agreements, sector-specific exceptions (care, hospitality) documented with the statute they rely on, every override attributable, and published guidance mapping each feature to the provision it serves.
The Shift Manager
What ships today is configurable caps and surcharges: maximum weekly hours, optional daily caps, overtime tiers with percentage surcharges linked to contract types, and conflict notices, but no rest-period check, no named ArbZG enforcement, and no statement whether a violation blocks or only warns. The Compliance+ add-on promising automatic detection of Arbeitszeitgesetz violations with rule sets for hospitality and retail is marked coming soon, and the only documented break rule is that paid breaks cannot be clocked. 6 8 9 1 2
The Operations Director
Configurable caps (a 50-hour default weekly maximum, a 40-hour flex cap, an optional daily cap), overtime tiers such as 120% after 8 and 150% after 12 hours, contract-hours tracking and conflict notices give the planner basic guardrails. The module that would keep every roster within working-time law and resolve violations automatically is marked coming soon, and we found no public information on rest-period or break checks, ArbZG-named enforcement, or a Minijob earnings-ceiling warning. 6 9 1 2
The Payroll Officer
The surcharge machinery is genuinely there: overtime policies per contract type with percentage tiers after set hours, period-linked paid surcharges where the highest wins, plus-minus hour accounts, Minijob contract types for Germany, and solver caps such as maximum weekly hours with an optional daily limit. But the module that keeps every plan within the Arbeitszeitgesetz with rule sets for hospitality and retail is marked only as coming soon, and I found no public information on rest periods between shifts, youth-protection limits, or a recorded and reasoned override when a planner breaks a rule. 9 8 6 2 2
The Works Council Advocate
Daily and weekly hour caps, contract-hour limits, and overtime rules with percentage surcharges tied to contract types are configurable, plus-minus accounts track each person, and German minijob contracts are supported — but I found no public information on rest periods between shifts, the eleven-hour rule, youth protection or collective-agreement surcharges. The add-on that names the Arbeitszeitgesetz with rule sets for hospitality and retail is explicitly marked as coming soon, so the rules exist as configuration today, not as law. 6 8 9 2 1 2
The Frontline Employee
Weekly maximum hours (50 by default) and optional daily caps are enforced when the scheduler builds the plan, overtime surcharges like 120% after 8 and 150% after 12 hours attach to contract types with day or week as the basis, and plus-minus balances and Minijob contracts are tracked. The module that promises automatic detection of Arbeitszeitgesetz violations with rule sets for hospitality and retail is explicitly marked 'coming soon', and we found no public information on rest periods between shifts or break-rule checks shown to the planner before publishing. 6 9 2 1
The Skeptic
What I can verify are configurable caps — weekly maximum defaulting to 50 hours, a daily cap left at "no limit" until set, a 40-hour flex cap — plus generic conflict notices and time-period ratecards for surcharges; we found no public information on an 11-hour rest-period check, break rules in planning, or whether a violation blocks the roster or only warns. The Arbeitszeitgesetz is named only on a paid add-on, Compliance+ at 0,50 € / Monat / Mitarbeiter, whose own pricing marks it "BALD", with rule sets for Gastronomie and Einzelhandel likewise announced rather than shipped. Minijob-Verträge for Deutschland are in Basic and maternity or care leave appear as absence columns in the payroll export — tracking, not enforcement. 6 8 9 1 2
Mobile self-service for deskless staff
Show reasoningHide reasoning
How this is scored
What the employee on the shop floor actually gets: a mobile app to read the roster, enter availability, request and accept swaps, claim open shifts and clock in — in their language, on their own device or a shared one.
0 — No employee access; the roster reaches staff only as a printout or PDF.
3 — An app or web view in which employees see their own shifts and are notified of changes.
5 — A mobile app with the roster, availability or absence requests, and shift swaps or open-shift claiming, with push notifications of changes.
8 — Swaps and open shifts resolved under the rule set (qualifications and rest periods checked before approval), clock-in by app or shared terminal with offline handling, a multilingual interface, and team communication that keeps shift talk out of private messengers.
10 — Self-service is designed for people who never open a laptop: swap and cover flows that resolve without a manager where the rules allow, accessibility and language coverage stated, use on a shared or personal device both supported, and employees able to see and export the data held about them.
The Shift Manager
The app covers the floor crew well: own and team roster, per-day availability, absence requests with balances, swap requests, open-shift invites, push on changes, clock-in with a personal kiosk code for a shared tablet, and five languages. I found no public information on offline handling for the time clock or on swap approvals being checked against qualifications and rest rules, and the in-app chat keeping shift talk out of WhatsApp is early access at a price still to be decided. 11 2 10 10 1
The Operations Director
iPhone and Android apps show own and team rosters, take per-day availability and absence requests with balances, handle swaps, open-shift claiming and push notifications, and clock in by phone or shared kiosk with a personal code — in five interface languages. The team chat that would take shift talk out of WhatsApp is early access and priced t.b.d., and we found no public information on swaps being checked against qualifications or rest periods before approval, or on offline handling. 11 10 2 2
The Payroll Officer
An iPhone and Android app with own and team schedules, per-day availability, absence requests with balances, shift exchanges and open-shift invites, push on changes, clock-in and a personal kiosk code for the shared tablet clock, five interface languages, and a GDPR-flagged team chat in early access to pull shift talk out of WhatsApp. I found no public information on offline handling at the terminal or on swaps and open shifts being checked against qualifications and rest periods before approval, so the phone is a window onto the plan rather than a rule-enforcing one. 11 10 10 1 2
The Works Council Advocate
The app covers what the shop floor needs — own and team roster, availability per day, swap requests, open-shift claiming, absence requests with balances, clock-in by phone or shared kiosk with a personal code, and push notices on changes — in five languages. I found no public information that swaps and open shifts are checked against qualifications or rest periods before approval, and the team chat that would move shift talk out of WhatsApp is still early access with no price. 11 2 10 10 2 1
The Frontline Employee
This is what I judge first, and the phone app genuinely delivers: my own and my team's schedule, availability entered day by day, swap requests I can accept or decline, open-shift invites, clock-in or a personal kiosk code on a shared tablet, a weekly hours view with wage and plus-minus balance, and push notifications when shifts change — in German, English, Dutch, Spanish or French. The team chat that would get shift talk out of WhatsApp exists only as an early-access add-on with no price yet, swaps still wait for a manager to release them rather than resolving under the rules, and we found no public information on offline handling or accessibility. 11 10 1 2
The Skeptic
The shop floor gets the full loop: own and team schedule, per-day availability, swap requests, open-shift invites, clock-in with a personal kiosk code, push on shift changes, in five languages, with the tablet time clock from Basic and unlimited kiosks plus geofencing on Premium. We found no public information on swaps or open-shift claims being checked against qualifications or rest periods before approval, on offline handling for clock-in, or on employees seeing and exporting the data held about them; the team chat that would pull shift talk out of WhatsApp is marked EARLY ACCESS at "t.b.d.". 2 11 2 10 1
Works council & employee data
Show reasoningHide reasoning
How this is scored
Whether the product can be introduced under co-determination (BetrVG § 87) — role-based visibility, what is logged, which monitoring can be switched off, retention of availability, absence and location data — and whether the vendor supplies what a works agreement needs.
0 — No access control: the vendor's pages show every user seeing all employee data, or tracking of individuals that cannot be switched off.
3 — Admin, manager and employee roles with different rights, and a privacy policy that covers employee data.
5 — Configurable roles and permissions limiting who sees whose data, a data processing agreement offered, and either location tracking stated as optional or a retention or deletion rule for employee data.
8 — Fine-grained visibility (absence reasons hidden from colleagues and line managers where not needed), GPS and similar tracking off by default, an audit log of who viewed and changed an individual's data, configurable deletion periods, and documentation the vendor offers for works-council approval under BetrVG § 87.
10 — Data minimisation is designed in and evidenced: a model works agreement or feature-by-feature data inventory published, no performance or behaviour scoring of individuals, monitoring functions individually deactivatable, and deletion executed automatically per configured period.
The Shift Manager
Four editable permission groups with per-department permissions — employees see only their own team's schedule and data, planners see timesheets but not salaries — and a published privacy policy, deletion rules after subscription end, and a data processing agreement in the trust centre. I found no public information on an audit log of who viewed an individual's data, on geofencing being off by default, or on documentation for works-council approval; the vendor does state its own administrators have unrestricted access to all customer data without permission. 3 5 12 13
The Operations Director
Four default permission groups plus custom ones, permissions scoped per department, employees limited to their own team and data, a planner role without salary visibility and an offered data processing agreement give a real basis for co-determination talks; the captured pages give different figures for post-termination retention (deletion from all systems after 30 days versus storage for up to 90 days). We found no public information on an audit log of views and changes, whether geofencing is off by default, configurable deletion periods, or documentation for works-council approval. 3 5 12 13
The Payroll Officer
Four default permission groups that can be renamed and extended, employees seeing only their own team and own data, planners blocked from viewing salaries, self-approval preventable by department, a data processing agreement in the Trust Center, and fixed deletion rules with retention up to 90 days after termination and deletion 30 days after the subscription ends. For a works-council conversation I found no public information on an audit log of who viewed or changed an individual's data, on geofencing being off by default, on configurable deletion periods, or on vendor documentation prepared for approval under BetrVG § 87; the privacy policy also names unrestricted administrator access for the vendor's own staff without a permission step. 12 13 5 3
The Works Council Advocate
Four default permission groups, adjustable per department, keep employees to their own team's schedule and own data and keep salaries away from planners, a data processing agreement is offered, and deletion happens 30 days after the subscription ends with a 90-day retention cap — that much supports a works agreement conversation. But I found no audit log of who viewed or changed a person's data, no configurable deletion periods, nothing stating geofencing is off by default, and no documentation aimed at works-council approval; and the privacy policy states Shiftbase staff in an administrator role have unrestricted access to all customer and personal data without permission, which no works agreement of mine would pass unexamined. 3 5 12 13 2
The Frontline Employee
Permissions are genuinely configurable: four default groups plus custom ones, employees see only their own team's schedule and their own data, planners cannot view salaries, permissions can be set per department, and there is a documented way to stop someone approving their own entries. A data processing agreement is offered and deletion is stated concretely (30 days after subscription end, up to 90 days for technical purposes), but we found no public information on an audit log of who viewed or changed an individual's data, whether geofencing is off by default, or documentation for works-council approval. 12 13 3 5
The Skeptic
Four default permission groups, editable and extendable, scoping per department, planners barred from viewing salaries, employees limited to their own team's schedule, and a setting to prevent self-approval make a genuinely granular model, alongside a listed data processing agreement and encryption at rest. For the works-council conversation the pages are thin: we found no public information on an audit log of who viewed an individual's data, on geofencing being off by default, or on vendor documentation supporting a works agreement under co-determination. Deletion runs on fixed vendor terms — 30 days after the subscription ends, up to 90 days retention — rather than configurable periods. 3 5 12 13
Payroll handoff & integrations
Show reasoningHide reasoning
How this is scored
How planned and worked hours, surcharges and absences reach payroll — DATEV, Lohn und Gehalt, the tax adviser — and how the roster connects to the POS, HR and time systems a shift business already runs.
0 — No payroll path: the product offers no export of hours and no integration.
3 — An export of worked hours and absences (CSV or Excel) intended for payroll.
5 — A named payroll integration or payroll export (DATEV Lohn und Gehalt or LODAS, or another named payroll system) covering hours and absences, plus several named HR, POS or accounting integrations.
8 — Vendor-maintained payroll integrations with a lock step before transmission, wage types mapped per surcharge, POS integrations feeding forecasting, an HR master-data sync, and a documented API.
10 — Payroll is designed for, not exported to: several named payroll systems maintained, retro corrections after the close handled, the tax adviser given scoped access, and a versioned public API with webhooks and a deprecation policy.
The Shift Manager
Approved hours reach payroll through a payroll report in Excel or CSV and a DATEV-compatible export mapping hour components, surcharges, cost centres and absence types per contract type, plus a direct API link to Personio, POS revenue feeding the plan, and public API documentation. The DATEV path delivers a CSV by email that the user imports, leave balances are not processed by that integration, and I found no public information on retro corrections after a closed period. 1 15 14 1 2
The Operations Director
Approved hours export to a payroll report in Excel or CSV with separate columns per surcharge and absence type, and the DATEV integration maps hour types, surcharges and absence types per contract type — but the file travels by email and the user imports it into DATEV payroll themselves, and leave balances are not processed. Personio connects by API, POS revenue feeds the plan, and API documentation is public, with API access sold through the App Center+ add-on or open on Enterprise. 15 14 1 2
The Payroll Officer
The preparation for Lohn is real: approved hours go to payroll, the payroll report splits surcharge columns per percentage with absence types and custom fields, and the DATEV setup maps hour types, surcharges and absence types per contract type alongside cost centres and employees, with a DATEV report, Personio over the API, a documented API and POS revenue feeding the plan. But the DATEV handoff itself is a CSV file sent by e-mail that the user imports into DATEV payroll software, leave balances do not flow in either direction, and I found no public information on retro corrections after the month has closed or on scoped access for the tax adviser — a wage-type mapping in an e-mailed spreadsheet is not a designed handoff. 14 15 1 1 1
The Works Council Advocate
Approved hours flow to payroll, hour components, surcharges, absence types, cost centres and employees are mapped for DATEV, Personio is connected by API, till revenue feeds the forecast, and API documentation is published. The DATEV delivery step itself sends a CSV by e-mail that the user imports into payroll, and leave balances are not carried over, so the handoff is well mapped but not fully maintained. 1 15 1 14 1 4
The Frontline Employee
Approved hours export DATEV-compatible with hour types, surcharges and absence reasons mapped per contract type (the help centre itself notes leave balances are not processed), hours go to Personio directly over the API, POS revenue feeds the schedule, and API documentation is public behind the App Center+ add-on. The DATEV handoff is described as a CSV sent by e-mail that you import into your DATEV payroll software yourself, which stops it short of a fully maintained payroll connector with retro corrections. 14 15 1 4 2
The Skeptic
The DATEV connection is a CSV delivered by email that the user imports into DATEV payroll themselves — hour components, surcharges and cost centres mapped, leave balances expressly not processed — an export rather than a maintained pipe, sitting behind App Center+ at 20 € / Monat, Pauschale, with Basic including three integrations. Personio is reached directly via the API, POS revenue feeds back into the plan, API documentation is public, and hours approval is the release step before export. We found no public information on retro corrections after the close, scoped tax-adviser access, webhooks or a deprecation policy. 15 2 14 4 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the employee data lives, who the contracting entity is, who the subprocessors are, and whether that is documented rather than assumed. Independently sourced by the sovereignty pipeline; weighted seriously here, because a scheduling tool holds availability, absence and often location data about employees who had no say in the vendor.
0 — Vendor, contracting entity and hosting of employee data all shown to be outside the EU, with no transfer safeguard stated.
3 — A named contracting entity and a privacy policy or data processing agreement; EU hosting offered as an option or claimed without a provider, or the hosting location not stated.
5 — EU hosting stated as standard, together with an EU contracting entity or a published subprocessor list, and a data processing agreement offered.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing — push notification services included — named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a DPA that covers the employee data the app collects on personal devices.
The Shift Manager
The contracting entity is Shiftbase B.V. in Zoetermeer, and the trust centre names Google Ireland Limited as hosting with EU data locations, alongside a mostly-EU subprocessor cast including Shiftbase GmbH in Berlin and GetStream in Amsterdam. The current subprocessor list sits behind a password, the privacy policy references DifferentLab without naming its seat, and I found no legal basis stated for the US-incorporated subprocessors such as Customer.io and Mixpanel. 3 5 5 4
The Operations Director
The contracting entity is the Dutch Shiftbase B.V. with its KvK registration, and the trust page names Google Ireland for hosting and infrastructure with EU data locations alongside subprocessors such as GetStream, Hotjar, Mixpanel, Customer.io and Shiftbase GmbH. The full subprocessor list is retrievable only with a password, and we found no public information on the legal basis for the US-headquartered subprocessors' processing or a named data-centre provider. 3 5 5 4
The Payroll Officer
The contracting entity is Shiftbase B.V. in Zoetermeer with a KvK number, the Trust Center lists a data processing agreement, and the subprocessor list names Google Ireland for hosting and infrastructure with EU data locations, alongside GetStream, Hotjar, Mixpanel and Customer.io all shown with EU data locations and a Berlin Shiftbase GmbH for DACH support. Data residency is not confirmed on the vendor's own pages as captured, the privacy policy gates the subprocessor list behind a password, the privacy policy references DifferentLab without naming its seat, and I found no legal basis stated for the processors headquartered in the United States. 4 5 5 3
The Works Council Advocate
The contracting entity is Shiftbase B.V. in Zoetermeer with a Dutch commercial register number, and the trust page names Google Ireland as hosting and infrastructure in the EU alongside a mostly EU-located subprocessor list, with a data processing agreement listed in the trust centre. The subprocessor list is only retrievable behind a password, the privacy policy references a "DifferentLab" without naming its seat, and standard EU hosting is not stated on the captured legal pages — for availability, absence and geofencing data I would want all of that in writing before signing. 3 5 5 4 2
The Frontline Employee
The contracting entity is Shiftbase B.V. in Zoetermeer with a KvK number, and the trust page names Google Ireland Limited in Dublin for hosting and infrastructure with EU data locations, alongside Shiftbase GmbH in Berlin and GetStream in Amsterdam. Two named subprocessors, Customer.io and Mixpanel, are US companies shown with EU data locations, and the current full subprocessor list sits behind a password rather than published openly; the main site's pages we read state no general hosting commitment of their own. 4 5 3 5
The Skeptic
The contracting entity is Shiftbase B.V. in Zoetermeer with a Berlin GmbH serving the DACH market, and the trust center names its processors — Google Ireland Limited for hosting and infrastructure with EU as data location, GetStream in Amsterdam, Mixpanel and Customer.io listed with EU data locations — alongside a listed data processing agreement. What holds it back: the privacy policy's own current subprocessor list is retrievable only with a password, the entries give data locations but no legal bases, and we found no public information on push-notification processing or where those services run. 3 5 5 4
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual invoice for their headcount and locations — including the time clock, payroll export, forecasting and other modules sold as add-ons — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public per-employee "from" price, a free tier or one priced tier, while the other tiers or what they include are not stated.
5 — Per-employee or per-location prices public for each tier with the billing period stated; add-on modules (time clock, payroll export, forecasting, terminal hardware) may still be unpriced.
8 — Every tier and add-on priced publicly with the per-employee maths, how inactive or seasonal staff are counted, minimum term and VAT treatment stated; only genuinely custom work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given headcount, location count and module selection, including hardware, onboarding and renewal terms.
The Shift Manager
Free, Basic at 30 €/month with 6 included and 4 € per extra person, Premium at 75 €/month with 12 included and 5,25 € per extra, plus priced add-ons (App Center+ 20 €/month flat, HR Pro 1 €/month/employee, Compliance+ 0,50 €/month/employee) and priced onboarding packages — most of an annual invoice is computable. Enterprise is Auf Anfrage, the chat add-on is t.b.d., VAT treatment and minimum term are not stated, and the captured pages give different figures for the onboarding packages (Boost 150 € versus 175 €). 2 2 2 2
The Operations Director
Free at 0 €, Basic at 30 € per month with 6 employees included and 4 € per further person, Premium at 75 € per month with 12 included and 5,25 € per further person, a 10% annual discount, and priced add-ons (App Center+ at 20 € per month flat, HR Pro at 1 € per month per employee with a 50% introductory discount, Compliance+ at 0,50 € per month per employee marked coming soon) make the annual invoice computable for three of the four tiers. Enterprise is on request, Chat is t.b.d., we found no public information on VAT treatment, minimum term or how seasonal staff are counted, and the captured pages give different figures for the onboarding packages (Boost 150 € versus 175 €, Plus 325 € versus 350 €, Expert 575 € versus 600 €). 2 2 2
The Payroll Officer
Public maths for every self-service tier: Basic at 30 € / Monat including 6 employees with 4 €/Monat pro weitere Person, Premium at 75 € / Monat with 12 included and 5,25 €/Monat each, a free tier to 15 employees, monthly billing with Jährlich -10%, and add-ons priced at 20 € / Monat, Pauschale for App Center+, 1 € / Monat / Mitarbeiter for HR Pro and 0,50 € / Monat / Mitarbeiter for the coming Compliance+, plus onboarding packages from 0 € upwards. Enterprise is Auf Anfrage, Chat is t.b.d., the captured pages give different figures for the onboarding packages, and I found no public information on VAT treatment, minimum term, or how inactive or seasonal staff are counted. 2 2 2 2
The Works Council Advocate
Free, Basic and Premium are public with per-employee maths — "30 € / Monat" including 6 people and "4 €/Monat pro weitere Person", "75 € / Monat" including 12 and "5,25 €/Monat pro weitere Person" — plus a stated 10% annual discount, and most add-ons carry numbers: App Center+ at "20 € / Monat, Pauschale", Compliance+ at "0,50 € / Monat / Mitarbeiter", HR Pro at "1 € / Monat / Mitarbeiter". Enterprise is "Auf Anfrage", the chat add-on is "t.b.d.", VAT treatment and minimum term are not stated, and the captured pages give different figures for the onboarding packages — "175 € / einmalig" versus "150 € / einmalig" for Boost, "600 € / einmalig" versus "575 € / einmalig" for Expert. 2 2 2 2
The Frontline Employee
Three of four tiers are fully priced with per-employee maths and billing period: Free at '0 €' up to 15 people, Basic at '30 € / Monat' with 6 included and '4 €/Monat pro weitere Person', Premium at '75 € / Monat' with 12 included and '5,25 €/Monat pro weitere Person', plus '-10%' billed yearly, and the add-ons carry numbers too — App Center+ at '20 € / Monat, Pauschale', Compliance+ at '0,50 € / Monat / Mitarbeiter', HR Pro at '1 € / Monat / Mitarbeiter'. Enterprise is 'Auf Anfrage' and the chat add-on 't.b.d.', the captured pages give different figures for the onboarding packages (150/325/575 € versus 175/350/600 €), and we found no public information on VAT treatment, minimum term or how inactive or seasonal staff are counted. 2 2 2 2
The Skeptic
Three of four tiers are computable from public pages — Free at 0 € up to 15 people, Basic at 30 € / Monat with 6 included and 4 €/Monat per further person, Premium at 75 € / Monat with 12 included and 5,25 €/Monat per further person, yearly billing −10 % — and most add-ons carry numbers (App Center+ 20 € / Monat, HR Pro 1 € / Monat / Mitarbeiter, Compliance+ 0,50 € / Monat / Mitarbeiter), with the time clock inside the plans rather than an extra. Against that: Enterprise is "Auf Anfrage", the chat add-on is "t.b.d.", the compliance add-on is marked coming soon, and the captured pages give different figures for the onboarding packages (150/325/575 € in one capture, 175/350/600 € in another). We found no public information on how seasonal or inactive staff are counted, on VAT treatment, or on a minimum term. 2 2 2 2
European sovereignty — proven facts
1 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in NL
unverified
Why unverified?The privacy policy also references 'DifferentLab' without naming its seat or any group relationship, but every legal page names Shiftbase B.V. as the sole contracting entity. |
2/2 pts | 4 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
| Transfer impact assessment |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | uncited Report an error |
Questions about Shiftbase
Is Shiftbase European?
Yes. whats-best.ai classifies Shiftbase as EU-Made. Its vendor, Shiftbase B.V., is incorporated in the Netherlands, per the vendor’s page captured 16 Nov 2026.
Where does Shiftbase store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Shiftbase have a free plan?
Yes. Shiftbase has a free plan, per the vendor’s page captured 22 Sep 2026.
What are the best alternatives to Shiftbase?
As of 18 Nov 2026, the panel rates Ordio (3/5), gastromatic (3/5) and tamigo (3/5) highest among the other 32 Employee Scheduling products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Ordio (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Shiftbase alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement, Transfer impact assessment, Hosting location. Not confirmed on the vendor’s own pages as captured.
- Weak sourcing — Legal entity. The privacy policy also references 'DifferentLab' without naming its seat or any group relationship, but every legal page names Shiftbase B.V. as the sole contracting entity.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 86 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 35 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 15 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 14 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 14 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (16)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.shiftbase.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 2 Pricing page www.shiftbase.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 3 Privacy policy www.shiftbase.com Checked 16 Nov 2026 Details →
- 4 Legal notice www.shiftbase.com Checked 16 Nov 2026 +3 earlier captures: 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 5 Security / trust page trust.shiftbase.com Checked 16 Nov 2026 +1 earlier capture: 30 Sep 2026 Details →
- 6 Roster building & demand planning — found from sitemap help.shiftbase.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 7 Roster building & demand planning — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 8 Working-time law & collective agreements — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 9 Working-time law & collective agreements — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 10 Mobile self-service for deskless staff — found from sitemap www.shiftbase.com Checked 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 1 Oct 2026 Details →
- 11 Mobile self-service for deskless staff — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 12 Works council & employee data — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 13 Works council & employee data — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 14 Payroll handoff & integrations — found from sitemap help.shiftbase.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 15 Payroll handoff & integrations — found from sitemap help.shiftbase.com Checked 16 Nov 2026 Details →
- 16 Structured-data backfill: markup only, no text or screenshot www.shiftbase.com Checked 8 Nov 2026 Details →