Most teams that adopt biometric fingerprint or face terminals for time tracking hit the same wall: the devices happily record punches, but getting that data into Odoo is a manual export-import chore. Odoo's native hr_attendance module is built around kiosk check-in/out and manual entry — it has no listener for the "push" protocol that low-cost biometric terminals use to POST punch events to a server over HTTP. Without a bridge, someone downloads logs to a spreadsheet nightly, reconciles employee IDs by hand, and payroll inherits every typo. That is exactly where Odoo runs out of road: it can store attendance, but it cannot ingest a device push stream on its own.

We build a dedicated HTTP endpoint inside Odoo that speaks the terminal's push dialect. The controller (a subclass of http.Controller with an auth='none', CSRF-exempt route) accepts the device handshake, options exchange, and attendance-log POSTs, parses the raw punch records, and writes them through the ORM. A new biometric.device model (models.Model with fields for serial number, location, timezone, last-seen heartbeat, and a state selection) represents each registered terminal, and a biometric.punch staging model captures every raw event before it is resolved to an hr.employee through a device-user-ID map. Matched punches are paired into hr.attendance check-in/check-out records using configurable pairing logic (first-in/last-out per day, or strict alternation), while unmatched or duplicate events are quarantined for review instead of silently corrupting the timesheet.

Because this is a real module and not a script, it ships with the full Odoo surface: ir.model.access.csv plus record rules so HR sees only their company's devices, backend list/form/kanban views (XML for 17/18, OWL-compatible for 19) to register terminals and browse the raw punch log, a QWeb report for a daily attendance-exception sheet, and an ir.cron heartbeat monitor that flags any device that stops pushing. Everything the endpoint receives is also reachable over Odoo's own XML-RPC/JSON-RPC API, so downstream payroll or middleware can read the same records. We handle multi-company scoping, timezone normalization per device, and idempotent writes so a device that re-sends its buffer after a network outage never double-counts a shift.

Delivery is build-to-order. After a short scoping call we confirm your device push protocol variant, Odoo edition (Community or Enterprise) and version (17.0/18.0/19.0), employee-mapping rules, and multi-company layout, then build against a staging copy of your database, run UAT with your real terminals, and cut over with a rollback plan. Typical delivery is 2–4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); additional device protocol variants, multi-company/multi-timezone rollouts, payroll-system integration, and historical punch-data migration increase the quoted scope.