Asset tracking is the most underestimated RFID application: inventory RFID aims for "every unit in the system", while asset RFID answers only two questions — where is it now, and when was it last confirmed where. Those two questions need no daily item-scanning routine, yet they shrink the annual audit of IT equipment, tools, medical devices and returnable containers from days to hours. This article explains how to land it on Odoo 17-20.
First, separate the two models
Odoo carries two meanings of "asset", and conflating them is the first reason asset projects fail:
- Accounting assets (the Assets module in Accounting): depreciation, disposal, book value. It cares about money, not about which room a device is in. Accounting assets do not need RFID — depreciation is a function of time.
- Physical presence (serialised inventory items or a dedicated tracking model): the physical location and check-in/check-out state of devices, tools and containers. This is the layer RFID actually serves.
The correct pattern is usually to keep accounting assets in Assets as-is, track the physical item in a separate model (or a serialised inventory product), and link the two by asset number. RFID writes to the physical model and, where needed, syncs "in use / pending disposal" state to the accounting side.
Tags: equipment demands anti-metal
IT equipment and tools are almost entirely metal surfaces. A standard inlay on a chassis reads at zero distance — not a power problem but an antenna boundary-condition problem:
- Chassis, servers, workstations: anti-metal tags (foam or ferrite backing), 1–4 m read range.
- Small tools: compact anti-metal or hang tags, 0.5–2 m.
- Returnable containers (pallets, bins, IT transport cases): standard inlays at USD 0.05–0.15.
- Medical devices: sterilisation-cycle survival is a hard constraint — demand autoclave data from the vendor.
Encoding can follow EPC SGTIN-96 or a private scheme; asset tracking does not depend on GS1 registration, unlike retail item-level RFID.
Check-in/check-out and audit workflows
- Check-in/check-out: a desktop reader at the tool crib or IT helpdesk — the employee taps a badge or selects their name, the device on the reader registers the loan or return automatically. This is the fastest-ROI asset scenario: tool-loss reduction is directly countable.
- Room/zone audit: walk in with a handheld and sweep. A 100-device room takes about 2–5 minutes.
- Full audit: fixed portals plus handhelds turn an annual audit from "two days with the helpdesk closed" into "half a day walking every room".
Door portals: let movement produce its own record
Fixed readers at server-room doors, tool-crib doors and storage exits generate a movement event whenever a tagged device passes: who, when, which door, carrying what. The value is retrospective — when equipment goes missing, the last door read is the search's starting point.
How state reaches Odoo
Middleware outside Odoo catches the read events and writes them back by rule:
- XML-RPC or JSON-RPC calls update the physical asset model — current location, last-seen timestamp, loan state, custodian.
- Movement events land in an event-log model, directly browsable in an Odoo audit view.
- Because the integration uses the public API, behaviour is identical on Community 17, 18, 19 and 20 and on Enterprise — SpidersRFID middleware is designed for all versions 17-20, so an Odoo upgrade never means rebuilding the integration.
What audit speed looks like in practice
A 200-device office area: manual barcode counting (find each item, scan each item) typically costs 2 people × 4 hours. An RFID handheld sweep takes 1 person × 30 minutes. With fixed portals in place, auditing becomes exception handling — only the "expected but not read" list needs human eyes. That is not an incremental improvement; it is a change in the cost structure of auditing.
Going deeper
Once asset tracking is running, the next question is the link to depreciation and the asset module — how the "in use" state confirmed by RFID should influence accounting-side depreciation and disposal decisions. SpidersRFID publishes a deeper companion article on that: odoo-rfid-asset-depreciation-module, covering how the asset depreciation module connects to RFID state.
Frequently asked questions
**Can Odoo Community edition do RFID asset tracking?** Yes. Loans and audits run on the inventory model plus a custom or integrated model, and middleware writes through the public XML-RPC/JSON-RPC APIs with identical behaviour on Community 17-20 and Enterprise — no Enterprise-only features required.
**Which tags fit assets?** Metal surfaces require anti-metal tags (USD 0.30–1.00 each); plastic housings work with standard inlays; returnable containers take low-cost standard tags. Medical devices need models rated for sterilisation cycles.
**Should accounting assets and physical tracking stay separate?** Yes. Depreciation is a function of time, not of physical location; RFID serves physical presence and loan state. Link the two by asset number and sync state changes as needed — never let RFID write depreciation fields.
