# Boni Reservations

Keep hotel or bus inventory, availability and bookings in one operator system, with Hotel OS and Bus OS over a shared core.

## Two products, one reservations core

Boni Reservations keeps an operator's sellable inventory, its live availability and its bookings in one system, then lets that inventory be sold through more than one channel without a second source of truth.

It is delivered as two operator products over a shared core:

| Product | Who it is for | Operator workspace |
|---|---|---|
| [Boni Hotel OS](/reservations/hotel-os) | Hotels, resorts, homestays, serviced apartments and small groups | **Hotels** in Boni Panel |
| [Boni Bus OS](/reservations/bus-os) | Private intercity bus operators, fleets, counters and agent networks | **Buses** in Boni Panel |

Screens use the language of the business. Hotel operators see properties, room types and rates; bus operators see routes, trips, seats and fares. The shared core underneath is an implementation detail, not something an operator has to learn.

## In this section

| Page | What it covers |
|---|---|
| [Boni Hotel OS](/reservations/hotel-os) | Properties, room types, rates and hotel booking operations |
| [Boni Bus OS](/reservations/bus-os) | Routes, trips, seat pools, fares and counter or agent selling |
| [Inventory and availability](/reservations/inventory-and-availability) | How units, availability, holds and bookings behave across both products |

## What runs today

Boni Reservations is in production. The reservations core, both operator workspaces and the scoped APIs are live and carry real inventory:

- canonical inventory units, dated availability, and rates or fares;
- holds that expire, with safe retries;
- confirmation of a hold into a booking.

Cancellation and refund workflows, channel connectors, settlement and outbound webhooks are configured per implementation rather than shipped as one fixed shape, because operators differ on all four. Boni agrees that scope with you during onboarding.

Boni Reservations is not a like-for-like replacement for every feature of a mature PMS, channel manager or bus GDS, and onboarding names what stays with an existing system. Where guest or passenger conversations matter, the reservation system stays authoritative for booking facts and [Bow Chat](/bow-chat/groups-monitoring) handles the conversation.

Talk to Boni to scope a reservations rollout.

Canonical: https://docs.boni.one/reservations/overview
Version: 3
Updated: 2026-08-19T09:27:47.867Z