Resort management software
A resort is a large, multi-service operation: lodging, several dining outlets, spa, activities and a big team that has to move in sync. Lokibed concentrates everything into a single folio per guest: the restaurant and bar POS works on a table map with zones, and when you close the order you pick cash desk or folio — if it goes to the folio, the total is posted against that reservation's open account. One caveat for an operation this size: the POS does not deduct F&B stock; audited stock lives in the supplies module, with purchase orders and suppliers, but it isn't wired to the POS yet. Housekeeping and tasks are assigned and prioritized by urgency to hold the standard at scale.
Profitability is managed with live RevPAR, ADR, occupancy and ALOS, plus seven management reports — KPIs, production by channel, pickup, forecast, cash audit, fiscal and segment, two of them with CSV export — and deterministic dynamic pricing: explicit projected-occupancy and pickup rules, no AI, which you approve before they touch the BAR grid. There is no channel manager, so that price does not travel to the OTAs. For groups running several properties the system is multi-company and multi-hotel, with isolation guaranteed by Row Level Security in Postgres and proven by tests that try to cross tenants; a per-customer isolated database is roadmap. The AI assistants exist with a declared, small scope: four actions inside the PMS and only one of them writes.
What it solves for your operation
- Single folio per guest consolidating lodging, dining, spa and activities.
- Restaurant and bar POS with a table map by zone; the order closes against the folio or the cash desk.
- The POS does not deduct F&B stock: audited stock sits in supplies, with purchase orders and suppliers, unwired to the POS.
- Large-scale housekeeping and tasks, assigned and prioritized by urgency for the whole team.
- Revenue: live RevPAR, ADR, occupancy and ALOS, seven management reports (two with CSV export) and deterministic pricing with manual approval.
- Multi-company and multi-hotel with isolation by Row Level Security in Postgres, proven by tests that try to cross from one tenant to another. A per-customer silo is roadmap.
Frequently asked questions
- Does it consolidate restaurant, spa and activity charges into one account?
- Yes. Everything posts to a single folio per guest: closing a POS order against the folio posts the total to that reservation's open account, and services and activities post to the same folio, with no loose tickets or manual reconciliation. If the charge isn't from a staying guest, the order closes against the cash desk. What that circuit does not do is move stock: the POS doesn't deduct F&B supplies.
- Is it ready to run several properties of a chain?
- Yes, it's multi-company and multi-hotel from the back-office, with role-based users and permissions. On isolation it pays to be precise, because it's every chain's question: it isn't one database per customer, it's Row Level Security in Postgres — a guarantee at the engine level, not a filter each query has to remember — with automated tests that try to read another tenant's data and verify the database refuses. A per-customer silo is a roadmap decision, not code we have today. White-label with your own domain is already supported by tenant resolution, with the certificate issued by hand at setup. And the public API, to be exact, is read-only today and exposes one thing: reservations, with hashed API keys, scopes and OpenAPI.
- What revenue reports does it include for a large operation?
- Live RevPAR, ADR, occupancy and ALOS on your real reservations and stays, plus seven management reports: KPIs, production by channel, pickup, occupancy forecast, cash audit, fiscal and production by segment. Two export to CSV. On top of that runs dynamic pricing, and here precision matters: it does not use AI. These are explicit projected-occupancy and pickup rules proposing a factor over the BAR; each recommendation stays suggested and you approve it, and applying it writes the price into your BAR grid, which is what the direct engine and agency net rates read. It does not reach the OTAs, because we have no channel manager.
Want to see it with your real operation?
Book a demo and we'll walk you through the PMS with your use case. We quote based on your properties, rooms and modules.
Request a demo