Integrations
The depth your machine allows
Any machine with an MDB bus, with two levels of control, plus an API for manufacturers and integrators. We review it before promising anything.
Three ways to connect
An ecosystem for the operator: from their phone, the customer gets every service the operator runs. The machine can connect by MDB or by board; the customer sees the same thing. What changes is how deep the panel goes. Pulse connection is in development.
TCN with board control
On TCN equipment with its own Android screen we replace the factory interface: prices, planogram, temperature alerts and error diagnostics from the panel.
Standard MDB
Sale, payment and transaction data over your machine’s standard MDB bus, without deep access to the board.
API
For manufacturers and integrators who want to connect their own hardware, their own panel, or an external delivery channel.
How we decide which depth applies
Compatibility isn’t promised in the abstract: it’s reviewed against your equipment’s manufacturer, protocol and architecture.
A TCN machine with its own Android screen supports the highest level of control because the interface runs on the machine itself. A machine with standard MDB supports sale, payment and transaction data, but not board control.
For manufacturers who want to build on top of uNobo Connect, the route is the API: it defines what data goes in and out, and which part of the flow stays in their own panel.
Frequently asked questions
How do I know which integration applies to my machine?
Tell us the manufacturer and the model. We review the protocol it uses and tell you whether TCN, MDB, or the API is the right route.
Is the API publicly documented?
Technical documentation is shared with manufacturers and integrators during the compatibility review, not on this site.
We’ll review your compatibility
Manufacturer, model and protocol: that’s enough to get started.
Tell us your case