Illustrative fingerprint and face-recognition attendance terminals

PLETOX / CONNECTED DEVICE OPERATIONS

Advanced Biometric
Management

Manage supported Realtime and eSSL machines across locations. Provision users remotely, sync Realtime enrollments, and track commands and attendance from one connected workspace.

Book a demo Explore features

Remote user management Multi-location control

Illustrative hardware. Supported models vary.

ONE VIEW ACROSS YOUR LOCATIONS

Less running between machines.
More control from your desk.

Keep device connections, employee mappings, and pending work visible together. Know which machine is online and which action still needs attention.

PletoxBiometric managementCompany / All locations

CONNECTED WORKFORCE

Devices & activity

2 online / 1 offline
Head officeMain entrance
RealtimeOnline
Last seenJust now
FactoryStaff entrance
eSSL / ADMSOnline
Last seen20 seconds ago
WarehouseDispatch entrance
RealtimeOffline
Last seen12 minutes ago
Head office / Mapped usersRealtime
AS
Asha ShahPIN 101 / Operations
Unlocked
RP
Rohan PatelPIN 102 / Operations
Unlocked
NP
Neha PatilPIN 103 / Operations
Locked
Recent attendancePunch delivery & processing
Asha ShahHead office / PIN 101
Processed
Rohan PatelFactory / PIN 102
Processed
PIN 204Warehouse
Needs mapping
Connections, people, and punch outcomesIllustrative preview / Sample data

Centralized device management

Organize machines by company and location. See their protocol, connection status, and last activity without checking each device in person.

Remote user provisioning

Add employees to supported machines, fetch their profiles, and manage lock, unlock, or removal actions from Pletox.

Multi-machine enrollment sync

Copy profiles and available fingerprint and face templates between compatible Realtime machines connected through the same Pletox gateway.

A command history you can follow

See queued, sent, successful, and unresolved commands with machine responses, attempts, and timestamps.

Reliable attendance delivery

Store incoming punches before forwarding, retry delivery failures, and use duplicate protection when records arrive again.

Connected to your workforce

Link machine users to employees and carry processed punches into the attendance, shift, and payroll workflows already in Pletox.

ENROLL ONCE. EXTEND TO MORE LOCATIONS.

Move enrollments.
Not your employees.

Use an enrolled source machine to prepare other compatible Realtime devices. Choose individual users or sync all eligible mapped source users to multiple destinations in one request.

  1. 01

    Choose the source and destinations

    Select devices within the same Pletox account and approved gateway. Sync all users is processed in batches, including sources with more than 500 users.

  2. 02

    Capture what is actually enrolled

    Transfer the user profile and available templates. A user does not need a face enrollment or every finger enrolled to be included.

  3. 03

    Follow each destination

    Review source captures and destination deliveries separately, with clear reasons and retry controls for work that needs attention.

Updating existing users can replace their details and biometric templates. Cross-brand template conversion between Realtime and eSSL is not included.

Enrollment syncIllustrative preview / Sample data
SOURCE / REALTIME

Head office

All source users

Profiles + enrolled templates
  • Factory entranceRealtime / Same company
    Completed
  • WarehouseRealtime / Same company
    In progress
User profile
Included
Fingerprints
Enrolled fingers only
Face template
When available
Delivery
Tracked per destination

New biometric capture still takes place on a compatible machine. Pletox transfers the enrollment already held by the source.

A CLICK IS NOT A DEVICE CONFIRMATION

Know what ran.
Know what needs a review.

Follow each command from request to confirmation. The gateway queues work for connected machines and records the response instead of treating a submitted request as success.

  • Queue work while a machine is offline

    Pending commands wait for the device connection. Track progress without leaving the user management workflow.

  • Recover unconfirmed user additions

    Eligible Add User commands can be checked after reconnection before the saved user details are resent.

  • Keep sensitive actions deliberate

    Destructive commands require confirmation. An uncertain outcome is flagged for review, not silently treated as a failure and repeated.

Command centerIllustrative preview / Sample data
  • Add userSuccess

    The machine confirmed the user addition.

    Queued / Sent / Acknowledged
  • Fetch userPending

    Waiting for a device connection.

    Not yet sent to the machine
  • Clear logsUnknown outcome

    The device disconnected before confirmation.

    May already have run / Review required

