Boni

Boni Reservations

Choose the reservation system that matches the operator.

Explore Boni Hotel OS, Boni Bus OS, and the underlying inventory APIs for availability, rates or fares, holds, bookings, distribution, operator work, and AI-assisted exceptions.

For: Independent hotels, resorts, homestays, small chains, private bus operators, fleets, counters, agents, and travel platforms.

Boni Reservations: operating workflow
  1. 01Set up the operator
  2. 02Publish availability
  3. 03Hold inventory
  4. 04Confirm the booking

Shared context · Clear responsibility · Review where it matters

Hotel OS
A hotel-native product for PMS workflows, room inventory, rates, reservations, guest operations, channels, and owner review.
Bus OS
A bus-native product for routes, trips, seats, fares, agents, manifests, bookings, channels, and operator review.
Shared foundation
Booking state, availability control, payments, webhooks, audit, channel sync, and operator exceptions.

How it works

Give every sales channel the same availability and booking truth.

The operator experience stays specific to the business while the underlying reservation lifecycle stays consistent and auditable.

  1. 01

    Set up the operator

    Create the property or transport operator, locations, roles, policies, inventory structure, and commercial rules.

  2. 02

    Publish availability

    Maintain rooms or seats, rates or fares, schedules, restrictions, and the channels allowed to sell them.

  3. 03

    Hold inventory

    Create time-bounded holds so two channels do not sell the same room or seat while a buyer completes checkout.

  4. 04

    Confirm the booking

    Turn a valid hold and payment outcome into one confirmed reservation with customer and source references.

  5. 05

    Operate changes

    Handle cancellation, release, refund, reschedule, guest or passenger updates, and service exceptions from the same record.

  6. 06

    Reconcile distribution

    Review bookings, channel source, payments, settlement, availability drift, and operator follow-up.

Product scope

What the product covers.

Hotel properties, rooms, rate plans, availability, holds, bookings, and guest workflows.

Bus operators, routes, stops, trips, buses, seat maps, fares, holds, and bookings.

Direct, agent, Bino, API, and approved external distribution paths.

Idempotent booking and payment references so callbacks do not create duplicate reservations.

Cancellations, inventory release, refund state, and operator-visible exceptions.

Customer confirmations and service follow-up connected to the reservation.

Payments and settlement evidence without treating the booking service as the accounting ledger.

API-first availability and booking contracts for approved partners.

Operator-specific views over a shared, auditable reservation core.

Built around your business operations.

Connect the right people, records and systems around your workflow, with clear ownership and the controls your team needs.

Designed for each operator

Hotel OS brings rooms, rates, stays and guest operations together. Bus OS organizes routes, trips, seats, fares and passenger operations. Each team works with the screens and terminology its business uses.

Inventory ownership is explicit

Each rollout defines which inventory Boni owns, mirrors, or distributes and how conflicts, stale availability, and channel updates are handled.

Payments do not equal settlement

A successful customer payment, operator payable, cancellation, refund, platform fee, and accounting entry remain separately traceable.

Connected reservation operations

Manage inventory, availability, holds and bookings in Boni. Configure the property or route network, sales channels and integrations around your operation, with booking changes and exceptions visible to the responsible team.

Questions

Common questions

Is this one generic reservation screen for hotels and buses?

No. Hotels and bus operators use separate operating views because rooms, rates, trips, seats, stops, and fares have different workflows. They share a reliable booking and distribution foundation underneath.

Can inventory appear on Bino?

Yes, a controlled implementation can expose approved hotel or bus inventory through Bino booking journeys while keeping the operator's reservation record authoritative.

Does this replace every PMS or operator system immediately?

Boni can connect to your existing PMS or operator system. Choose the properties, routes and channels to manage in Boni, then synchronize availability and booking updates across the systems your team uses.

Is the product generally self-serve?

Boni Reservations is in production and available now. Onboarding, inventory setup, distribution scope, payment and settlement rules, and operator support are agreed with you before go-live.

See it working for your business

Bring your process, files and team. See the workflow configured around your business.

Discuss a reservations rollout