Technology / Middleware
REAOX middleware sits between RFID hardware and your software. It handles device connection, capability control, command execution, EPC events, device status, and remote operations, so applications and business systems receive clean, reliable data.
Device adapters
RFID devices
Android SDK
Android apps
REAOX Console
Operations console
Platform API
Business systems
01Integration paths
Pick the part of the system you own today. Each path shows where you connect, what to prepare, and what you get.
I have RFID devices
Share the device model, vendor SDK, and capability list. REAOX absorbs the vendor differences so every app and system above it sees the same commands and events.
See supported devicesI have an Android app
Your app opens an authorized session, receives the devices and capabilities it may use, calls commands, and gets EPC, status, and command-result callbacks.
See the Android SDKI have a business system
Your system queries devices, capabilities, and tasks, and receives structured RFID events. ERP, WMS, or MES remains your system of record.
See system integrationI manage field devices
See device status, alerts, command history, configuration, updates, and lifecycle records in one place, and diagnose problems remotely.
See device operationsI use a partner solution
For ready-made or partner-built systems, REAOX agrees the system boundary, data ownership, and rollout scope with you, then connects devices through the same platform.
Talk to our technical team02Platform components
Device differences across manufacturers and models are normalized in the adapter layer. Applications integrate through a consistent permission model, command set, and event contract, keeping device onboarding and business-system integration clear, reliable, and extensible.
REAOX Console
Operations workspace
Operations console
Manage devices, permissions, and field operations
Service running
Devices
Recent events
Authorized capabilities
Read activity
Tracked by device and task
Change log
Android SDK
Call any supported device the same way
Service running
SDK call sequenceDevice-specific behavior remains in the adapter layer.
APP IDcapabilityCodesopenSessionexecuteonEpcCallbacks
onEpcEPC receivedonCommandResultInventory startedonDeviceStateDevice onlineAuthorized capabilities
Platform API
Deliver reliable events to business systems
Service running
Standard event objectIllustration, not live data
RFID devices
Device adapters
Vendor differences stay here. New devices add an adapter.
What connects on top
Business systems
ERP, WMS, MES, POS
Delivery
Recent events
Illustration, not live data
Operations consoleCONSOLE
For administrators and device teams who register devices, grant access to apps, and keep devices running.
Android SDKSDK
For app developers who want RFID in their Android app without maintaining each vendor's SDK.
Platform APIAPI
For back-end teams connecting ERP, WMS, MES, or custom systems to RFID data.
03Device access
These models can be evaluated for project integration. Additional devices can join through the same adapter model without changing the upstream interface.
For hazardous-area work, industrial inspection, and asset verification. Hazardous-location use still requires project-level certification review.
For mobile stocktake, item search, and transfer checks, using the same session and event model as every other device.
Send the device details, vendor SDK, and capability list. We extend the adapter layer; your apps and business systems keep the same interface.
The same capability model can extend to NFC, barcode scanning, printing, and access control, so every device runs on one operations platform.
04Device operations
Middleware is not an extra relay. It turns device status, command history, read quality, and lifecycle into information your team can act on.
ALERT
Can flag disconnections, offline devices, failed commands, and abnormal reads according to project rules.
REMOTE_OPS
Provides project-configurable status checks, diagnostic data, configuration delivery, and version-management interfaces.
READ_QUALITY
Can review EPC volume, duplicates, and task completion by device, model, site, and task.
LIFECYCLE
Can retain records from receiving and assignment through service, updates, and retirement.
Trace problems by device, app, task, and event, instead of piecing together scattered logs and field reports.
05Integration steps
Five steps, so device, app, and business-system teams can each see where their work fits.
CREATE_APP
Set up the app identity, credentials, callback address, and tenant scope.
GRANT_SCOPE
Choose which device models and capabilities the app may use.
OPEN_SESSION
The SDK receives the devices, models, vendors, and available capabilities.
EXECUTE
Initialize, read, start and stop inventory, and write tags.
DELIVER_EVENT
Get EPC data, command results, device status, and exception events.
Evaluation and technical resources
This area will bring together a middleware sandbox, interface documentation, white papers, and deployment notes. Planned resources remain clearly labeled until they are available.
Validate device onboarding, event processing, rules, and business-system handoff.
REST APIs, adapters, event fields, and integration guidance in one place.
Platform architecture, deployment boundaries, data flows, and integration patterns.
06Before you start
These details move the conversation from whether it can connect to a clear pilot scope, ownership, and go-live criteria.
01DEVICE
Device models, vendor SDK, Android version, read and write needs, and site network conditions.
02SCOPE
Which tenants, users, and apps may use which devices and capabilities.
03EVENTS
What counts as a valid read, how duplicates are handled, and which events your systems need.
04INTERFACE
Authentication, callback address, task queries, data ownership, and offline handling.
Scope and responsibilities
08Integration questions
REAOX RFID middleware software connects multi-vendor readers and handhelds with Android apps, ERP, POS, WMS, MES, LIS, and custom systems through consistent commands, permissions, APIs, and RFID events.
RFID middleware sits between readers, handhelds, and business applications. It normalizes device capabilities, permissions, commands, status, and events so application teams do not need to integrate each device model separately.
The integration path can use the Android SDK, platform APIs, or reliable event delivery. The appropriate path depends on where device control runs, which business events are required, and how the target system accepts data.
Yes, for validated devices and capabilities. Device adapters keep vendor-specific behavior in the adaptation layer while the application uses a consistent permission model, command set, and event specification.
We will review your setup and recommend a clear integration path.