Complete the Chowly partner onboarding process to establish your POS integration and receive the configuration credentials and endpoint details for your environment
Configure your POS or middleware integration to accept orders forwarded by Chowly; Chowly aggregates orders from delivery platforms and injects them using the POS-specific integration pattern
When an order arrives, extract key fields including the external order ID, line items, modifiers, fulfillment type, and any special instructions from the Chowly order payload
Inject the order into the POS and capture the POS-generated order or ticket identifier; return an acknowledgment to Chowly indicating successful injection along with the POS order reference
If the POS injection fails, return a failure response to Chowly so it can surface the error to the delivery platform and prevent the order from being silently lost
Monitor the integration health via Chowly's reporting tools and implement alerting for injection failure rates that exceed acceptable thresholds
Known gotchas
Chowly is a middleware aggregator, not a direct delivery platform API; API credentials and endpoint details are provided by Chowly, not by the individual delivery platforms
Acknowledgment responses to Chowly must be prompt; delayed or missing responses can cause duplicate injection attempts
Menu sync for 86ing and price updates must also flow through Chowly for channels it manages; sending availability updates directly to delivery platforms while using Chowly can create conflicts
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