The time clock that speaks Odoo.
Employees hold their badge against the terminal and the attendance is in your Odoo straight away. No second system, no per-employee fee.
Set it up and forget it
A terminal on the wall should not occupy anyone. We judge every decision by how little work it creates. Four numbers say what that adds up to.
Ten minutes and two secondsto the first entry.
Mount it
5 minutesOn the wall, one network cable with PoE. Power and network in one. Wi-Fi works too.
Connect it
5 minutesThe device shows a QR code. Scan it, enter your Odoo access, wait for the connection test.
Clock in
2 secondsHold a badge against the device. The entry is in Odoo.
Why this device and not another
Odoo-native, including Odoo Online
Entries go directly into your Odoo. The only solution on the market that also works with Odoo Online. The usual module-plus-terminal setups fail there structurally.
Check compatibilityNo per-employee fees
Buy the device once. Whether ten or two hundred people clock in changes nothing about the price.
See pricingTime data stays with you
Your employees' attendance data never reaches our servers. That is how the architecture is built; there is no other path.
Privacy architectureWhat else you could do
Three routes lead to electronic recording. We show all three, including where our device loses.
| Tablet with Odoo kiosk | Classic terminal | Our terminal | |
|---|---|---|---|
| Books directly into Odoo | ja | nein | ja |
| Works with Odoo Online | ja | nein | ja |
| Per-employee fee | none | usually yes | none |
| Central management of several devices | nein | ja | ja |
| Offline buffer with true timestamps | nein | ja | ja |
| One cable for power and network | nein | usually yes | ja |
| No way out into other applications | nein | ja | ja |
| Access control | nein | ja | nein |
| Usable without Odoo | nein | ja | nein |
Classic terminal prices from public listings, July 2026.
Where the device hangs on the wall
Fitters arrive at the yard in the morning, drive out, come back in the evening. Times are noted on paper and typed up in the office.
Terminal at the yard gate. The paper goes away and the times land in Odoo immediately.
At shift change thirty people clock in within five minutes. The tablet currently on the wall freezes regularly.
Under two seconds per entry, even with a queue in front of it.
Night shifts outside office hours, three buildings, and a works council that looks closely at time recording.
One device per building, centrally configured. No camera, no biometrics, data stays in your own Odoo.
Your situation is not listed? We can go through it on a call.
A time clock, not a tinkering project
The usual improvisation is a tablet on the wall, a USB reader on an office PC, or a build around a single-board computer. That works until somebody closes the app, unplugs the power supply, or needs the tablet for something else.
Our terminal does exactly one thing. It sits in a wall bracket with cable routing, needs a single cable over PoE for power and network, and nobody gets from the clocking screen into another program.
It draws less power than a tablet kept permanently on charge.
We are building the device we needed ourselves
We come from Odoo integration work and implement Odoo for industrial customers. For clocking in at the wall we kept building it ourselves: Raspberry Pi, NFC reader, browser in kiosk mode. It works, but it is handwork every time and nobody pays for it.
At some point the question stops being how to pull it off at the next customer, and becomes why you cannot simply buy this.
You already have the module.We bring the clock to the wall.
If you run Odoo, Attendances is already in the house. What is missing is the device. Until now people improvise with tablets in kiosk mode, USB readers and homemade scripts. That is the gap we close.
Will it work with your Odoo?
Not every Odoo plan unlocks the interface we need. Three questions and you'll know, before you buy anything.