The following describes the details of the Reserve with Google integration process that are unique to the beauty vertical.
Integration
Follow the standard high-level integration process outlined in the end-to-end integration guide.
Key Beauty Guidance
The following are examples and tutorial covering features that are required by the beauty integration:
- Feeds:
- Managing Availability Feed Size
- Availability feeds in the beauty vertical tend to be very large and
require various features to manage:
- Use sharding on the availability feed
- We recommend compressing your feeds before sending them
- Stylists’ Schedules
- If you have multiple Stylists that you allow users to choose from, you will need to implement staff_id and staff_name fields within the service_availability.availability.resources message
- Sample Beauty Feeds
- Booking Server:
- Implement the standard booking server integration
- Real-time updates:
- Structuring Real-Time Updates
- Note: You cannot update a time within a slot recurrence without updating
- The start_timestamp_restrict and end_timestamp_restrict in v1alpha.inventory.partners.availability and v1alpha.inventory.partners.merchants.services.availability endpoints only apply to the start_sec of the recurrence structure
Optional Beauty Features
Below are a list of features that are compatible with the beauty integration. None of these are required, but many will be necessary to make sure Reserve with Google follows your company’s business logic when serving your inventory:
- Appointments Requiring Merchant or Stylist Approval (Async Booking)
- Adding cancellation windows
- Setting a minimum advanced booking time
- Adding merchant specific terms
- Enabling service prepayment
- Recurrences: Modeling slot as repeating events in a day