Hotel software is selected at reception and paid for at the back office. The demonstration shows a calendar and a booking form. The problems appear later: a room sold twice because a channel update was delayed, a deposit that cannot be matched to a reservation, a folio split across two guests, or a night audit that takes three hours because the previous shift did not close the day.
This guide treats booking software as an operating system for a property, not as a website add-on. It is for the owner or general manager of an independent hotel, guesthouse or small group in Bangladesh that is outgrowing a paper register, a spreadsheet and the OTA extranets.
The operating loop to test
Map the guest journey before looking at features: enquiry, quotation, reservation, room and rate assignment, deposit, arrival, check-in, folio charges, departure, payment settlement, housekeeping turn, and the nightly close. Then map the inventory loop that runs beside it: room availability, rate plans, restrictions, channel updates and overbooking checks.
A system that handles the first loop but not the second creates double bookings. A system that handles the second but not the first creates disputes at checkout. The evaluation should follow both loops end to end with one real reservation.
Requirements that separate demos
- Room and rate inventory: room types, individual rooms, seasonal rates, occupancy pricing, minimum stay and closed-to-arrival rules.
- Channel synchronisation: documented connections to the OTAs you actually use, with a visible error queue when an update fails.
- Direct booking: availability, rate and confirmation that agree with the front desk, including deposits.
- Deposits and payments: partial prepayment, balance on arrival, refunds and a reference that can be reconciled to the provider statement.
- Folio and billing: split folios, extras, city ledger, company accounts and a clear audit trail for adjustments.
- Groups and blocks: room blocks, cutoff dates, rooming lists and group billing.
- Housekeeping: room status, cleaning assignments and a link between maintenance blocks and availability.
- Night audit: a close that reconciles cash, card and MFS takings, posts room charges and produces the day's reports.
- Multi-property: shared guest records with property-level rate and user control, if you operate more than one site.
- Resilience: a defined process for internet or power interruption, and a way to take bookings without losing the audit trail.
- Guest data: retention, access and consent for identity and contact information.
Five procurement routes
All-in-one property management system
One vendor covers reservations, front desk, billing, housekeeping and reporting, often with a channel manager attached. Integration is simpler and accountability is clearer, but you accept the vendor's model for rates, folios and groups. Best for a property that wants a single accountable vendor.
Channel manager plus a separate PMS
Specialist tools connected by an interface. Each may be stronger in its area, but the seam between them becomes your operational risk. Ask who supports the interface when a rate update fails at midnight.
OTA extranets only
The cheapest route and the weakest for direct operations. It can work for a very small guesthouse with few rooms and one channel, but it fragments availability and makes direct bookings harder to manage.
Custom build on an existing stack
A property with unusual inventory, long-stay pricing or a loyalty model may need software shaped around it. Custom build can fit, but only with a realistic maintenance budget and a plan for OTA connectivity, which is rarely a simple build.
Local ERP with a hotel module
Useful when the property already runs accounting or inventory on the same platform. Check whether the hotel module is actively maintained and whether front-desk staff can use it at pace during check-in.
Scoring hotel software vendors
Score one to five and require a demonstration for every high mark.
- Front-desk speed: can a new staff member check in a walk-in guest in a reasonable number of steps?
- Inventory accuracy: does availability update across channels, and how are failures surfaced?
- Money control: deposits, split payments, refunds and night audit reconcile without a spreadsheet.
- Reporting: occupancy, average rate, source mix, dues and cash position are available without custom exports.
- Integration: documented APIs, supported channel connections and a named escalation path.
- Support: hours that match your front desk, language coverage and a tested response process.
- Training: role-based training for reception, housekeeping and accounts, not one session for managers.
- Exit: guest history, folios and rate data can be exported in a usable format.
Pricing questions for hotels
Ask whether pricing is per room, per property, per module, per user or per transaction. A per-room model behaves differently in low season than a flat subscription. Clarify commission on direct bookings, payment processing fees, channel connection fees, onboarding, data migration, training, support and hardware. Ask what happens when a second property is added and whether the rate plan is renegotiated. Request a low-season and high-season model, because a hotel's cash flow is not flat.
A two-week parallel pilot
Run one rate plan and one channel through the new system while the current process continues. Create a direct booking, an OTA booking, a modification, a cancellation, a no-show, a deposit refund and a group block. Attempt an overbooking and confirm that the system blocks or warns correctly. Complete a night audit and compare the result with the existing close. The pilot is successful only when the front desk can complete these tasks without calling the vendor for each one.
Contract traps
- Rate parity or channel restrictions that limit direct selling.
- An API described as "available" without documentation, limits or support commitments.
- Guest data ownership left ambiguous, or export treated as a paid professional service.
- Support limited to office hours while the front desk operates overnight.
- Commission or transaction fees that change without a defined notice period.
- Implementation priced low while training and configuration are excluded.
Exit and data recovery
Before signing, ask for a sample export of reservations, guest profiles, folios and rate plans. Confirm the format, the time required and the cost. State who owns the data and what is deleted after termination. A property that cannot take its guest history to another system is not really choosing a vendor; it is accepting a permanent migration risk.
Where custom hotel software fits
We build booking and back-office workflows for hospitality operators under Custom Software & Integrations. Fees, implementation scope and support terms are explained on the pricing page. If channel and payment integrations are part of the decision, the API design checklist will help you ask better technical questions.
Sources
- PCI Security Standards Council, accessed 17 November 2026.
- NIST, Cybersecurity Framework 2.0, accessed 17 November 2026.
- DataGuidance, Bangladesh data protection overview, accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.