Multi-site organizations rarely run one brand of biometric hardware. A head office standardizes on Suprema, a factory floor runs eSSL, a new branch was fitted out with Hikvision, and a retail site inherited Matrix and Realtime terminals. ERPNext ships an Employee Checkin DocType and can compute attendance from it, but out of the box it does not talk to any of these devices — the native integration is limited, brand-specific tooling is fragmented, and most teams end up exporting .dat/.xlsx logs and importing them by hand. That manual bridge is where payroll disputes, missing punches, and duplicated shifts come from. ERPNext runs out of road exactly at the point where heterogeneous hardware has to become one trustworthy stream of check-ins.

The Universal Biometric Device Connector is a proper Frappe app (its own module, DocTypes, and hooks.py) that ECOSIRE builds around the specific devices you actually operate. At its core is a vendor driver library — pluggable adapters for eSSL/ZKTeco-family, Suprema (BioStar), Hikvision (ISAPI), Matrix, Realtime and others — each translating a device's native protocol into a normalized punch record. Devices are modeled as a Biometric Device DocType (IP, port, serial, brand, location, timezone, poll interval) and managed as a fleet from one list view. The connector runs in two modes: a real-time push mode where devices POST events to a whitelisted Frappe REST endpoint (@frappe.whitelist(allow_guest=True) with token/HMAC verification), and a pull mode where a scheduler event polls each device on an interval, dedupes against the last synced cursor, and only writes new punches. Every raw punch is mapped to a standard ERPNext Employee Checkin (employee, time, log_type IN/OUT, device_id), so downstream attendance, shift, and payroll logic works unchanged.

Because raw hardware is messy, the mapping layer is where most of the engineering goes. A Device Employee Map links each device's enrollment/biometric ID to the correct ERPNext Employee, so a single person clocking on three brands still resolves to one record. Server-side logic (a controller validate/on_submit plus doc_events hooks in hooks.py) enforces IN/OUT alternation, drops duplicate punches inside a debounce window, and — when enabled — assigns the correct Shift Type on sync based on device location or punch time, so Attendance auto-generation and shift-based rules land correctly. Client scripts add device health and a manual re-sync action in the desk UI, and dedicated Role Profile/permission rules keep HR, site managers, and the sync service account cleanly separated. A Biometric Sync Log DocType records every run, per-device status, and error detail for auditing and troubleshooting.

Delivery is build-to-order — this is not a Frappe Cloud Marketplace download you install yourself. We start with a short scoping call to inventory your exact device brands, models, firmware, network topology (LAN vs. VPN vs. cloud), and whether push, pull, or a mix fits each site. ECOSIRE then builds and validates the connector on a staging bench against your real devices (or matched test units), runs UAT with your HR team, and installs on your production ERPNext with a rollback plan. Typical delivery is one working week from confirmed scope, depending on how many device families and edge cases are in play. You receive the full source as a versioned Frappe app in a git repo you own, plus documentation, training, and a post-go-live support window. The app targets Frappe/ERPNext v15 and v16.