Manage Menus

Applies to: Catalog API

Learn how to manage menus with the Catalog API and catalog categories.

This guide walks you through syncing menus using the Square Catalog API, for example, to display a seller's offerings in your kiosk, mobile application, or online ordering site. You'll also learn how to create root menu categories and organize menus for different services, such as breakfast and lunch.

When a seller creates a menu through the Square Dashboard, the system automatically creates catalog categories with a CategoryType of MENU_CATEGORY. These categories are used to organize items in the seller's menu and are distinct from regular catalog categories.

Key points about menu categories:

• Automatically created when sellers build menus in the Square Dashboard.
• Have a category_type of MENU_CATEGORY.
• Used specifically for menu organization.
• Like regular categories, can have parent-child relationships.
• Can be used across different sales channels.

• A Square account with Square Free, Plus, and Premium subscribers with advanced restaurant capabilities added.
• A Square account with full service, quick service, or bar mode enabled in the Square Point of Sale application.
• Your Square application credentials.
• Authorization to use the Square Catalog API.

When integrating with your application or other external systems, you need an efficient way to sync menu data. This section covers both the initial sync and incremental updates.

CatalogCategory objects handle location visibility differently than other Catalog objects. Instead of direct location assignment, they use channels as an abstraction layer:

• Channel objects act as the bridge between menu categories and locations.
• Each Location has a corresponding channel (identified by reference.type = "LOCATION").
• Menu categories declare visibility by listing channel IDs in their channels array.

To synchronize menus for a specific location:

1. Get the channel ID for your target location.
2. Filter menu categories to include only those referencing that channel.
3. Sync only these filtered categories to ensure location-specific accuracy.

for more information about mapping channels to locations, see Channels API - Menu visibility.

In the following examples, a restaurant creates a breakfast menu and lunch menu. Each menu has a root category and child categories. The breakfast beverages menu has a submenu for coffee drinks.

To perform a complete menu sync with an external service (such as a delivery platform), you need three specific API calls to get all menu-related catalog objects in the correct hierarchy.

Get all of the descendants of the root categories.

{
  "object": {
      "type": "CATEGORY",
      "id": "ZTVXYFS633S6GSLMHVP5O5IG",
      "updated_at": "2025-06-02T22:04:56.684Z",
      "created_at": "2025-06-02T22:04:56.898Z",
      "version": 1748901896684,
      "is_deleted": false,
      "present_at_all_locations": true,
      "category_data": {
        "name": "Coffee-drinks",
        "image_ids": [
          "BAXRGSINXCHS7RW4ZMQSHGGL"
        ],
        "category_type": "MENU_CATEGORY",
        "parent_category": {
          "id": "H5P6BRQKWKL6BDZKIS4FGPSM",
          "ordinal": -2251731094208512
        },
        "is_top_level": false,
        "channels": [
          "CH_IT55vdjtd81xkZvF68NXQqPO54qnOXkyQRkiBQlQuYC",
          "CH_leic5ZC8kuuyAVAIQUlxuEG72EYFNBoxFCz5574e9945o"
        ],
        "online_visibility": false,
        "root_category": "3H3ADZMYJU6U27JYO2PZFANQ"
      }
    }
}

To complete the menu, your application needs to get the items, variations, any modifier lists, images, and other resources related to the items shown on the menus. You can get all this information with a single API call. Note that you need to include the "include_related_objects": true query parameter.

To keep your application's menu data current with the seller's Square catalog, implement a periodic sync strategy to capture various types of menu changes.

• Item modifications (price, description, or images)
• Menu structure changes (new categories or item reorganization)
• Item availability updates
• New item additions or removals

To learn about tracking availability updates, see Monitor Sold-out Item Variations or Modifiers.

You can efficiently track these changes using the updated_at timestamp in the SearchCatalogObjects endpoint:

After retrieving any changes to the menu structure, you want to get any changes to menu items and related types.

When working with the Catalog API, it's important to understand the distinction between menu categories and regular categories:

• Menu categories

  • Created through the Square Dashboard's menu builder.
  • Have category_type = "MENU_CATEGORY".
  • Used specifically for menu organization.
  • Like regular categories, support parent-child relationships.
  • Can be synchronized across channels.

• Regular categories

  • Created through the Catalog API.
  • Have category_type = "REGULAR_CATEGORY".
  • Used for general item organization.
  • Might appear as duplicates of menu categories.

For Food & Beverage operations, Square supports separate kitchen display names to streamline back-of-house operations. These properties allow restaurants to use different names for kitchen staff versus customer-facing displays, improving order accuracy and kitchen efficiency.

Available properties:

• CatalogItem.kitchen_name - A kitchen-friendly name for the menu item.
• CatalogItem.buyer_facing_name - The customer-facing name displayed to buyers.
• CatalogItemVariation.kitchen_name - Kitchen name for specific item variations (sizes and options).
• CatalogModifier.kitchen_name - Kitchen name for modifiers (such as add-ons and customizations).

Benefits for restaurant operations:

These properties help restaurants:

• Use abbreviated or coded names on kitchen display systems (KDSs).
• Maintain appetizing, descriptive names for customer receipts and online ordering.
• Reduce confusion during food preparation with standardized kitchen terminology.
• Speed up order fulfillment by using familiar kitchen shorthand.
• Support multi-language operations (kitchen names in one language, buyer names in another).

Example: Creating items with kitchen names

