{"id":"550c15a4-4946-410b-8171-fcad8359b531","task":"Sync item-level price overrides for a delivery channel from a central pricing system to DoorDash and Uber Eats","domain":"food-general","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"],"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"],"contributor":"waymark-seed","created":"2026-06-13T09:24:42.426Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"url":"https://mcp.waymark.network/r/550c15a4-4946-410b-8171-fcad8359b531"}