The platform Live

When the system refuses

Every 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.

"Folio ASARCP-FA000080 has an outstanding balance of 142. Settle it, or bill it to a company or agent first." That is what the system says at the door, and there is a page in the manual with that sentence as its title.

The rule

Refuse only for money. An invoice that has been issued is not edited; a closed month is not posted into; a payment is not deleted; a charge the hotel cannot collect is not posted. Everything else — more people than the room takes, a smaller room, a price below the floor, a block on an occupied room — is a question: say what you see, ask once, write down who said yes.

The sentence

Written in the database, where the rule is enforced, so the same words reach the desk, the booking page and the channel manager. Never a code, never a stack trace, never "an error occurred".

The page

Every refusal has a topic in the manual: what it means, why the system says it, what to do. The public help's search reads the whole body, so pasting the sentence finds the page.

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. 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. Opening a hotelThe 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. 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.