Skip to main content

How Tagnet Works

Tagnet is an enterprise RFID inventory and tracking platform. It connects to the RFID readers on your floor, turns the raw tag reads into clean inventory movements, and gives your team live visibility plus automated actions. No one has to scan a clipboard or key in counts. The same platform fits many jobs: work-in-progress tracking in manufacturing, utility pole and transformer tracking across a network, vendor-managed inventory for consumables, and IT and capital asset tracking.

Tagnet architecture overview: RFID devices stream reads and telemetry into the Tagnet platform, which provides reader management, inventory management, automation, and an optional AI assistant (Tagnet AI, requires Azure OpenAI), secured by role-based access, audit logs, and access scopes. Tagnet stores data in SQL Server or SQLite, serves a web portal and dashboards to your users, and integrates with your systems over the REST API

From tag to action​

Every time a reader sees a tag, Tagnet turns that read into a trusted inventory action. Here is the journey, from the floor to your team and systems:

From tag to action: readers on your floor feed the capture and validation step, which updates the inventory system of record, drives the automation engine, and surfaces dashboards, alerts, outbound HTTP integrations, and API access to your team and systems

  1. On your floor: Each item carries an RFID tag. Whatever device is closest reads it: a dock-door reader, a forklift reader, a handheld scanner, or a smart cabinet or kiosk.
  2. Capture and validate: Tagnet groups the reads, ignores stray background noise, and confirms when something actually moved. This is what separates a real movement from a tag that simply sat within range.
  3. Inventory system of record: Confirmed movements update a complete model of your inventory: products and assets, where they are, and a full history of every transaction.
  4. Automation engine: Rules turn those reads into actions automatically.
  5. What your team and systems get: Live dashboards, in-app alerts, outbound HTTP calls to external systems (ERP, WMS, or any HTTP endpoint), and an open REST API for everything else.

A scenario anyone can follow: A tagged pallet rolls through the receiving dock. The dock-door reader sees it, Tagnet confirms it is a real movement, records the receipt against the right product, moves it into Receiving, sends the supervisor an in-app alert, and posts the update to your ERP via an outbound HTTP call. No one scanned a barcode or typed anything.

Automation that does the work​

Most of the day-to-day value comes from the automation engine. Every rule follows the same simple shape, so it is easy to reason about: something happens, Tagnet checks whether it matters, then it acts.

  • Trigger: A scan event happens, for example a pallet read at the dock.
  • Filter: Tagnet checks whether the event matches the conditions you set, such as a specific reader, item type, or location.
  • Act: When it matches, Tagnet runs one or more actions. It can move inventory (receive, put-away, ship), send an in-app alert, or call an external system with a formatted HTTP payload.

Because the rules are configured rather than coded, your team can adjust how Tagnet responds without a software release.

Security and access​

Tagnet controls who can see and do what. Role-based access control sets each user's permissions, access scopes segment data by site, department, or business unit, and an audit trail records security-relevant activity for review.

Where Tagnet runs​

Tagnet installs on your own Windows Server (Tagnet Enterprise) or runs hosted for you (Tagnet Cloud). Either way, your deployment is a dedicated instance with its own database, so your data is fully isolated.

Next steps​