---
title: "Business Menus Model"
description: "A menu groups the products and fulfillment modes available from a business."
canonical: https://docs.ordering.co/api-reference/guides/menus-model/
---

# Business Menus Model

A menu groups the products and fulfillment modes available from a business.

## Operations

| Action | Method   | Resource                                  |
| ------ | -------- | ----------------------------------------- |
| List   | `GET`    | `/business/{business_id}/menus`           |
| Find   | `GET`    | `/business/{business_id}/menus/{menu_id}` |
| Create | `POST`   | `/business/{business_id}/menus`           |
| Update | `PUT`    | `/business/{business_id}/menus/{menu_id}` |
| Delete | `DELETE` | `/business/{business_id}/menus/{menu_id}` |

## Shared concepts

- `name` and `comment` provide the menu's visible identity and supporting text.
- `schedule` defines menu availability unless `use_business_schedule` selects the business schedule.
- `pickup`, `delivery`, `eatin`, `curbside`, `driver_thru`, `seat_delivery`, `catering_delivery`, `catering_pickup`, and `reservation` identify supported fulfillment modes.
- `enabled` and `snooze_until` affect availability.
- `all_products` can include every available product; otherwise `products` identifies explicit product associations.

The model contains more fields and relations than every response returns. available fields depend on the operation.

## Access and listing behavior

Business-manager mutations are scoped through associated businesses. The list operation does not require operation-level authentication.

For list requests, `mode=dashboard` changes enabled, fulfillment, snooze, and related-business filtering. Do not generalize those list semantics to the single-menu route.