What OPC UA is and why machine builders use it
OPC UA is an industrial standard that allows machines, PLCs, and software systems to exchange structured data. Instead of loose measurements without context, a machine can offer values with names, types, and hierarchy. This is attractive for machine builders because the same machine can then communicate with different systems without having to build a separate connection for each customer.
For a manufacturing company, that sounds logical: if the machine speaks OPC UA, Odoo should be able to see what is happening directly, right? In easy cases, that is partially true. A modern machine can, for example, offer status, counter readings, alarms, or production values. An industrial gateway can use those values to bring Odoo closer to the shop floor.
But OPC UA is not a guarantee that the right business information is available. A machine can publish hundreds of tags while the planner only has three questions: has the order really started, is the operation finished, and does the actual time deviate from the standard? The value is therefore not in the number of tags, but in the translation to a usable Odoo record.
What Odoo can do with this and what you should not promise
Odoo is strong in work orders, planning, inventory, quality, and maintenance. When machine information is reliably captured, ERP becomes much more practical. Operators need to type less afterward, planners see earlier where capacity shifts, and maintenance can be based on actual load instead of just calendar days.
The mistake occurs when OPC UA is sold as if it automatically provides a complete Odoo machine connection. It does not. A protocol can make data accessible, but it does not automatically determine which data is business-critical, which registration in Odoo is needed, and what action should follow.
Therefore, a good project does not start with the question of how many OPC UA tags there are. It starts with the question of which decision is being made too late today or based on incorrect assumptions. More about that broader perspective can be found on our page about machine connectivity with Odoo.
Tags, subscriptions, and write-back: useful, but not automatic enough
OPC UA can enable reading, tracking, and in some cases, writing back. In plain language: a system can retrieve values from a machine, track changes, and sometimes return a command. This is useful, especially when the machine builder has documented the interface well.
However, write-back is something to handle carefully. A command from Odoo to the shop floor affects planning, safety, operators, and responsibility. Not every request should go back to the machine. Sometimes an Odoo action is sufficient, such as preparing a quality check, opening a maintenance task, or alerting a planner that a work order is structurally delayed.
Linky Business uses protocols like OPC UA where they fit, but does not present them as a ticket. The connection must be reliable enough for daily use, clear enough for operations, and limited to data or actions that truly have business value.
Where it goes wrong in practice
In practice, it often goes wrong at three points. The machine has OPC UA, but the available tags are mostly technical and not directly usable for planning. The machine has OPC UA, but only on an option card or software license that was never purchased. Or the machine has no modern protocol at all, because it is fifteen, twenty, or thirty years old.
Retrofitting a modern control interface on such a machine is usually expensive, sometimes impossible, and often dependent on the machine builder. That is exactly why you should never present OPC UA as a requirement. Modbus, MQTT, and OPC UA only exist on machines that were purchased with that capability or were later intentionally upgraded.
For a software-only ERP partner, that quickly becomes a limit. They can configure Odoo, but usually cannot safely assess what is happening electrically in a control cabinet. In machine coupling, someone must be able to read the electrical diagram, work inside the cabinet, and know which signal has operational significance.
If OPC UA is missing: why raw signals are often the surest route
If OPC UA is available and usable, that is the simple route. If it is missing, the project does not have to stop. Linky Business then looks at readable signals that the machine is already producing: digital and analog I/O, relay and contactor contacts, limit switches, light screens, sensor outputs, and power consumption on an existing cable.
This keeps the machine itself untouched. Nothing is modified in the machine, warranty or certification is not affected, and the machine builder does not need to cooperate. If a device produces a readable signal, we can link it to the information needs in Odoo.
That is also the reason why a machine from the nineties can still start and stop a work order in Odoo. Not because the machine suddenly becomes modern, but because the existing reality on the shop floor is made usable for ERP. See also how Linky Business connects machines, devices, and sensors with Odoo.
Example: modern cell with OPC UA next to a lathe from 1995
Take a metal company with two machines in the same schedule. The modern processing cell has OPC UA and provides a reliable indication of production progress. In addition, there is a lathe from 1995 without a digital protocol towards ERP. Both machines cause the same problem: the actual runtime comes too late in Odoo, causing planning to calculate with overly optimistic times.
After the connection, Odoo sees that for 34 work orders per week, a recurring operation does not take an average of 50 minutes, but 63 minutes. That difference of 13 minutes per order is 442 minutes per week, so over 7 hours of capacity that was previously invisible. The planner uses that information to correct the routing and promises the next series with more realistic capacity.
The chain remains commercially traceable. In the modern cell, the usable machine status reaches the Linky gateway via OPC UA. For the lathe, the status comes from existing readable signals. Odoo records start, stop, and result with the work order. The decision is concrete: planning adjusts the standard time, maintenance sees actual running hours, and sales does not sell delivery times based on outdated assumptions.
The most important point is not which machine has the best protocol. The point is that both machines end up in the same Odoo reality. The modern machine via the easy route, the older machine via the route that works when no protocol exists.
What a first step concretely entails
A wise first step is small. Choose one machine where OPC UA seems available and one older machine where only existing signals are usable. In a two-machine pilot, you can immediately see if the promised data is really available, which Odoo registration has value, and which decision is improved as a result.
Expect about two weeks for such a first step until the first real data in Odoo, after a technical quick scan and with a fixed price for the agreed scope. Linky Business also works with a low, fixed, and predictable monthly fee per location for the gateway and per additional node. Customization at the beginning may vary by situation, but does not increase the monthly fee due to complexity. The current rates are on the pricing page.
The gateway and nodes are provided by Linky Business as part of the subscription. The customer owns their own machines, their own data in Odoo, and the results. Support, expansions, and changes can be agreed upon separately. This keeps the first step clear without pretending that industrial connections remain free after delivery.
Conclusion
OPC UA can be an excellent basis for Odoo machine connection. When a machine builder has set up the interface well, it is often the fastest route to usable shop floor data.
But OPC UA is not a promise that you should sell blindly. It does not automatically mean that the right tags are available, that write-back is sensible, or that older machines are out of scope. For many companies, the mix of modern and old is the daily reality.
Therefore, the practical question is not: does this machine speak OPC UA? The better question is: which signal is readable, which Odoo record becomes more reliable because of it, and which decision will be made better tomorrow?
Do you want to be sure what OPC UA really delivers for your machine?
Linky Business assesses the machine, the signals, and the Odoo process and makes the first connection concrete.