- 首页
- Apps
- SaaS Tools
- Face Recognition Attendance with GPS Geofencing
示意预览Contactless AI face check-in with GPS multi-geofencing so staff only clock in inside authorized locations.
Built for Odoo 17/18/19.
什么是 Face Recognition Attendance with GPS Geofencing?
Contactless AI face check-in with GPS multi-geofencing so staff only clock in inside authorized locations. Built for Odoo 17/18/19. Built to order by ECOSIRE for Odoo 17, 18, 19 — indicative price from $999.00 USD; request a quote for a scoped proposal.
核心功能
按需定制,全程代劳
无需自行搭建——由 ECOSIRE 构建、安装并提供支持的可用应用。
- 1
您下单
以一次性构建价格开始。我们在启动时与您共同确定范围。
- 2
我们构建与安装
ECOSIRE 在您的 Odoo 上构建、配置并安装。
- 3
上线 + 支持
约一个工作周内上线,并包含两周上线支持。我们交付的代码中的缺陷免费修复。
技术规格
- Odoo 兼容性
- Odoo 17, Odoo 18, Odoo 19
- 版本
- 企业版和社区版
- 许可证
- 许可证需要确认
- Python 要求
- Python 3.10+
- 数据库
- PostgreSQL 12+
关于此产品
Buddy punching, edited timesheets, and staff clocking in from the car park are attendance frauds that quietly inflate payroll every month. This build-to-order module replaces the honor system with proof: an AI face match plus a GPS coordinate captured on every single punch, so a check-in only counts when the right person is physically inside an authorized location.
ECOSIRE designs, builds, installs, and supports this module for your Odoo 17, 18, or 19 database (Community or Enterprise). It is NOT an instant download from apps.odoo.com — it is a net-new module we engineer to your locations, shift rules, and privacy requirements, then hand over as clean, documented source you own. Typical delivery is one working week from confirmed scope and access.
Under the hood we extend the standard hr.attendance model rather than replacing it, so every punch flows straight into Odoo's native Attendances, Timesheets, and Payroll reporting with no parallel system to reconcile. New fields (face_match_score, gps_latitude, gps_longitude, geofence_id, selfie_image, ip_address) are added via a proper models.Model extension, with a computed is_within_geofence flag driven by @api.depends on the captured coordinates and the assigned geofence radius. A new hr.geofence model stores each authorized location as a center point plus radius (or polygon), and record rules scope employees to only the geofences their department or contract allows.
The face-recognition engine runs against enrolled reference photos and returns a confidence score on each attempt; you set the acceptance threshold, and low-confidence or off-site attempts are flagged (or blocked) and routed to a manager for review via an automated action. Employees check in from a mobile browser/PWA on their phone (GPS + selfie from the device) or from a fixed kiosk tablet at the entrance. Every record stores the selfie, the score, the coordinates, and the request IP address for a complete, tamper-evident audit trail.
Managers get a geo-map dashboard of live punches, exception lists for out-of-fence attempts, and QWeb PDF/Excel attendance reports filtered by geofence, employee, or date. Because the module speaks Odoo's own XML-RPC/JSON-RPC API, kiosks, gate hardware, or an external HR app can post attendance programmatically. We build it around your consent and data-retention rules so biometric handling is deliberate, not accidental.
You receive the full module source, an install on your server (staging then production), configuration of your real geofences and thresholds, admin training, and a support window. This is proper Odoo engineering — security CSV, record rules, tested views, upgrade-safe manifest — not a black box.
你得到什么
- Complete, commented module source code (models, views, security CSV, record rules, QWeb reports) that you fully own — delivered as a versioned repository
- Installation on your server: deployment to staging first, validation, then production cutover, with a manifest kept upgrade-safe for your Odoo version (17, 18, or 19)
- Configuration of your real authorized locations — geofences with correct center coordinates and radii, plus per-department/contract assignment
- Face-enrollment setup and threshold tuning against your acceptance-accuracy and false-reject tolerance
- Admin & manager training session covering enrollment, exception handling, the geo dashboard, and running attendance reports
- Documentation pack: admin guide, employee check-in instructions, data-flow/architecture notes, and a biometric data-retention/consent reference
- Post-launch support window (bug fixes and configuration adjustments) for the agreed period after go-live
- Source-code handover so your team or any Odoo partner can maintain and extend the module independently
这是给谁的
Field-services & construction operators
Companies with crews spread across job sites who need to know a technician actually reached the site before the clock starts. Multi-geofencing ties each punch to the correct location and kills 'clocked in from home' timesheet padding.
Remote & hybrid workforce HR managers
HR teams managing distributed or work-from-anywhere staff who want verifiable, contactless attendance without deploying biometric hardware everywhere. Face match plus GPS and selfie logging gives audit-grade proof from any smartphone.
Multi-branch retail, security & facilities firms
Operations running many outlets, guard posts, or sites who need one shared kiosk per location and central visibility. Record rules keep each branch manager scoped to their own geofences while head office sees the full geo dashboard.
Face Recognition Attendance with GPS Geofencing 如何比较
| 标准 | 伊科西尔 | 定制建造 | 竞争对手 | Odoo 原生 |
|---|---|---|---|---|
| Contactless AI face recognition on each punch | Built in with configurable confidence threshold | Possible but you build and maintain the vision pipeline yourself | Varies; many attendance apps are PIN/badge only | 不包括在内 |
| Multi-geofence GPS enforcement (unlimited authorized locations) | Dedicated hr.geofence model, per-employee assignment | Hand-rolled, no reuse | 部分支持 | 不包括在内 |
| Selfie + IP + GPS audit trail on every attendance record | Stored on native hr.attendance for tamper-evident review | 部分支持 | 部分支持 | 不包括在内 |
| Flows into native Timesheets & Payroll (no parallel system) | Extends hr.attendance, zero reconciliation | Depends on how you build it | 部分支持 | 包含 |
| Odoo 17 / 18 / 19, Community & Enterprise | Targeted and tested for your exact version | Your responsibility to port across versions | Depends on vendor's version support | 包含 |
| Record-rule scoping (managers see only their geofences) | ir.model.access.csv + record rules included | Must be designed and tested by you | 部分支持 | 部分支持 |
| Full source ownership + install + training + support window | Delivered and handed over by ECOSIRE | You own it but carry all the effort and risk | Usually licensed; source often obfuscated | 不包括在内 |
| Off-site / low-confidence block or manager-escalation workflow | Automated actions configured to your policy | Build the escalation logic yourself | 不包括在内 | 不包括在内 |
关于Face Recognition Attendance with GPS Geofencing的常见问题
How long does delivery take, and is this an instant download?
This is not an instant apps.odoo.com download. It is a net-new module ECOSIRE builds, installs, and supports specifically for your database. Typical delivery is one working week from kickoff, depending on the number of geofences, whether you need kiosk plus mobile, and your privacy/consent requirements. You get a staging deployment to review before we cut over to production.
What do support and updates cover after go-live?
Every build includes a post-launch support window for bug fixes and configuration adjustments (geofence tweaks, threshold tuning) after go-live. Because you receive the full source and it extends native hr.attendance, the module is upgrade-safe for your Odoo version. When you move between Odoo 17, 18, or 19 we can quote a compatibility pass, and extended support/enhancement retainers are available.
Does it work on Odoo Community or only Enterprise?
Both. The module targets Odoo 17, 18, and 19 on Community and Enterprise. It extends the standard hr.attendance model, adds a dedicated hr.geofence model, and wires into native Attendances, Timesheets, and Payroll — so it fits whichever edition you run. We confirm your exact version and edition during scoping.
How does it actually stop buddy punching and off-site clock-ins?
Each punch requires an AI face match above your configured confidence threshold AND captures GPS coordinates, a selfie, and the request IP. A computed is_within_geofence flag (via @api.depends) checks the coordinates against the assigned geofence radius. You choose whether off-site or low-confidence attempts are hard-blocked or logged and escalated to a manager through an automated action — so a valid punch means the right person was physically inside an authorized location.
Where is the biometric and location data stored, and is it private?
All data lives inside your own Odoo database and filestore — nothing is sent to a third-party ECOSIRE service. Reference photos, selfies, scores, coordinates, and IPs are stored on standard Odoo records protected by ir.model.access.csv permissions and record rules, so employees see only their own punches. We build in a consent/enrollment step and configurable data-retention/auto-purge so you can align with your local privacy law and internal policy.
Can it integrate with our kiosk hardware or an external app?
Yes. Staff can check in from a mobile browser/PWA or a fixed kiosk tablet, and the module exposes Odoo's XML-RPC/JSON-RPC API so gate hardware, an external kiosk client, or a third-party HR system can post attendance programmatically. We scope any specific hardware or endpoint integration during requirements gathering.
相关模块
Face Recognition Attendance with GPS Geofencing
Contactless AI face check-in with GPS multi-geofencing so staff only clock in inside authorized locations. Built for Odoo 17/18/19.
- AI facial-recognition check-in that returns a confidence score on every attempt, with a configurable acceptance threshold (default 99%+ match) before a punch is accepted
- Multi-geofence enforcement: define unlimited authorized locations as center-point + radius (or polygon) in a dedicated hr.geofence model, each assignable per employee, department, or contract
- GPS latitude/longitude captured on every punch and stored on the attendance record, with a computed @api.depends is_within_geofence flag that marks off-site attempts
- Hard block or soft-flag modes — out-of-fence or low-confidence punches can be rejected outright or logged and escalated for manager approval



