Booking

In Kasura

A booking in Kasura is the central record that reserves a specific asset for a specific customer over a specific period, carrying the agreed price, the deposit arrangement and the current payment state as part of the same record. This single-record design exists so these interdependent pieces of information — what is booked, for how much, with what security, and whether it has been paid — cannot drift apart into separate, inconsistent sources. Depending on workspace type, a booking takes on more specific terminology: in a vehicle workspace it becomes a reservation before pickup and an active rental once handed over; in an accommodation workspace it becomes a stay, measured in nights between check-in and check-out. These are specializations of the same booking concept, following the same overall lifecycle — reserved, active, returned — even though the vocabulary differs. Kasura deliberately treats a booking record as distinct from the operational work required to fulfil it: creating a booking is broken into ordered sections (asset and customer selection, dates and duration, advanced options) rather than a single flat form, reflecting the view that staff need to know the next step, not simply see a complete data record. A booking precedes and triggers the corresponding handover process — pickup for vehicles, check-in for accommodation — and its lifecycle stage determines which actions are currently available on it.