Odoo IoT: Devices, Triggers, and Shop Floor Connections

Introduction

Odoo IoT amplifies the rest of the suite: dashboards, documents, Studio, and IoT only create value when sales, stock, and finance data is already trustworthy.

Teams adopt Odoo for transactions first, then ask for better insight and tailored screens, which is where platform apps and careful customization enter.

IoT helps leaders and power users shape how information is presented and accessed without breaking the core data model underneath.

COOs, product owners, and internal Odoo champions evaluating the next layer of maturity will see when to extend standard apps versus when to call for expert help.

IoT is part of Odoo's modular ERP. Teams adopt it when they want clear responsibilities, repeatable workflows, and searchable history instead of isolated messages and offline spreadsheets. Odoo IoT: Devices, Triggers, and Shop Floor Connections states the storyline for stakeholders approving budgets.

This article is a ranked Top 10 from Level 1 (easy) to Level 10 (expert). Every level includes numbered steps: what you would actually click in Odoo IoT.

Start where you are comfortable, not at level 10 because it sounds impressive.

Read the challenge section next, then open the level that matches your team today.

In this guide, you will see:

• What Odoo IoT is responsible for in a typical company stack
• Where teams feel the most friction today (and why)
• Ten ranked use cases from beginner discipline to advanced strategy
• When automation or integrations justify bringing in an Odoo partner

The Challenge

Leadership opens a beautiful dashboard, then asks why the cash number does not match accounting. Someone built a view on incomplete data, and now every meeting starts with trust issues, not decisions.

Leaders want insight and tailored processes, but data and customization sprawl without governance. Dashboards and Studio changes only help when they sit on reliable transactional data.

Sound familiar? Teams usually hit these walls:

• KPIs that do not match operational reality
• Customization without sandbox discipline
• Integrations that break silently after upgrades

The good news: you do not need a big-bang project to fix everything. Pick one use case below, run it for 30 days in Odoo IoT, and measure what changes.

Top 6 IoT Use Cases

6 use cases for Odoo IoT, ranked from Level 1 (easy, do it this afternoon) to Level 6 (expert). Each one answers: what would we build, and what are the clicks in Odoo?

Level 1 is the easy starter. The last level is the ambitious scenario you might dream about but rarely build alone.

Pick your level, follow the numbered steps in a test database, then move up when the previous level feels boring.

1. Connect your first IoT box and print a receipt from Point of Sale Level 1 — Easy

Level 1 is the simplest possible IoT action: one box, one printer, one POS receipt. No automation, no triggers, just a physical device that finally talks to Odoo.

Here's how you'd do it in Odoo:

1. Plug the Odoo IoT Box into power and Ethernet, then connect a USB receipt printer to it.
2. Open the IoT app, IoT Boxes, click your box, and verify the printer appears under Devices.
3. Go to Point of Sale, Configuration, Point of Sale, open your shop, and set the Receipt Printer to the IoT device.
4. Launch a POS session, close a small sale with one product and cash payment, and confirm the receipt prints automatically.
5. Check the IoT app, Devices, to see the printer status and the last activity timestamp.

What you get: Your cashier prints a receipt with one click instead of plugging a printer into every till, and the device status is visible from Odoo on day one.

2. Add a USB barcode scanner to speed up warehouse picking Level 2 — Easy

Level 2 introduces the most common warehouse IoT device. A USB scanner replaces typing product references and removes the most frequent picking mistake on the floor.

Here's how you'd do it in Odoo:

1. Plug a USB or Bluetooth barcode scanner into the IoT box already paired with the warehouse PC.
2. In the IoT app, open the box, confirm the scanner is listed, and assign it the role Barcode Scanner.
3. Print product barcodes from Inventory, Products by selecting a product and clicking Print, Labels.
4. Open Inventory, Operations, Transfers, pick a delivery, and scan each product to validate the line.
5. Watch the picking screen auto-confirm quantities, finish with Validate, and the transfer closes in one click.

What you get: Pickers move twice as fast with fewer wrong-product errors, and the system stays in sync without keyboard input on the warehouse floor.

3. Capture a precise weight automatically inside a quality check Level 3 — Medium

Level 3 wires a measurement device to Quality. A digital scale streams the weight directly into the quality control point so operators never write numbers on paper again.

Here's how you'd do it in Odoo:

1. Connect a serial or USB scale (Mettler Toledo, Adam, Dini) to the IoT box and confirm it under IoT Devices.
2. Install the Quality app, then go to Quality, Configuration, Control Points, New.
3. Set Product Category or Operation Type, choose Measure as the Test Type, and pick the scale under Device.
4. Set Norm to the target weight with a tolerance band (for example 500 grams plus or minus 2).
5. Run the operation: place the item on the scale, the value is captured, and Pass or Fail logs to the record.

