食事の座席セクションを追加する

レストランには、バーやパティオなどの個別の座席エリアがあり、5 コースの試食メニューやワイン テイスティングなど、さまざまな体験を提供するのが一般的です。アクション センターではこの区別がサポートされており、ユーザーはテーブルを予約する領域を指定できます。

予約可能な時間枠と会議室名

図 1: 座席セクションのあるレストランのスロット選択例

このインベントリの分離を使用するには、可用性スロットの resources メッセージで room_id、room_name、フィールドを設定します。部屋の説明を含めるには、Resources メッセージ内の room_description フィールドを使用します。

// A resource is used to disambiguate availability slots from one another when
// different staff, room or party_size values are part of the service.
// Multiple slots for the same service and time interval can co-exist when they
// have different resources.
message Resources {
  // One of staff_id, room_id, or party_size must be set.

  // Optional ID for a staff member providing the service. This field identifies
  // the staff member across all merchants, services, and availability records.
  // It also needs to be stable over time to allow correlation with past
  // bookings. (optional but required if staff_name is present)
  string staff_id = 1;

  // Optional name of a staff member providing the service. This field will be
  // displayed to users making a booking, and should be human-readable, as
  // opposed to an opaque identifier. (optional but required if staff_id is
  // present)
  string staff_name = 2;

  // An optional ID for the room the service is located in. This field
  // identifies the room across all merchants, services, and availability
  // records. It also needs to be stable over time to allow correlation with
  // past bookings. (optional but required if room_name is present)
  string room_id = 3;

  // An optional name for the room the service is located in or experience of
  // of the service. This field will be displayed to users making a booking,
  // and should be human readable, as opposed to an opaque identifier.
  // A room name should only be used for seating areas or prepaid experiences.
  // Examples of room names include "Bar", "Patio", "Dining Room". Examples of
  // dining experiences using room names include "Five-Course Tasting Menu",
  // "Chef Omakase". It is strongly recommended that the default seating area
  // does not have a room associated with it.
  string room_name = 4;

  // Applicable only for Dining: The party size that can be accommodated
  // during this time slot. A restaurant can be associated with multiple Slots
  // for the same time, each specifying a different party_size, if for instance
  // 2, 3, or 4 people can be seated with a reservation. (optional)
  int32 party_size = 5;

  // Localized room description with a limit of 500 characters. If set,
  // a default value must be provided, it is preferred to use the common
  // languages for the merchant's locale.
  Text room_description = 7;
}

この情報はスロット定義の不可欠な部分であり、すべての予約オペレーションとリアルタイム更新オペレーションに加えて、フィードにも含める必要があります。room_id と room_name の指定例については、食事、縦型固有のフィード例をご覧ください。

エクスペリエンスの部屋名を使用した空きスロット

予約のお支払いリダイレクトを実装済みまたは実装中の場合は、room_name と room_descriptions を使用して、事前払いのダイニング エクスペリエンスを実現できます。次のスクリーンショットは、ウェブでどのように表示されるかを示しています。

図 1: 部屋の説明を含む座席セクションがあるレストランの例の座席選択

部屋のサンプル

{
  "availability": [{
    "merchant_id": "dining-A",
    "service_id": "reservation",
    "start_sec": 1535853600,
    "duration_sec": 2700,
    "spots_total": 2,
    "spots_open": 2,
    "resources": {
      "room_id": "A-dining-room",
      "room_name": "Bar",
      "party_size": 2,
      }
    }
  }]
}

エクスペリエンスのサンプル

{
  "availability": [{
    "merchant_id": "dining-A",
    "service_id": "reservation",
    "start_sec": 1535853600,
    "duration_sec": 2700,
    "spots_total": 2,
    "spots_open": 2,
    "resources": {
      "room_id": "A-dining-room",
      "room_name": "Wine Tasting Menu Pair",
      "description": "This Wine Tasting Menu Pair showcases American cuisine rooted in the nostalgic flavors of the 20th century American experience. Each experience is hand-crafted, with a progression from small bites to more substantial plates.",
      "party_size": 2,
      }
    }
  }]
}