141 pages, one for each thing the cloud does.

For a hotelThe front desk, the rates, the channels, the booking page, housekeeping and the night audit — one record from the booking to the books, for a hotel of any size. For a restaurantThe POS on its own — tables, KOTs, bills, the store and the day end — for a restaurant, bar or café with no hotel behind it, and no booking chart anywhere in sight. For a group of hotelsOne guest list, one central desk, one heatmap, one set of books per legal entity — and every hotel keeping its own day. Built inside a group of twenty properties. For banquets and eventsHalls that sell by the hour, the diary, the event order the kitchen works from, charges on the same folio as the rooms — and an event that keeps its own books. For the ownerOne sheet before breakfast, every hotel a row, the books that close themselves, and a log under everything — for the person who is not at the desk and needs to know anyway.

The booking chartRooms down the side, nights across the top, every stay drawn as a bar — the one screen a front desk lives on, with the price and the rules on it. Taking a bookingA room, a rate and a guest in under thirty seconds — quoted first, so the price the desk says is the price the system takes. Check-inThe guest, their ID and the room in one screen; the bill that is already open is the bill; and a room is free the moment the last guest has left. The registration cardThe GRC the guest signs, on the hotel's own paper, drawn from the booking and reprintable. The folioOne stay, one bill — or several windows on it when the company pays the room and the guest pays their own dinner. The GST invoiceA tax invoice with the right slab, the CGST/SGST split, the buyer's GSTIN when there is one, and a QR code anyone downstream can verify. Check-outSettle, or bill to a company, or — for a small balance — waive it at the door with a reason and a name. The bill is still there after the guest has gone. Credit and debit notesAn issued invoice is never edited. A wrong value goes down by a credit note and up by a debit note — separate, numbered, pointing at the original. Room move and upgradeMove a stay to another room, or up a category, from the chart, with the reason and the person written on the move. No-shows and cancellationsA policy on every booking, a retention charge the audit applies, and a charge the hotel cannot collect is not posted as if it could. Group bookingsOne booking, many rooms, a rooming list, and each room checked in and billed on its own or on the master. The guest recordOne guest is one row across every hotel. A shared email is not a person, and the guest who is already booked is not booked again. Corrections by the administratorThe administrator can correct any booking — audited, in house, departed, billed — and the log is the price. Room blocks and closed datesRight-click a room to block it, with a reason, a range and a name; close a date for the whole hotel; and the channels are told in the same minute. Arrivals and departuresWho is expected, who has not arrived, who has not left — with the rate and how they pay, because the desk asked for those two columns. Money owedEvery balance somebody has to chase, in one panel — and a payment link that is chased until somebody knows what happened to it. Every change says who made itThe booking's own timeline: taken, changed, moved, checked in, billed — each with a person, a time and a machine. A full room is a question, not a wallThe owner's standing rule — refuse only for money; otherwise say what you see, ask once, and write down who said yes. A discount on the bill is a decision with a name on itThe folio's fourth tab: a percentage or an amount off the whole bill, the room, the food or one line, the GST reduced with it, a reason from the hotel's list and a name on every line — a manager above the hotel's limit. And a small leftover forgiven at the door, under a ceiling, recorded. The clock on the door has a priceEarly check-in and late check-out as the hotel's own policy — as many bands per side as it wants, in hours from the door time, each a percentage of the night or a flat amount. The desk posts; a manager waives with a reason; the list of who was charged or waived is a report. A mistake made today is undone todayUndo on the card walks back what the desk did — a check-in, a payment, a charge, a cancellation — as a stack, until the night audit closes the day. A cancelled booking is put back from Find. A bill closed at zero is reopened by an administrator to void, refund and close again. Every one recorded.

