Configurable hospitality software should fit the operation

Hospitality businesses do not all run the same way. One operator may already trust its accounting platform. Another may have an accounts-payable process it is not ready to replace. A third may want purchasing, inventory and finance managed more closely together.

Technology becomes disruptive when implementation starts with a prescribed process rather than the operation that already exists.

Aaron Resch summarised the alternative:

“We want to be able to say to a customer, we understand and we will flex to you and your operation. That's the key.”

Configurable needs to mean something concrete

Configurability is not a longer settings screen. It means the product can reflect relevant differences between operations, including site structures, departments, approval routes, product libraries and the systems that hold financial or sales data.

The aim is to preserve what already works while improving the gaps between it. Sometimes that means connecting Hops directly to another product. Sometimes it means using the Hops Connect Gateway to move data between two external systems. In other cases, the right answer may be to change the process rather than reproduce it.

Flexibility still has technical boundaries

The original LinkedIn post used the phrase “integrate with anything”. Our current position is more precise. New connections depend on an accessible API, usable data and technical feasibility. That qualification matters because a promise is only useful when it can be implemented and supported reliably.

The principle remains the same: software should support how the operation runs rather than force every operator into one prescribed workflow. Explore Hops Connect to understand integrations and the Gateway, or see customer examples of Hops across different hospitality businesses.

View the original LinkedIn post: Hops' configurability post, published 24 July 2026