Booking
Appointments, calendars, availability and bookings.
8 pages
All topics in this area
- Appointment Booking — SettingsThis is where you set up the foundations of your appointment-booking feature: which products and appointment types are bookable, which staff and teams…
- Booking AnalyticsThis page gives you an overview of how busy your appointment-booking team is. Booking Analytics shows the daily workload per staff member, open…
- Booking ManagementThis page lists every appointment booked through your booking widgets - with customer, appointment type, assigned staff member, and status. From here…
- Booking WidgetsBooking widgets are embeddable booking forms you can place on your website or in emails so customers can book appointments themselves. This page is…
- Email Rules (Booking)Email rules let you automate what happens on certain booking events — for example, tagging a booking with a label, assigning it to a specific staff member…
- Google WorkspaceThis is where you connect SELLERLOGIC Commerce Services to your Google Workspace so users from a specific organizational unit can be automatically…
- My BookingsThis page shows your own upcoming appointments and your own recorded availability. It's meant only for you, as a bookable staff member, and never…
- Staff AbsencesUse this page to record when a bookable staff member is unavailable (e.g. vacation or sick leave). The system automatically checks which existing…
What's new?
-
The calendar id is no longer stored twice
With the Google Workspace sync, a person's calendar id is always their email address. Until now that address was therefore written a second time into the staff member's Google calendar id field - the same address stood in the record twice. From now on it is only derived there: the field stays empty for synced staff members and the appointment scheduling uses the stored email address automatically. The same identifier is still displayed, and nothing changes about booking. An identifier entered by hand - a room or resource calendar, for instance - stays untouched and still takes precedence. Existing duplicates are cleared by the system on its next start.
-
The shared Google key belongs to the personnel area while the calendar integration is running
Since appointment booking and the calendar integration use the same Google service account, it could be overwritten on the Google Workspace page by people who may only manage appointments - in the worst case the calendar sync of the entire workspace stood still afterwards. While the calendar integration runs on that access, admin email, domain and the key are now reserved for the Manage calendar integration permission; an attempt to save without it is refused and leaves the existing credentials untouched. You still set the organisational unit here as before, and a workspace without an active calendar integration sets the connection up on this page unchanged.
-
Booking dashboard now shows load errors instead of empty lists
When one of the four booking dashboard views (Daily Overview, Reschedule Requests, Analytics, Reporting) failed to load - for example due to an expired session or a server error - it used to show the exact same empty state as a day with genuinely no bookings. A failed load now shows its own error message, so it is clear whether there really is nothing to show or the request should be retried.
-
Booking list now shows a fault message on a load error (#3406)
A failed booking list request used to render the same empty table used for genuinely zero bookings - the list already knew about the error internally, it just never displayed it. The list now shows a visible notice that loading failed.
-
Booking page styling completed
Part of the styling was missing on the public booking page: font sizes, spacing and table headers of the shared controls were not shipped and fell back to inherited values. The page now ships its styling in full and looks like the rest of the product.