Everything below is a module in Orian HMS, not a concept. Shipped means it is running in production today. In progress and planned are the honest gaps, the things we already know the platform is missing.
The whole property on one timeline. Drag a booking to move it, drag an edge to extend the stay, every move checked against double-booking and blocked rooms.
Arrivals sorted by ETA, guarantee and balance flagged before the guest reaches the desk, identity captured once and reused on the statutory register.
The day sheet built from the booking picture, turnovers flagged urgent, work balanced by minutes rather than task count, and re-spread when somebody clocks out.
A direct booking engine priced from live inventory, with member rates, promo codes, occupancy pricing and real room content. No per-booking fee, ever.
Availability, rates and restrictions pushed per room type per night; OTA bookings, changes and cancellations pulled back in. A sale on one channel closes the room on every other.
Named sellable rates derived off the base rate, with cancellation and deposit terms snapshotted onto the booking so a later policy edit can never rewrite history.
Demand scored per stay date and room type from pace, pickup, day of week, events and scarcity, then a rate proposed with the reasoning written out. A price set by hand always wins.
Track your comp set day by day, see your rank and your parity against the market average, and feed that gap straight into the pricing engine.
Most revenue systems maximise revenue. Ours knows what a half-board guest costs to feed, so it will not sell a room for less than serving it costs.
Digital check-in, one-tap requests that raise real tasks for real staff, room service, a live bill, pay-balance and express checkout.
Aria answers the phone around the clock in natural conversation, checks live availability and books. WhatsApp threads carry reservation and folio context, and staff can take over mid-conversation.
Every guest request carries two clocks, one for being answered and one for being done, with an escalation ladder that resolves to whoever is actually on shift.
Kitchen display, table plan, cashier sessions with Z-reports, split bills to the cent, priced modifiers, set menus, scheduled price windows and charge-to-room.
Cost a dish from its ingredients, then decompose the gap between what the recipes say you should have used and what actually left the store.
A booking book paced against the kitchen rather than the seat count, which knows a half-board guest has already paid for dinner.
A real book of record with period locking, reversals instead of edits, departmental reporting and a profit and loss that ends at GOP. Not a report that recomputes itself.
Duplicate-invoice guard, allocated supplier payments, bank statement reconciliation, fixed assets and depreciation, with an authorisation ladder over all of it.
Rosters that refuse to schedule somebody on approved leave, attendance derived from real clock-ins, leave counted in working days, and payroll that posts itself into the ledger.
Every competitor shows what the hotel sold. Because we own the recipes, the stock ledger and payroll too, we show what it kept, today, with every cost labelled actual, accrued or estimated.
Plan in occupancy and rate rather than a lump revenue figure, then see a shortfall split into how much came from fewer room-nights and how much from rate.
Idempotent automations sweeping the property every few minutes, and an operations assistant on every screen that answers from live data and can take action.
The channel driver is complete and proven end to end against a full protocol mock. What remains is commercial: a production account with the distribution provider.
Cards are tokenised and pre-authorised today, with no card number ever reaching our servers. Real capture through a gateway goes behind that same interface.
Staged payment schedules and escalating reminders both exist and are triggered by a person on purpose. Letting them run unattended is opt-in, and is being built that way.
Pricing by length of stay is live on direct channels. Pushing that ladder out to the OTAs, which today carry only a minimum-stay restriction, is next.
The website and booking engine already translate themselves and cache the result. The guest portal, the lobby kiosk and automated messages follow.
Single sign-on runs on OpenID Connect today, which covers Entra, Okta and Google Workspace. SAML and automatic deprovisioning are for the estates that mandate them.
Banquet contribution is costed to the plate today. The roster already knows who worked the wedding, so attributing their hours turns food cost into full direct cost.
The front desk keeps working from a redacted local copy when the line drops. Housekeeping and the till each need their own answer to what changed while they were away.
Erasure, export and consent are all implemented and run by staff. Letting a guest raise and track their own request is the remaining half.
We build from what properties actually ask for. Tell us what your hotel is missing and it might end up on this list.
Send a Request