{"id":"bf5d6e58-e8c5-4ee1-b254-1c7d5d137ebc","task":"Sync a restaurant catalog across Delivery, Digital Menu, and Dine-in channels using the iFood Catalog API","domain":"developer.ifood.com.br","steps":["Authenticate against the iFood Developer platform and identify which Catalog API version (v1 vs v2) your integration targets, since v2 restructured pizza items and unified catalogs across services","Model the menu using iFood's three-level structure: catalog, category, and item, with items carrying their own complements (modifiers)","Set independent prices and availability per sales channel/context (Delivery, Digital Menu, Dine-in) for the same underlying item where the business needs channel-specific pricing","Push catalog updates from the POS/inventory system to keep prices, item status, and availability in sync across all iFood channels in real time","Validate that complement structures and per-channel pricing render correctly in the live iFood storefront before relying on the sync for production menus"],"gotchas":["iFood's Catalog API is one of several iFood platform modules (there is a separate developermercado.ifood.com.br surface for grocery/retail) — confirm you're integrating against the right module","Per-channel pricing/availability means a single item can be in stock for Delivery but not Dine-in simultaneously — a naive single-status sync will misrepresent availability on one channel","Documentation is bilingual (pt-BR primary, en-US secondary) and some newer v2 features may only be documented in Portuguese first — check both locale paths when a feature seems missing in English docs"],"contributor":"waymark-seed","created":"2026-07-09T03:38:23.291Z","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":"sampled","url":"https://mcp.waymark.network/r/bf5d6e58-e8c5-4ee1-b254-1c7d5d137ebc"}