EPORDO

EPORDO P Series

Smart identification & access management

Terminals handle verification and door control. Connect handles connectivity and events. Business rules stay in your own systems. Connect devices. Unify identities. Control access. Capture every event.

ET-P5 · IP65 ET-P7 · 7 inch + Connect
ET-P5 · IP65

How it fits together

One solution. Three clear layers.

Not just a reader. Not just an API kit. Field recognition, platform connectivity, and your business apps work as one solution—with responsibilities that stay easy to explain.

Three-layer solution: P Series terminals, EPORDO Connect, and customer applications

02 · Identity

Multi-modal identification at the door

P Series terminals complete verification and door control on site. Fingerprint, face, palm, RFID, and PIN can be enabled per hardware configuration. Results and enrollments flow through Connect into your business systems.

Multi-modal identification at the door
On-device recognition & door control · ET-P5 with IP65 for outdoor / wet areas · ET-P7 with a larger ~7" interface
FP

Fingerprint

Fast, cost-effective for high-traffic doors and workstations—easy to combine with card or PIN.

FC

Face

Contactless flow for lobbies, reception desks, and membership entrances that need quick checks.

PL

Palm

Palm biometrics for doors that need a cleaner, more hygienic experience (when the unit supports it).

RF

RFID card

Fits existing badge and membership-card habits without forcing a rip-and-replace.

PN

PIN

A practical backup or emergency path alongside biometrics and cards.

Supported modalities depend on each model’s hardware. One Connect tenant can manage both ET-P5 and ET-P7. For outdoor lanes, prioritize the IP65-rated ET-P5.

ET-P5
ET-P7 front
ET-P7 detail
ET-P7 rear

03 · Centralized Identity

Central identity—synced across sites

HQ, branches, and stores plug into one Connect tenant. Enroll once on a device, then push supported credentials to compatible units—less re-enrollment at every door.

Central identity—synced across sites
Flow: on-site enrollment → Connect aggregates identity & events → credentials pushed to compatible branch / store devices

Enroll once. Pass at authorized sites.

Enrollment data reaches Connect from the device. Your ops team can push by device or group. Local verification stays on the terminal; events return to the center and your business apps.

Multi-site device fleetEnrollment uploadCredential pushEvent feedback

What sync really means

We sync supported identity credentials across compatible devices. Biometric algorithms and template formats can differ by model—project delivery follows real hardware compatibility.

Compatible devicesSupported credentialsModel-aware rollout
Installation scene
Accessories
Packaging

04 · EPORDO Connect

Device connectivity & integration platform

Connect is not your membership or payroll product—and not “another attendance suite.” It connects devices, identities, events, and commands so P Series terminals work with the systems you already run.

Click to enlarge Portal preview · Overview: device counts, recent events, Webhook / MQTT status (demo data)
Portal preview · Overview: device counts, recent events, Webhook / MQTT status (demo data)
Click to enlarge Portal preview · Device detail: online / door state · enrolled users · credential push
Portal preview · Device detail: online / door state · enrolled users · credential push
Click to enlarge Portal preview · Event list: filter verification, online, and other device-side facts
Portal preview · Event list: filter verification, online, and other device-side facts
Click to enlarge Portal preview · Event detail: verification record, capture placeholder, and JSON payload for integration
Portal preview · Event detail: verification record, capture placeholder, and JSON payload for integration
Click to enlarge Portal preview · Device groups: multi-site fleet with group-level sync / status / remote open
Portal preview · Device groups: multi-site fleet with group-level sync / status / remote open
DEVICES

Device management

Register, group, and watch online / offline status across every site.

EVENTS

Event intake

Granted / denied verification, enrollment, door activity, and remote-action results.

COMMANDS

Command delivery

Push or delete users, set time zones, pull logs, and run remote door open.

REMOTE

Remote open

Reception or security can release a door from the center and confirm the result.

PORTAL

Ops portal

