Restaurant Menu Guide

Menu Guide

A menu side integration allows partners to create and retrieve menus, as well as update specific item availabilities throughout the day for individual locations. Menus and item updates pushed to Wolt are processed asynchronously.

Menu Components

The documentation will make reference to various components that make up a menu. In Wolt these are:

• Items - the individual products or meals that are on sale, for example a pizza or a burger

• Options - items can have different customisations (size, cooking style etc.) or add-ons (extra cheese, dessert etc.). At Wolt, these are called options and can be linked to one or multiple items in the menu.

• Categories - All items need to be assigned a category for them to be visible on Wolt

API Workflows

Create a Menu (mandatory)

Use this to create a full menu structure, including categories, items, and options. This is useful for syncing your POS or ERP system’s menu to be the live menu on Wolt.

Menu API specs & endpoint

Use this endpoint to:

• Create a whole menu: categories, items and options. Every new menu push overwrites the previous version completely.

Recommendation: make sure all items and options have unique identifiers (sku or pos_id or gtin)

Update Menu Items (mandatory)

Item API specs & endpoint

Use this endpoint to manage smaller item-level changes throughout the day, such as:

• Mark items as temporarily unavailable

• Update item visibility

• Update item pricing, including setting discounts

Update Menu Options (mandatory)

Option API specs & endpoint

Use this endpoint to manage smaller option-level changes throughout the day, such as:

• Update option visibility

• Update option pricing

Fetch Menu (optional)

Get Menu specs & endpoint

Use this endpoint to retrieve the full menu, including categories, items, and options for a specific venue. This is useful for syncing your system with an already built menu on Wolt.

Use this endpoint to:

• Get all created categories and items

• Track item and option availability

• Map unique identifiers in your system

Best Practices

• Respect rate limits to avoid request blocks.

• Cache menus locally and only re-fetch if significant updates are expected.

• Use item updates for frequent availability changes.

Rate Limits

All limits are enforced per venue; exceeding these limits will result in 429 errors.