The platform Live

Opening a hotel

The wizard takes the code, the GSTIN, the room types with real room numbers and a rate each; readiness says what is still missing; the board tracks it to open — and the hotel opens itself.

A hotel is opened in an afternoon. The wizard creates it in one call — the code, the name, the address, the GSTIN, the time zone, the check-in and check-out times, the room types with their real room numbers, a rate on each — and from that moment the chart draws.

Readiness

The readiness check says what the hotel is still missing before it can sell: a cancellation policy, a tax setting, a payment method, a rate for next month, a login for the desk. Each line is a link to the screen that fixes it.

The board

The onboarding board tracks every hotel being opened — what is done, who is doing it, what is waiting on the hotel — for the group opening twenty.

Opening is the hotel's own move

A hotel opens itself when it is ready; nobody at the platform flips a switch. A hotel that has not opened is on the menu, marked, so its details can be filled before the day it trades.

In bulk

A spreadsheet of hotels, or of six thousand corporate accounts, is loaded in one run by a script that reports what it created, what it skipped and why.

More on The platform

One database, not five that talk to each otherEvery integration between two systems is a place where a guest becomes two guests and a bill becomes two bills. The way not to have that problem is not to have two systems. The hotel ID, and who may see whatSign-in is a hotel ID, an email and a password; row-level security in the database decides what that login may see; a platform user sees nothing until a hotel has let them in. Roles and capabilitiesFront desk, housekeeping, back office, manager, administrator — and under each role a catalogue of capabilities that reach down to the button, gated by the module the account has bought. A group of hotelsOne hotel or twenty, on one account: each with its own business date, rates and rooms; the group with one guest list, one central desk, one heatmap and one set of consolidated numbers. Support access is granted, time-boxed and loggedOur own people cannot open a customer's hotel. The account lets them in for a window, the session is logged, and the account can see afterwards who was inside and when. The manual ships with every screenA hundred and twenty-four pages, written for the person at the desk, filtered by module and role, opened with one key on any screen — and published free at pms.theorionhotels.com/help. When the system refusesEvery refusal is a sentence written for the person at the desk, in the manual, findable by pasting it in — and the rule for what gets refused is one line. The log is the priceEvery change to every record carries who, when, from which login, which address and which machine — and the log is read on one page, by support and by the hotel. Modules and the subscriptionEach module is licensed on its own, switched per account by the platform, and the switch has teeth — a suspended account cannot sign in. EmailConfirmations, invoices, payment links, the morning sheet, scheduled reports — sent in the hotel's name, replies routed to a person, every send on the log. SecurityRow-level security in the database, credentials in an encrypted vault, host-only sessions per door, SSH guarded by fail2ban, backups before every migration, and a test suite that signs in as the application role.