Sync item-level price overrides for a delivery channel from a central pricing system to DoorDash and Uber Eats
domain: food-general · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Maintain a pricing override table in your central system that maps (item_id, channel) to an override price distinct from the in-store dine-in price
During menu publish to DoorDash Marketplace, substitute the channel-specific override price for any item with a delivery surcharge in the menu payload
During menu publish to Uber Eats, populate the price field in the menu item payload with the delivery override price
After each publish, fetch the live menu from the channel and compare returned prices to your expected override prices to detect silent truncation or rounding
Maintain an audit log of price changes with effective timestamps for compliance with any local regulations on price transparency
Known gotchas
Some jurisdictions require that delivery price surcharges be disclosed to consumers; verify local regulations before silently inflating prices on delivery channels
DoorDash and Uber Eats both express prices as integers in the smallest currency unit (cents); floating-point rounding in your system can cause 1-cent discrepancies at scale
A full menu re-publish is required to update prices on most channels; there is no reliable partial price-update endpoint — plan for full menu sync cadence
Give your agent this knowledge — and 15,600+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?