How a booking engine works
- The guest picks dates and guests on the hotel website.
- The engine reads live availability and rates from the PMS.
- The guest chooses rooms, enters details and pays a deposit if required.
- The reservation is created in the PMS and a confirmation is sent.
Booking engine checklist
| Feature | Why it matters |
|---|---|
| Same inventory as the desk | No double bookings between direct and walk-in |
| Multi-room checkout | Families and small groups book in one go |
| Deposit options | Protect against no-shows without losing conversions |
| Hosted payments | Card data never touches the hotel's systems |
| Self-cancellation | Fewer emails; the room returns to sale faster |
| Prices shown including tax | No surprises at checkout |
Direct bookings vs OTA bookings
A direct booking avoids agency commission and gives the hotel the guest relationship. OTAs bring reach. Most properties use both, which is why the booking engine, the channel manager and the PMS must share one availability calendar.
How bedsKey's booking engine works
Bookings from your own booking page use the same path a clerk uses, so the database-enforced no-double-booking guarantee holds. Guests can book several rooms in one checkout. Web bookings stay tentative until confirmed and lapse automatically, returning the room to sale; guests confirm their email, and unopened bookings release sooner. Deposits can be nothing, the first night, a percentage or a fixed amount, paid on the gateway's own page and posted to the folio automatically, or a card hold can be taken only if the guest never arrives. Stripe, bKash, Nagad, SSLCommerz and bank gateways (Brac Bank, City Bank, DBBL) are integrated (bKash go-live depends on the hotel's own merchant account), every gateway starts in sandbox, and no card data is stored by bedsKey.