Odoo IoT Box: what can it do and what can't it?

What the IoT Box actually is

The Odoo IoT Box is intended as a practical bridge between Odoo and a selection of physical devices. Think of printers, scanners, payment terminals, measuring equipment, and some scales that fit within Odoo's supported scenarios. For an office, reception, warehouse post, or simple production task, this can be very useful.

The power lies in simplicity. If the device fits into the standard route, Odoo can, for example, print a label, retrieve a weight, or support an action at the workplace without someone manually retyping data. For companies already working with Odoo, this feels logical: fewer separate actions and less chance of errors.

But the name IoT Box sometimes raises expectations that reality does not fulfill. Many production managers read "IoT" and think of machines, PLCs, Modbus, MQTT, OPC UA, energy measurement, fault status, and current production planning. That is exactly where you need to be sharp in advance. The standard IoT Box is not a general machine integration layer for every factory.

Which devices work directly

The easy cases are devices that Odoo recognizes or for which the standard flow already exists. A supported label printer at a workstation, a barcode handling in inventory, or a scale that falls within the known Odoo route can quickly deliver value.

Take a packing station where an operator currently does three things separately: searching for an order in Odoo, overwriting weight from a table scale, and then printing a label. If the used scale and printer fit into the standard route, Odoo can request the weight, link the result to the action, and directly print the correct label. With 80 packages per day and 45 seconds less manual work per package, that saves about 60 minutes per day.

These are the situations in which the IoT Box fits well: defined actions, supported hardware, little process logic, and a direct action at a workstation. Then you should especially not make it too complicated.

What the IoT Box does not do

The limitation becomes visible as soon as the question changes from device control to real shop floor data. A production machine does not automatically talk to Odoo just because there is an IoT Box nearby. And much equipment in factories was never purchased with a modern data layer.

Modbus, MQTT, and OPC UA are the comfortable cases in such a project: if a machine already has them, we are happy to use them. But they only exist on machines that were ever delivered with such an interface or were later professionally upgraded. For older machines, retrofitting a modern control interface is often expensive, technically challenging, or impossible within warranty or certification.

Therefore, Linky Business does not treat a protocol as a condition. Our rule is: if a device produces a readable signal, we can connect it. We can work with categories such as digital and analog I/O, relay and contactor contacts, limit switches, light screens, and power consumption with a clamp around an existing cable. The machine itself is not modified, warranty and certification remain unaffected, and cooperation from the machine builder is not required.

That is indeed a different field than Odoo configuration. You need to be able to read an electrical diagram, work safely in a control cabinet, and understand which existing signal has business significance. That is exactly the part that an ERP partner who only provides software usually does not deliver. Those who only work on the Odoo side often realize too late that the machine has no ready-made interface at all.

More about that broader approach can be found on our page about machine connectivity with Odoo.

The subscription costs that people forget

In addition to the technical boundary, there is a commercial boundary. The Odoo IoT Box requires a subscription component for production use. That doesn't have to be a problem if you connect a few supported devices and the business case is clear. It becomes important once you think in terms of ten, twenty, or thirty connections on the shop floor.

Suppose a company starts with two packaging stations and later wants to expand to twelve workstations or machines. Then the choice should not only be about the purchase price of hardware but also about recurring costs, management, and whether each additional connection incurs a monthly fee again.

The monthly amount at Linky Business is intentionally low and fixed: a fixed amount per location for the gateway and a fixed amount per additional node. Customization costs more at the beginning, depending on the complexity, but the monthly amount does not change as a result. The current rates are on the pricing page.

Example: a lathe from 1995 next to a label printer without a network port

A realistic first project does not have to be large. Take a metal company with two problems: a lathe from 1995 without a digital machine interface and a label printer without a network port at the shipping table. Operators register work orders too late and sometimes retype label information.

On paper, a recurring operation is set at 45 minutes. After the connection, it turns out from twenty repeat orders that the effective operation takes an average of 57 minutes. That difference of 12 minutes per order is 240 minutes per month, so 4 hours of capacity that was not previously in the planning.

The chain remains commercially simple: a readable machine signal comes through the Linky gateway to Odoo, Odoo stores the actual start and stop time with the work order, and the planner adjusts the routing time before the next order is scheduled. At the shipping table, Odoo sends a print job to the local label printer from the same order context, even though that printer itself has no network port.

The decision changes as a result. Sales no longer calculates with an overly optimistic processing time, planning sees four hours of extra monthly load in the same product family, and shipping prevents double entry. This is not a dashboard to look at, but operational data that causes a concrete action.

This type of machine connections with existing equipment fits the approach we describe on connecting machines, devices and sensors to Odoo.

When a Linky Business gateway is smarter

A Linky Business gateway is especially smarter when the demand is broader than a supported peripheral. Think of a PLC that can provide data via Modbus, a machine park with mixed ages, a label printer without a network, an RFID port, a compressor, a door contact, or a sensor that needs to block a quality control.

Where a protocol exists, that is the easy route. Where it is lacking, raw I/O often remains the approach that saves the business case. A machine from the nineties can still start and stop a work order in Odoo, as long as there is a relevant and readable signal. You do not replace the machine; you translate what the machine is already showing into information that Odoo can use.

Another advantage is direction back to the shop floor. Odoo can not only register but also trigger an action: printing a label, changing a lamp status, querying a weight, or prompting an operator to act at the right moment. This requires an integration layer that understands both the ERP logic and the physical environment.

Decision flowchart: IoT Box or industrial gateway?

Use the IoT Box when the device is supported, the action is standard, and you mainly want to simplify an Odoo workspace. For a known printer, a simple counter action, or a supported scale, that can be the shortest route.

Choose an industrial gateway when you want to connect machines, PLCs, sensors, older equipment, or multiple workstations. Also choose that route when the data needs to not only be displayed but also directly influence work orders, scheduling, maintenance, quality, or shipping.

The practical question is therefore not: can the IoT Box do anything? Yes, certainly in the right situation. The better question is: does your process fit within the standard list, or does Odoo need to be connected to the reality on the floor?

What a first step usually involves

A wise first step is small and measurable. For many manufacturing companies, that is a two-machine pilot with about two weeks until the first real data in Odoo. For example, an older machine without a protocol and a workplace device like a table scale or label printer.

The scope should be concrete: which two devices, which Odoo registration needs to be reliable, which decision needs to be improved, and which reporting is sufficient to assess the business case. After a technical quick scan, such a pilot can be defined at a fixed price.

After that, the follow-up question is simple: expand to more machines, first correct routing times, or choose a second process such as shipping, quality control, or maintenance. This way, you avoid an abstract digitization process and start with data that directly changes something.

Conclusion

The Odoo IoT Box is useful when you stay within its standard world: supported devices, clear workplace actions, and limited complexity. That is what you should use it for.

For manufacturing companies, the real issue often begins afterwards. Machines have no protocol, devices are outside the supported list, costs accumulate per connection, or Odoo needs to not only read but also send back to the shop floor.

Then the Linky gateway is not a luxury, but a practical way to make existing equipment usable in Odoo. If you want to know which route fits your situation, start with the devices that are already there and the decision that needs to be improved. More background is on our page about machine connectivity.