Sync a restaurant menu to a delivery platform via the Qu POS single-menu management API to ensure consistent pricing and item availability across all digital channels
Coordinate with your Qu POS representative to enable API access; Qu POS integrations require direct engagement with Qu before API credentials are provisioned
Authenticate to the Qu REST API using the credentials and authentication flow provided by Qu during the integration onboarding process
Retrieve the current menu configuration from Qu, which uses a single-menu data model (Qu-1MENU) that centralizes all items, prices, and modifiers across channels and locations
Identify the specific items, categories, and modifier groups that are in scope for the target delivery platform and transform them into the delivery platform's required menu schema
Submit the transformed menu to the delivery platform via its menu API; use the platform's upsert or replace-menu operation and verify the response confirms successful publication
When Qu menu changes are detected (for example, price updates or new items), re-pull the affected portion of the Qu menu and re-push the changes to the delivery platform to maintain parity
Known gotchas
Qu's single-menu architecture means all channel pricing and availability derives from one source; changes made in Qu propagate broadly and should be validated against all channels after any update
Qu API access is not self-service and requires Version 3.5 or higher of Qu POS for third-party integrations; confirm the restaurant's Qu version before beginning integration planning
Delivery platform menu APIs vary in how they handle partial updates versus full menu replacements; use the platform's supported update pattern to avoid unintentionally removing items during a partial push
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp