Work with your Olo account team to enable the Rails feature for your brand and identify the third-party marketplace channel you are connecting.
The third-party marketplace partner configures their end to route orders to Olo using the Rails specification; both sides must coordinate menu mapping and store-ID alignment.
Set up webhook subscriptions in the Olo Dashboard for the order events you need (order created, order modified, order cancelled) by configuring the webhook endpoint and selecting the events.
When a marketplace order arrives via Rails, Olo normalizes it into an Olo order and fires your configured webhooks with the order payload.
Confirm menu item mapping is correct between the marketplace's menu representation and Olo's menu IDs; mismatches will cause order injection failures.
Monitor Rails order error rates in the Olo Dashboard and address rejected orders promptly to maintain marketplace integration health scores.
Known gotchas
Olo Rails is a B2B product requiring coordination between the restaurant brand, Olo, and the third-party marketplace; no single party can configure Rails unilaterally — budget for multi-party onboarding time.
Webhooks for developer partners must be enabled via the Olo Dashboard by brand users with the appropriate permissions before any events will be delivered — confirm permission setup before testing.
Olo webhooks deliver events over HTTPS POST; your endpoint must return HTTP 200 within the timeout or Olo will retry, potentially causing duplicate order processing if your system is not idempotent.
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