레스토랑 세부정보를 제공하려면 판매자 피드에 설명된 데이터 사양을 따르세요.
JSON 파일의 예시는 샘플 JSON을 참고하세요.
데이터 파일 이름은 업로드 간에 고유해야 합니다. 파일 이름에 타임스탬프를 포함하는 것이 좋습니다(예: menu1_1633621547.json).
메뉴 피드의 파일 세트 설명자에서 name 필드를 google.food_menu로 설정합니다.
설명자 파일 콘텐츠의 예시는 설명자 파일 JSON 샘플을 참고하세요.
설명자 파일의 이름은 업로드 간에 고유해야 합니다. 파일 이름에 타임스탬프(예: descriptor_1633621547.filesetdesc.json)를 포함하는 것이 좋습니다.
설명자 파일은 메뉴 피드의 일부로 일반 SFTP 서버에 업로드해야 합니다.
단일 메뉴 항목에 필수 옵션이 여러 개 있는 파트너 (예: 크기 옵션과 우유 옵션이 있는 라떼)는 Google에 이러한 옵션을 가장 잘 표시하는 방법을 결정해야 합니다. Google에서는 다음을 권장합니다.
메뉴 피드는 파트너의 주문 사이트 (또는 위치에 주문 사이트가 없는 경우 레스토랑의 매장 내 식사 메뉴)와 일치해야 합니다.
주문 사이트에 개별 가격이 표시되는 상품에는 MenuItem을 사용해야 합니다.
상품이 기본 가격과 여러 옵션으로 표시되는 경우 MenuItemOption을 사용해야 합니다.
다음과 같이 옵션 목록을 길게 포함하지 마세요.
닭고기 부리토
치즈가 들어간 치킨 부리토
살사가 들어간 치킨 부리토
살사와 치즈가 들어간 치킨 부리토
과카몰레가 들어간 치킨 부리토
과카몰레와 살사가 들어간 치킨 부리토
메뉴 항목 옵션은 요리에 옵션 중 하나를 선택해야 하는 경우에만 지원됩니다. 예를 들어 피자를 주문할 때 크기는 필수 옵션입니다. 부가기능용 메뉴 항목 옵션('아보카도 추가 옵션' 등)은 지원되지 않으며 피드에 포함해서는 안 됩니다.
메뉴 항목 옵션 가격은 해당 옵션이 선택된 항목의 전체 가격이어야 합니다.
가격은 메뉴 항목 또는 옵션에 설정해야 하며 둘 다에 설정할 수는 없습니다.
메뉴가 여러 개인 레스토랑
하나의 레스토랑 (엔티티)에는 하나의 메뉴만 있을 수 있습니다. 메뉴가 여러 개 (예: 점심 메뉴와 저녁 메뉴가 별도로 있음)인 레스토랑의 경우 모든 메뉴를 MenuSections이 있는 단일 메뉴로 결합할 수 있습니다(예: 점심 섹션과 저녁 섹션이 있는 메뉴 하나). 결과 메뉴의 구조는 다음과 같습니다.
메뉴
점심 섹션
스프
Soup 1
수프 2
샌드위치
샌드위치 1
샌드위치 2
저녁 식사 섹션
시작 조건
Starter 1
Starter 2
메인
메인 요리 1
메인 요리 2
여러 음식점 간 메뉴 공유
메뉴의 merchant_ids 목록에 모든 레스토랑을 포함하면 하나의 메뉴를 여러 레스토랑에서 공유할 수 있습니다. 이 목록은 엔티티 피드를 사용하는 파트너의 엔티티 ID를 허용합니다.
기본 언어를 TextField의 첫 번째 언어로 제공합니다. LocalizedText 객체를 여러 개 전송하는 경우 텍스트 목록의 첫 번째 객체가 사용자에게 표시됩니다.
모든 메뉴 항목은 메뉴 섹션에 추가해야 합니다.
메뉴 객체에 메뉴 항목을 직접 추가하지 마세요.
utf-8 인코딩을 사용하여 콘텐츠를 제공합니다. 비ASCII 문자는 이스케이프 처리하지 않아도 됩니다.
여러 지역에서 출시하는 경우 units 및 nanos 필드에 올바른 통화 코드와 단위를 사용해야 합니다. 단위의 10^-9인 nanos 필드에 특히 주의하세요. 인벤토리 뷰어의 메뉴 시각화 도구를 사용하여 가격을 올바르게 설정했는지 확인합니다.
사용자에게 시각적으로 풍부하고 포괄적이며 최신 메뉴를 제공하는 것은 유용하고 매력적인 사용자 환경을 제공하는 데 매우 중요합니다. 가격, 설명, 사진, 식이 정보는 모두 의사 결정을 유도하는 핵심 요소이며, 파트너는 최적의 사용자 및 판매자 환경을 제공하기 위해 이러한 데이터를 최대한 많이 제공하는 것이 좋습니다.
개발 및 테스트 도구
메뉴 피드가
출시되면 메뉴 피드 데이터가 탐색 환경에 표시될 수 있으며 음식점 장소 시트의 '메뉴' 탭에 표시될 수 있습니다. 메뉴 탭은 Google 검색 (모바일 및 데스크톱)에서 지원되며, Google 지도를 비롯한 추가 표시 경로로 환경이 확장될 예정입니다. 렌더링된 환경은 표시 경로에 따라 다를 수 있습니다.
그림 3:
모바일의 비즈니스 프로필에 메뉴 피드 콘텐츠가 표시되는 방식의 예
메뉴가 올바르게 구성되었는지 확인하려면 인벤토리 뷰어에서 메뉴 시각화 도구를 사용하여 메뉴를 미리 봅니다.
음식점 메뉴는 Google 비즈니스 프로필을 통한 음식점 자체, 음식 주문 및 예약 파트너, 메뉴의 사용자 사진 등 다양한 소스에서 가져올 수 있습니다.
여러 소스에서 동일한 음식점의 메뉴를 제공하는 경우 판매자는 Google 비즈니스 프로필 메뉴 편집기에서 기본 제공업체를 선택할 수 있습니다.
[null,null,["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eGoogle's Reservations Waitlists integration allows partners to provide structured menu data for restaurants, enhancing their Google Business Profile and other Google surfaces.\u003c/p\u003e\n"],["\u003cp\u003ePartners need to follow specific guidelines for creating and uploading menu feeds, including using Generic Feeds and adhering to a daily upload cadence.\u003c/p\u003e\n"],["\u003cp\u003eMenu item options should only be included if they are required choices that impact the price or are essential to the dish, avoiding lengthy option combinations.\u003c/p\u003e\n"],["\u003cp\u003eRestaurants with multiple menus can utilize MenuSections to combine them into a single, structured menu within the feed.\u003c/p\u003e\n"],["\u003cp\u003ePartners should utilize development and testing tools like Menu Visualizer to ensure menu data accuracy and preview how it appears on various Google surfaces.\u003c/p\u003e\n"]]],["Partners using the Reservations Waitlists integration can integrate restaurant menus into Google Business Profiles via Generic Feeds. Key actions include completing account setup, understanding the feed upload process, and configuring the account for uploads. Menu data should adhere to a specific schema, with files named uniquely, including timestamps. Feeds require daily, full refreshes, limited to 1000 shards. Menu item options should only include required selections. One menu per restaurant is recommended, combining multiple menus into sections when necessary, and menus can be shared across restaurants.\n"],null,["# Overview\n\n| **Note:** Please fill out [this](https://tables.area120.google.com/u/0/form/9C6jXsBTJ-H87lYbmAA4L_/t/bfEXtCjIOfN88524UMV4zX8n1lccicZLz1xpvLdMmkGpbSm8og5CHXHdrn2heNl_Sp) form if you are interested in enabling menus for your existing Reservations Waitlists integration.\n\n\nGoogle partners can provide structured menu data to Google through the Reservations Waitlists\nintegration for use in the **Menu** section of a restaurant's Google Business Profile and other\nentry points across Google consumer surfaces.\n\n\nMenu data are ingested using the Generic Feeds. Before you begin:\n\n1. Make sure that you have completed [account setup](/actions-center/verticals/reservations/waitlists/integration-steps/setup)\n2. Understand the [Generic Feed upload process](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/generic-sftp)\n3. Understand how to [configure](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/generic-sftp) your account for Generic Feed uploads\n\nSchema\n------\n\nThe full menu schema can be found [here](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed).\n\nCreating and uploading Menu Feeds\n---------------------------------\n\nWhen creating and uploading Menu Feeds, follow these guidelines and conventions:\n\n- To provide restaurant details, follow the data specification described in [Merchant Feed](/actions-center/verticals/ordering/reservations/waitlists/reference/feeds/merchants-feed). For example JSON file refer to the [sample JSON](/actions-center/verticals/reservations/waitlists/reference/feeds/merchants-feed#samples). Data file names should be unique between uploads. It is recommended to include a timestamp in the filename, for example, `menu1_1633621547.json`\n- In the fileset descriptor for the menu feed, set the `name` field to `google.food_menu`. To see an example of the descriptor file contents, refer to the [Descriptor File JSON sample](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#descriptor-file). The names of descriptor files should be unique between uploads. It is recommended to include a timestamp in the filename, for example, `descriptor_1633621547.filesetdesc.json`. The descriptor file must be uploaded to the generic SFTP server as part of the menu feed.\n- Feeds must be uploaded to the generic SFTP server on a daily cadence as full refreshes.\n- Limit feeds to 1000 shards (files) as mentioned in [Using the Generic Feed sftp](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/generic-sftp)\n\nFeed ingestion status can be found in the [Feeds \\\u003e History](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds)\nsection of the partner portal. Feed SFTP server info can be found in the [Configuration \\\u003e Feeds](https://partnerdash.google.com/apps/reservewithgoogle/configuration/feeds)\nsection of the Partner Portal.\n\n\n**Figure 1:** Generic SFTP server info\n\nFeed ingestion status can be found in the [Feeds \\\u003e History](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds)\nsection of the Partner Portal. Feed SFTP server info can be found in the [Configuration \\\u003e Feeds](https://partnerdash.google.com/apps/reservewithgoogle/configuration/feeds)\nsection of the Partner Portal.\n\nWorking with menu item options\n------------------------------\n\n\nMenu item options can be specified using the\n[`MenuItemOption`](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#MenuItemOption-definition) proto.\n| **Note:** The exact user experience will depend on the Google surface. In Google Search, only the lowest priced MenuItemOption will be displayed to the user.\n\n\nPartners with multiple sets of\nrequired options for a single menu item (for example, a latte with size options and milk options)\nmust decide how best to display those options in Google. Google recommends the following:\n\n- The menu feed should match the partner's ordering site (or the restaurant's dine-in menu if you don't have an ordering site for the location). If the item is displayed with an individual price on the ordering site, a [`MenuItem`](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#MenuItem-definition) should be used. If the item is displayed with a base price and multiple options, a [`MenuItemOption`](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#MenuItemOption-definition) should be used.\n- Avoid including a long list of options, for example:\n - Chicken burrito\n - Chicken burrito with cheese\n - Chicken burrito with salsa\n - Chicken burrito with salsa and cheese\n - Chicken burrito with guacamole\n - Chicken burrito with guacamole and salsa\n- Menu item options are only supported if the dish **requires** one of the options to be selected. For example, when ordering a pizza, size is a required option. Menu item options that are for add-ons (i.e. \"option to add avocado\") are not supported and shouldn't be included in feeds.\n\nThe menu item option price should be the full price of the item with that option selected.\nThe price should be set for the menu item or for its options, but not for both.\n\nRestaurants with multiple menus\n-------------------------------\n\n\nA single restaurant (Entity) can only have one menu. For a restaurant which has multiple menus (i.e.\nseparate Lunch and Dinner menus) you can combine all menus into a single menu with [MenuSections](https://developers.google.com/actions-center/verticals/ordering/redirect/reference/menu-feeds/menus-feed#MenuSection-definition)\n(i.e. one menu with a section for Lunch and a section for dinner). The resulting menu would have\nthe following structure:\n\n- Menu\n - Lunch section\n - Soups\n - Soup 1\n - Soup 2\n - Sandwiches\n - Sandwich 1\n - Sandwich 2\n - Dinner section\n - Starters\n - Starter 1\n - Starter 2\n - Mains\n - Main dish 1\n - Main dish 2\n\nSharing menus across restaurants\n--------------------------------\n\n\nA single menu can be shared across multiple restaurants by including all restaurants in the\nmenu's `merchant_ids` list. Note that this list accepts entity ids for partners using\nthe [Entity](/actions-center/verticals/ordering/redirect/reference/feeds/entity-feed)\nfeed.\n\nBest Practices\n--------------\n\nThe following are best practices to follow when developing menu feeds.\n\n- Associate only one [menu](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#Menu-definition) to a restaurant. **Note:** The Menu section on a merchant's Google Business Profile does not differentiate between pickup and delivery menus. We recommend listing the menu information that most closely aligns with the merchant's in-store menu.\n- Provide the preferred language as the first language in the [TextField](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#TextField-definition). If you are sending multiple [LocalizedText](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed-proto-bundle#Localized-text-definition) objects, the first object in the text list is displayed to users.\n- All [menu items](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#MenuItem-definition) must be added to [menu sections](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/menus-feed#MenuSection-definition). Don't add menu items directly to the menu object.\n- Provide content using utf-8 encoding. It is not necessary to escape non-ascii characters.\n- If you are launching in multiple regions, ensure you are using the correct currency codes and denominations in the units and nanos field - pay extra caution to the nanos field which is 10\\^-9 of a unit. Use Menu Visualizer in [Inventory Viewer](https://actionscenter.google.com/inventory/fo-epa) to confirm you have correctly set prices.\n- Providing users with visually rich, comprehensive, and fresh menus is key to providing a helpful and engaging user experience. Prices, descriptions, photos, and dietary information are all key elements in driving decision making and partners are encouraged to provide as much of this data as possible to provide an optimal user \\& merchant experience.\n\nDevelopment \\& Testing Tools\n----------------------------\n\n\nAfter menu feeds are [launched](/actions-center/verticals/reservations/waitlists/add-ons/add-menus/onboarding-process#launch), your menu feed data will be eligible to surface on discovery experiences and may be\nvisible on the restaurant placesheet \"Menu\" tab. The menu tab is supported on Google\nSearch (mobile \\& desktop), and the experience will be expanding to additional surfaces including\nGoogle Maps. The rendered experience may differ depending on the surface.\n\n\n**Figure 3:** An example of how menu feed content is displayed on Business Profile on mobile \n\nTo ensure your menu is structured correctly use Menu Visualizer in [Inventory Viewer](https://actionscenter.google.com/inventory/fo-epa)\nto preview your menus.\n| **Note:** The menu from your feed may not appear for a restaurant if there are multiple menu providers for the restaurant.\n\n\nRestaurant menus can come from many sources, including from restaurants themselves via their\nGoogle Business Profile, food ordering and reservations partners, user photos of menus, and more.\nIf multiple sources are providing menus for the same restaurant, the merchant can [choose a preferred provider](https://support.google.com/business/answer/9455840?sjid=3456950423954086848-NA#zippy=%2Cselect-preferred-menu)\nin the Google Business Profile menu editor."]]
