Odoo Integration
RFID data is only useful once it lands in the ERP. These articles cover Odoo integration patterns — middleware architecture, XML-RPC and JSON-RPC interfaces, inventory model changes, idempotency and data governance.
Articles in this topic
RFID across multiple Odoo companies and warehouses without losing control
Shared readers, company-scoped data, inter-company transfers and the tag identity rules that stop a multi-entity RFID rollout from corrupting stock records.
Customer Behaviour Analytics with RFID: What the Fitting Room Actually Tells You
Item-level RFID observes garments, not shoppers. The useful question is not who walked in, but which item was carried to a fitting room and did not come out as a sale.
Work Order Reporting with RFID: Report Events, Not Optimistic Percentages
A work order is a claim about time, quantity and who did the work. RFID can supply two of the three well, and the third only if the identity binding is honest.
Usage-Based Depreciation in Odoo: Where RFID Data Legitimately Fits
An RFID read is not a depreciation entry. What it can do is evidence: which assets are idle, which are running hard, and which have disappeared entirely.
Electronic Shelf Labels and Odoo: The Coordination Is the Project
A light on a shelf saves searching time, not walking time. What decides the return is how Odoo batches orders, maps pick faces and handles the confirmation step.
RFID Drones Over High-Bay Racking: Fly a Mission, Not a Photo Pass
A drone over high-bay racking produces observations, not stock levels. The difference between a useful pilot and a shelved project is whether the flight, the pose and the snapshot are modelled before the ERP is touched.
Inventory Robots and Odoo: Sync a Reconciliation, Not a Number
A robot that counts a thousand locations a night produces a variance report, not an inventory truth. Whether Odoo ends up trusting it depends on how the sync models position, time and uncertainty.
Odoo and RFID Access Control: Integrate Entitlements, Not Just Badges
Access control is an authorization process that happens to end at a door. When Odoo owns the roster and the door owns the decision, the integration is a policy pipeline with an audit trail — not a nightly spreadsheet that grants a contractor six extra weeks.
Handheld Batch Import into Odoo: Design the Import Before You Design the Scanner
A handheld that collects counts offline is easy to buy and hard to trust. The difference is whether the import is designed as a staging pipeline with idempotency, timing and conflict rules, or as a CSV someone uploads on Monday morning.
Wiring an Impinj R700 into Odoo Without Making Odoo a Reader Driver
The R700 is a Linux computer with an antenna, not a serial peripheral. That changes the integration architecture: the reader owns its state, the middleware owns the semantics, and Odoo owns the inventory. Mixing those three responsibilities is the usual failure.
AGV and Odoo integration with RFID: scheduling, handoffs and exceptions
How RFID verifies what an AGV actually moved, how to model transport jobs in Odoo, and why the exception path decides whether the fleet is trusted.
Event-Driven Inventory in Odoo: Making MQTT Subscriptions Production-Grade
Forty fixed readers, six handhelds and two portals all publish into one broker. The difference between a working pilot and a working plant is not the broker choice — it is the event contract, the subscriber process, duplicate handling and the ability to prove the pipeline is alive at 3 a.m.
Writing RFID Counts into Odoo: From stock.inventory to stock.quant Adjustments
The count is the easy half. The hard half is turning a stream of EPC reads into a defensible stock adjustment: deterministic matching, expected-versus-counted arithmetic that respects reservations, batch writes that do not deadlock, and an audit trail accounting will accept.
Odoo and Zebra Fixed Readers: Standardise on LLRP, Use the SDK Sparingly
A Zebra FX9600 on an Odoo site is not a plug-in. The durable integration uses LLRP for configuration and reporting, wraps the vendor SDK only where it adds value, filters and deduplicates before the ERP, and treats time synchronisation as an inventory problem. Architecture and field notes.
Odoo 17 Community RFID Module: A Small Module Beats a Big Fork
Community edition has no IoT Box, and that is fine. A compact custom module — three models, inherited views, two ACL groups, one controller and a cron — connects an RFID gateway to stock.quant without forking inventory. Structure, security and upgrade discipline.
MQTT Between the Reader and Odoo: A Broker Is Infrastructure, Not a Solution
HTTP polling saturates the ERP and loses events under jitter. MQTT decouples readers from business logic — but only if the topic tree is treated as a contract, QoS is chosen deliberately, and the bridge owns deduplication, backpressure and replay. A practical design guide.
Odoo stock.quant and RFID: The Gateway Is the Product
Readers emit thousands of duplicate tag events per second; Odoo writes one row per quant and deadlocks under concurrency. The durable answer is a gateway that parses EPCs deterministically, deduplicates in time windows, aggregates into deltas and applies them idempotently. Architecture, field mapping and the failure modes nobody documents.
Dense Reader Deployment: Making Twenty Readers Behave Like One System
Adding readers to an RFID site does not add capacity linearly: past a certain density, readers interfere with each other, tags are drowned by neighbouring antennas, and the whole installation reads worse than a third of its size. Dense deployment is a coordination problem, and coordination has to be designed.
RFID Outdoors: Designing for Rain, UV and the Storm That Ends the Pilot
An indoor RFID design taken outdoors fails in ways the datasheet never mentions: UV embrittles the housing, condensation forms inside a sealed box, and a nearby strike takes out three readers at once. Outdoor deployments succeed when protection is designed as a system rather than bought as an IP rating.
RFID Data Quality Governance: Why Your Inventory Is Only as Good as the Pipeline
RFID produces observations; an ERP needs assertions. The gap between them is where inventory accuracy dies. A practical governance framework covering the four defect classes, deduplication rules, edge versus core validation, exception workflow and the metrics that prove the pipeline is healthy.
RFID + ERP/WMS Integration: Where the Value Is Won or Lost
The readers work and the tags read at 98 %, yet month-end still produces inventory adjustments nobody can explain. Almost every non-physics RFID failure is an integration failure. Here is how to split the layers, choose the pattern and avoid the shortcuts that break Odoo, SAP and Yonyou.
RFID Middleware Architecture: Where Devices End and Business Logic Begins
Middleware is the part that turns a stream of read events into a defensible business record. Architecture, buffering, filtering, deduplication and replay decide whether the ERP sees the truth or a traffic jam.
RFID and IoT Convergence: From an Island Reader to a Data Backbone
A reader on the network is not a sensor in the platform. The distance between identification and infrastructure is architectural: four layers, one event contract, latency budgets per hop, and five anti-patterns that quietly cost more than the hardware.