Front desk & hotel operations software
The front desk is the operational heart of the hotel, and Lokibed runs it from a single screen. You move reservations with drag & drop on the tape chart — and that move releases the old allotment and deducts the new one inside the same transaction, or does neither — you run check-in and check-out against an open cash folio, and you see every room's status live. Allotment control lives in the database: a constraint that keeps inventory from going negative, plus a row lock on the per-night availability record.
At the end of each day you run the night audit: it closes the hotel's business date, consolidates charges, reviews balances and leaves folios ready for the next day. It's idempotent, so closing the same date twice duplicates nothing and nobody has to remember whether it already ran. Let's be exact about one thing: your team triggers it from the close screen — there is no scheduled job running it on its own yet. The whole team works on the same data, with role-based permissions, and every movement is logged.
What's included
- Drag & drop tape chart: grab a reservation and reassign room or date instantly.
- Check-in and check-out with a cash folio tied to the booking lifecycle.
- Allotment control in the database: non-negative inventory constraint + per-night row lock.
- Idempotent night audit: you run it at close and repeating it duplicates no charges or balances.
- Live room status, coordinated with housekeeping and team tasks.
- Role-based users and permissions, with every movement audited.
Frequently asked questions
How does the system 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: a night with no rate or availability loaded isn't policed, and control is by room type, not by physical room.
Does the night audit run on its own?
No: your team triggers it at day-end, from the close screen. There is no scheduled job running it unprompted yet. What the system does solve is making it safe to repeat: it's idempotent, so closing the same business date twice duplicates no charges or balances. In one run it consolidates charges, reviews balances and leaves folios ready for the next day.
Can I control what each front desk user sees and does?
Yes. You define role-based users and permissions, so front desk staff access only what they need and every action is logged for audit.
Want to see it in your operation?
Book a demo and we'll show you this feature with your real use case.