Threshold

Everything the guest consumes, on one folio.

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.

  • Reservations
  • Guest folios
  • Housekeeping
  • Restaurant POS
  • Room service
  • Inventory

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

The restaurant till and the front desk are the same business, told otherwise.

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

What the team actually looks at.

The shape below is true to the real product. The numbers are not — these are illustrative values, never customer data.

03 / Capabilities

What it does, in detail.

9 capability areas, each built because the operation breaks without it.

01

Rooms and room types

Room inventory by type with live status and a status log that records every transition and who made it.

02

Reservations

Bookings spanning multiple rooms and dates, tied to a guest record that persists across stays.

03

Guest folios

An itemised account per stay that accumulates room charges, food and beverage, room service and extras as they happen.

04

Housekeeping

Tasks generated from room status and assigned to staff, closing the loop between a departed room and a sellable one.

05

Restaurant point of sale

Menu categories and items, tables, orders and order lines — posting either to a walk-in payment or straight onto a guest folio.

06

Room service

A separate ordering path with its own items, landing on the same folio as everything else.

07

Inventory

Stock items with recorded movements, so consumption in the kitchen and the minibar is visible before the shelf is empty.

08

Tax and payments

Configurable tax handling and payment capture against the folio, with the arithmetic done once in one place.

09

Staff profiles

Staff records and role separation across front desk, housekeeping and food and beverage.

04 / Surface area

21 modules, one system.

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.

  • Hotels
  • Room types
  • Rooms
  • Room status log
  • Guests
  • Reservations
  • Reservation rooms
  • Folios
  • Folio charges
  • Housekeeping tasks
  • Restaurants
  • Tables
  • Menu categories
  • Menu items
  • POS orders
  • Room service
  • Inventory items
  • Inventory movements
  • Taxes
  • Payments
  • Staff profiles

05 / Architecture

One guest account, many posting points.

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.

  1. L1 Front desk Reservations, check-in and check-out, folio review and settlement.
  2. L2 Outlets Restaurant POS and room service posting to folios or walk-in payment.
  3. L3 Housekeeping Task assignment driven by room status transitions.
  4. L4 Folio core Charges, taxes and payments assembled continuously per stay.
  5. L5 Inventory Items and movements consumed by the outlets.

06 / Integrations

Built to connect, not to be a silo.

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.

Payments

Card and mobile money settlement against the folio or an outlet order.

Printing

Kitchen tickets, outlet receipts and folio statements.

Messaging

Booking confirmations and pre-arrival messaging to guests.

Hospitality

Want Threshold for your operation?

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.