Distributed teams, field staff, and multi-site operations break the assumption Odoo's core hr.attendance was built around: a kiosk or a badge reader at a fixed location. When employees check in from their phones on the road, at client sites, or from home, native attendance gives you a timestamp but no answer to the question that actually matters to payroll and compliance — was the person where they were supposed to be? Odoo core has no location capture on the check-in, no geofence validation, and no review-before-it-counts step. Managers end up cross-checking timesheets against messages and calendars by hand, and disputed hours turn into email threads instead of an auditable record.

Portal Attendance is a made-to-order Odoo application that ECOSIRE designs, builds, and installs for you. It extends hr.attendance with GPS capture on every check-in and check-out, validates each punch against the geofences you define (site radius, allowed zones, or per-employee assignment), and routes flagged or all records through an approval workflow before they are confirmed for reporting and payroll. Employees interact through a lightweight portal — a self-service page rendered with QWeb and OWL that works on a phone browser — so you don't need to hand out backend Odoo logins to hourly or field staff. Every action is captured on the record so the timeline is defensible.

Technically, we add location fields (latitude, longitude, accuracy, and a resolved address) to the attendance model and a related geofence model with computed distance checks via @api.depends, so an out-of-zone punch is flagged the moment it lands rather than during a month-end audit. State moves through draft → to approve → approved/refused on a Selection field, driven by server actions and, where you want it, base.automation automated actions (for example auto-approve punches inside the geofence, escalate the rest to the line manager). Access is locked down with ir.model.access.csv plus record rules so a portal user only ever sees their own attendance and a manager sees their team; QWeb reports give you exportable timesheets and exception summaries, and the whole surface is reachable over Odoo's XML-RPC/JSON-RPC API if you need to feed a payroll engine or BI tool. It ships for Odoo 17.0, 18.0, or 19.0, and we build against Community or Enterprise depending on what you run.

Because this is build-to-order, delivery follows a clear path: a short scoping call to pin down your geofence rules, approval hierarchy, portal fields, and target Odoo version and edition; a fixed written quotation; then development on a staging copy, UAT with your team, and go-live with a rollback plan. Typical delivery is 2-4 weeks from confirmed scope. Pricing starts from $249 (indicative, single-company base scope); multi-company rollout, deeper localization, payroll/timesheet integration, or migrating historical attendance data increases the quoted scope. You get a fixed price once the scoping call defines exactly what "done" means for you.