Rate plans and seasonsA hotel keeps its own plans — room-only, breakfast, half board, full board — each saying what it includes, priced by season, and read by every screen that quotes. Every plan is priced on one formRoom-only, breakfast, half board and full board for every room type across a date range — set in one press, not twelve. Derived ratesThe tariff is one number and the gaps: type the display rate, the room gap and the meal gap, and every plan on every type is derived — with the OTA promotion on top. A room is priced by who sleeps in itSingle, double, triple, the extra bed, the child under six and the child under twelve — the quote reads the occupancy, and the channel receives the same table. RestrictionsMinimum stay, closed to arrival, stop sell, a closed date — written once, shown above the chart, and pushed to every channel. The GST slabThe slab follows the tariff by law. The system reads the rate on the night and applies the slab in force — and a channel price that says tax zero is a price with the tax inside it. The rate agreed is the rate carriedThe price on the booking is the price the night is posted at. The desk may name it until the guest leaves; after that a change is a note, not an edit. Rooms and room typesA hotel keeps its own inventory — types, real room numbers, floors, how each is made up — and changes it after go-live without raising a ticket. How many rooms are left each nightThirty nights down the page with the sold, the blocked and the free — for the person deciding whether to open the rate. The rate is recommended with its reasons, and a person says yesEvery night of every room type scored every hour against what is on the books — occupancy against the hotel's own booking curve, pickup, last rooms, need dates, events — and a price proposed with the reasons in words. Approve writes it and the channel is told the same minute. Off by default; no autopilot.

The channel managerPart of the product, not a second subscription: rates, inventory and restrictions out; bookings, modifications and cancellations in; every call kept. A booking arrives, and is on the chart in the same requestThe channel's booking is applied inline — guest, room, price, tax and payer — and the acknowledgement says whether it landed, and if not, why. What is pushed, and whenRates, rooms and restrictions go the moment they change. The channel is told more than we have on purpose, and told less when the house keeps rooms back. A queue that is not moving says soEvery push has a status, an attempt count and the error; a queue that has stalled is a sentence on the screen, not a silence. The sync logEvery call both ways, hotel by hotel, with the request body and the response body — a dispute with a channel is settled by reading. The OTA is who we collect from, not who the invoice is forAn OTA that collected from the guest is the payer; the guest is still the person on the invoice; the commission is what the channel said, never a silent zero. An oversell is not a failureAn overbooking allowance per type, and a booking that lands into a full type goes on the chart waiting for a room — visible, draggable, decided by the desk. The channel's credentials live in the productThe connection's keys are in an encrypted vault the application role cannot read, with a trail that survives a key change. AxisRoomsThe connector the two Asar hotels trade through today — sixteen of nineteen endpoints built, real bookings from six OTAs since 10 September 2026, every push acknowledged.

The hotel's own booking pageA guest searches, sees the hotel's own rates for their party and dates, and reserves — with no commission on the price and nothing typed twice. Payment links and gatewaysA hotel takes money its own way — Razorpay or PhonePe on its own account — with a link the guest can settle from before they arrive, receipted straight to the folio. The confirmation, and the reply that reaches a personA reservation tells the guest, on the hotel's letterhead, from an address whose replies reach the desk — and every email the hotel sends is on the log. Central reservationsOne desk over every hotel in the group: every booking on one screen, and a booking taken into a hotel nobody is standing in — with that hotel's own business date respected. Group availability, priced, in one searchFull on the 14th? The sister property four kilometres away has four rooms at eight hundred less — and the refusal for the full hotel is in the booking engine's own words. A refused booking can come backA push refused at the door — a key that did not match, a hotel not yet mapped — is kept whole and applied from the log once the cause is fixed. Where the business came fromWalk-in, phone, the hotel's page, a company, an agent, an OTA — on every booking, coloured on the chart, cut by every report, and deciding who is billed.

