Most teams running Odoo hit the same wall with the standard hr.attendance model: a check-in is just a timestamp with an optional kiosk PIN, and nothing about it proves where the employee was or who actually pressed the button. Field crews clock in from home, one worker punches for another, and remote or multi-site staff have no honest audit trail. Odoo core gives you attendance records and worked-hours computation, but it has no concept of a geofence, no biometric verification, and no hardened mobile endpoint for a workforce that lives on phones rather than at a shared kiosk. That gap is where payroll disputes, buddy-punching, and unreliable overtime numbers come from.

This is a build-to-order module that ECOSIRE designs, writes, and installs on your database — not an off-the-shelf download. We extend hr.attendance and add supporting models (an attendance-location model carrying fields.Float latitude/longitude and a configurable radius) so every check-in stores a captured GPS coordinate, a verification method, and a confidence result. A @api.depends-driven compute field flags whether a punch fell inside an allowed geofence using a haversine distance calculation, and a second layer requires the employee to pass a PIN plus a face-verification step before the record is accepted. Face templates and location data are governed by ir.model.access.csv plus record rules so a team lead sees only their own crew's rows, and every verification event is written to an audit log you can surface in a QWeb report.

On the technical side we ship real Odoo, not a bolt-on. Views are authored in XML with OWL components for the capture widget; an automated action (or ir.cron) can reconcile out-of-geofence punches or notify a manager; and configuration lives in res.config.settings so radius, tolerance, and whether face verification is mandatory-or-advisory are all admin-controlled without touching code. The mobile-friendly layer is a thin, authenticated controller exposed over the JSON-RPC / XML-RPC API surface so your own app, a PWA, or a lightweight React Native shell can submit a check-in with coordinates and a face frame and receive a structured pass/fail. The build targets your exact Odoo series — 17.0, 18.0, or 19.0 — and we note Community vs Enterprise differences up front (for example, how it sits alongside Enterprise's presence/attendance kiosk features versus a Community-only stack).

Delivery is straightforward and made-to-order. We start with a short scoping call to pin down sites, geofence rules, verification strictness, and how the mobile side integrates, then produce a fixed-scope quote and a signed spec. We build on a staging copy of your database, run UAT with you, and hand over the installable source plus a git repository, technical docs, and a user-training session before go-live — with a rollback plan in case anything needs to unwind. Pricing starts from $499 (indicative, single-company base scope); additional geofenced sites, multi-company rollout, deeper mobile-app integration, and payroll/localization hooks increase the quoted scope.