Architecture

Each physical restaurant location should have its own OpenApp integration profile. Product listings, menu data, prices, availability, POS credentials, queue configuration, callbacks, health, and status are scoped to that location profile.

OpenApp-to-POS communication can use either direct HTTP delivery or OpenApp-managed queue delivery.

Delivery mode	When to use it	How it works
HTTP REST API	The POS backend exposes a stable HTTPS endpoint reachable by OpenApp.	OpenApp calls the POS endpoint directly and receives the operation result in the HTTP response. Endpoint paths is configurable by the merchant.
OpenApp-managed queue	The POS system cannot be reached from the internet or cannot accept inbound HTTPS traffic.	OpenApp writes POS commands to a queue. The POS connects outbound to the queue, receives commands, processes them, and sends results back to OpenApp over HTTP.

POS-to-OpenApp communication always uses HTTP. For queue-based OpenApp-to-POS commands, the POS sends the result back through an asynchronous OpenApp HTTP callback correlated by the original message identifier.