Ensure the restaurant is live on Olo Ordering and that the target delivery channel is an active Rails partner (e.g., DoorDash, Grubhub, Uber Eats)
Make menu and price changes in the Olo Dashboard or via the Olo Ordering API — Rails consumes the same menu data as the ordering platform
Trigger a menu export by updating any menu entity; Olo's Menu Export Service generates a new menu file for all configured Rails partners automatically
Allow several minutes for propagation; the change should be reflected on marketplace sites within minutes for most partners
Use the Olo Dashboard's Rails status view to confirm each partner has received and acknowledged the updated menu
If a partner shows stale menu data, contact your Olo account team to force a re-export — there is no public self-serve re-export endpoint
Known gotchas
Rails is built on top of the Olo Ordering API and does not have a separate API; integrators interact with Olo's ordering endpoints, not a distinct Rails endpoint
Not all menu features (such as nested modifier groups beyond two levels) are supported by all Rails marketplace partners — verify partner capability before modelling complex menus
Menu export can take longer when many stores are updated simultaneously; plan batch updates during off-peak hours to minimize propagation delay
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