Rooms and room types
Room inventory by type with live status and a status log that records every transition and who made it.
Threshold
Threshold runs hotel operations as a single system: room types and live room status, reservations across multiple rooms, guest folios with itemised charges, housekeeping task flow, restaurant tables and point of sale, room service, inventory movement and tax handling — all posting to the same guest account.
Built, pre-launch Full property operation from reservation through folio settlement.
24entities
covering rooms, reservations, folios, POS and inventory
1folio
every charge on the property lands on one guest account
Liveroom status
with a status log behind every change
Multioutlet
restaurant, room service and front desk on one system
01 / The problem
A guest orders dinner, takes a drink at the bar, and has a late checkout. Three systems record three transactions, and at checkout someone reconciles them by hand while the guest waits with a taxi outside.
Meanwhile housekeeping works from a printed sheet, the front desk does not know which rooms are actually ready, and inventory only becomes visible when something runs out.
Threshold puts one folio under the guest and one status model under the room, so the bill is assembled continuously rather than at the counter.
02 / In operation
The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.
Illustrative interface with sample data — no guest information is shown.
03 / Capabilities
9 capability areas, each built because the operation breaks without it.
Room inventory by type with live status and a status log that records every transition and who made it.
Bookings spanning multiple rooms and dates, tied to a guest record that persists across stays.
An itemised account per stay that accumulates room charges, food and beverage, room service and extras as they happen.
Tasks generated from room status and assigned to staff, closing the loop between a departed room and a sellable one.
Menu categories and items, tables, orders and order lines — posting either to a walk-in payment or straight onto a guest folio.
A separate ordering path with its own items, landing on the same folio as everything else.
Stock items with recorded movements, so consumption in the kitchen and the minibar is visible before the shelf is empty.
Configurable tax handling and payment capture against the folio, with the arithmetic done once in one place.
Staff records and role separation across front desk, housekeeping and food and beverage.
04 / Surface area
Breadth is only an asset when the parts share a data model. Every module here reads and writes the same records — there is no export step between them.
05 / Architecture
A Laravel 11 application where the folio is the centre of gravity. Every outlet — front desk, restaurant, room service — is a posting point onto the same account, and room status is a modelled state machine rather than a flag somebody remembers to set.
06 / Integrations
Third parties are first-class parts of the architecture, isolated behind stable internal contracts so any one of them can be replaced without touching the core.
Card and mobile money settlement against the folio or an outlet order.
Kitchen tickets, outlet receipts and folio statements.
Booking confirmations and pre-arrival messaging to guests.
Hospitality
We can walk you through the live platform, talk about how it maps onto how you work today, and be honest about where it does not fit.