Check in a guest, post a charge, take a payment, print a GST invoice, fire a KOT, close the night — and prepare the GST return from the same rows. Built inside a working hotel group, on the floor, at the desk — not in a product meeting.
Each sees only the screens it needs and pays only for what it runs.
Rooms, F&B and the books on one record. 10 to 150 rooms.
The POS, priced as a restaurant, with no hotel attached.
Central reservations, a group CRM, one set of books per entity.
Halls by the hour, packages split correctly, F&B on the same folio.
Most hotels run a PMS, a separate POS, a spreadsheet for corporate rates and a WhatsApp group for housekeeping. Every join between them is a place figures stop agreeing. In Asar the restaurant bill, the room charge, the corporate invoice and the night audit are the same ledger.
Six departments, one set of numbers. Nothing is re-keyed anywhere.
Twenty modules in one product, and every picture is the running product, not a mockup. There is no per-module price list, and no module you discover is extra after signing.
Rooms down, nights across, three weeks at a time. Drag to move a guest, pull the edge to extend, right-click a room to book or block it. Quote and book are one call, so nothing can disagree.
Walk-in on one screen including the ID. Registration card from the booking. Check-out that ends in a GST invoice with a QR anyone can verify — and a small balance waived at the door as a recorded allowance.
Charges, payments, split tender, routing, refunds that name the payment they return, credit and debit notes, cashier shifts counted by denomination. A void is a new line; the original stays.
Group over branches, because the branch has the GSTIN. Credit pools with sub-limits, contracted rates that inherit, statements and ageing — and since September a real AR ledger with receipts, TDS withheld and reminders.
Tables, menu and the open order on one screen; KOTs per station; per-channel prices the restaurant keeps itself; each outlet closing its own day; the kitchen's stock valued at landed cost. Sells alone to a restaurant with no rooms.
Nine stages, all live: the attendant's phone with a PIN, rules that decide each room's clean, scored inspections, the store and minibar, faults with an SLA, people and shifts, a floor map, sixty-three daily KPIs and a manpower forecast.
Halls that sell by the hour and block the ballroom they are part of. The diary, the banquet event order, pax on guarantee or actual, deposits onto the same folio as the rooms, a P&L per event.
One transaction: post every room and its tax, price every no-show, roll the date, lock the day. Runs itself after 5 am in each hotel's own timezone; refuses rather than guesses; reversible; cannot post a night twice.
Rate plans and meal plans; derived rates as one number plus gaps; seasons materialised into the daily sheet; minimum and maximum stay, closed to arrival and departure, stop-sell; whole rupees by rule; the hotel sets its own price.
One desk that sees what every hotel in the group can sell, priced through the same quote the desk uses, and books into any of them. The group forward, hotel by hotel, day by day.
Everybody the group has ever taken a booking for, with what they have spent beside the name. Enquiries on a board, one timeline, segments and outreach with do-not-email absolute. No second copy of a person.
Rates, inventory and restrictions out to AxisRooms; bookings, modifications and cancellations back in and on the chart in the same request. Every call recorded whole. 371 OTA bookings delivered this way between 8 September and 1 October.
Your own booking page, on your own domain, on your own rates, no commission. Razorpay and PhonePe. A payment link a guest settles from before they arrive, receipted to the folio.
A double-entry ledger per legal entity, posted by the night audit and every document. Vendor bills with TDS, payment runs with two signatures, bank statements matched, gateway and OTA payouts reconciled, fixed assets under both books.
GSTR-1 and 3B prepared from the documents and frozen per period; GSTR-2B imported and matched; 26Q and 16A; e-invoice queue built and awaiting sandbox certification.
Tally, Zoho Books, QuickBooks, Xero and CSV as batches with a control total and a versioned account map. Signed webhooks out; keyed doors in; a documented API in the manual.
118 in the catalogue, every one computed from the same ledger the folio uses. By email on a schedule. The ones that cannot be produced from live data say so instead of returning an empty page.
267 topics written as the product was built and versioned with it. Press ? on any screen; paste the sentence it refused with and the search finds the page. Published to the web too.
Eight roles over seventy-seven capabilities, enforced on every route and in the database. One login, several hotels, different roles. Two-person rules where money moves. Support access granted by you, time-boxed, logged.
Templates in the hotel's voice; an outbox that records every message that should have gone. Confirmations, payment links and scheduled reports by email today from your own domain; WhatsApp click-to-chat now, the API sender when your Meta account exists.
The sync engine, the conflict rules and per-device invoice ranges are built and tested. The client that runs on the front desk machine is what remains.
Every picture is the product, taken this week by a script that drives a demo hotel with sixty nights of trading in a real browser — and fails rather than guesses when a screen has moved. Click any of them.
Every charge, every payment, every correction sits on one bill the cashier can read aloud to a guest. A ₹5,000 balance settled as ₹2,000 cash and ₹3,000 card is a single action — and if the card is refused, neither half survives to be unpicked later.
₹5,000 taken as Cash ₹2,000 + Card ₹3,000. ₹5,400 still outstanding.
One bill, two tenders, one transaction — and a voided line still visible.
We are building the third answer: the cloud product, with a local database on every device and a machine at the property that keeps the building talking to itself.
The building keeps running. The queue drains the moment the line comes back.
The hotel's own words, with this booking's dates, room and balance filled in.
Templates in your voice, not ours. An outbox that records every message that should have gone — what it said, who it was for, whether it went and who sent it. A guest saying "nobody told me" is answerable from a record.
Confirmations, payment links and scheduled reports go by email today from the hotel's own verified domain. The WhatsApp API sender reads the same outbox and needs your Meta business account — that one is yours to hold, not ours to assume.
The slab depends on the tariff you actually declared for that night — so a rate change mid-stay changes the tax for the nights after it and not the ones before. Asar computes it. Nobody at the desk has to know it.
Peak nights cross the boundary; the slab follows the tariff, night by night.
Derived from the declared tariff on the night being charged. No table for the receptionist to remember, and no wrong invoice to reissue.
Held on the company branch, because that is the entity registered — and the branch is what decides whose GSTIN prints.
Every closed folio, settled bill and note, one row per rate, classified and split. Frozen per period, JSON for the offline tool, filed with the ARN — and Form C from what was captured at check-in.
A queue by trigger for B2B invoices, the IRP payload, GSP credentials encrypted, IRN and QR on the invoice, cancel within 24 hours. Certified against a live sandbox it is not yet.
The restaurant, the bar, room service and the spa run on the same database as the rooms. That is why a bill posts to a room in one action and shows on the folio immediately — and why the day's food revenue is in the manager flash without an export.
One ticket, two stations, and a bill that lands on the right stay.
One hotel and forty hotels are the same product, at different depths.
Because the tenancy is built in at the bottom, a single hotel is not carrying a chain's complexity on screen, and a chain is not reconciling forty separate installations at month end.
The established Indian cloud products are mature and broad. Here is an honest read of the trade — including the rows where they still win today.
| What matters | Typical cloud PMS | Typical desktop PMS | Asar |
|---|---|---|---|
| POS in the same ledger | Usually a separate module or product | Separate | Same database, posts to the room in one action |
| The books | Export to Tally | Export to Tally | Ledger, payables, bank, GST filing and fixed assets inside — and a Tally export for the accountant who wants one |
| Corporate: group over branches | One flat company record | One flat company record | Group + branch, each with its own GSTIN and sub-limit; a real receivables ledger behind it |
| GST slab on declared tariff | Usually | Often manual | Computed per night; GSTR-1 and 3B prepared from the documents |
| Housekeeping | A status board | A status board | The attendant's phone, inspections, the store, rules, people, forecast |
| Central reservations & CRM | Separate products, separate guest records | Rare | One desk over every hotel; a CRM that holds no second copy of a person |
| OTA connectivity | Built in, many channels | Usually third-party | Through AxisRoomsLive — Booking.com, MakeMyTrip, Agoda, Expedia and more arriving |
| Booking engine on your own site | Included, mature | Add-on | Ours, on your domain, Razorpay and PhonePe, no commission |
| e-Invoice IRN | Usually | Often add-on | BuiltAwaiting sandbox |
| Works with the internet down | Screen stops | Yes, but not cloud | Cloud + local + LANIn build |
| Custom report builder | Fixed report menu | Fixed report menu | 118 reports todayBuilder on roadmap |
| Pricing model | Per module, per add-on | Licence + AMC | One price per room, per month |
| Your data leaves when you want | Export on request | It is your machine | Open documented API, webhooks, warehouse CSV, no lock-in |
Every screen is measured against these before it ships. A receptionist should be trainable in half a day.
New reservation, empty screen to confirmed — under 30 seconds.
Walk-in check-in including the ID — under 60 seconds.
Check-out with a GST invoice in the guest's hand.
Night audit — or set a time and it runs itself.
The deepest navigation anywhere in the product.
Search, filter, choose columns, export — always, no exceptions.
To train a receptionist, with error messages in plain language.
Wherever possible, instead of a frightening confirmation box.
We run twenty properties. We know what it is like when the booking screen takes nine clicks, when the rate calendar fights you at season change, and when a receptionist keeps a paper register because the software cannot be trusted at 3am.
So we built our own. Our properties are the first users of everything we ship — when it breaks, it breaks for us first, in front of our own guests. That turns out to be a very effective quality process.
“More Comfortable. More Classy.”
The promise our hotels make to guests — and the standard we hold the software to.

