Sync a restaurant catalog across Delivery, Digital Menu, and Dine-in channels using the iFood Catalog API
domain: developer.ifood.com.br · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
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
Known 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
Give your agent this knowledge — and 15,500+ 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?