Start with the business result
Inventory accuracy, asset custody, production traceability, stocktake speed, anti-loss control, or chain-of-custody visibility.
Products
Three layers, one RFID operating system
REAOX products should be understood as a system: the device-and-tag layer captures data, middleware turns signals into reliable events, and application software makes those events useful for daily business operations.
Explore
Layer 01
RFID Tags & Devices
The physical data-capture layer: tags, labels, readers, modules, antennas, handheld terminals, and workflow equipment.
- Tags selected by item and environment
- Readers and antennas selected by read zone
- Terminals and equipment selected by workflow
Explore
Layer 02
Middleware Platform
The event and integration layer: device adapters, filtering, workflow events, APIs, and data handoff to ERP, POS, WMS, LIS, or custom systems.
- Device abstraction
- Event filtering and workflow rules
- ERP / POS / WMS / API integration
Explore
Layer 03
Application Software Systems
The business operation layer: software workflows for jewelry retail, asset management, warehouse visibility, industrial traceability, laboratory control, and public-service operations.
- Industry workflow modules
- Dashboards and exception handling
- Role-based operating screens
Selection Logic
Product selection should follow the business workflow
This keeps the site from looking like a loose device catalog. It helps a buyer understand why REAOX is a systems company, not just a reader supplier.
Then define the operating scene
Counter, gate, cabinet, shelf, warehouse dock, conveyor, lab rack, field asset, mobile inspection, or self-service machine.
Then choose the layer stack
Some projects only need hardware. Mature deployments usually need hardware, middleware, and application workflows together.
Supporting Materials
Product Library is a reference center, not a fourth product layer.
Manuals, images, specifications, and model pages remain available for detailed comparison, but the public product story stays organized around devices and tags, middleware, and application software systems.