Free serviced apartment booking system

Problem: A paper diary cannot tell a guest which particular apartment or room is free.

Cabans feature: Create a separate Short Let listing for each independently bookable unit. Each has its own availability, nightly prices and booking rules. Bookings are on by default; review and save each calendar before sharing its listing.

Result: Guests choose dates for the actual unit you advertised. Keep outside bookings blocked manually: Cabans has no calendar sync.

Problem: Transfer screenshots and phone promises leave your team unsure whether a stay is confirmed.

Cabans feature: Guests pay online through Paystack when they book. Paystack's fee is paid by the guest. With instant book on, paid bookings confirm straight away; otherwise you accept or decline a paid request within your answer time.

Result: Your team works from the booking status. You are paid after the stay; the payment and payout help explains the terms. Free software does not mean booking payments have no charges.

Problem: Different notebooks for different rooms make arrivals and unanswered requests easy to miss.

Cabans feature: Your store's Bookings page has Requests, Upcoming, Arriving, In house, Leaving, Past and Cancelled tabs. Select one unit in the Property filter or leave All properties selected.

Result: Reception can review the whole operation and then open the right stay. Deposits are handled on the booking, including finished stays that still need attention.

Problem: Repeating arrival instructions by message creates gaps, and sending door codes too early creates avoidable risk.

Cabans feature: Save house rules, check-in instructions and the Wi-Fi network name in Stay information. Those appear from confirmation. The door code and Wi-Fi password appear only while the guest is checked in, and are never emailed.

Result: Guests see the right information at the right stage. Your team still prepares the unit, hands over access and approves check-in.

Problem: A request for towels or help can disappear between a phone call and a shift change.

Cabans feature: Guests use their stay page to request room service, a cleaner, help or an issue response. Your team receives an email for each request and can press Start, then Mark as done.

Result: A request has a visible status against its stay. You arrange and deliver the service; a cleaner request is not a housekeeping rota.

Problem: Breakfast, bottled water or an airport pick-up can be delivered without a clear record of what the guest owes.

Cabans feature: Add stay extras and choose the units that offer them. Checked-in guests can buy from their stay page. For extras they used, choose quantities in Bill the guest and send a bill for online payment.

Result: The stay carries the request for payment. Your team agrees what is offered, delivers it and checks whether the bill has been paid. This is not a restaurant POS or stock-control system.

Problem: A disagreement about damage is harder to resolve when neither side has a useful record.

Cabans feature: Set a caution deposit on the listing, add check-in and check-out condition photos, and release the deposit after checking the unit. If you raise a dispute, the Cabans team considers the evidence and decides.

Result: Your team follows a defined deposit process rather than negotiating an undocumented deduction. Photos should show the actual condition, not an assumed cause of damage.

Problem: Sharing the owner's sign-in makes it hard to control who can change a booking.

Cabans feature: Add team users to the store and assign roles. Read access lets a role see bookings and calendars; processing access also permits booking actions, calendar changes, check-in and access to door codes.

Result: Each person signs in with their own account and works within the role you assign. Review the full permission table: read access also includes information such as Earnings, so do not assume it hides money.