The front desk, the restaurant, housekeeping, the banquet diary, central reservations and the sales desk are not six products here. They are six screens over one database — so the bill a guest runs up at dinner is on their folio before they reach reception, and the company that booked them is the same company the invoice is raised to.
Every picture on this page is the running product, not a mockup. Click any of them.
Each one is licensed on its own — a restaurant with no rooms buys the POS and never sees a booking chart; a resort with no outlet never sees a KOT. What none of them is, is a separate database.
The stay view, bookings and holds, check-in and check-out, the folio and the cashier, GST invoicing, and a night audit that closes the day in one press.
Outlets, tables, menus and KOTs. A bill settles at the counter or goes to the room — and when it goes to the room it is on the folio, not in a second system.
One desk that can see what every hotel in the group can sell — including the ones it cannot, and why. Full on the 14th? The sister property four kilometres away has four rooms at eight hundred less.
Every guest, company and travel agent the group already knows — nobody imports anything. With what they have actually spent beside the name, before the phone is picked up.
Room status the desk and the floor agree on, attendants, sections and the morning sheet — with out-of-order rooms taken out of what can be sold.
Halls that sell by the hour rather than the night, the function diary, and the event order the kitchen and the floor both work from.
Ingredients, recipes and stock behind the kitchen, with vendors, purchase orders and goods received.
Your own booking page, on your own domain, with no commission on it — and a payment link a guest can settle from before they arrive.
Rates and inventory out to the OTAs, bookings back in. The connection to AxisRooms is built and running against their sandbox; going live waits on their certification, not on us.
These are captured by a script that drives the demo hotel in a real browser and fails rather than guesses when a screen has moved — so a picture on this page cannot quietly drift away from the software it is selling.
Every integration between two systems is a place where a guest becomes two guests and a bill becomes two bills. The way to not have that problem is to not have two systems.
The guest ate at the hotel's restaurant. Nobody carried a chit to reception, nobody keyed it in twice, and nothing was reconciled at checkout — the bill is a line on the folio, taxed at its own slab, next to the room charge taxed at its.
Two systems with an integration between them can produce this too, on a good day. They cannot promise it on a bad one.
Somebody who stayed in Delhi in March and books Goa in October is the same person, on the same card, with one history. Not a match run overnight — the same row.
Dinner, the bar, the spa, the banquet hall and the room are postings on one folio. The desk does not reconcile anything at checkout; there is nothing to reconcile.
The reservations desk, the booking page and the front office all price a stay through the same engine. If one of them refuses a date, they all refuse it, for the same stated reason.
The corporate the sales desk is chasing in the CRM is the corporate the folio is billed to and the GST invoice is raised against. Opening one does not create a second.
Fifty named things a person can be permitted to do, bundled into roles. A receptionist cannot close the day or read the revenue journal because the database says so, not because a screen hides a button.
Separation is enforced by the database on every read and write, not by remembering to filter. With no account set it returns nothing — a bug fails closed.
The same system behind all of them. A restaurant manager should not have to walk past a booking chart to reach the till.
pms.theorionhotels.com
The hotel itself — the chart, the desk, the folio, the night audit.
POSpos.theorionhotels.com
The restaurant — tables, KOTs, bills, and the day end.
CRScrs.theorionhotels.com
Central reservations — group availability, the board, every booking.
CRMcrm.theorionhotels.com
Sales — guests, companies, agents, enquiries and follow-ups.
Whether a room can be sold, whether a bill can be closed, whether a guest may be written to — decided in one place, by the same code every screen calls. A second copy of a rule is a second answer waiting to disagree with the first.
"Minimum stay 3 nights." "Stop sell." "This company already has a CRM record with history against it." A refusal with no route forward is how work starts happening outside the system.
Voids, rate overrides, comps, write-offs and corrections all carry a name, a time and a reason from a list the hotel maintains. Not because auditors ask — because somebody will.
GST at the slab in force on the night, state codes checked against the GSTIN, the registration asked for after the guest has gone, and Form C for foreign nationals.
We will set up a property with your room types and your tariff, and you can take a booking, charge a dinner to it and close the day yourself.