Bookings
Time slots, resources, and guests — booked.
Whatever gets reserved — courts, rooms, tables, appointments — bookings tie the resource, the guest, and the payment together, so double-booking and unpaid slots stop happening.
- Resources you define
- Guests with history
- Bookings with payments
- A booking report that adds it up
What it does
Bookings, in practice.
- Bookings
- Guests
- Resources
- Payments
Any bookable thing
Define your resources — courts, rooms, chairs, equipment — and take bookings against them.
Guests, not strangers
Guest records keep history, so regulars are recognized and no-shows are remembered.
Money attached
Payments record against the booking, so the calendar and the cash agree.
Reported like revenue
The booking report totals what happened — by period and by branch.
Runs alongside anything
A gym with a shop, a hotel with a restaurant — bookings share clients and books with the rest of your platform.
Only need this module?
Buy just Bookings — Flowyana is sold per module, sized by your users and branches. Add more only when you want more.
How pricing works →One platform
Plays well with the rest.
Bookings shares its records with every other module you switch on — no connectors, no syncing, no re-typing.
Questions
Asked about bookings.
What can be booked?
Anything you define as a resource — sports courts, rooms, studios, appointments, equipment. Bookings hold the time, the guest, and the payment together.
How is this different from rentals?
Bookings reserve time on a resource; rentals hand an asset over and track it until it comes back. Many businesses use both — they share the same clients and books.
Can we take payment with the booking?
Yes — payments record against bookings, so unpaid slots are visible before the guest arrives.
Put Bookings to work.
Tell us what your business runs. We’ll show you this module live — on its own or alongside the rest — and follow up with an itemized quote.