Custom Eitje integration
Eitje is a Dutch scheduling app for hospitality, covering rosters, time tracking, clocking in and out, leave and team communication. Eitje has integrations with payroll systems and point-of-sale systems, plus an API. Appfront builds the integration with the systems that are not on that list, such as your own reporting, your HR system or a group-wide cost analysis, so hours and labour costs are not transferred by hand.
What is an Eitje integration?
Eitje is a staff scheduling app for hospitality. Managers create the rota, employees see their shifts on their phones, clock in and out, and request leave. Hours are approved, contracts are tracked, and Eitje shows what staff cost. There are integrations with payroll systems such as Nmbrs and with point-of-sale systems, so revenue sits alongside the schedule.
Whatever is not covered by the standard integrations is often done by hand. A hospitality group wants labour costs and revenue for all its locations side by side, and exports them venue by venue. The head office HR system knows different contracts than Eitje. And a custom report or a budget per location is filled with figures that someone first has to gather.
We build custom because businesses differ: one venue or a group, which payroll system and which point of sale, and which figures need to go where. The integration runs via the API that Eitje offers. We look at what data it contains and under what conditions in the first step, together with you and with Eitje.
Hours in one place
Approved hours in your own systems.
Labour costs alongside revenue
Per location and part of the day.
Via the API
Aligned with Eitje.
How we build your Eitje integration
We start with your business: which systems you use alongside Eitje, which data is currently handled by hand, who needs to see what, and whether your system might already be among the standard integrations. Then we look together with Eitje at what the API offers for your situation. We often start with approved hours and labour costs per location flowing into reporting, because that immediately saves manual work. Employees and contracts from a single source, plus leave and sickness, follow once the first integration is running well. After that, we maintain the integration when Eitje or your own systems change, and after every change we check that hours and costs still match the payroll system.
Systems, data and who needs to see what.
What Eitje offers for your situation.
Hours, costs and employees.
Go-live, monitoring, and maintenance when things change.
What an Eitje integration actually does
The components below come back in almost every Eitje integration. Which ones you need depends on your business and systems.
Hours
Approved, per shift.
Rota
Shifts per location.
Labour costs
Alongside revenue.
Employees
From a single source.
Leave and sickness
Included where needed.
Log
Every message recorded.
Who we build an Eitje integration for
The integration is intended for hospitality businesses that use Eitje alongside systems that are not covered as standard. The more locations and employees, the more time it saves.
Hospitality groups
Multiple venues. Comparing costs is what counts.
Hotels and caterers
Multiple departments. A single overview is what counts.
Franchise chains
Many operators. Benchmarking is what counts.
Software suppliers
A product for hospitality.
Technology and integrations
This page is about integrations with Eitje. For the point of sale alongside the schedule, see our page on the MplusKASSA integration; for your own scheduling system, our page on staff scheduling software; and for your own hospitality app, our page on hospitality apps. You can read about our approach on building custom software.
Why Appfront for your Eitje integration?
Hours exported venue by venue, and labour costs that are only set against revenue after the month has ended, cost a hospitality group time and control. That is what we build on: hours in one place, labour costs alongside revenue, and an integration via the Eitje API.
No exports
Hours arrive automatically.
Managing costs
Alongside revenue.
Official route
Via the API.
Security and privacy for an Eitje integration
The integration processes employee data such as names, contracts, hours, leave and sometimes sickness. That is personal data, and sickness is sensitive. We only use the data that is needed, API credentials are stored encrypted, and every message is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about an Eitje integration
Questions hospitality owners ask before they get started.
Eitje is a Dutch app for workforce scheduling in hospitality. Managers create rosters, employees see their shifts and clock in and out, hours are approved, and leave and contracts are tracked. Eitje also shows what staff cost.
Yes, including with payroll providers such as Nmbrs and with point-of-sale systems. If your system is on that list and the integration does what you need, a custom build isn't necessary, and we'll tell you so. A custom integration is for systems and reports that aren't on the list.
Through the API that Eitje provides. In the first step, together with you and with Eitje, we look at which data is available, how access is arranged and under what conditions. Only then do we build, so you don't get stuck on a route that doesn't exist.
Yes. Approved hours and labour costs from Eitje are combined with revenue from your till, per location, per day and per part of the day. That shows you where staffing is too expensive for the level of trade, and where you could have put more people on.
Yes, if that is your source. The integration passes new employees and changed contracts on to Eitje, so nobody has to maintain them in two places. You decide which system is the master.
The integration reports it and records what went wrong. The message is retried or queued for review, so no hours are lost or arrive twice at the payroll provider.
For hospitality groups with multiple locations, for hotels and caterers with multiple departments, for franchise organisations that want to compare sites, and for software vendors that want to connect their product to Eitje. If you run a single venue and use the standard integrations, a custom integration is often not needed.
Want Eitje connected to your own systems?
Tell us which systems you use alongside Eitje and which data is currently transferred by hand. We'll show you which route is available and what the integration looks like.