Tenant login to review events, configure channels, and download integration docs.

API

Developer surface

REST, Webhook, and MQTT connect device capability to your own applications.

05 · Integration

Fit your stack—don’t replace it

Once devices sit on Connect, pick REST, Webhook, or MQTT to match how you already build. One platform. Several ways in.

Fit your stack—don’t replace it
Layer boundaries and two-way flow: terminals report events / receive commands · Connect exposes REST, Webhook, and MQTT to your apps
Pull / Command

REST API

Query events, push users, and open doors on demand—ideal when your backend prefers to call.

Event Push

Webhook

Connect posts to your HTTPS URL so near-real-time actions (deduct visits, notify, tickets) fire when events land.

Subscribe

MQTT

Long-lived subscriptions for teams that already run an MQTT bus across sites and services.

Click to enlarge Portal preview · Webhooks: register HTTPS callbacks, choose event types, review delivery attempts
Portal preview · Webhooks: register HTTPS callbacks, choose event types, review delivery attempts
Click to enlarge Portal preview · MQTT: managed broker, credentials, and topics (sample hostnames)
Portal preview · MQTT: managed broker, credentials, and topics (sample hostnames)
Click to enlarge Portal preview · Event payload: the same structured data your apps get via REST / Webhook / MQTT
Portal preview · Event payload: the same structured data your apps get via REST / Webhook / MQTT

06 · Scenarios

Where it lands

Same playbook—terminals + Connect + your apps—swap the business rules for the industry. Four common project patterns:

01 · MEMBERSHIP

Multi-site membership access

Gyms, training centers, clubs: members verify by face or card at any authorized store.

  • Your app validates membership or deducts visits from Connect events
  • Front desk can remote-open for trial guests
  • All store devices share one tenant for ops
ET-P5
02 · WORKPLACE

Multi-site offices & branches

Enroll at HQ; branch devices join the same Connect tenant. IT and facilities see online state and denied attempts.

  • Connect to existing OA / HR with REST or Webhook
  • Push credential updates to selected devices after HR changes
  • Fits chained offices and regional branches
Portal preview · Device groups: multi-site fleet with group-level sync / status / remote open
03 · CAMPUS

Campus, building & zone access

Hotels, schools, parks, mixed-use towers: group devices by zone. Who enters which zone stays in your ACL system.

  • Connect delivers credentials to the right device groups
  • Pass / deny facts return for security or housing desks
  • Visitor, staff, and resident policy live in your apps
Installation scene
04 · VENUE

Venues, tickets & facilities

Shows, events, training halls, self-service centers: pass facts drive redemption, prompts, and reports in your systems.

  • Group entrance devices; watch online status and anomalies together
  • Your ticketing / facility system owns packages and session rules
  • Remote open helps staff clear queues when needed
Portal preview · Event list: filter verification, online, and other device-side facts

Model tip: outdoor or wet environments favor ET-P5 (IP65); larger operator UI favors ET-P7 (~7"). Both join the same Connect platform.

07 · Developers

Developer resources

This page sells the solution story. Auth, fields, commands, and error codes live in the public API guide and the Connect portal.

API guide

REST auth, events, Webhook / MQTT, canonical commands, and error codes for integrator and customer engineering teams.

Download API guide PDF →

Connect portal

After onboarding, review devices and events, configure Webhook / MQTT, and grab docs from Help.

Open Connect portal →

Clear ownership

Membership billing, shift payroll, and approvals stay in your apps. Connect supplies device-side facts and controllable actions.

See integration architecture →

Next step: bring this into your project

Download the brochure, request a quote, or talk to sales and channel managers. You can also explore the live Connect portal.

Website:epordo.com · Connect:connect.24hoursonlinesys.com · WhatsApp:0086 186 6533 2487 · Email:sophia@securiticn.com
ET-P5
ET-P5 · IP65
ET-P7
ET-P7 · 7 inch