The hotel, in one piece.
Oristelo runs the front desk, rates, OTA channels, the restaurant, housekeeping, banquets and the books on one record — so dinner is on the folio before the guest reaches reception, and the night audit closes straight into the ledger.
Illustration
CONNECTS WITH THE CHANNELS, PAYMENTS AND BOOKS A HOTEL ALREADY USES
- Booking.com
- Agoda
- Expedia
- Go-MMT
- Cleartrip
- Razorpay
- PhonePe
- Tally
- Zoho Books
- QuickBooks
- E-invoicing (IRP)
Most hotels run five systems and five versions of the guest.
Every connection between two systems is a place where a guest becomes two guests and a bill becomes two bills. Oristelo doesn’t connect systems — it doesn’t have more than one.
The usual stack
A PMS, a POS, a channel manager, a CRM and spreadsheets — kept roughly in step by exports, imports and somebody’s Monday.
Oristelo
Every module reads and writes one record. Nothing is synced, because nothing is copied.
Built for the desk, the floor and the back office.
A look at six of the twelve modules. Each tile is an illustration of the real screen’s job.
Dinner is on the room bill in the same transaction
Not an export, not a midnight sync. The POS and the folio are the same row.
Every plan priced on one form
Set one rate; derived plans follow. Restrictions by night, carried to every channel.
The floor is a map
Rooms change colour as attendants tap through the clean.
The day closes itself
At the hour you choose, and never before the day has ended.
- Business date checked
- Room charges posted
- No-shows marked
- Closing into the ledger
- Reports to the inbox
The owner’s morning sheet
Every hotel a row, before breakfast.
Every call to every OTA, kept
What was sent and what came back — so a dispute with a channel is settled by reading, not remembering.
Every change says who made it
Who, when and from which machine — on one page for every module.
One stay, start to finish — six modules, one record.
None of these steps sends anything to the next. They are all looking at the same guest.
A booking arrives
From an OTA, the hotel’s own page or the central desk — it is on the chart in the same request, and the room count goes back out to every channel.
- No nightly sync, no double-sell window
- Prepaid OTA stays show the OTA as the payer
Channel log
The guest checks in
The registration card, the room and the folio are one record — and the guest is the same guest the CRM knows, at every hotel in the group.
- ID captured once, masked where it should be
- The company that booked is the company invoiced
Arrivals today
Dinner goes to the room
The restaurant closes the table to the room, and the bill is on the folio in the same transaction — before the guest is back at reception.
- KOTs per kitchen station
- Food at its own GST rate
Folio · Room 103
The room is turned
The attendant works one tap per step on a phone; the supervisor passes the room; the floor map changes colour as it happens.
- Works without a signal
- Every room keeps its own story
Floor 1
The day closes itself
At the hour the hotel chose, the audit posts each night’s charge, marks the no-shows, refuses a day that has not ended — and closes into the books.
- Double-entry ledger per legal entity
- Tally, Zoho or QuickBooks get the day once
Night audit · 02:00
The owner reads one sheet
Every hotel a row, in the inbox before breakfast. Occupancy, rate, revenue, what is owed — read from the live record, not a spreadsheet someone built.
- The flash, the heatmap, the day book
- View-only for everyone who can sign in
Morning sheet
Twelve modules. Switch on what you run.
Each module is switched on for your property on its own. What none of them is, is a separate database.
From one restaurant to a group of hotels.
Your data is yours, and so is the say.
Sign-in is hotel ID, email and password. The database itself — not just the screen — decides what each login may see.
Front office, revenue, accounts, a cluster, a group: each role reaches exactly as far as it should, and no further.
Every change says who made it, when, and from where. Corrections by an administrator are allowed — and recorded.
The people who run the platform see nothing until your hotel grants access, for a limited time, and the visit is logged.
An action taken today can be undone today, as one step, while the day is still open.
A browser for the desk and the counter; a phone for housekeeping that keeps working without a signal.
Before you switch.
Do we need to install anything?
No. Every desk opens Oristelo in a browser and signs in with the hotel ID, an email and a password. Housekeeping runs on a phone.
Can we take only some modules?
Yes. Each module is switched on for your hotel on its own — a restaurant with no rooms runs only the POS. None of them is a separate database.
Does it work with our OTAs?
Booking.com, Agoda, Expedia, Go-MMT, Cleartrip and others connect through one two-way channel connection. Bookings land on the chart in the same request.
Will our accountant have to change software?
No. The day is sent to Tally, Zoho Books or QuickBooks once — or the accountant can keep the books in Oristelo, with GST returns and e-invoicing.
How do we move from our current PMS?
During setup, your room types, rates and companies are brought across from the system you use today. Ask on the demo how the move would be planned for your property.
How is it priced?
One price per room, per month, with every module in it. A group is invoiced once; a restaurant without rooms pays per outlet. See Pricing.
See your own hotel in one piece.
Thirty minutes, on a working hotel, with your room types and your rates. Bring the person who closes your books — they usually have the best questions.