Hotel management software
A hotel lives on a front desk that never stalls at peak and on inventory that never sells twice. Lokibed unifies the drag & drop tape chart — you drag the reservation and the move releases the old allotment and deducts the new one in the same transaction, or does neither —, check-in/out with a cash folio, and the night audit, which is idempotent and triggered by your team at close. Allotment control doesn't live on the screen: it's a database constraint that keeps inventory from going negative, plus a row lock on the per-night availability record.
On top of that sits direct sales: a white-label booking engine with zero commission on your own site, a guest portal with web check-in, a B2B portal for your agencies with net rates and an enforced credit limit, and our multi-hotel marketplace. Let's be exact about distribution, because that's where this industry exaggerates: we have no channel manager. The five OTAs are modelled and the credential is stored encrypted, but the client that talks to their API does not exist — today an OTA reservation enters by import with duplicate control, not by sync. The CRM turns inquiries into reservations with a public-link quoting tool, and revenue shows live ADR, RevPAR, occupancy and ALOS.
What it solves for your operation
- Drag & drop tape chart with check-in/out, cash folio and an idempotent night audit.
- Allotment control enforced in the database: non-negative inventory constraint + per-night row lock.
- White-label booking engine with zero commission and a guest portal with web check-in.
- Live revenue: ADR, RevPAR, occupancy and ALOS, with seven management reports (two with CSV export).
- Invoices with atomic fiscal numbering per point of sale, plus manual entry of the ones you issue elsewhere. No electronic invoicing: the CAE is simulated, there is no ARCA/AFIP connection.
- No channel manager: an OTA reservation enters by import with duplicate control, not by sync.
Frequently asked questions
- Does it work for an independent hotel and for multiple properties?
- Yes. It's multi-company and multi-hotel from day one: run one or many properties from a single back-office, with role-based users and permissions. Isolation between companies doesn't depend on every query remembering to filter: it's Row Level Security in Postgres — a guarantee at the engine level — with automated tests that try to cross from one tenant to another and verify the database refuses. A per-customer isolated database (a silo per hotel) is roadmap, not something we have today.
- How does it prevent overbooking?
- With a rule in the database, not on the screen: per-night, per-room-type inventory has a constraint that prevents it from going negative, and every booking locks that row before deducting it. Every channel we actually have — front desk, direct engine and agency portal — goes down the same path. Two honest caveats: we do not sync with OTAs, so a Booking reservation only affects your inventory once you import it; and control is by room type, not by physical room.
- Does it issue electronic invoices?
- No, not yet, and we'd rather say so before the proposal. The invoice comes out of a closed folio with atomic fiscal numbering per hotel, point of sale and type — sequential, idempotent, with folio charges posted and its PDF — but the CAE is simulated: there is no connection to ARCA/AFIP, and Paraguay, Peru and Uruguay are not implemented. What does solve the day-to-day is manual entry of the invoice you issue elsewhere, tied to the reservation, with its external number and the PDF attached, and it enters the period's fiscal report. If your hotel needs to issue fiscally from the PMS, we are not your system for that today.
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