Native modules, not connected products.
Leonbee was built as one system. The PMS, the POS and the guest application share a database, a guest record and a ledger — so the work that usually goes into integrations does not exist here. What genuinely lives outside, we connect to properly.
What we connect to →Ten everyday jobs, and what they cost you.
These are not edge cases. They are the things a property does every day of the season.
| The job | Typical stack | Leonbee |
|---|---|---|
| A restaurant bill charged to a room | POS → PMS interface, per-outlet licence, nightly reconciliation | The same folio. Posted at the moment of the order. |
| Guest history across outlets | Separate databases, matched by name if at all | One guest record. Rooms, F&B, spa and tours on it. |
| A management report for the property | Exports from each system, assembled in a spreadsheet | One report. No export, no assembly. |
| A digital menu that matches the till | A menu tool synced from the POS, often behind | The digital menu is the POS menu. |
| A hotel guest booking a table | A restaurant booking tool with its own diary, phoned through to the outlet | Booked from the room. The table lands in the restaurant diary with the guest and the room on it. |
| A spa booking on the room bill | Spa software plus a PMS interface | A treatment is a resource in the same diary. |
| Tips split across a shift | A spreadsheet, or nothing | Clock-in data and house rules, calculated nightly. |
| A guest request that must not be lost | Shared mailbox, hope, a paper note | A task with a department, a room and a deadline. |
| A second restaurant opens | A second POS installation and a second contract | A setting. Same account, same report. |
| Feedback before it goes public | A review tool with its own guest list | Sent from the stay, scored, turned into a task. |
Native inside the property. Open at its edges.
Some things genuinely live elsewhere — the OTAs, the bank, the tax authority, your accountant. Those we integrate, and we maintain the connection.
Channel managers
We connect to the channel manager, which handles distribution to the OTAs. Availability, rates and restrictions go out through it; bookings come back mapped and priced.
Established channel-manager providersPayment terminals
Card present and card on file, pre-authorisation at check-in, refunds from the folio.
Major acquirers and terminal vendorsFiscalisation
Receipt and invoice reporting to the tax authority where the country requires it.
Country-specific, maintained by usAccounting systems
We do not keep your books. We deliver the figures your accounting system needs — journals, invoices, payments and taxes — in the format the established hospitality accounting packages read.
Standard exports and per-client mappingLive before the season, not during it.
Five steps, run by people who have opened properties before.
- 01
Property setup
Categories, rooms, floors, outlets, tables, users and roles, configured with you in one session.
- 02
Rates and menus
Seasons, rate plans, taxes and child rules; price lists and preparation groups for every outlet.
- 03
Data import
Existing reservations, guest profiles and price lists brought in and checked line by line.
- 04
Connections and hardware
Channel-manager mapping, terminals, printers, kitchen screens and tablets tested on site.
- 05
Training and first shift
Role-based training, then a live shift with us beside the desk and the pass.
- Your data comes with you — reservations, guests and price lists imported, not retyped
- Training per role — reception, service, kitchen, housekeeping, management
- One support line — for the whole property, in your language