Spatial MapSpatial Map
Get started
Hardware · Integration

RFID hardware integration for the readers, handhelds and printers you already own

Spatial Map is browser-based indoor mapping software that shows live device data on a 3D floor plan — it does not sell hardware. Our team connects the devices you already run — fixed RFID readers and antennas, Android RFID handhelds, rugged barcode computers, RFID printers, gates and BLE gateways — using each vendor’s own SDKs and APIs, so their reads land on the map, in reports and in share links.

Spatial Map: no credit card for the trial, runs in the browser, Pro is $60/month for up to 4 facilities. Explore the live demo

Illustrations of device types — not vendor product photos.

Works with hardware from

Zebra, Chainway, SATO and Sanray are trademarks of their respective owners. Spatial Map is not affiliated with or endorsed by them; we integrate with devices our clients already own using the vendors’ SDKs and APIs.

Hardware-agnostic by design

Spatial Map has no device drivers and no hardware of its own. It reads rows: anything that can produce a JSON record — a reader’s network output, RFID middleware, a handheld app, a WMS export — can feed a Spatial Map table, and a data link puts those rows on the floor plan.

The part that talks to the device is either something you already run (your RFID middleware or RTLS engine) or a small piece of software we build for you as part of a project: an Android app on the handheld, an edge service next to the fixed readers, or a print workflow for the label printer. Either way the devices stay yours, configured with the vendor’s own tools.

What runs where

A typical project has four layers. Only the last one is the Spatial Map product; the rest is your equipment, your systems, and — where needed — custom code.

  • On the device — an Android app on the RFID handheld or barcode computer, built on the vendor’s SDK: trigger, read, filter, count, encode.
  • On the network — fixed readers and gates send tag events to a small edge service or your middleware, which maps antennas to doors and zones and drops duplicate reads.
  • In your systems — the WMS or ERP stays the system of record for stock and assets; the connector reads expected quantities from it and writes results back.
  • In Spatial Map — reads arrive through the table write API, REST polling or a file upload, and show up on the 3D map, in reports and in share links.

What the product does not do — and how a project covers it

Spatial Map does not configure readers, tune antennas, encode tags or compute positions from signal strength, and it has no built-in alerting. Those jobs belong to the vendor’s tools, your middleware or RTLS engine — or they can be built as part of a custom project: a handheld app that encodes tags, an edge service that sends notifications, or a connector to the positioning engine you already use.

Keeping that line clear is what makes the map easy to drop into an existing RFID or BLE installation: nothing on the device side has to change for Spatial Map.

Devices we integrate

Device types, not a parts list — the same approach works for other vendors that publish an SDK, an API or a network output. Illustrations, not vendor product photos.

  • Fixed RFID readers and antennas

    Overhead and dock-door readers with external antennas. Tag events go over the network to an edge service, which maps each antenna to a door, zone or rack and posts batched reads.

  • Handheld RFID computers

    Android handhelds with a built-in or sled UHF reader and a pistol grip. A custom app uses the vendor SDK for stock counts, searches, audits and encoding, and syncs when online.

  • Rugged barcode computers

    Android mobile computers with a scan engine for receiving, put-away, picking and asset checks where items carry barcodes instead of — or as well as — RFID tags.

  • RFID printers and encoders

    Label printers that print and encode RFID labels. We generate the label and the encode command from your item data, and record which EPC went on which carton.

  • RFID gates and portals

    Pedestals at exits, dock doors and cage gates. Their reads become door events on the map — what passed, when, in which direction your middleware reports.

  • BLE gateways and tags

    Gateways that hear beacons and BLE tags. Room or zone presence comes from the gateway that hears a tag; positions come from your RTLS engine, if you run one.

  • RFID tags and labels

    Smart labels, hang tags and hard tags. The EPC or tag ID is the key that joins the read, your item master and the shape on the map.

How it connects

From a tag read to a live map

The same path for every device type: the vendor’s SDK or API at one end, Spatial Map’s write API at the other.

  1. 01

    Device

    Reader, handheld, gate, printer or gateway — configured with the vendor’s own tools.

  2. 02

    Vendor SDK or API

    An Android app on the handheld, or the reader’s network output, collects tag IDs, antennas and times.

  3. 03

    Edge service or middleware

    Filters duplicate reads, maps antennas to places, joins your item master, batches rows.

  4. 04

    Spatial Map table

    The connector posts rows to a table with the table write API: HTTPS, one bearer key per system, bulk upsert, 60 requests a minute per key — so it batches reads.

  5. 05

    Data link and map

    A data link binds the table to markers, zones and racks: last read, counts, status colours and the History player for movement.

  6. 06

    Reports and sharing

    Built-in reports and the report builder use the same rows; read-only share links give a site manager or client the live view.

REST polling also works when your middleware already exposes an endpoint — it runs in the browser of whoever has a map open, so the API must allow requests from the app (CORS). For device feeds the write API is usually the better fit.

Integration notes by brand

One page per vendor: what they make (from their own websites), and how their devices connect to Spatial Map.

Zebra integration

Zebra makes mobile computers, barcode scanners, RFID readers, antennas and portals, label and RFID printers, and RFID labels and tags.

Chainway integration

Chainway makes Android mobile computers, handheld and Bluetooth UHF RFID readers, fixed RFID readers, rugged tablets and printers.

SATO integration

SATO makes barcode and RFID label printers, print engines, labels, tags and RFID media, plus label design and printer management software.

Sanray integration

Sanray makes UHF RFID readers and modules, handheld and Bluetooth readers, and active 2.45 GHz RFID readers and tags.

What you get from a hardware integration project

A device and data map

Every reader, antenna, gate and handheld placed on the floor plan, named to match the IDs in your data.

The connector

The app, edge service or middleware configuration that turns device output into table rows — documented, with a runbook for your team.

Tables and data links

Read tables, item and asset tables, and the data links, style rules and filters that put them on the map.

Reports and share views

Built-in and custom reports on the same rows, plus read-only share links for site managers, clients or auditors.

Hardware integration — frequently asked questions

No. Spatial Map does not sell readers, handhelds, printers or tags, and is not a reseller or partner of any hardware vendor. You buy devices from the vendor or your usual supplier; we integrate the devices you own.

No. Spatial Map is not affiliated with, certified or endorsed by these vendors. We build integrations with the SDKs, APIs and printer languages the vendors publish for their customers and developers.

Not always. If your RFID middleware or RTLS engine can post JSON, it can write to a Spatial Map table directly with the table write API. Custom work is needed when nothing sits between the devices and the map yet — for example a handheld app or an edge service for fixed readers.

Any device whose data can reach a JSON row: through a vendor SDK on Android, a reader’s network or serial interface, the vendor’s middleware or a file export. Send us the model and its documentation and we will tell you which route fits.

Spatial Map itself has no alerting: it shows state on the map and in reports. Your gates, EAS system or middleware keep raising alarms, or notifications can be built into a custom app or edge service as part of a project.

No. It shows the room or zone your gateways report, or the coordinates your RTLS engine computes. Connecting a positioning engine can be part of a custom project; see BLE asset tracking.

Show us your devices — we’ll show you your building.

Send the models you run, a floor plan and a sample of their output. We will reply with the integration route and a live map of your own facility.