Published because you should be able to plan against it — and hold us to it.
Reservations, holds with a guest payment link, front desk, folio and cashiering with split tender, corporate city ledger, group bookings, upgrades, restaurant POS with per-outlet day-end, night audit, and the lists the hotel keeps itself.
Central reservations over every hotel, the guest and trade CRM, the AxisRooms channel manager with bookings applied in the same request, the hotel's own booking page with Razorpay and PhonePe, and the night audit running itself per hotel, per timezone.
The room's story, the rules, inspections, the store, maintenance and lost-and-found, people and shifts, guest requests, the dashboard and floor map, the forecast. All nine live on 15 September.
General ledger, receivables, payables and TDS, bank and reconciliation, GST filing and TDS returns, connectors to Tally, Zoho and QuickBooks, cost of sales, fixed assets, period close and approvals, budgets and USALI reporting, group consolidation.
Eleven hotels moved from eZee in one evening on 26 September, with their rooms, a price for every date a year ahead and 318 future bookings. Per-night prices, day-use rooms, the Today screen, the phone layout on every screen, and logins built as jobs with hotel and cluster administrators.
The remaining Orion hotels and their history from eZee's reports; channel links for the hotels that moved; e-invoice against a live GSP sandbox; reading a photographed bill into the day book; HR records under payroll.
Connect the API sender to the outbox that already exists. Then the edge application that makes the offline engine visible to a receptionist, and LAN mode.
Real modules, deliberately deferred. Each waits on a counterparty's account or on a customer who needs it, and none is needed to run rooms, F&B and the books.
Every number below was taken from the live system or a drill somebody ran, and each says when.
Their rooms with their real numbers, a price for every date to September 2027, and 318 future bookings, each carrying its eZee reference so nothing is loaded twice.
Booking.com, MakeMyTrip, Goibibo, Agoda, Expedia and Cleartrip, each on the chart in the same request that delivered it.
At the hour each hotel chose, in its own timezone, with nobody watching, refusing rather than guessing where a person should decide.
From their spreadsheet, in an afternoon, on 13 September — each a group over branches with its own GSTIN.
Decrypt, restore into a scratch database, compare eight tables and the function count against live. Drilled, not assumed.
Run against a restored copy of production before anything reaches it. On the first honest evening they stopped four defects at the door.
Per-device number blocks are what make an offline-issued invoice number safe by construction.
Whether a room can be sold or a bill closed is decided once, by code every screen calls — not in a browser that can be argued with.
Captured by a script that fails rather than guesses when a screen has moved, so a picture cannot quietly drift from the software it sells.
Every topic is a migration, reviewed like everything else, and published to the web from the same rows the product reads.
Written against a 970-line requirement list in one day, each stage trialled on a restored copy before it went on.
Yes. Reservations, the front desk, folio and GST invoicing, corporate receivables, housekeeping, the restaurant, banquets, the night audit, central reservations, the CRM, the booking page with Razorpay and PhonePe, and the books through to a prepared GSTR-1 are live and running in thirteen of our own hotels. What you would not get today is the offline client, e-invoice IRNs signed by a certified GSP, or a WhatsApp API sender. If any of those is the reason you are switching, we will say so at the demo rather than after.
Through AxisRooms. We built a two-way integration with them rather than a channel manager of our own — they already maintain those connections, and a dozen fragile OTA integrations is not where a hotel gets value from us. Rates, inventory and restrictions go out; bookings, modifications and cancellations come in and land on the chart in the same request.
Where it stands: live. Bookings from Booking.com, MakeMyTrip, Goibibo, Agoda, Expedia and Cleartrip have arrived through it since 8 September — 371 of them by 1 October, each on the chart in the same request. Hotels we moved from eZee are linked one at a time, after go-live. If you already run AxisRooms, that stays exactly as it is and we plug into it.
Both answers are available. The books are inside the PMS — a double-entry ledger per legal entity, posted by the night audit and by every document; vendor bills with TDS; bank statements matched; GSTR-1 and 3B prepared from the documents themselves; fixed assets under both the Companies Act and Income-tax books. If your accountant lives in Tally, Zoho Books or QuickBooks, the same journals export there as batches with a control total. Period close with approvals, budgets and group consolidation are live too.
Not yet, and we mark it that way everywhere. The engine underneath — sync, conflict rules, per-device invoice number ranges — is built and tested. The client that runs on the front desk machine is what remains, and it is the largest single piece of work in the project.
As a restaurant. A standalone outlet with no hotel attached runs on the same system, and you are not sold a hotel PMS you will never open.
You take it. Full export of guests and transactions in an open format, plus a documented REST API you can pull from at any time. We would rather earn the renewal than hold the data hostage — and we say so in writing.
The Orion Group of Hotels — a mid-segment group operating 20 properties and 509 rooms across Delhi, Mumbai, Goa, Varanasi and Lucknow under the ASAR brand. The product was built for our own operations first, thirteen of our hotels run on it today, and they are still the first to get every release.
We have done it eleven times in one evening. Your rooms come across with their real numbers, every rate plan with a price for every date a year ahead, and your future bookings with their eZee reference on each. What eZee's interface does not give is past history; that comes from its report exports. You keep running eZee until the day you switch, and channel links move one hotel at a time after go-live.
A day with us: room types, counts, tariff, tax group and the first business date, with your room list and corporate accounts read from Excel — one loaded 6,930 corporate accounts in an afternoon — or read straight from eZee. There is no self-serve signup yet, and we would rather be measured against that day than describe it, so ask at the demo how the last one actually went.
Screen shared, a live property, and a straight answer about anything that is not built yet. No sales team — you will speak to someone who works on it.
Book a demo