A missing acknowledgement is not proof that a write failed. Recovery depends on the command and its recorded outcome.

FROM A DEVICE PUNCH TO A WORKING DAY

Attendance delivery.
With a trail behind it.

Keep the original event, delivery status, and processing result connected. Unresolved punches remain visible so your team can act on them.

  1. 01

    Receive & store

    The gateway stores incoming punches before forwarding them to Pletox.

  2. 02

    Forward & retry

    Queued delivery retries temporary failures, with duplicate protection for repeat events.

  3. 03

    Map & process

    Pletox resolves the employee mapping and shows processed or unresolved results.

  4. 04

    Review attendance

    Use processed records with your configured shifts, attendance rules, and payroll review.

Automatic cleanup manages completed delivery history while protecting unresolved punches, duplicate-protection records, and actual attendance records.

Explore attendance & shifts

THE RIGHT CONNECTION FOR EACH MACHINE

Realtime and eSSL.
One connected workforce.

Device management follows the protocol each model supports. We confirm firmware, connectivity, and template compatibility before rollout.

Realtime

Realtime / WebSocket

Gateway-based device connections, remote user commands, enrollment sync, and tracked attendance forwarding.

  • Multi-device sync on the same gateway
  • Available fingerprint and face templates
  • Queued commands and acknowledgement tracking
Shop Realtime devices
eSSL

eSSL / ADMS

Supported ADMS machines stay connected to the existing device management and attendance workflows in Pletox.

  • ADMS device communication
  • Employee and device mappings
  • Operations depend on the machine and firmware
Shop eSSL devices

Enrollment sync requires compatible Realtime machines connected through the Pletox gateway. eSSL devices and other connection setups retain their existing management options and are not part of this sync workflow.

THE MACHINE IS JUST THE START

Connected to the rest
of your working day.

Keep device operations close to the employee records and reviewed attendance that your HR team already uses.

People & onboarding

Connect machine users to the right employee record.

Explore module

Attendance & shifts

Review punches alongside shifts and attendance rules.

Explore module

Payroll & salary rules

Carry reviewed attendance into your payroll process.

Explore module

Employee self-service

Let employees review enabled records and request corrections.

Explore module

BEFORE CONNECTING YOUR MACHINES

Your biometric
questions, answered.

Start with the devices you have and the operations your team needs.

Book a demo

Pletox supports configured Realtime WebSocket and eSSL ADMS connections. Support depends on the model, firmware, network access, and available commands. Share your device models during the demo so we can confirm the connection and management options.

You can provision user details remotely and copy existing enrollments between compatible Realtime machines within the same Pletox account and approved gateway. New fingerprint or face capture still happens on the source machine, not in a web browser.

No. Sync all users includes all eligible active employees mapped to the source in Pletox and visible to your account permissions. It processes that selection in batches, including sources with more than 500 users. Unmapped machine-only users are not automatically included. You do not need to submit the same sync twice. Each destination has its own delivery progress.

The sync uses the user profile and the biometric templates actually enrolled on the source. A missing face enrollment or unused finger slots does not require the user to enroll every biometric type. Invalid or unreadable source data is still reported for review.

No. Fingerprint and face formats may differ between brands, models, or firmware. Enrollment sync is for compatible Realtime machines connected through the same Pletox gateway. eSSL devices and other connection setups retain their existing management options.

Commands that have not been sent wait for a connection. If the connection drops after a write but before acknowledgement, the outcome may be unknown. Eligible Add User recovery checks the device before resending; destructive commands are not blindly replayed. Recovery of punches recorded while offline also depends on the device retaining and uploading its logs.

Updating existing users from the source can replace their details and biometric templates. Review the source and destination selection and the update confirmation before queuing a sync. It should not be treated as a merge of different biometric enrollments.

The gateway records delivery attempts and Pletox shows the processing outcome, employee or PIN, punch time, and any unresolved reason. Temporary delivery failures are retried and repeated events are checked for duplicates. Attendance still follows your configured employee mappings, shift policies, and review process.

Book a demo