Integration roles
Your software can be a POS, marketplace, middleware, ordering channel or delivery software, combining several roles. This describes what it does; it does not automatically make it an operator.
Commercial model
The Operator represents the restaurant in OpenQloud, acts on its behalf and covers its service consumption. Software integrations operate with independent permissions.
Your software can be a POS, marketplace, middleware, ordering channel or delivery software, combining several roles. This describes what it does; it does not automatically make it an operator.
Each location has one Operator. Any ecosystem player can cover one or several restaurants. Authorized systems work with the location without thereby becoming its operators.
What OpenQloud charges for
The infrastructure maintaining data and connections for restaurants in your network.
Use of OpenQloud services to exchange orders and coordinate connected systems.
Some providers apply their own charges. Their charges and terms are disclosed before activating the connection.
We agree the scope, billable concepts and payment arrangements with you. Project volume and commitment can qualify for specific terms. Third-party charges are identified separately.
Contact us →The company authorized to represent a restaurant in OpenQloud, act on its behalf and cover its service consumption. It can be the restaurant owner or a delegated provider. Operator is not a software category.
No. Integrating software and covering a restaurant's usage are independent decisions. You pay only for locations for which you accept the Operator responsibility.
Yes. One Operator account can cover several locations. Each location has one Operator, even when several software providers connect.
Someone authorized to onboard it and assign an Operator accepting its usage. This can be the Operator or an authorized third party. Being middleware or POS does not automatically grant that permission.
Payment alone does not grant access. The Operator acts under the restaurant’s authorization; its users and integrations require explicit permissions for each operation. An authorized POS can manage the catalog without being the Operator.
Email [email protected] with your project scope, expected locations and required operations. Billable concepts, payment arrangements and volume terms are agreed before activating the service.
No. OpenQloud provides APIs and a technical console. Restaurant operational screens and support belong to software providers.
We use essential technical and analytics cookies to improve your experience. Review the cookie policy