The CRMA PMS records what happened; a CRM records what somebody is trying to make happen, and to whom. This one reads the record the desk already writes — nobody imports anything. People, companies and agentsA company has branches, each with its own GSTIN and its own answer to "when do you pay"; an agent has a commission; a person has a history across every hotel. Enquiries on a boardBusiness that has not happened yet, on a board by stage, weighted by what it is worth, and closed only by somebody saying what became of it. One timelineStays, bills, complaints, calls, messages, meetings — everything that happened between the hotel and a person, in order, on one page. The card says what they are actually worthEleven stays, thirty-one room nights, ₹4,86,000, ADR ₹15,677, nothing owed — without anybody typing anything. Segments and outreachTwo hundred and forty people who stayed twice and have not been back since June — and what happens when somebody presses send, with do-not-email absolute.

The restaurant POSTables across the top, the menu below, the open order down the right. Punch, fire the KOT, settle at the counter or send it to the room. KOTs and the kitchenA ticket per station, a modification the kitchen sees as a reprint, and a KOT the kitchen can hold — with the store drawn down on every fire. Tables, stewards and the floorThe table belongs to somebody. Steward-wise sales are answerable because the captain on the table is a fact, not the login on the till. Charge to the roomThe bill goes to the guest's folio in the same second, as a restaurant charge with its own tax — after the guest's name and room are matched. The bill and its GSTA numbered GST bill per outlet with HSN codes per line, the slab per dish, and service charge that is taxable because the law says so. Tenders and reversalsA tender is controlled — cash, card, UPI, on account, to the room, complimentary — and a bill that was wrong is reversed, not deleted. Cashier shifts and the outlet day endA shift opens with a float and closes with a count; the day end closes every open table, reads the tenders, and refuses to close a day still in the future. An order arrives from somewhere elseZomato, Swiggy, the outlet's own online menu — an order posted as JSON lands as a ticket, once, with unmapped items refused by name. The menu, and a price that knows what time it isCategories, dishes, variants, a price per channel, and a schedule — happy hour is a window on the menu, not a second menu. A restaurant without a hotelThe POS sells on its own — an outlet that is a customer in its own right, with no booking chart, no room, and every till, bill and day end working. The kitchen storeUnits, locations, ingredients, recipes with yield loss, an append-only stock ledger, and consumption on every KOT — so the food that was used is a cost the day carries.

Housekeeping, in nine stagesFrom a room that keeps its own story to a system that predicts how long each clean will take — all nine stages shipped, on one database with the front desk. The room keeps its own storyOpen any room and read, in order, everything that happened to it — who was sent, what they found, when they paused, who passed it, what broke, what the guest asked for. Which clean a room is owedA checkout clean, a stay-over, a turndown and a deep clean are different work; the rules decide every morning which one each room gets, and say why. The phone on the floorOne tap per step, the room read live, and a phone that works without a signal and speaks the floor's languages. Who assigns, and who passes a roomCleaning your own room and calling it inspected is not an inspection. A supervisor passes a room on a sheet with a score, a pass mark and critical lines. The day is opened, planned, handed over and reportedThe night audit opens housekeeping's day with the cleans, the preventive work and the public-area rounds; the supervisor plans it from the bookings and hands it over in writing. The rooms are shared out fairlyA room is worth credits, some come first, and the hotel can share out the day itself — a suite to somebody trained for a suite, a VIP never to a trainee. The guest asks for something, and the world is toldA request is a ticket with a clock; the guest is remembered; every open thing is swept for its deadline; and a webhook tells anything outside that wants to know. The floor is a map, and the day is one screenRooms placed on a grid per floor, coloured by their live state; one dashboard for the day; the numbers kept; and the group compared against its standard. The minibar, linen, and what a clean costsWhat the room was given, what the guest drank, linen out to the laundry and back, and the cost of one clean added up from what went in. Faults, preventive work, and the lobby cleaned on the hourThe attendant raises the AC ticket from the room in one tap; engineering fixes it and housekeeping rechecks; the schedule generates the deep cleans and the servicing; public areas are swept by scanning a code on the wall. The day is predicted, and a move is recommendedHow long this attendant takes on this clean in this room, from the last ninety days of the story; what the week will need from the store; and a recommendation every hour. Who cleans well, and what keeps failingInspection scores by attendant and by area, over time — so training is aimed at the line that fails, not at the floor in general.

