Vendor-agnostic Odoo connector for HikVision, Anviz, Suprema & Convoy — normalized punches into HR Attendance. Built for you. One-time license from $299.00 USD for Odoo 17, 18, 19 — includes 12 months of updates and support.

Vendor-agnostic Odoo connector for HikVision, Anviz, Suprema & Convoy — normalized punches into HR Attendance. Built for you.
No payment now. This sends a quote request to our team — we'll follow up by email with pricing and next steps.
Most Odoo biometric connectors assume ZKTeco. If your fleet runs HikVision face/card terminals, Anviz fingerprint readers, Suprema controllers, Convoy panels — or a mix of all four across sites — you are stuck exporting CSVs and reconciling them by hand every payroll cycle.
HikVision face + card terminal support via ISAPI event-listening / event ISAPI push, with vendor SDK fallback for firmware that requires it
Anviz fingerprint and multi-modal reader integration (TCP/IP polling or SDK subscription) mapped to normalized punches
Suprema controller / BioStar integration for fingerprint, face and access events pulled into Odoo HR Attendance
Convoy and other generic TCP push-log devices handled through a pluggable device-adapter layer — add new vendors without core changes
Unified punch normalization: every vendor event becomes a single hr.attendance-ready record (employee, device, direction, verify method, corrected timestamp)
Auto employee mapping — biometric enrollment ID / card number / device user-ID resolved to the correct hr.employee, with an admin screen for unmatched punches
ECOSIRE builds you a vendor-agnostic biometric attendance connector that speaks each vendor's native protocol and normalizes every event into a single, clean stream inside Odoo's HR Attendance app. HikVision terminals push events over ISAPI / event-listening (with SDK fallback where firmware requires it); Anviz and Suprema devices are polled or subscribed via their respective SDK/BioStar interfaces; Convoy and other TCP push-log devices are handled through a pluggable device-adapter layer. Whatever the source, each raw punch lands as a normalized record: employee, device, direction (check-in/check-out), timestamp (timezone-corrected), and verification method.
This is a build-to-order engagement, not an off-the-shelf apps.odoo.com download. We architect the module against your exact device models, firmware versions, network topology and Odoo edition, then build, install, test and support it. Under the hood it ships as a proper Odoo addon: a versioned __manifest__.py, models.Model classes for devices and raw logs with @api.depends computes for punch normalization and duplicate suppression, ir.model.access.csv plus record rules for multi-company / multi-site isolation, backend list/form views and OWL/QWeb dashboards, ir.cron scheduled actions for polling and health checks, and clean write-through into hr.attendance so Payroll, Timesheets and Presence all work unchanged.
Delivered for Odoo 17, 18 and 19 (Community or Enterprise), with source code you own, deployment on your server or Odoo.sh, admin documentation, a training session, and a post-launch support window. No proprietary lock-in — the adapter layer is documented so new device models can be added later.
Manages a mixed fleet of HikVision, Suprema and Anviz terminals across branches and is tired of stitching per-vendor exports together. Wants one connector, one normalized stream into Odoo, device health alerts, and multi-site data isolation — without maintaining brittle scripts.
Runs monthly payroll on Odoo and needs attendance they can trust. Cares that every punch maps to the right employee, that double-swipes don't inflate hours, timezones are correct, and there's a raw-log audit trail to settle disputes — so payroll stops being a manual reconciliation exercise.
Rolling out or supporting Odoo for a client whose existing biometric hardware is non-ZKTeco. Needs a maintainable, documented addon with a clean adapter layer and standard hr.attendance write-through, so it survives Odoo upgrades and can be extended to new device models later.
Buy the license on ecosire.com and download the HikVision / Anviz / Suprema Attendance Connector module ZIP from your account dashboard.
Extract the ZIP into your Odoo custom addons folder on the server (or upload via Apps > Install from file on Odoo.sh / runbot).
Activate Developer Mode, open Apps, click Update Apps List, search for HikVision / Anviz / Suprema Attendance Connector, and press Install.
Open the new menu, paste your ECOSIRE license key, connect any external credentials (Shopify, Amazon, Stripe, etc.), and save.
Run the built-in connection test, sync your first 10 records, and schedule the recurring cron. Contact support if anything fails.
| Criterion | ECOSIRE | Custom Build | Competitor | Odoo Native |
|---|---|---|---|---|
| Non-ZKTeco vendor support (HikVision, Anviz, Suprema, Convoy) | Native adapters for all four, plus a pluggable layer for more | Whatever you scope and can maintain in-house | Usually ZKTeco-only; rare add-ons per single vendor | |
| Mixed / multi-vendor fleet in one normalized stream | Unified punch normalization across all vendors into hr.attendance | Possible but you build and maintain the normalization | Rarely — most modules bind to one protocol | |
| Auto employee mapping + unmatched-punch queue | Built in, with an admin screen for unresolved IDs | You design and build it | ||
| Duplicate suppression & timezone-correct posting | Configurable window + per-device timezone handling | Depends on your implementation effort | ||
| Device health monitoring via scheduled ir.cron | Offline/silent devices raise alerts instead of dropping punches | Only if you build and schedule it | ||
| Multi-company / multi-site data isolation | ir.model.access.csv + record rules configured to your org | You implement the security model | ||
| Fit to your exact devices, firmware & Odoo edition | Built and tested against your real hardware at discovery | Generic; hope your model/firmware is covered | ||
| Source ownership & documented extensibility | You own the code; adapter layer documented for new devices | Vendor-controlled; extension often blocked or paid | ||
| Delivery model | Build-to-order, installed & supported (2-4 wk lead time) | Full in-house project, indefinite timeline | Instant download, integration is on you |
This is a build-to-order engagement with a typical lead time of 2 to 4 weeks after kickoff — it is not an instant apps.odoo.com download. We start with a short discovery to capture your exact device models, firmware versions, network topology and Odoo edition, then build against those specifics, install on your environment, run acceptance tests on your real devices, and hand over. Timeline depends on the number of distinct vendors, sites and device quirks; we confirm the schedule at kickoff.
You get a post-launch support/warranty window (scope agreed at kickoff) covering bug fixes and compatibility with Odoo minor updates on your target version. Because you receive the full source with a documented adapter layer, your own team can add new device models or extend behavior without depending on us. We also offer ongoing support and 'add a new device vendor' extensions as a separate engagement if you prefer we handle it.
HikVision face/card terminals, Anviz fingerprint/multi-modal readers, Suprema controllers (BioStar-family), and Convoy plus other generic TCP push-log devices via the pluggable adapter layer. If you run a specific model we haven't listed, tell us at discovery — the architecture is designed so a new vendor is a new adapter, not a rewrite. Mixed fleets combining several of these are the core use case.
We build for Odoo 17, 18 and 19, on Community or Enterprise. The module writes into the standard hr.attendance model, so it works with the free HR Attendance app on Community as well as Enterprise Payroll, Timesheets and Presence. We target the single version you're on; a multi-version build can be scoped if you're mid-migration.
HikVision terminals are integrated via ISAPI event-listening / event push (with vendor SDK fallback where firmware requires it); Anviz and Suprema via their SDK/BioStar interfaces (subscription or polling); Convoy and similar via TCP push-log parsing. An ir.cron scheduled action handles polling and device health checks, and each raw event is normalized through @api.depends computes into an hr.attendance record. Real-time push is used where the device firmware supports it; otherwise near-real-time polling is configured.
No — these are exactly what the module is built to prevent. Duplicate/bounce suppression collapses repeated punches within a configurable window, auto employee-mapping resolves each device ID to the right hr.employee (with an admin queue for anything unmatched), and per-device timezone handling posts correct local times. Every original device event is also kept as a raw-log audit trail, so any payroll dispute can be traced back to the source punch.
Yes. Access is controlled with ir.model.access.csv and record rules so each company or site only sees its own devices, logs and attendance. This is standard Odoo multi-company security applied to the connector's models, configured to match your org structure during the build.
Vendor-agnostic Odoo connector for HikVision, Anviz, Suprema & Convoy — normalized punches into HR Attendance. Built for you.