Boni Hotel OS
Controlled pilotBoni Hotel OS connects property setup, room inventory, rates, availability, reservations, PMS workflows, guest operations, distribution, and AI-assisted exception work in one controlled hotel operating system.
For: Independent hotels, resorts, homestays, serviced apartments, management companies, small chains, travel platforms, and hospitality operators.
What the product connects
One operating record across the workflow
One room truth
Keep room types, dated availability, holds, bookings, blocks, restrictions, rates, and source references attached to the same inventory record.
One guest operation
Connect reservations to arrivals, departures, stay notes, payment state, messages, exceptions, and accountable staff work.
One distribution view
See how direct, Bino, partner, agent, and approved external channels relate to sellable inventory and booking state.
How it works
The product begins with correct room and booking state, then connects the operational work that normally gets fragmented across a PMS, channel tools, spreadsheets, inboxes, and staff memory.
Define properties, room types, occupancy, amenities, policies, taxes, check-in rules, content, and operator roles.
Maintain dated capacity, safety buffers, stop-sell state, stay restrictions, rate plans, and the channels allowed to sell.
Use time-bounded, idempotent holds and revalidate availability before a payment or approved confirmation becomes a booking.
Track arrival, departure, room assignment, guest details, stay notes, service work, no-show, changes, and cancellation state.
Bring booking questions, payment reminders, policies, changes, escalations, and post-stay follow-up into Bow Chat with reservation context.
Separate booking, payment, refund, operator payable, channel settlement, invoice, and reconciliation evidence so each can be reviewed correctly.
Product scope
Property and room-type records with operator, location, capacity, pricing, policy, and channel context.
Date-level availability with available, held, booked, safety-buffer, and available-to-sell state.
Minimum and maximum stay rules, closed-to-arrival, closed-to-departure, blocks, and stop-sell controls.
Time-bounded holds and idempotent confirmation into a canonical reservation record.
Hotel-specific views for rates, PMS work, channels, bookings, guest communication, reviews, revenue, and reports.
AI operations signals for scarce inventory, stale sync, broken channels, risk reasons, and next actions.
Organisation and workspace context so property work can remain scoped to the responsible business.
API routes for approved hotel inventory, availability, rate, hold, booking, channel, and AI-operations workflows.
Connections to Bino demand, Bow Chat guest operations, and broader Boni work, communication, payment, and reporting modules.
Operating areas
Create the operating definition of the property instead of scattering it across booking sites and spreadsheets.
Control what can be sold on each date and under which commercial conditions.
Keep the pre-stay, in-stay, and post-stay lifecycle attached to the confirmed booking.
Map inventory to the channels that can sell it and make sync failures visible as operator work.
Connect messages and calls to the reservation instead of asking staff to reconstruct context during every interaction.
Give operators a clearer view of operational truth and commercial truth without collapsing them into one status.
AI inside the operation
Extract draft rooms, rates, policies, restrictions, and channel mappings from approved spreadsheets, PDFs, messages, screenshots, or exports, with the source evidence attached.
Staff review the draft before it becomes sellable inventory.
Flag scarce dates, inconsistent capacity, stale channel state, dead holds, or overbooking risk and explain the evidence behind the warning.
AI does not confirm inventory or stop a channel without policy and audit.
Prepare pricing suggestions from occupancy, pickup, pace, restrictions, events, and operating constraints rather than applying unexplained rate changes.
Price changes require an approved policy or human confirmation.
Draft replies using the actual booking, payment, policy, and stay context, then route unusual cases to the responsible team.
The assistant must not invent availability, refund, or booking facts.
Match reservation, payment, refund, channel settlement, invoice, and exception evidence and surface mismatches for review.
Money-moving actions remain explicitly approved and traceable.
Summarize weak dates, stale channels, unresolved guest issues, payment exceptions, and the few actions that deserve management attention.
Every conclusion should resolve back to structured operating evidence.
Implementation paths
Begin with guest communication, channel exceptions, Bino distribution, owner reporting, or another bounded workflow while the incumbent PMS remains authoritative.
Use Boni Hotel OS as the source of truth for an agreed property, room pool, direct channel, partner allocation, or controlled pilot workflow.
Use the Hotel Inventory API for approved availability, holds, bookings, and event-driven integrations without giving every partner access to the operator workspace.
Each rollout names the workflow, participants, source records, owner, success measures, and the parts that remain in existing systems.
The working V0 foundation covers core hotel inventory, availability, holds, bookings, PMS views, channel state, and AI signals. Advanced production depth is agreed against the actual property workflow.
Every implementation states whether Boni owns, mirrors, or receives each inventory and booking record and how conflicts, retries, and stale data are handled.
AI can prepare and recommend. Price, booking, cancellation, refund, settlement, and customer-impacting actions follow explicit policies and audit.
Bino and partner distribution can add useful routes to market, but a channel connection is not a promise of bookings, acceptance, or revenue.
Connected products
Give approved products and partners bounded access to room availability, holds, bookings, and lifecycle events.
Explore the Hotel APIConnect guest questions, booking changes, payment reminders, calls, escalations, and service work to the reservation context.
Explore guest operationsAdd a customer-facing discovery and booking journey where approved inventory and support responsibilities are ready.
See the booking journeyQuestions
It covers PMS-style operating work such as property and room setup, arrivals and departures, reservation state, guest context, rates, availability, channels, and reporting. A pilot can own a bounded workflow or operate alongside an existing PMS; it should not be presented as universal feature parity with every mature PMS.
A controlled implementation can use an approved API, webhook, structured import, or reviewed email workflow where the existing system supports it. The source of truth, mapping rules, sync direction, failure handling, and operator review must be agreed before launch.
AI is attached to operational evidence. It can draft property setup from room sheets and policy documents, flag stale availability, explain channel failures, prepare guest replies, recommend rate changes, and summarize owner actions. Booking, price, payment, refund, and cancellation changes remain policy-controlled and auditable.
Yes, where the inventory, commercial terms, support process, and booking path are ready. Bino can become an additional discovery and booking surface while Boni Hotel OS keeps the approved availability and reservation record authoritative.
No. It is offered as a controlled pilot. The first scope defines the property, rooms, rates, channels, existing systems, guest workflows, payment boundaries, operator owners, and success measures before wider rollout.
Start with one bounded workflow