curl https://connect.squareupsandbox.com/v2/catalog/object \
  -X POST \
  -H 'Square-Version: 2026-08-19' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "idempotency_key": "unique-key-789",
    "object": {
      "type": "ITEM",
      "id": "#grilled_chicken_salad",
      "item_data": {
        "name": "Grilled Chicken Caesar Salad",
        "kitchen_name": "GRL CKN CAESAR",
        "buyer_facing_name": "Caesar Salad with Grilled Chicken",
        "description": "Fresh romaine lettuce with grilled chicken breast",
        "category_id": "SALADS_CATEGORY_ID",
        "variations": [
          {
            "type": "ITEM_VARIATION",
            "id": "#salad_regular",
            "item_variation_data": {
              "item_id": "#grilled_chicken_salad",
              "name": "Regular",
              "kitchen_name": "REG",
              "pricing_type": "FIXED_PRICING",
              "price_money": {
                "amount": 1295,
                "currency": "USD"
              }
            }
          },
          {
            "type": "ITEM_VARIATION",
            "id": "#salad_large",
            "item_variation_data": {
              "item_id": "#grilled_chicken_salad",
              "name": "Large",
              "kitchen_name": "LG",
              "pricing_type": "FIXED_PRICING",
              "price_money": {
                "amount": 1595,
                "currency": "USD"
              }
            }
          }
        ],
        "modifier_list_info": [
          {
            "modifier_list_id": "DRESSING_MODIFIER_LIST_ID"
          }
        ]
      }
    }
  }'

Example: Adding kitchen names to modifiers

curl https://connect.squareupsandbox.com/v2/catalog/object \
  -X POST \
  -H 'Square-Version: 2026-08-19' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -d '{
    "idempotency_key": "unique-key-456",
    "object": {
      "type": "MODIFIER_LIST",
      "id": "#dressing_options",
      "modifier_list_data": {
        "name": "Dressing Options",
        "modifiers": [
          {
            "type": "MODIFIER",
            "id": "#ranch_dressing",
            "modifier_data": {
              "name": "Ranch Dressing",
              "kitchen_name": "RANCH",
              "modifier_list_id": "#dressing_options"
            }
          },
          {
            "type": "MODIFIER",
            "id": "#caesar_dressing",
            "modifier_data": {
              "name": "Caesar Dressing",
              "kitchen_name": "CAESAR",
              "modifier_list_id": "#dressing_options"
            }
          },
          {
            "type": "MODIFIER",
            "id": "#no_dressing",
            "modifier_data": {
              "name": "No Dressing",
              "kitchen_name": "NO DRESS",
              "modifier_list_id": "#dressing_options"
            }
          }
        ]
      }
    }
  }'

Best practices for kitchen names:

1. Keep it concise - Kitchen names should be short and easy to read on kitchen display screens.
2. Use standard abbreviations - Develop consistent abbreviations your kitchen staff understands.
3. Consider screen space - Kitchen display systems often have limited character width.
4. Test with staff - Ensure kitchen names are clear and unambiguous to your team.
5. Update consistently - When adding new items, maintain your naming conventions.

Common kitchen name patterns:

Use the Catalog API to retrieve existing menu categories.

When creating categories for different locations, ensure that you:

• Set the correct category_type.
• Establish proper parent-child relationships.
• Use consistent naming across locations.

The following shows an example for a delivery service menu category:

When creating subcategories, always reference the parent menu category.

When working with menu categories, it's important to understand that the structure you see in the Square Dashboard is represented by MENU_CATEGORY types in the Catalog API. The following example shows how different menu structures might look:

Restaurant Menu (MENU_CATEGORY)
├── Beverages
│   ├── Non-Alcoholic
│   │   ├── Iced Tea (Small/Large)
│   │   ├── Soft Drinks (Regular/Large)
│   │   └── Coffee (Small/Large)
│   ├── Beer
│   │   ├── Draft (Domestic/Craft)
│   │   └── Bottled (Domestic/Imported)
│   └── Wine
│       ├── Red (Glass/Bottle)
│       └── White (Glass/Bottle)
├── Appetizers
│   ├── Mozzarella Sticks
│   ├── Wings (6pc/12pc)
│   └── Nachos
└── Entrees
    ├── Sandwiches
    │   ├── Club
    │   └── BLT
    └── Salads
        ├── Caesar
        └── Garden

Delivery Menu (MENU_CATEGORY)
├── Beverages
│   ├── Iced Tea (Small/Large)
│   ├── Soft Drinks (Regular/Large)
│   └── Coffee (Small/Large)
├── Appetizers
│   ├── Mozzarella Sticks
│   ├── Wings (6pc/12pc)
│   └── Nachos
└── Entrees
    ├── Sandwiches
    │   ├── Club
    │   └── BLT
    └── Salads
        ├── Caesar
        └── Garden

• Cause: Items appearing in both menu and regular categories.
• Solution: Filter specifically for MENU_CATEGORY types.
• Prevention: Use proper category type filtering in API calls.

• Cause: Looking at the wrong category type.
• Solution: Check both menu and regular category associations.
• Prevention: Implement proper category type checking.

• Cause: Mixing menu and regular categories.
• Solution: Maintain proper parent-child relationships.
• Prevention: Validate category types and relationships.

1. Category filtering

   Search catalog objects

   cURL

2. Relationship maintenance

   • Track both menu and regular category IDs.
   • Update all relevant category associations.
   • Maintain a proper hierarchy.

3. Data validation

   • Verify category types before updates.
   • Check parent-child relationships.
   • Validate item associations.

1. Verify data

   • Compare item counts.
   • Validate category structures.
   • Check modifier associations.

2. Monitor performance

   • Track sync times.
   • Monitor API usage.
   • Optimize query patterns.

3. Setup alerts

   • Configure sync failure notifications.
   • Monitor for pricing discrepancies.
   • Alert when structure changes occur.