The night auditOne press, or none: the day closes itself at the hour the hotel sets, posts every night, marks the no-shows, tells the channel, and says what it did. A day is closed only after it has endedThe business date is the trap every hotel system falls into; this one refuses to close a day before the hotel's midnight, and can undo the last close. The closed day can be read backThe night audit statement — the one document a manager reads every morning, an owner is sent, and an auditor asks for by the month. The owner's morning sheetOne sheet for the whole estate, in the owner's inbox after every night audit — today beside month-to-date, the rooms in green, the ratios in gold, the money in blue, and tomorrow's status under it. Every log is read on one pageBookings, rooms, mail, the channel manager, housekeeping, the books — every log the system keeps, on one screen, filtered by hotel, kind, person and day. Invoices for the dayEvery bill for the business date with its CGST/SGST split, what is paid and what is owed — and the GSTIN that can be added after the guest has gone. Form C and the foreign guestA foreign guest's arrival is reported to the FRRO in its own format, raised from the registration already taken, and kept as a register the hotel can read back. The desk stops until the day is closedWhen yesterday has not been audited, today's check-ins wait — because a room charged on the wrong date is a wrong invoice, and a wrong invoice is a credit note.

Every rupee has two sidesThe night audit closes into a double-entry general ledger — per legal entity, with a chart seeded for a hotel, control accounts that must agree with the sub-ledgers, and no journal that does not balance. ReceivablesA bill to a company is an invoice that is owed; a receipt is allocated to named invoices and the shortfall has a name; the debtor is reminded, and a debt is forgiven only with a signature. Payables and vendorsA vendor belongs to the books and says who it is — PAN, GST registration, MSME, TDS section — and a vendor's bill is matched against what arrived and what was agreed before it is owed. TDSThe deduction is a dated rule and the threshold is per year — two per cent of the contractor, ten of the professional, ten of the rent — held back, deposited by the seventh, returned each quarter. The payment runWhat is due is paid — MSME first, by law — with a bank file, an advice to the vendor, retention held, an advance adjusted, and one journal per run. Bank and cashThe hotel has bank accounts and the till has a float; the statement is read into the books and matched line by line; the cash position is one screen. Gateway and OTA settlementsThe gateway pays out net and the difference is the fee; the channel remits what it collected and takes its cut — both matched booking by booking against the statement. GST filingA registration is per state and every rule has a date; GSTR-1 and GSTR-3B are prepared from the books in the portal's shape; the purchase credit is only what the supplier declared. E-invoicingAbove the threshold a B2B invoice is registered with the portal — IRN, acknowledgement and signed QR on the printed bill — with cancellation inside twenty-four hours and a credit note after. Tally, Zoho and QuickBooksThe day leaves the books once and says where it went: Tally vouchers with the party and the GST fields, Zoho journals and invoices by API, a CSV QuickBooks reads — and a webhook for anything else. Cost of sales and the food costThe food that was used is a cost the day carries — consumption from the store, not purchases from the vendor — and stock on the shelf is an asset. The banquet ledger, packages, and a night not yet sleptAn event is a ledger of its own — deposits held, costs tagged, margin read; a package is split for the management accounts without touching the bill; and a night not yet slept is not yet earned. Fixed assetsA thing the hotel owns is numbered and wears out — the register, two books, depreciation, disposals, physical counts and capital work in progress. The owner reads the statement the industry readsThe uniform system's operating statement — departmental profit, undistributed expenses, GOP, GOPPAR — read from the same ledger as the hotel's P&L; with the cash-flow statement, changes in equity, the KPI sheet, and every hotel side by side. The year is planned by account, and the month is measured against itA budget per account per month: the rooms lines derived from occupancy and rate, the outlet from covers and check, the rest typed; approved by a second person; then every month the ledger is measured against it and a rolling forecast says where the year is heading. The wages are a journal the books receiveThere is no HR module. The payroll engine's result — by department: gross, PF, ESI, PT, TDS, advances, net — is imported once a month, posted as one journal, and paid: the staff, then each authority with a challan. The group adds up across its hotelsOne statement for a hotel, for a legal entity's hotels, or for the whole account — profit and loss, balance sheet, consolidated trial balance — and the owner's page: equity, the result, distributions, the FF&E reserve. A rupee is not the only moneyAn overseas agent invoiced in dollars, an OTA remitting in dollars: the invoice keeps its rupee value, carries a foreign face at the rate it was quoted, and at month end the open balance is revalued with the gain or loss named in the books. The books notice what is unusualRules, not models, read the live books every day and raise an alert with its evidence — a near-duplicate bill, an odd manual journal, a cashier's voids, a vendor's price drift, a bad GSTIN, an uncharged room, an unmatched bank line. Nothing posts by itself. The month is closed by a list, and reopened by a signatureA month locks only when its checklist is done — every day audited, the sub-ledgers agreeing, the bank reconciled — and at the lock the trial balance is snapshotted and hashed. What one person must not do alone gets a second signature. Finance audits each day before it is believed. NextWhat is next in the booksThe two things the accounting programme deliberately left for a customer to ask for — intercompany posting between two legal entities, and the model-based assistance — and the remaining "approved by" boxes moving onto the approval machine.

