Most independent hotels in India run on a mix of OTA extranets, a shared notebook for walk-ins, and a WhatsApp thread where the owner confirms reservations manually. It works — until it doesn't.
The problem is not that hoteliers are disorganised. It is that the tools available were never built with them in mind. Enterprise property-management software is designed for 200-room branded chains with IT departments and long contracts. OTA extranets are designed to serve the OTA, not the operator. And the gap in the middle — a practical, affordable system for a 15-room guesthouse, a homestay cluster, or a family-run resort — has largely gone unfilled.
Boni Hotel OS is our attempt to fill that gap. It is honest about where it stands: this is a V0, an early product, not a decades-old enterprise PMS.
The Real Problem: OTA Dependence and No Direct Channel
If your property gets most of its bookings through one or two online travel agencies, you know the cost. OTA commissions in India typically run 15–25% per booking. On a room sold at Rs 2,500 a night, you might clear Rs 2,000 or less. Over a busy season, that adds up.
The commission is visible. The compounding effects are less so:
The OTA owns the guest relationship. You get a name and a check-in date. Building a return-guest programme, sending pre-arrival messages, or offering a loyalty discount needs data you do not have.
Rate management is manual and slow. Most independent properties update rates by logging into each OTA's extranet separately. When a long weekend or festival drives demand, rates should move across every channel at once — manual processes make that slow or inconsistent, creating pricing gaps OTAs penalise with lower ranking.
Inventory lives in multiple places. Every OTA holds its own copy of your availability. When a booking comes in on one channel, the others still show that room open until you close it manually — and that window is where double-bookings happen.
Direct bookings have nowhere to go. A guest who finds you on Google, a referral, or WhatsApp has no clean way to confirm and pay without going back to an OTA. Without your own booking engine, direct channels exist in name only. These problems feed each other.
What Boni Hotel OS Is
Boni Hotel OS is a property-management and reservations system for independent hotels, resorts, homestays, and small property groups. It is not a channel-manager add-on or a booking widget — it is meant to be the single place where your rooms, rates, availability, and bookings live, and from which every channel is served.
Both the operator panel and the guest-facing booking flow run in a browser. No separate desktop software, no manual installation.
How It Works — In Plain Language
The core idea: you define your property once, and that definition becomes the live source of truth for availability across every booking channel.
You set up your property — room types, capacity, check-in/out times, base nightly rates, policies — once, in a browser panel, not once per channel.
Availability is live. Each room type has a daily availability count. When a booking is confirmed — through Bino, an agent, or a direct inquiry you close manually — the count updates in one place, and every channel reads the same number. No reconciliation step.
Holds work before payment. When a guest is interested but not yet confirmed — a travel agent, a group inquiry, a wedding party — you place a time-limited hold on specific rooms. When it expires, the inventory releases back to available. Rooms do not stay blocked because someone forgot to follow up.
Rates update once. You set rate logic at the room-type level — base rate, weekend adjustments, seasonal rules, length-of-stay restrictions — and an update applies across connected channels. No logging into four extranets to make the same change four times.
Direct bookings are first-class. Guests book directly through Bino (Boni's consumer travel surface) or other connected channels; a direct booking lands in the same system as any other, with the same availability update, confirmation, and payment handling.
What You Can Do With It Today
Boni Hotel OS is early-stage. Live and operational in the current V0:
Property and room setup — define name, location, room types, counts, amenities, policies.
Rate and availability management — base nightly rates per room type; open/close specific dates; minimum-stay rules; seasonal pricing; updates reflect across connected channels.
Hold management with automatic expiry — time-limited holds for agent inquiries, group bookings, or pending payments, releasing automatically if not confirmed.
Booking management — track confirmed bookings across all sources in one view; state moves through hold, confirmation, check-in, check-out, cancellation or no-show.
Payment collection in the booking flow — handled as part of booking, not a separate manual step, so direct bookings actually collect payment cleanly.
Distribution to Bino and partner channels — your inventory connects to Bino's consumer travel surface and to the ONDC open commerce network, so guests discover your property beyond the major OTAs.
WhatsApp-first onboarding for homestays — a fast flow starting from a WhatsApp conversation (property details, photos, pricing, availability), aiming to get a property live with a bookable page in under five minutes, without forms, upfront document verification, or a sales call.
A direct booking page for guests — each property gets a shareable URL where guests see availability, pick dates, and complete a booking with payment. Share it on WhatsApp, link it from your own site, or distribute it anywhere.
Operator panel — rooms, rates, calendar, bookings, channels, check-in status, all from a browser. No app.
What Is Still Being Built
This is a V0 with real gaps. In active development:
- OTA channel-manager connections (Booking.com, MakeMyTrip, Agoda) are not yet live — the current distribution surface is Bino and the ONDC network; native OTA sync is on the roadmap.
- Automated host payouts via a split-settlement rail are in design.
- GST compliance tooling (platform-issued invoices for unregistered hosts, automated tax) is being built alongside the payments work.
- Full PMS workflows — digital housekeeping boards, night audit, folio management, staff tasks — are on the longer roadmap.
- Google Hotels and vacation-rental distribution are planned once the booking surface is fully live.
If you want a mature enterprise PMS with ten years of integrations, this is not it yet. If you are an independent operator managing availability on a spreadsheet, taking bookings by phone, and manually updating OTA extranets — the gap between where you are and where Boni Hotel OS is today is the relevant comparison.
Who It Is For
Independent hotels and resorts (roughly 10–100 rooms) heavily dependent on OTAs, with no working direct booking engine, managing rates manually or inconsistently.
Homestay owners — single properties or small clusters — currently taking bookings by WhatsApp or phone who want a simple, fast bookable direct page and additional distribution, without a long setup, a technical team, or upfront documents.
Small hotel groups with multiple properties on fragmented tools that want a single panel across properties.
Operators open to being early users — where feedback shapes what comes next and the current gaps do not block the minimum daily workflow.
This is not the right fit yet for large branded chains, heavily integrated operators running complex channel-manager setups, or properties that need the full depth of an established enterprise PMS today.
The Homestay Case in Particular
India has a large, genuinely underserved segment: independently owned homestays — family homes, heritage bungalows, plantation stays, hill-town rooms — that host guests but operate entirely outside formal property-management systems. They typically have no booking engine, no centralised availability, and no way to collect payment before check-in except a UPI transfer by phone. Guests find them through OTAs (heavy commission), word of mouth, or a Google search that leads nowhere actionable.
Boni Hotel OS's WhatsApp-first onboarding targets exactly this: share a few photos, confirm price and availability, and get a live booking page — aiming for under five minutes, with KYC and verification happening in the background after go-live, not blocking it.
Whether you are a single-room homestay in Coorg or a three-unit cluster in Himachal Pradesh, the intention is that you can have a working direct booking page by the end of the same WhatsApp conversation where you first heard about the product.
How to Get Started
There is no sales call required to start. For homestay owners, onboarding begins on WhatsApp. For hotels and larger properties, reach out to Boni through the website and the team will walk you through what is live today, what your setup would look like, and whether the current V0 fits.
Be clear-eyed: you are getting into a product early — some things are still being built, your feedback is taken seriously, and the commercial terms are designed to be accessible rather than enterprise-locked. If your current situation is spreadsheets, manual OTA updates, and no direct booking channel at all, this is worth exploring.
To connect with the team and see what Boni Hotel OS looks like for your property, visit Boni Hotel OS.
Top comments (0)