Stay organized with collections
Save and categorize content based on your preferences.
The following is a high level overview of the Actions Center Reservations End-to-End integration
process.
Figure 1. Onboarding overview for the Reservations End-to-End integration.
Onboarding plan
Your End-to-End onboarding plan is outlined in the Home tab of the Actions Center.
This plan tracks your integration progress with milestones that turn green upon completion. Each
milestone includes relevant tasks that track each integration step. Tasks turn green upon
completion or provide errors that you need to resolve before you move to the next task.
Your integration launches after you successfully pass the Sandbox and subsequent Production
reviews.
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.
Sandbox review:
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.
Production development
When you complete Sandbox testing, your Production inventory becomes bookable, but end users can't
discover externally on Google.
Production implementation:
deploy your tested Sandbox infrastructure to your Production environment.
Production review:
Google reviews a series of test cases against your Production inventory.
Launch
Google enables your inventory after the Production review of your integration succeeds. This
completes the integration, and any external user can book or reserve your inventory through the
Actions Center.
Launch and monitor:
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-22 UTC."],[[["The Reservations End-to-End integration requires daily Merchant, Service, and Availability feeds via SFTP, ensuring accurate location details for Google listing matching."],["A booking server is essential for managing reservations, confirming availability, and handling booking modifications, adhering to Google's performance thresholds."],["Real-time updates, while optional, enable immediate booking and availability changes, improving user experience by reducing unbookable slots."],["Consider 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."],["Merchants 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."]]],["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"]]
