Boni Hotel OS
Manage properties, room types, availability, rates and bookings for hotels, resorts, homestays and serviced apartments.
What a hotel operator manages
Boni Hotel OS holds a property's sellable inventory and its bookings in one place, so direct, partner and Boni-sourced demand all draw on the same availability instead of separate spreadsheets or extranets.
Operators work in the Hotels workspace in Boni Panel.
| Object | What it represents |
|---|---|
| Property | A hotel, resort, homestay or serviced apartment, with its address and details |
| Room type | A sellable category rather than a specific physical room |
| Availability | How many of that room type can be sold for a given date |
| Rate | The price attached to a room type for a date or period |
| Booking | A confirmed stay, created by confirming a hold |
Selling by room type rather than room number is deliberate: it is how demand actually arrives, and it lets the property assign specific rooms at arrival without an availability recount.
Who it suits
Independent hotels, resorts, homestays, serviced apartments and small groups that want to keep control of their own inventory and reduce dependence on a single distribution channel. Larger chains with deep existing PMS and channel-manager integrations should read the boundaries in the Reservations overview before planning a move.
What connects to it
| Layer | What it does |
|---|---|
| Boni Panel | Day-to-day operator work on inventory, availability, rates and bookings |
| Hotel inventory API | Scoped programmatic access to inventory, availability, rates, holds and bookings |
| Bow Chat | Guest enquiries, messages and calls, with the reservation record staying authoritative |
| Boni CRM and Accounting | Account relationships and financial records where those modules are enabled |
Before you plan a rollout
Availability, holds and bookings behave the same way across both reservation products; read Inventory and availability for the exact model. Cancellation, refund, connector and settlement depth is configured per implementation; confirm the exact scope during onboarding.