Reservations Waitlists Integration Policies

The following integration policies apply to the Reservations Waitlists integration.

Warning: Waitlist integration is only available for the basic dining table waitlist experience. Waitlists for other experiences are not in scope. The merchant must be a food-related merchant (most commonly a restaurant).

Food Menu Policy and Requirements

Please read through the following integration eligibility criteria before beginning an integration. Partners must adhere to the food menu policies and meet the following requirements to be eligible to integrate. Please note that Google reserves the right to display menu & dish data in ways that are helpful to users.

Failure to meet the requirements and policies may result in integration, merchants or services being suspended or removed from the platform.

Policy and Requirements

1. Partners must not send prohibited information (see details) in menu feed such as foul language, prohibited images, personally identifiable information (PII) or user generated content.
2. Partners should not use the menu feed to share non-menu items such as services (ex: curbside, promotion codes, etc.).
3. Partners are required to provide all required data in Reservations E2E menu spec or Ordering Redirect menu spec (max file size 2MB). The technical requirements are addressed in the Reservations E2E menu spec or Ordering Redirect menu spec by marking fields as optional/required.
4. Partners should only provide menu items available for the corresponding restaurant locations.
5. Partners must send a complete menu for each location. Merchants with incomplete menus may not be eligible for display.
6. Partners and merchants are required to ensure menus are accurate and should provide updates on a daily basis.
7. Menu items photos should be well-lit, feature one in-focus menu item, must not include people or other non-food images, and must conform to image spec (see photo guidelines).
8. Prices should be shown, per menu item, without tips, taxes or fees; unless required by local laws and ordinances. Partners must explicitly provide local currency.
9. Specialty menus are supported and should be removed when no longer available (ex: prix fixe, seasonal, limited time specials).
10. Merchants are required to provide menus in a text-based format, enabling users to select and add items to their order. Menus presented solely as images are not permitted.

Dining Policies

To ensure a consistent experience for consumers, merchants, and partners using Actions Center, Reservations Waitlists inventory must adhere to the appropriate guidelines. Failure to adhere to these policies will lead to suspension of your Reservations Waitlists integration.

Waitlist

For partners enabling online Reservations Waitlists, the partners should follow the guidelines:

• Partners must provide accurate and up-to-date wait times.
• Partners must be able to send confirmation and status updates to users via SMS.