Permissions
Which restaurants can it work with?
With those that authorize it, for the actions they allow. Orders, menus and connection management are separate permissions, not privileges attached to a software role.
Integrated software
Connect your middleware to OpenQloud, just like a POS or a marketplace. Using its APIs does not make you a distributor, require you to onboard restaurants or automatically assign you their billing.
Operating is not provisioning or paying.
Your software can work with orders, catalogues, availability and connections for authorized restaurants. The account onboarding a restaurant and paying for its usage may belong to your company or another one. That responsibility is independent of the integration type.
Your software in OpenQloud
What does your software do?
Combine the integration roles your software needs: POS, marketplace, middleware, ordering or delivery. Being an Operator is a separate responsibility: covering usage for one or more restaurants.
- POSReceive orders and share your catalog.View integration →
- MarketplaceRead menus and send orders.View integration →
- MiddlewareCoordinate connections and integrated systems.View integration →
- Ordering applicationsConnect ordering, QR and kiosk software.View integration →
- Delivery softwareExchange deliveries and tracking updates.View integration →
Integration roles
Your company can combine several functions.
You can be a POS, a POS and middleware, or add the Operator role too. Managing connections does not automatically make you the restaurant's operator.
Operator
One restaurant. One Operator.
The Operator represents the restaurant in OpenQloud, acts on its behalf and covers its consumption. One account can represent several restaurants; integrations retain independent permissions.
Looking for a product with screens?
OpenQloud provides APIs and a technical console, not restaurant applications. A middleware or another integrated product can provide the screens and workflows you need.
Tell us what you need