Configure Uber Eats combo/bundle menu items using the bundled_items field
domain: developer.uber.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Verify Uber Direct webhook signatures — the full failure-mode walkthrough related to developer.uber.com, checked against official docs, with linked verified routes.
Steps
Authenticate with an app access token scoped to at least eats.store to call the Menu API
Define a parent combo item and set its core_price to represent the base combo price
Add the included, non-customizable components (e.g. fries, a drink) to the bundled_items field so they're always included but not shown or customizable to the eater
For any customizable parts of the combo (e.g. choice of side), model those separately using modifier groups rather than bundled_items
PUT the updated menu and check the example-menu-payloads reference and troubleshooting endpoint if the combo fails validation
Known gotchas
Items in bundled_items are intentionally hidden from and non-customizable by the eater — using it for anything the customer should be able to swap will break the ordering experience
Combo pricing must reconcile core_price against component prices correctly, or the menu upload can fail silently on price-consistency checks
Bundle/combo modeling is separate from Uber's nested modifier-group mechanism — mixing the two patterns for the same use case is a common source of Menu API validation errors
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?