Hotel Booking and Operations Application

The problem

A small hotel or serviced-apartment operator running on Zoho hits the same wall every time: Zoho Books can invoice a guest, but it has no concept of a room-night. There is no availability calendar, no rate plan, no folio that accumulates charges across a stay, and no way to stop two bookings landing on the same room for the same night.

So the operation runs on a shared calendar or a wall chart for availability, a spreadsheet for rates, and Books only at the end — where a single invoice is typed up from whatever the front desk remembers. The predictable failures follow: a double-booking that costs a walk-in, a minibar charge that never reaches the bill, a corporate account whose negotiated rate was applied for one stay and forgotten on the next, and a month-end where occupancy and average rate have to be counted by hand because nothing in the system knows how many room-nights were sold.

The usual answer is a full property management system, which for a twenty-room property or a serviced-apartment block means a per-room monthly licence, a separate login, a separate support relationship, and an accounting integration you now have to maintain. For an operator already paying for Zoho, that is a second system to run the same business.

What ECOSIRE builds

This is a build-to-order application. Nothing is pre-built or instantly downloadable. After a scoping call and a fixed quote, we build the Creator application, Deluge logic and Zoho Books integration described below into your own Zoho account.

Room inventory and rate plans in Zoho Creator

The operational core is a Zoho Creator application. Forms cover Property, Room Type, Room, Rate Plan, Rate Calendar, Reservation, Stay, Folio, Folio Charge and Housekeeping Task.

Room Type carries occupancy limits, bed configuration and default inclusions. Room carries the physical unit, its floor and its current status. Rate Plan defines the commercial product — a walk-in rate, a corporate rate tied to a CRM Account, a long-stay rate for serviced apartments with weekly or monthly pricing, a non-refundable rate with its own cancellation rule. The Rate Calendar holds date-specific pricing so a season, a weekend or a local event can be priced without editing the plan itself.

Availability is computed, never typed. A Deluge function evaluates room-type inventory against confirmed stays for the requested date range, and the same function guards the Reservation form on submit, so a booking that would oversell a room type is rejected at the point of entry rather than discovered at check-in. Where you deliberately allow controlled overbooking, that tolerance is a configured number per room type rather than an accident.

Reservations, folios and the front desk

A Reservation moves through defined states — enquiry, tentative, confirmed, checked in, checked out, cancelled, no-show — with Deluge enforcing what each transition requires: a deposit before confirmation, an assigned room before check-in, a settled folio before check-out.

The Folio is the piece Books cannot model on its own. On check-in a folio opens against the stay, and a scheduled Deluge function posts the night's room charge and any recurring package items each night the guest is in house, so the bill is correct at any moment rather than assembled at departure. Additional charges — restaurant, laundry, minibar, late check-out, damages — are posted to the folio as they occur, from the front desk or from a Creator mobile form used by the department that raised them.

Split folios are supported where the commercial arrangement needs them: a company settling room and tax while the guest settles extras, or a group booking with a master account and individual incidentals. Deluge routes each charge to the correct folio according to the routing rules configured on the reservation.

Settlement into Zoho Books

At check-out, folio settlement calls the Zoho Books REST API to create the Invoice against the correct customer — the guest, the corporate account or the travel agent, depending on the billing instruction on the reservation — with line items carrying your service and revenue account mapping so room revenue, food and beverage, and other income land in the right accounts without a journal correction.

Tax is configured properly rather than approximated. Where your jurisdiction applies GST, VAT, a tourism levy or a municipality fee, we configure the tax rates and rules in your Books organization and apply them at the folio-charge level, because room revenue and food and beverage frequently attract different rates and a single invoice-level rate produces a wrong return. Payments taken at the desk — card, cash, transfer, wallet — are recorded against the invoice through the API, and deposits held before arrival are applied as advance payments so the guest's balance is right throughout.

For corporate and agency business we build the ledger side: a Zoho CRM Account holds the negotiated rate plan and credit terms, city-ledger stays post to that account rather than to the guest, and a periodic consolidated invoice with a stay-level statement goes out from Books. Agency commission is calculated in Deluge and posted as a Bill or a deduction according to your contract.

Housekeeping and operations

Housekeeping status is tracked per room — vacant clean, vacant dirty, occupied, out of order, out of service — and updated automatically by the check-in, check-out and stay-over events rather than by someone remembering. A Creator mobile form lets room attendants update status, log linen changes and raise maintenance issues with photos from the corridor.

Maintenance tickets route to the responsible team, and a room placed out of order is removed from availability automatically, which closes the gap where a room is sold while it is unusable. Arrival, departure and stay-over lists generate for each day, and a Sigma widget gives the duty manager one screen with occupancy, arrivals, departures, in-house count and rooms not yet ready.

Reporting

We build the reports an operator is actually judged on: occupancy percentage, average daily rate and revenue per available room by day, month and room type; source and channel mix; corporate and agency production; folio charge analysis by department; and a revenue summary that reconciles to Books rather than diverging from it. Zoho Flow handles the surrounding automation — booking confirmations and pre-arrival messages by email or WhatsApp, guest feedback requests after departure, and scheduled report distribution to ownership.

Who this is for

Independent hotels, guest houses, boutique properties, serviced-apartment operators and small resort groups already using Zoho Books, typically under a hundred rooms, where a per-room property management system licence is hard to justify and the accounting already lives in Zoho.

It is a poor fit if you need live two-way distribution to online travel agents with automatic rate and inventory push, or if you are running a large property with an existing channel manager and revenue management system — in that case a dedicated property management system is the right answer and we will tell you so on the call. We can import bookings from a channel source on a scheduled basis, but we do not build a channel manager.

How delivery works

1. Scoping call. We walk through your room types and inventory, rate structure and seasons, corporate and agency arrangements, folio and charge-routing rules, tax position, and your existing Books chart of accounts. We ask to see one real guest folio and one corporate statement — those two documents define the build more precisely than any specification. 2. Fixed quote. A written, itemised scope at a fixed price with a delivery window. Later additions are quoted separately rather than absorbed. 3. Build. Development happens in our own Creator environment and a test Books organization against sample data you supply. Your live property data is not touched. 4. Install in test. Deployed into your test environment with your real room inventory and rate plans. Your front-office manager runs a full arrival-to-departure cycle including a split folio and a corporate check-out; your accountant confirms the resulting invoice, tax and account mapping. Findings are fixed before production. 5. Production go-live. We load rooms, rate plans, corporate accounts and forward bookings, configure roles so a room attendant cannot see rates and a front-desk agent cannot edit the rate calendar, and run a parallel period alongside your current process — usually starting on a low-occupancy weekday. 6. Support window. A stated post-go-live support period covering defects, configuration adjustment and staff questions, with Deluge source, the Creator application definition and written documentation handed over.

Everything runs inside your own Zoho account on your own subscription. You own the code and the data, and you can take maintenance in-house or elsewhere at any point.