In Olo's vendor portal, create or select the target Rails channel corresponding to the delivery marketplace partner
Enable the price override feature for the channel and upload a channel-specific price list CSV mapping product IDs to delivery-specific prices
Verify the override is applied by retrieving the product catalog through the channel endpoint and confirming delivery prices differ from the base menu prices
Configure the tax handling flag to indicate whether Olo or the marketplace is responsible for tax collection on this channel
Submit a test order through the channel in sandbox mode and confirm the order total reflects the overridden prices and correct tax treatment
Schedule a nightly sync job to push updated channel-specific price overrides whenever the base menu pricing changes, using Olo's import API
Known gotchas
Price overrides on Olo Rails are channel-scoped; a misconfigured channel ID will silently apply the wrong price list to all orders from that partner
Some marketplace partners contractually prohibit delivery-price surcharges above in-store prices; verify partner agreements before enabling markup overrides
Olo does not automatically propagate base-menu price changes to channel overrides; a separate sync process is mandatory or the overrides will diverge from the intended delta
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