The following deployment methods are available:

• Enterprise Level: Cloud endpoint (most common) for simplified connectivity, centralized access, and easier partner onboarding. Oracle Restaurants recommends this method for mobile ordering and other off-premises use cases. As a failover, Oracle Restaurants recommends off-premises ordering solutions have a plan for implementing the local-based API (this requires changes from your third-party integrator).
• Property/workstation (on-premises) Level: Local workstation endpoint for low‑latency, venue‑resilient access directly to the POS—often preferred for kiosks and other on‑premises workflows. For on-premises integrations, such as direct connections with in-store devices, Oracle Restaurants recommends this method.

When using the enterprise cloud deployment method and multiple POS API client workstations are available within a revenue center, Oracle Restaurants recommends enabling at least two such devices to provide resiliency. This ensures order processing continuity if one workstation becomes unavailable.

To have a higher level of resiliency across the business, Oracle Restaurants recommends that on-premises integrations use the property-level local deployment method. This is especially recommended for companies with high volumes of kiosk orders and for those that have reduced the number of traditional counter ordering stations, resulting in fewer POS devices as part of their digital transformation.