Connect the shop floor to Odoo, not to a spreadsheet.
Barcode scanners, RFID readers, label and document printers, scales, payment terminals, PLCs, and production equipment — integrated with Odoo so a physical event becomes an ERP record without anyone retyping it.
What we connect
Device support is about the integration behind it: what the device emits, which Odoo record it should change, and what happens when the network or the device is not there.
Barcode scanners
Handheld, wearable, and fixed-mount scanners driving picking, receiving, work order steps, and quality checks. USB-HID, Bluetooth, and network-attached devices.
RFID readers
Fixed portals and handheld readers for pallet-level moves, asset and tool tracking, and access or attendance logging where item-level scanning is too slow.
Printers
Thermal label printers and laser document printers driven directly from Odoo — no browser print dialog between the operator and the label.
Scales and measurement devices
Weight captured into receipts, deliveries, production consumption, and point of sale, with the reading recorded rather than transcribed.
Payment terminals
Card terminals paired with Odoo point of sale and invoicing flows, so the transaction and the accounting entry agree.
PLCs and manufacturing equipment
Machine signals — cycle complete, fault, counter, sensor state — turned into work order progress, quality records, or maintenance triggers.
A gateway on your network, not a cloud round trip per scan
Devices talk to a gateway on the local network. The gateway speaks Odoo. That keeps scan latency local and keeps the line moving when the internet does not.
What happens inside Odoo
- Events mapped to records
- A scan, a weight, or a machine signal is mapped to a specific Odoo operation — not dropped into a free-text field for someone to interpret.
- Station-aware routing
- The same barcode means different things at receiving and at final assembly. Devices are bound to stations, and stations to operations.
- Validation at the scan point
- Wrong part, wrong quantity, wrong sequence, or an unmet quality gate is rejected where the operator can still fix it.
- Offline tolerance
- The gateway queues events locally and reconciles when Odoo is reachable again, so a network blip does not become a production stoppage.
- Print routing
- Reports go to a named printer chosen by user, station, or warehouse, with label formats defined per device class.
- Traceability
- Device identity is recorded with the transaction, so an operation can be traced back to the station and reader that produced it.
The part most ERP projects underestimate
Most hardware problems are not software problems. They are cabling, power, network segmentation, driver versions, and a reader mounted where it cannot see the tag. We treat that as part of the work.
One station first, then the plant
Survey
Walk the process, list the devices, and identify where data is being retyped today.
Pilot station
One station wired end to end, on a staging Odoo environment, with the real operators.
Harden
Handle the failure cases the pilot exposes: bad reads, offline periods, and wrong-sequence attempts.
Roll out
Replicate the proven configuration across stations, with device health visible in monitoring.
Your device is not on the list?
If it exposes a protocol — serial, TCP, HTTP, Modbus, OPC UA, or a vendor SDK — it can usually be integrated. Tell us the device and what it should change in Odoo.