Resource and calendar
Slot, room, vehicle, service — with duration and capacity. The staff day view and the client availability view come from one calendar.
Capabilities · Operational platforms
Booking systems — resource, availability and confirmation
A booking is a set of availability rules, not just a calendar. The platform holds the resource (a slot, a room, a vehicle, a service), a hold, a deposit and release after cancellation. A clash is visible at save time. The same engine can later sit under tourist-offer sales or a unit — without a second calendar.
Resource · calendar · rules
When a calendar in mail stops working
Two channels book the same slot. The deposit arrived and the calendar still says free. A cancellation does not release the date. Staff see a different day queue than the client on the website. Overbooking appears after the invoice. A second property or a second service type produces a second spreadsheet.
Modules
What sits in this process
Availability rules
Minimum / maximum time, buffer, overbooking, service blocks, season. The rule runs at save time, not as a comment on the calendar.
Channels
Website, partner, call centre, API. A clash between channels is visible immediately. The partner does not get a private copy of the calendar.
Deposit and confirmation
The booking waits for payment or becomes confirmed. No payment in time releases the slot. The invoice binds to the booking.
Cancellation and no-show
Resource release, refund rule, a no-show mark. No-show statistics are not a manual tick list.
Day queue
Staff see what is on today, what waits for confirmation, what collides. The client — their status and documents.
Integrations
- Payment gateway — deposit, supplement, refund after cancellation.
- Mail / SMS confirmation and a reminder before the date.
- API for a partner or the own website — the same resource state.
- Reports: utilisation, no-shows, revenue per slot, sales by channel.
Directed solutions
- Services with a calendar — a room, a hall, equipment, a service slot.
- A property with rooms or stations — capacity and blocks.
- A layer under travel or unit sales — one engine, a different product on top.
Example first stage
One resource type and one channel: calendar → collision rule → booking → deposit → confirmation or release. Tests: two parallel saves, cancellation, missing payment. Next stage — a second channel or a second resource type.
Related areas
Describe your business need — we will propose the right technology and the next work stages. Contact: [email protected]
Go to contactView all capabilities