تنظيم صفحاتك في مجموعات
يمكنك حفظ المحتوى وتصنيفه حسب إعداداتك المفضّلة.
في ما يلي نظرة عامة شاملة على عملية دمج ميزة "الحجوزات الشاملة" في "مركز الإجراءات".
الشكل 1. نظرة عامة على عملية إعداد ميزة "الحجوزات الشاملة"
خطة الإعداد
يتم توضيح خطة الإعداد الشامل في علامة التبويب الصفحة الرئيسية في "مركز الإجراءات".
تتتبّع هذه الخطة مستوى تقدّمك في عملية الدمج من خلال معالم رئيسية يتحوّل لونها إلى الأخضر عند اكتمالها. يتضمّن كل معلم رئيسي المهام ذات الصلة التي تتتبّع كل خطوة من خطوات الدمج. تتحوّل المهام إلى اللون الأخضر عند اكتمالها أو تعرض أخطاء عليك حلّها قبل الانتقال إلى المهمة التالية.
يتم إطلاق عملية الدمج بعد اجتياز مراجعات Sandbox وProduction اللاحقة بنجاح.
التحديثات في الوقت الفعلي جاهزة:
تتيح لك التحديثات في الوقت الفعلي إرسال إشعارات بشأن عمليات إلغاء الحجز قبل أن يحاول المستخدم الاطّلاع على
مدى توفّر الأماكن.
مراجعة Sandbox:
تراجع Google سلسلة من حالات الاختبار مقارنةً بمستودع Sandbox. بعد اجتياز مراجعة Sandbox بنجاح، يتحوّل تركيزك من بيئة Sandbox إلى بيئة الإنتاج.
تطوير الإنتاج
عند إكمال اختبار Sandbox، يصبح مستودعك المتاح للبيع في مرحلة الإنتاج قابلاً للحجز، ولكن لا يمكن للمستخدمين النهائيين العثور عليه خارجيًا على Google.
مراجعة الإصدار العلني:
تراجع Google سلسلة من حالات الاختبار مقارنةً بمستودع الإصدار العلني.
إطلاق
تتيح Google مستودعك الإعلاني بعد نجاح مراجعة عملية الدمج في بيئة الإنتاج. بهذا الإجراء، تكتمل عملية الدمج، ويمكن لأي مستخدم خارجي حجز أو حجز مسبق لمنتجاتك من خلال "مركز الإجراءات".
الإطلاق والمراقبة:
بعد الإطلاق، من المهم مراقبة حالة عملية الدمج. سيؤدي عدم الحفاظ على حدود Health Check المتسقة إلى إيقاف عملية الدمج.
تاريخ التعديل الأخير: 2025-07-26 (حسب التوقيت العالمي المتفَّق عليه)
[null,null,["تاريخ التعديل الأخير: 2025-07-26 (حسب التوقيت العالمي المتفَّق عليه)"],[[["\u003cp\u003eThe Reservations End-to-End integration requires daily Merchant, Service, and Availability feeds via SFTP, ensuring accurate location details for Google listing matching.\u003c/p\u003e\n"],["\u003cp\u003eA booking server is essential for managing reservations, confirming availability, and handling booking modifications, adhering to Google's performance thresholds.\u003c/p\u003e\n"],["\u003cp\u003eReal-time updates, while optional, enable immediate booking and availability changes, improving user experience by reducing unbookable slots.\u003c/p\u003e\n"],["\u003cp\u003eConsider features like sharding for large Availability feeds, and explore additional functionalities like Async Booking, seating sections, waitlists, and cancellation windows for enhanced business logic implementation.\u003c/p\u003e\n"],["\u003cp\u003eMerchants in Reservations End-to-End are limited to a single service for displaying availability, and a static service_id is recommended for consistency across locations.\u003c/p\u003e\n"]]],["The Reservations End-to-End integration requires daily Merchant, Service, and Availability feeds via SFTP, ensuring location data matches Google listings. A booking server handles availability checks and booking actions, with specified latency and error thresholds. Define the party size for all availability. Real-time updates are optional but enhance accuracy. File sharding is required if compressed availability feeds exceed 200MB. Additional features like async booking, seating sections, cancellation windows, waitlists, and minimum booking time are available.\n"],null,["# Integration Overview\n\nThe following is a high level overview of the Actions Center Reservations End-to-End integration\nprocess.\n**Figure 1.** Onboarding overview for the Reservations End-to-End integration.\n\nOnboarding plan\n---------------\n\n\nYour End-to-End onboarding plan is outlined in the [**Home** tab of the Actions Center](https://actionscenter.google.com/home).\nThis plan tracks your integration progress with milestones that turn green upon completion. Each\nmilestone includes relevant tasks that track each integration step. Tasks turn green upon\ncompletion or provide errors that you need to resolve before you move to the next task.\n\n\nYour integration launches after you successfully pass the Sandbox and subsequent Production\nreviews.\n\n### Get started\n\n1. [Setup](/actions-center/verticals/reservations/e2e/integration-steps/setup):\n 1. [Configure contact information](/actions-center/verticals/reservations/e2e/integration-steps/setup/config-contact-info)\n 2. [Upload your public SSH key](/actions-center/verticals/reservations/e2e/integration-steps/setup/public-ssh-key)\n 3. [Configure Booking Server credentials](/actions-center/verticals/reservations/e2e/integration-steps/setup/config-booking-server)\n 4. [Enable Cloud APIs](/actions-center/verticals/reservations/e2e/integration-steps/setup/enable-cloud-apis)\n 5. [Configure your brand](/actions-center/verticals/reservations/e2e/integration-steps/setup/config-brand)\n\n### Sandbox development\n\n2. [Feeds Ready](/actions-center/verticals/reservations/e2e/integration-steps/feeds): feeds transmit merchant, services, and availability data to the Actions Center.\n 1. [Merchant Feed Ready](/actions-center/verticals/reservations/e2e/integration-steps/feeds/merchants-feed)\n 2. [Services Feed Ready](/actions-center/verticals/reservations/e2e/integration-steps/feeds/services-feed)\n 3. [Availability Feed Ready](/actions-center/verticals/reservations/e2e/integration-steps/feeds/availability-feed)\n 4. [Data quality check](/actions-center/verticals/reservations/e2e/integration-steps/feeds/data-quality-check)\n3. [Booking Server Ready](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready): the Booking Server acts as Google's entrypoint to confirm the availability and also to create, update, delete, and modify the bookings made through Google surfaces.\n 1. [BatchAvailabilityLookup](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready/batchavailabilitylookup): [page load](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready/batchavailabilitylookup#page-load) and [slot click](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready/batchavailabilitylookup#slot-click)\n 2. [CreateBooking Ready](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready/createbooking)\n 3. [Enable availability checker](/actions-center/verticals/reservations/e2e/partner-portal/dashboards/other-dashboards#availability_checker)\n 4. [UpdateBooking Ready](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready/updatebooking)\n 5. [Health check](/actions-center/verticals/reservations/e2e/integration-steps/booking-server-ready#health-check)\n4. [Real-Time Updates Ready](/actions-center/verticals/reservations/e2e/integration-steps/real-time-updates-ready): Real-Time Updates (RTUs) let you send updates on booking cancellations before a user attempts to access your availability.\n - [BookingNotification Ready](/actions-center/verticals/reservations/e2e/integration-steps/real-time-updates-ready/bookingnotification-ready)\n5. [Sandbox review](/actions-center/verticals/reservations/e2e/integration-steps/sandbox): Google reviews a series of test cases against your Sandbox inventory. After you successfully pass your Sandbox review, your focus shifts from the Sandbox environment to the Production environment.\n\n### Production development\n\n\nWhen you complete Sandbox testing, your Production inventory becomes bookable, but end users can't\ndiscover externally on Google.\n\n6. [Production implementation](/actions-center/verticals/reservations/e2e/integration-steps/move-to-prod): deploy your tested Sandbox infrastructure to your Production environment.\n7. [Production review](/actions-center/verticals/reservations/e2e/integration-steps/prod-review): Google reviews a series of test cases against your Production inventory.\n\n### Launch\n\n\nGoogle enables your inventory after the Production review of your integration succeeds. This\ncompletes the integration, and any external user can book or reserve your inventory through the\nActions Center.\n\n8. [Launch and monitor](/actions-center/verticals/reservations/e2e/integration-steps/launch-and-monitoring): after you've launched, it's important to monitor the health of your integration. Failure to maintain consistent Health check thresholds results in integration take-down."]]
