Skip to main content
Face Recognition Attendance (Kiosk + Mobile) — AI face-recognition clock-in via tablet kiosk or mobile selfie that writes ver — 1/1Illustrative preview

AI face-recognition clock-in via tablet kiosk or mobile selfie that writes verified attendance straight into

ERPNext HR. A ready-to-install Frappe app that

ECOSIRE installs, commissions, and supports for your team.

What is Face Recognition Attendance (Kiosk + Mobile)?

AI face-recognition clock-in via tablet kiosk or mobile selfie that writes verified attendance straight into ERPNext HR. A ready-to-install Frappe app that ECOSIRE installs, commissions, and supports for your team. One-time license from $499.00 USD for ERPNext 16 — includes 12 months of updates and support.

Key Features

Custom `Face Enrollment` DocType storing per-employee face embeddings (templates, not plaintext photos) with versioned re-enrollment history
Tablet kiosk mode as an installable PWA and a mobile selfie mode, both calling the same `@frappe.whitelist()` capture endpoint
Liveness detection / anti-spoofing pass that rejects printed photos, screen replays, and static images before matching
Configurable 95–100% match-confidence threshold with a manual-review queue for borderline scores instead of silent false accepts
On a confirmed match, creates the native `Employee Checkin` so Shift Type, auto-attendance, and payroll flow downstream unchanged
`Kiosk Device` registry with per-device tokens, site binding, and scheduler-event revocation of stale or lost devices
Per-site enrollment and template management so a multi-branch retailer isolates each location's roster
Offline capture with a local queue that syncs through an idempotent whitelisted endpoint once the network returns
`hooks.py` `doc_events` on `Employee` for enrollment reminders and `scheduler_events` for offline reconciliation and cleanup
Dedicated Role Profiles (Kiosk Operator, HR Manager) so operator devices create check-ins but cannot read salary or HR data
Optional geo-fencing and shift-window enforcement via Server Scripts, rejecting punches outside the allowed radius or shift
Full Frappe REST API surface plus a `Face Checkin Log` audit DocType capturing device, score, liveness result, and timestamp
Client Scripts driving camera permission handling, capture UX, and inline validation on both kiosk and selfie screens
Packaged and tested for Frappe/ERPNext v15 and v16 with a clean `bench install-app` migration path

Installation overview

  1. 1

    Download from ECOSIRE

    Buy the license on ecosire.com and download the Face Recognition Attendance (Kiosk + Mobile) app ZIP from your account dashboard.

  2. 2

    Add the app to your bench

    Extract the ZIP into your bench's apps folder, or run `bench get-app` with the path to the extracted app.

  3. 3

    Install on your site

    Run `bench --site SITE_NAME install-app APP_NAME` followed by `bench migrate` to install Face Recognition Attendance (Kiosk + Mobile) and apply its schema.

  4. 4

    Activate your license

    Open the ECOSIRE License settings on your site and activate your license key. Requires the free ecosire_connect and ecosire_license_client apps.

Technical Specifications

ERPNext Compatibility
ERPNext 16
License
Licence confirmation required
Python Requirement
Python 3.10+
Database
MariaDB 10.6+

About this Product

Add consent-based face enrollment, mobile web check-in and paired kiosk attendance to ERPNext v16. The app creates native Employee Checkin records for your existing ERPNext and HRMS workflows.

Version 0.2.2 includes separate /face-checkin and /face-kiosk pages, company-aware enrollment and paired device controls. Matching and liveness use configurable heuristics; confidence settings are not measured accuracy guarantees or certified anti-spoofing protection. Validate the capture environment, permissions and attendance processing before rollout.

A paired kiosk supports a bounded offline queue of up to 200 captures for seven days. Pre-issued offline challenges provide weaker assurance and records can require HR review. Unpairing removes queued local data, so operators must monitor and reconcile pending captures.

The source package was verified on a fresh ERPNext v16 bench. Installation needs ERPNext, HRMS and approved model weights. Confirm deployment, enrollment, training and support arrangements for your site.

Compatible with ERPNext 16

What you get

  • ERPNext v16 source package at version 0.2.2
  • Setup, kiosk, mobile check-in and troubleshooting documentation

Who this is for

HR and attendance teams

Review enrollment, pending offline captures and native employee check-in records.

ERPNext administrators

Configure the v16 app, model files, permissions and paired devices before rollout.

Frequently Asked Questions about Face Recognition Attendance

What is available, and how is installation arranged?

The source package targets ERPNext v16 with ERPNext and HRMS installed. Confirm server requirements, model setup, enrollment and rollout arrangements before deployment. Existing accepted installation, commissioning and support agreements remain unchanged.

How do face matching and liveness checks work?

Employees enroll with consent. The app compares a capture with enrolled embeddings and applies configurable matching and liveness heuristics. A confidence threshold is a setting, not a measured accuracy guarantee. The checks are not certified presentation-attack detection and cannot guarantee rejection of every spoof.

Does this replace ERPNext HR?

The app creates native Employee Checkin records. ERPNext and HRMS continue to handle shifts, attendance processing and payroll. Validate those workflows for your site during rollout.

What happens when a kiosk loses its connection?

A paired kiosk can queue up to 200 captures for up to seven days using pre-issued challenges. These captures have weaker assurance and can require HR review. Unpairing clears local data. Operators should monitor and reconcile pending records; offline capture does not guarantee against data loss.

Which versions and interfaces are verified?

Version 0.2.2 was tested on a fresh ERPNext v16 bench. The app provides a separate mobile web check-in page and a paired kiosk page. It does not add an attendance tile to the separate Frappe HR mobile application. Other versions require compatibility review.

What biometric data and models are required?

Enrollment stores face embeddings. Setup requires approved model weights, employee consent and appropriate access controls. Review retention, browser/device security and local biometric requirements before enabling collection.

Talk to an ECOSIRE expert about Face Recognition Attendance

Get a custom quote, a live demo, or help evaluating fit.

Start the conversation