What you get: Every produced unit gets a real measured weight on file in seconds, and a deviating batch is caught at the workstation instead of by a complaining customer.

4. Take a quality control photo from the workstation camera Level 4 — Medium

Level 4 plugs a webcam into the IoT box and turns the manufacturing work order into a visual paper trail. The picture lands on the chatter of the production record, time-stamped and immutable.

Here's how you'd do it in Odoo:

1. Plug a USB webcam (or IP camera) into the IoT box and check it appears under IoT Devices as a Camera.
2. In Quality, Configuration, Control Points, create a Take a Picture check on the Final Assembly operation.
3. Open Manufacturing, Operations, Work Orders, and start the next work order on the shop-floor screen.
4. When the quality step opens, click Capture: the IoT camera shoots, and the file attaches to the MO chatter.
5. Review the picture from the office: Quality, Quality Checks, filter by Failed to audit any rejected unit.

What you get: Defect investigations stop being a he-said-she-said exercise because every finished unit ships with a dated photo proving what left the line.

5. Drive an Andon signal lamp from a workstation status Level 5 — Hard

Level 5 turns the IoT box into an output device. A three-color lamp at the work center reflects the machine state live so the supervisor sees a problem from across the floor instead of waiting for a phone call.

Here's how you'd do it in Odoo:

1. Wire a three-color signal lamp (green, yellow, red) to the IoT box GPIO or to a USB relay module.
2. In the IoT app, open the device, set its Type to Output, and label each color with a Trigger Name.
3. In Manufacturing, Configuration, Work Centers, edit the station and link IoT Triggers per state: Running, Idle, Blocked.
4. Add a Maintenance request rule: when the lamp turns red, create a request assigned to the maintenance team.
5. Test by pausing a work order: the lamp turns yellow; mark a breakdown: it turns red and a maintenance ticket appears.

What you get: Supervisors spot a stopped station in seconds, maintenance is dispatched without a radio call, and you start measuring downtime by station instead of guessing.

Wiring GPIO outputs, designing work-center state machines, and linking IoT triggers to Maintenance is the kind of cross-app setup Dasolo runs as a partner-led engagement.

6. Run a smart factory with MQTT sensors, predictive maintenance, and a live OEE dashboard Level 6 — Expert

Level 6 is the full operating system: MQTT vibration and temperature sensors feed Odoo IoT, anomaly detection triggers maintenance and field service, and a real-time dashboard shows the whole plant in one view.

Here's how you'd do it in Odoo:

1. Deploy MQTT sensors (vibration, temperature, current) on critical machines and connect them through the IoT box broker.
2. Configure thresholds per equipment: sustained vibration above the band generates a Maintenance Request with sensor data attached.
3. Critical alerts open a Field Service task, route the closest technician via Planning, and notify the manager by Discuss.
4. Studio adds MTBF and Availability fields on Equipment; values are computed from IoT events and refreshed every minute.
5. An AI service consumes the MQTT stream, flags anomalies before they cross thresholds, and posts a predictive alert with confidence.
6. A Spreadsheet dashboard tracks OEE, downtime by cause, sensor health, and predicted failures, refreshed live for the morning stand-up.

What you get: Unplanned downtime drops sharply because problems are caught hours before they break the line, and management sees one live picture of the plant instead of waiting for end-of-shift reports.

Designing the MQTT topology, the anomaly rules, the IoT to Maintenance to Field Service handoff, and the live OEE dashboards is the architecture Dasolo designs as a partner-led smart-factory engagement. Most teams need an outside team to assemble these pieces correctly the first time.

When Expert Help Makes Sense

If levels 1 to 4 fit your world, you can often succeed with standard Odoo IoT, a patient internal owner, and a sandbox where people are allowed to break things safely.

From level 5 upward, the stakes rise: automated workflows that email the wrong customer, Studio fields that block upgrades, APIs that silently stop syncing stock at 2 a.m.

That is not a failure of your team. It is a signal that architecture, testing, and governance matter.

Bring in a partner when you need multi-app design, country-specific compliance, complex integrations, or a go-live date the board already put in the calendar.

Work With Dasolo

Dasolo helps companies implement Odoo the way they actually work: custom apps, clean integrations, and training people will remember after the consultants leave.

If your roadmap for IoT includes the advanced use cases in this guide, we can map a phased plan: quick wins first, then automation and integrations with clear owners and test scripts.

You keep control of scope and budget. We bring the Odoo depth so your team does not learn expensive lessons in production.

Book a free consultation:

Schedule your demo