リアルタイム更新は必須ではありませんが、ユーザーが空き状況にアクセスする前に、予約のキャンセルや空き状況の変更に関する最新情報を非同期で Google に送信できます。これにより、BatchAvailabilityLookup が失敗した場合に、ユーザーに表示される予約不可の時間が全体的に減ります。詳しくは、リアルタイム更新の構造化に関するドキュメントをご覧ください。
[[["わかりやすい","easyToUnderstand","thumb-up"],["問題の解決に役立った","solvedMyProblem","thumb-up"],["その他","otherUp","thumb-up"]],[["必要な情報がない","missingTheInformationINeed","thumb-down"],["複雑すぎる / 手順が多すぎる","tooComplicatedTooManySteps","thumb-down"],["最新ではない","outOfDate","thumb-down"],["翻訳に関する問題","translationIssue","thumb-down"],["サンプル / コードに問題がある","samplesCodeIssue","thumb-down"],["その他","otherDown","thumb-down"]],["最終更新日 2024-11-09 UTC。"],[[["The Reservations End-to-End integration requires daily Merchant, Service, and Availability feeds sent via SFTP, with consistent location details for accurate Google listing matching."],["Merchants can only have one service for displaying availability and should use a static `service_id` across all merchants if reservations are their only service."],["A booking server is required to manage availability and bookings, adhering to specific error rate and latency thresholds for optimal user experience."],["Real-time updates for booking cancellations or availability changes are recommended to improve accuracy and user experience."],["Consider additional features like sharding for large datasets, restaurant approval for reservations, seating sections, cancellation windows, waitlists, no-show fees, and minimum advanced booking times to align with specific business needs."]]],[]]