Skip to main content
Zuply and Vendo integration for smart vending machines – Software & Integrations
Case study

Zuply and Vendo integration for smart vending machines

Software & Integrations IoT / Vending Active December 2023

Integration of a new Vendo vending machine into existing vending software, with real-time visibility into dispensing events, errors, and stock through the Zuply platform.

What we delivered

A mix of strategy, design, and engineering that shortens the path from idea to working solution.

Skills

Project management Hardware integration Hardware ⇄ Software architecture Stakeholder coordination

Technologies

Python JavaScript TypeScript Vue PHP Raspberry Pi Buddy Docker

Project overview

For this project, I worked on integrating a new Vendo vending machine into existing vending software and the broader Zuply platform. The machine needed to do more than dispense products. It also had to support smart vending functionality such as analytics, remote management, and embedded marketing tools around the vending experience.

My main contribution was connecting the vending UI software to the new Vendo hardware so machine events, error messages, and stock updates could flow correctly into the software layer and the dashboard behind it.

Collaboration

This project brought together multiple parties: Quiosk as the client, Zuply on the hardware side, and Innovend on the software side. I worked across developers and stakeholders while building the connection between the Vendo controller, the Raspberry Pi, and the existing software environment.

That made the project more than a technical integration. The solution had to fit an existing product setup without making day-to-day machine behaviour or supplier collaboration unnecessarily complex.

The business challenge behind the work

The practical challenge was clear: how do you add a new type of vending hardware to existing vending software without rebuilding the whole product? For machine owners, that meant a broader hardware choice. For customers using the machine, the experience still had to feel clear, reliable, and familiar.

So the value was not only in connecting one machine. It was in expanding the platform with a wider hardware range that could still operate inside the same software and management structure.

What I worked on

  • Integration of the Vendo machine with the existing vending UI software.
  • Connections between machine events, stock, error codes, and the cloud platform.
  • Alignment between hardware behaviour, the user interface, and the backend.
  • Coordination across the involved parties to keep the integration practical to deliver.

Technical implementation

  • Python microservice on the Raspberry Pi to pass machine-controller signals into the software layer.
  • PHP backend for transactions, error handling, and synchronization with VendingWeb.
  • Vue, JavaScript, and TypeScript for the vending interface used by customers and operators.
  • Cypress tests for key UI flows and error handling.
  • Buddy CI/CD with controlled rollout per machine.

Challenges

  • Limited documentation around the Vendo integration, so protocol behaviour had to be confirmed through testing and direct contact.
  • The new machine had to fit existing hardware and software flows without disrupting other parts of the product.
  • Coordination across multiple parties and suppliers during development and rollout.

Result

  • Support for Vendo machines within the existing platform.
  • Real-time visibility into dispensing events, stock, and errors.
  • Smoother integration with the existing vending software.
  • Easier remote monitoring and management for machine owners.
  • A production-ready base for rolling out this hardware type further.

Inspired by this project?

If you see similar friction or growth potential in your own business, we can translate this into a practical roadmap for you.

Other projects