Booking Calendars
For Booking-type shops (for example lodging, rentals, services, or any schedule-based offering), Etalasse provides a booking calendar system that manages availability, sessions, and blocked dates.
Beyond fixed sessions, services can use duration and buffer, staff, deposits (DP), rescheduling, and no-shows. All of it is optional per service: see the booking depth section below.
The feature appears under Products → Booking Calendars and Products → Blocked Dates, and is only available for Booking-type shops.
How booking calendars work
Availability belongs to a calendar, not directly to a product. A single calendar can be shared by several products or variants, so schedules do not have to be configured over and over.
Supported calendar types:
- Global — one calendar for the entire shop
- Seller — a calendar owned by a seller (for multivendor shops). Sellers create and manage these themselves in the Seller Center; the merchant does not manage them from the dashboard
- Product — a calendar dedicated to a single product
- Custom — a special-purpose calendar for specific needs
Each calendar manages:
- weekly sessions — the schedule of available slots and their capacity
- blocked dates — dates deliberately closed (holidays, maintenance, private events)
- booked dates — dates already reserved by customers
Preventing schedule conflicts
Etalasse checks for time overlaps, not just exact session matches. A new booking whose time overlaps another booking on the same calendar is rejected, so double bookings cannot happen.
Blocking dates also follows the calendar type: blocking a date on a Global calendar closes the entire shop on that date, while blocking on a Product calendar only closes that product.
Sessions that have passed
A session whose time has passed can no longer be booked, from Catalog and Link or from POS. "Passed" is judged on the shop time zone (WIB by default), not the customer's phone. Example: a shop in Jayapura uses WIT. The 10:00 session closes at 10:00 WIT, even when a customer books from Jakarta, where it is only 08:00.
Fixed sessions or duration
A calendar supports two ways for customers to choose a time:
- Fixed sessions (default): the customer picks one session from the weekly schedule, with a capacity per slot
- Duration: the customer picks a start time, and the weekly sessions are read as open hours. Slots are computed from the service duration, buffer, and slot interval. See Service Duration and Buffer
Booking depth
| Topic | What it covers |
|---|---|
| Service Duration and Buffer | service length, buffer, slot interval, minimum notice, days ahead |
| Staff, Schedules, and Time Off | the people who perform services, working hours, and leave |
| Choosing Staff | staff modes and the "anyone" rule |
| Deposit and Refund Window | deposits, free cancellation, and a worked example |
| Rescheduling Bookings | by customer and merchant, limits, policy |
| No-shows | manual and automatic marking |
| Booking Reminders | WhatsApp the day before and notifications |
| Booking List and Calendar | monitoring and handling bookings, recording the balance |
| Booking Plans and Roles | Growth plan, staff quota, and cashier role |
| Booking FAQ | frequently asked questions |
A shop that sets nothing up keeps running as before: fixed sessions, no staff, no deposit.
Recommended setup flow
- decide on the calendar structure — one global calendar, or one per product/seller
- create the calendars in Products → Booking Calendars
- configure weekly sessions and the capacity of each slot
- link products or variants to the appropriate calendar
- block holidays or unavailable dates in Products → Blocked Dates
- place a test booking from a customer channel to verify availability
What customers see
In Catalog and Link, customers see an availability calendar on booking product pages — available, booked, and blocked dates — then pick a schedule before ordering.