The report catalogueA hundred and eighteen reports, each reading the live record, each saying when it cannot be produced — and readable by anyone who can log in, because they are view-only. The manager flashOccupancy, ADR, RevPAR and revenue, today beside month-to-date and the same day last year — the numbers a general manager reads before the first coffee. The occupancy heatmapOne row per hotel, one column per day of the month, each cell rooms / occupancy / ARR coloured by occupancy — the days passed from what was invoiced, the days ahead from what is on the books. The revenue report, bill by billA date range and a payment-mode filter, six tiles, and one row per invoice — filtered every way the owner asked. The channel reportOTA production and commission, and the channel's traffic both ways — what was pushed, what came back, hotel by hotel. Reports in the inboxAny report on a schedule, in the hotel's name, to the people who read it — and an alert when a number crosses a line. Compliance reportsThe GST sales register, the tax summary by slab, the Form C register, the police arrival and departure lists, the TDS ledger — the reports a hotel is asked for by somebody with a badge.

The hall sells by the hourA venue with a diary, sold by the slot rather than the night, billed on the same folio as the rooms — because for a city hotel the wedding is often the larger revenue line. The banquet event orderThe one document the kitchen, the floor and the client all work from — the menu, the timings, the setup, the equipment, the numbers — printed from the booking. An event in the booksDeposits held as client money, every cost tagged to the event, and a margin read when the last bill is in.

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

The companyAsar Cloud is built by The Orion Group of Hotels, inside its own hotels, for its own desks first — and sold to hotels that want the same. SupportWhat support looks like here: a manual on every screen, refusals written for the person at the desk, a log that answers "what happened", and a person at the other end of the mail. How it comparesAgainst an enterprise hospitality ERP — ten modules that talk to each other, a menu per vertical, a price per module — what is the same, what is different, and what you give up. The numbers, and where each comes fromEvery figure on this site, with its source — a query on the live database, a count in the repository, or a date. Nothing here is a claim. PrivacyThis website sets no cookies, runs no analytics and has no forms. What the product itself holds about a hotel's guests belongs to the hotel, in India, under the hotel's own control. IntegrationsLive: AxisRooms for the OTAs, Tally and CSV for the accountant, signed webhooks and mail. Built and switched on with the first hotel that holds the account: Razorpay and PhonePe, Zoho Books and QuickBooks, and IRP e-invoicing. Aggregators can already post orders in. PricingOne price per room, per month, and everything on this site is in it — the POS, the booking page, housekeeping, the CRM, the books. A restaurant with no rooms pays per outlet. NextWhat is nextEverything else on this site is running on a working hotel today. These are written, tested by their suites and staged, and each waits on a deliberate apply — or, in three cases, on a customer who needs it.