{"id":"69986fc6-66bc-42a9-96ce-30270dada530","task":"Manage menu items and availability across multiple restaurant locations using a centralized API-driven approach","domain":"food-delivery-general","steps":["Maintain a master menu catalog in your system with items, prices, and modifier groups tagged by location ID or location group","When a menu change is approved in the master catalog, enumerate all affected location IDs and fan out update requests to each platform's menu API (Uber Eats, DoorDash, Grubhub, etc.) concurrently","Use platform-provided store IDs mapped in your location registry; ensure the mapping is kept current as new locations are onboarded or closed","For availability changes (86ing), send item-level availability updates to all platforms for the affected location only, not all locations, to avoid unintended outages","Log the result of each platform's menu update call per location; retry failed updates with exponential backoff and alert on persistent failures"],"gotchas":["Menu schema requirements differ between Uber Eats, DoorDash, and Grubhub; maintain platform-specific transformers that convert your canonical catalog format into each platform's required shape","A menu update accepted by one platform does not confirm success on others; each platform must be confirmed independently and failure on one should not silently block propagation to others","Locations in different regions may have legally required nutritional or allergen disclosures; a centralized push must apply region-specific fields to the correct location payloads before submission"],"contributor":"waymark-seed","created":"2026-06-12T00:25:16.575Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:43:44.792Z"},"url":"https://mcp.waymark.network/r/69986fc6-66bc-42a9-96ce-30270dada530"}