How Alpha Logistiek cut CAO admin from days to minutes
- ›
- Customers stories
- ›
- Alpha Logistiek
Industry:
Transportation-
Employees:
50+ Customer since:
2023
Established:
AmersfoortInterviewed:
Jordi de Koning, Co-owner
Anyone who plans drivers under the road-transport collective labour agreement, the CAO, knows how the month tends to end. The hours are logged, but turning them into correct pay is the hard part, and it has to be right. The CAO gives drivers real entitlements: a meal allowance after a long shift, extra for night and weekend hours, overtime that turns on each driver's contract hours rather than one fixed line. Get it wrong and it cuts both ways: a driver underpaid, or the business paying for overtime it never needed. Some of it stacks and some of it explicitly does not, and a single driver's day can run to a dozen rules or more. So the hours sit in one system, the sums get done by hand in a spreadsheet, and the one person who truly understands the agreement becomes the person you cannot run payroll without.
Jordi de Koning runs Alpha Logistiek in Amersfoort with his co-owner Dave Roemeling, moving medicines, vaccines, and
temperature-sensitive freight for healthcare clients across the country. Alpha runs its operation on Shiftbase, where Jordi plans his drivers, tracks their hours, and keeps the team's records in one place. By connecting CAO / API on top of that foundation, Jordi got the CAO applied to those hours automatically and correctly. The result: work that used to take a couple of days a week now takes a few minutes a month, drivers paid exactly what the CAO entitles them to, a running view of what the hours cost so overtime stops slipping through, and a pay calculation anyone can explain, line by line.
Image: (Frank @ CAO / API) & Jordi (Alpha co-founder)
The challenge: the CAO lived in a spreadsheet and one person's head
Jordi de Koning and Dave Roemeling started Alpha Logistiek in 2020 and built it into a specialist in medical and pharmaceutical logistics: conditioned vehicles, trained drivers, vaccines, and diagnostics moving on tight windows. Today more than 50 people work across the operation, most of them drivers, and all of them fall under the CAO Beroepsgoederenvervoer, the collective labour agreement for road transport.
The hours themselves were never the hard part. Alpha already had them clean and in one place in Shiftbase. Turning them into correct pay was the challenge. Every period, the team copied the hours into Excel and applied the transport CAO by hand, and that agreement is one of the harder ones to get right. One person spent about two days a week on it. Worse, all of that knowledge lived with a single colleague, so the stretch it had to run without them was the stretch the risk became obvious.
Looking back, Jordi puts it plainly:
"All those hours went into an Excel sheet, and one person spent about two days a week on it. When that knowledge wasn't available to us, we were stuck. That is not a position you want to be in."
Jordi de Koning, Co-owner, Alpha Logistiek
The solution: Shiftbase at the core, with CAO / API plugged in
The platform was already in place. Alpha runs its operation on Shiftbase, where it plans its drivers, tracks their hours, keeps its employee records, and pulls the reports it needs. Because the schedules, hours, and absences all live there, accurate and in one system, Alpha had a single, reliable source of truth to build on, and that foundation is what made the next step easy.
Jordi wanted the CAO rules to run themselves, without a bigger spreadsheet or another colleague holding them in their head. So Alpha became the launch customer for CAO / API and plugged it into Shiftbase. It pulls the hours, schedules, and absences from Shiftbase automatically over an API. Alpha subscribed to the transport CAO template, and CAO / API applies those rules to the worked hours in real time, turning the agreement into usable logic Jordi can tune to the way Alpha actually runs. It also surfaces what needs a human eye, flagging where overtime is building up so Jordi can catch avoidable labour cost before it lands on the payroll. Set-up took minutes, guided the whole way, with no big implementation project, nothing new for the drivers to learn, and nothing to copy over.
What sold him was simple: because everything already lived in Shiftbase, the connection was quick to switch on, the calculation came back in seconds, and every line could be traced to the rule behind it.
"I was sold straight away. Now I am not dependent on one person. The software does the work, and I can see exactly what it did."
Jordi de Koning, Co-owner, Alpha Logistiek
For CAO / API, Alpha is the kind of customer the tool was built for, and the timing matters.
"Collective labour agreements keep getting more complex, and from 2027 employers have to show people exactly how their pay is built up. Because Alpha's hours already lived in Shiftbase, switching us on took minutes, and every allowance we apply can be explained back to the rule."
Frank Müller, Operational Director / Program Manager, CAO / API
Results at a glance
The change shows up right across the month-end at Alpha:
|
Aspect |
Before |
Now (Shiftbase + CAO / API) |
|---|---|---|
|
Scheduling and hours in one place |
Hours tracked in Shiftbase, then copied into a spreadsheet for pay |
Drivers planned and hours captured once in Shiftbase, ready to use downstream (Shiftbase) |
|
Knowing who to plan |
No clear view of who still had hours to give |
Jordi sees each driver's hours, costs, and can plan sharper (Shiftbase) |
|
CAO processing time |
About two days a week, by hand in Excel |
A few minutes a month, straight from the Shiftbase hours (CAO / API) |
|
Getting pay right and explained |
Manual calculation, hard to check or explain |
The CAO applied automatically and in real time, every allowance correct and traceable to a rule (CAO / API) |
|
Overtime and labour cost |
Hard to see the cost, or which overtime was avoidable |
CAO / API shows the live cost of hours and flags building overtime, so Alpha curbs avoidable cost in real time (CAO / API) |
|
Key-person risk |
The CAO sat with one colleague |
The rules run in software, on data already in Shiftbase (Shiftbase + CAO / API) |
The impact: the CAO runs in software, not in one person's head
These days, month-end closing runs smoothly. The hours come out of Shiftbase, CAO / API applies the CAO in real time as they land, and the finished wage components are ready for the accountant, automated and explainable, every line traceable to a rule. Jordi can still look at any driver in Shiftbase and see who has hours left to give, so his planners know who to put on a route. And because the cost of those hours is visible as they happen, not weeks later once payroll has paid out, he stays ahead of the exceptions: he can watch overtime building and act on it, and keep a grip on labour cost while he can still change it. What used to take days is now a quick check, and when someone asks why an allowance came out the way it did, the answer sits right there against the rule.
"What used to take days now takes only a few minutes. And throughout the week, I can see per driver who still has hours left, which allows us to plan better as well."
Jordi de Koning, Co-owner, Alpha Logistiek
The bigger change is what Jordi no longer carries.
"The best part is that it no longer hangs on one person. The software is the colleague who is always there. I was really enthusiastic about it, and I still am."
Jordi de Koning, Co-owner, Alpha Logistiek
What's next, for Alpha Logistiek and for Shiftbase
With the calculations off his plate, Jordi is focused on growing Alpha and keeping its healthcare clients served on time. The timing helps him: from 2027, Dutch employers have to give hired and flexible workers a clear view of the rules behind their pay, and Alpha can already produce exactly that.
Shiftbase is built to grow with operators like Jordi, and not every specialist job belongs inside one platform. The App Center is where partners like CAO / API plug in, so a transport company can keep planning and tracking hours in Shiftbase and hand the most demanding part of the CAO to a tool built for it. Solve the hard part today, grow into the next stage tomorrow.
Frequently asked questions
-
Alpha already ran its planning and time tracking in Shiftbase, so the operation lived in one place. The hard part was applying the road-transport CAO to those hours, which ate about two days a week and lived with one colleague. CAO / API plugs straight into Shiftbase and applies the agreement on its own, so Alpha kept working in Shiftbase and handed off the part that was slowing it down.
-
Scheduling, time tracking, and employee records in Shiftbase, with reporting when they need it. That is the core the operation runs on. The CAO / API connection sits on top: the hours, schedules, and absences flow from Shiftbase to CAO / API, the CAO is applied in real time, and CAO / API hands the finished wage components to the accountant, into Loon.nl in Alpha's case and into many other payroll packages besides.
-
Work that used to take a couple of days a week now takes a few minutes a month. On top of that: drivers paid exactly what the CAO entitles them to, a clear view of which drivers still have hours so planning is sharper, the live cost of hours so overtime stops slipping through, every allowance traceable to a rule and in line with the CAO, and no more dependence on one person holding the whole agreement in their head.
-
Jordi was an early and enthusiastic adopter, and the day-to-day is calmer for it. The drivers carried on as before, since nothing about how they log hours changed, and the month-end work that used to loom is now a quick check.
-
Shift-based businesses that run under a complex collective labour agreement, where the hours are easy to record but turning them into correct pay is slow and specialist. It pays off most when you have a lot of employees, a lot of rules, or rules that change regularly. Road transport and logistics are an obvious fit, and so is any sector where allowances stack and someone is currently doing it all by hand in a spreadsheet.