Qu API
Qu is a unified commerce platform that turns the restaurant point of sale into a data-driven operating system across POS, kiosk, drive-thru, online, and third-party ordering, kitchen orchestration, and multi-brand enterprise management. An unofficial API lets you programmatically pull orders, menus, locations, channels, and kitchen and reporting data—and push updates like new orders, menu changes, and status events back into Qu.
What is Qu?
Qu is a unified commerce platform that transforms the restaurant point of sale into a data-driven operating system for quick-service, fast-casual, and multi-unit restaurant brands. Restaurants use Qu to take orders across POS, kiosk, drive-thru, online, and third-party channels; orchestrate the kitchen with a Kitchen Display System and equipment intelligence; and manage menus, brands, franchises, and reporting from a single enterprise layer—powered by Qu's native intelligence engine, Qube (Qu Business Edge).
Core product areas include:
- Omnichannel Ordering (POS, kiosk, drive-thru, online ordering, third-party channel integration)
- Kitchen Orchestration (Kitchen Display System, order status tracking, energy and equipment intelligence via Qu Equip)
- Enterprise Management (unified menu management, channel management, brand and franchise control)
- Qu Notify (mobile insights and AI-powered operational alerts)
- Unified Data and Reporting (near real-time, system-wide visibility) with the Qube intelligence engine
Common data entities:
- Orders, Order Items, Order Status, Tickets
- Menus, Menu Items, Modifiers, Pricing
- Locations, Brands, Franchises, Channels
- Payments, Tenders, Discounts
- Kitchen Display events, Equipment telemetry, Reporting and Analytics outputs
The Qu Integration Challenge
Qu runs high-volume, peak-hour workloads across many channels and locations, but turning its omnichannel surfaces into reliable API-driven automation is non-trivial:
- Partner certification gates: Qu invites developers to become certified integration partners, and much API access flows through partnership agreements and the partner ecosystem before keys are issued
- Order-routing model: Third-party orders post to the Qu Data Access API and are then pulled by in-store POS, so timing, acknowledgement, and reconciliation must be handled carefully
- Multi-brand and franchise spread: Menus, pricing, and channels differ by brand, franchise, and location, so generic integrations break across tenants
- Channel variability: POS, kiosk, drive-thru, online, and third-party ordering each carry their own payloads and lifecycle states that must be normalized
- Offline and redundancy behavior: Qu's triple-redundant, offline-capable architecture means data can sync after the fact, complicating real-time assumptions
- Authentication and session handling: Cloud authentication and managed sessions complicate headless, always-on automation
How Supergood Creates Qu APIs
Supergood reverse-engineers Qu's authenticated cloud flows and REST surfaces—including the Data Access API used for omnichannel ordering—to deliver a resilient API layer for your Qu deployment across brands and locations.
- Handles cloud authentication and MFA securely within a managed session
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across orders, menus, locations, channels, and kitchen events so you integrate once and rely on consistent objects
- Aligns with brand-, franchise-, and location-specific menu and pricing configurations to ensure accurate access
Use Qu with AI agents: Qu MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your channels, brands, locations, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready Qu adapter tailored to your deployment, channels, and menu configuration.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as Qu evolves.
API Endpoints
Authentication
/authenticateAuthenticate to a Qu deployment and obtain a session token for downstream calls.
Orders
/ordersList orders across POS, kiosk, drive-thru, online, and third-party channels with filters for location, brand, status, and time range.
Orders
/create_orderSubmit a new order to the Qu Data Access API so in-store POS systems can pull and fulfill it.
Menus
/menusRetrieve menus, items, modifiers, and pricing scoped by brand, franchise, location, and channel.
Menus
/menusUpdate menu items, modifiers, availability, and pricing across brands and locations.
Locations
/locationsList locations, brands, and channel configurations for a deployment.
Use Cases
Sync omnichannel order data into your warehouse
- Pull orders, items, and status events from POS, kiosk, drive-thru, online, and third-party channels - Stream order and payment events to downstream BI, finance, and customer-experience tools - Reconcile orders across channels and locations for unified reporting
Inject third-party orders through the Data Access API
- Post online and marketplace orders to Qu so in-store POS systems pull and fulfill them - Confirm acknowledgement and routing to the correct location and channel - Reconcile injected orders against fulfillment and payment records
Manage menus and pricing across brands and locations
- Pull menus, items, modifiers, and pricing scoped by brand, franchise, and channel - Push availability, price, and modifier changes across multiple locations at once - Keep third-party ordering channels in sync with in-store menu configuration
Surface kitchen and reporting data for operations
- Stream Kitchen Display and order-status events to monitoring and forecasting tools - Pull equipment telemetry and operational metrics from Qu Equip and Qube - Feed unified reporting outputs into enterprise dashboards across locations
Technical Specifications
Authentication
Cloud credentials and MFA handled in a managed session
Connectivity
Authenticated cloud flows plus Qu's REST surfaces, including the Data Access API for omnichannel ordering
Response format
Normalized JSON across orders, menus, locations, channels, and kitchen events
Rate limits
Adaptive throttling tuned to your deployment to avoid platform-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for orders and status events, with offline-synced data reconciled as it arrives
Security
Encrypted credential vault, scoped access tokens, SOC 2-aligned controls, and audit logging
Webhooks
Event-style callbacks for new orders, order status, menu changes, and kitchen events
Latency
Sub-second reads on cached entities; multi-second writes when posting orders and menu changes
Throughput
Horizontally scaled workers sized to peak-hour, multi-location order volume
Reliability
Retry, backoff, and idempotency keys for order injection and menu updates, matching Qu's triple-redundant architecture
Adaptation
Continuous monitoring of Qu platform releases, partner-API changes, and brand-specific configuration drift
Frequently asked questions
No. Supergood works with your existing Qu deployment and authenticated sessions. Qu's certified-partner program is only required when you specifically want a listed, certified integration brokered through Qu's partner ecosystem.
Yes. Supergood mirrors the Data Access API pattern, posting orders to Qu so in-store POS systems pull and fulfill them, and handling acknowledgement, routing, and reconciliation.
Yes. Endpoints are scoped by brand, franchise, location, and channel, and Supergood preserves each tenant's menu, pricing, and channel configuration rather than forcing a generic schema.
Qu is offline-capable, so some data syncs after connectivity returns. Supergood pulls in near real time where data is live and reconciles offline-synced records as they arrive, with optional scheduled batch syncs.
Yes. Kitchen Display events, equipment telemetry from Qu Equip, and unified reporting outputs are exposed through the same normalized API surface alongside order and menu data.