Property management system · India

The whole hotel, on one record. From the front desk to the books.

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.

Book a 30-minute demo See every module Built and run inside The Orion Group of Hotels · 13 hotels and 313 rooms live on it
GST invoice 27ACP0142₹8,399 · CGST + SGST split
KOT #412 → Room 202Posted to the folio
Room 301 · InspectedHousekeeping, from the phone
Night audit closed02:00 · day rolled, reports mailed
13Hotels running on it today
313Rooms on it, from Delhi to Goa
2,411Rules in the database, not the browser
1Price. Every module included
Tenancy enforced at the row GST-native: slab, GSTR-1, 3B, 2B One database, no integrations between modules Restore drilled: 4 seconds Open API, webhooks, full export One price per room, no add-ons
What is live, said plainly. The front desk, folio and GST invoicing, corporate receivables, housekeeping in nine stages, restaurant POS, banquets, the night audit, central reservations, the CRM, the AxisRooms channel manager, the booking page with Razorpay and PhonePe, and the books through to a prepared GSTR-1 run today in thirteen of our own hotels. The offline client, the WhatsApp API sender and e-invoice certification are still being built. Every claim on this site carries a Live, In build or Roadmap label, so you can plan against it.
Who it is for

Four shapes of business. One system.

Each sees only the screens it needs and pays only for what it runs.

The shape of it

One system, not seven that email each other.

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.

One ledger append-only Front desk check-in · folio · invoice Restaurant POS KOT · bill · post to room Housekeeping status · minibar Corporate city ledger · GSTIN Night audit rolls the day, locks it Reports same figures, always

Six departments, one set of numbers. Nothing is re-keyed anywhere.

  • A restaurant bill posts to the room in one action — with the guest name checked against the room, so it cannot land on the wrong stay.
  • Nothing is edited in place. A void is a new entry reversing the old one, and the original stays on the bill. That is what makes an audit possible.
  • Every record carries who, when and from which device — and whether that device was online or offline at the time.
  • A report and an invoice cannot disagree, because the report is computed from the same ledger the invoice was printed from.

Every module, explained

The toolkit

What a hotel actually touches — from the front desk to the books.

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.

Live

The chart & reservations

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.

Live

Front desk

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.

Live

Folio & cashiering

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.

Live

Corporate & receivables

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.

Live

Restaurant & bar POS

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.

Live

Housekeeping

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.

Live

Banquets & events

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.

Live

Night audit

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.

Live

Rates, seasons & restrictions

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.

Live

Central reservations

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.

Live

Guest & trade CRM

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.

Live

Channel manager

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.

Live

Direct booking & payments

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.

Live

The books

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.

Live

GST filing & TDS returns

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.

Live

Connectors & API

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.

Live

Reports

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.

Live

The manual, inside

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.

Live

Users, roles & permissions

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.

Live

Guest messaging

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.

In build

Offline & LAN mode

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 module, in detail →

The screens themselves

Nothing here is a mockup.

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.

Folio & cashiering · live

The money, in one place, and never quietly rewritten.

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.

  • Split the bill by charge type, by percentage or by nights; route the room to the company and the extras to the guest.
  • Discounts enforced against the role's ceiling, not the operator's judgement — over the limit asks for a manager on the same screen.
  • Cashier shift opened and closed with a denomination count, so the variance is stated rather than absorbed.
Folio ASRGOA-FA000112 · Room 301 · Kapoor
Room charge — Suite08 Aug · BAR CP · GST 18%₹8,260
Spice Route — dinnerKOT 4412 · posted from POS₹2,140
Laundryvoided — wrong room · Ravi₹480
Payment — Cashdrawer · split 1 of 2− ₹2,000
Payment — CardHDFC 4411 · split 2 of 2− ₹3,000
Balance₹5,400

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

The hard problem

A cloud PMS dies with the line. A desktop PMS is not really cloud.

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.

Asar cloud line down · 24 queued Property server LAN mode · everything still works Front desk check-in · folio · invoice Restaurant KOT · bill · settle Housekeeping status · minibar

The building keeps running. The queue drains the moment the line comes back.

  • Invoice numbers pre-allocated per device, so two desks billing during an outage cannot produce the same GST invoice number. Proven at 4,000 references across two devices, zero collisions.
  • Conflict rules per entity — room status is last-writer-wins, folio postings merge and never overwrite. Anything genuinely ambiguous is raised for a person instead of guessed.
  • Queued and fired on reconnect — OTA updates, online payments, WhatsApp and e-invoice IRN generation.

Where this actually stands

Sync engine, conflict model, device stateBuilt & tested
Per-device number rangesBuilt & tested
Front desk client, LAN serverIn build
Namaste Shabnam, Your booking at ASAR Goa is confirmed. Booking: ASRGOA-000020 Stay: 14 Aug to 17 Aug (3 nights) Room: Deluxe Total: ₹10,800 Check-in from 2:00 pm, check-out by 11:00 am.10:42 ✓✓
Thank you! Can we get an early check-in?10:44
We are holding a Deluxe for you until 6:00 pm today. Secure it here: pms.theorionhotels.com/pay10:45 ✓✓

The hotel's own words, with this booking's dates, room and balance filled in.

Guest messaging · email live, WhatsApp API in build

The guest journey lives where the guest already is.

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.

  • Indian mobiles arrive as 98765 43210, +91-9876543210 and 09876543210. They are normalised to the one shape WhatsApp accepts.
  • A message with something missing — no number, or a payment link that does not exist yet — is held back and reported, not sent half-written.
  • Until your WhatsApp Business account is approved, the desk sends from the phone on the counter and the send is still recorded.

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.

India, properly

GST on a hotel room is not a percentage. It is a rule.

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.

₹7,500 declared tariff 12% 12% 18% 18% 12% 14 Aug 15 Aug 16 Aug 17 Aug 18 Aug One stay · one invoice · the tax right on every line

Peak nights cross the boundary; the slab follows the tariff, night by night.

Live

The slab switches itself

Derived from the declared tariff on the night being charged. No table for the receptionist to remember, and no wrong invoice to reissue.

Live

B2B invoices carry the right GSTIN

Held on the company branch, because that is the entity registered — and the branch is what decides whose GSTIN prints.

GSTR-1 and 3B, prepared from the documents

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.

Built · awaiting sandbox

e-Invoice IRN & QR

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.

Restaurant & bar · live

Built in, not bolted on.

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.

  • KOT routed to kitchen, bar or bakery; modify and cancel with a reason and a reprint, because the kitchen has already started.
  • Per-channel pricing and day-part scheduling — a dish costs one thing at the table and another on room service.
  • Recipe-based stock deduction, low-stock alerts, purchase orders and vendor payables.
  • Each outlet closes its own business date — a rooftop bar shutting at 3am and a café shutting at 4pm cannot share one day.
KOT 4412 · Spice Route · Table 7
KITCHEN
09 Aug 2026 · 20:41 · Steward: Ravi
Goan fish curryless spicy2
Prawn balchão1
Neer dosahalf plate3
Kingfisher — to BARrouted to the bar station2
Settlement: post to Room 301 — verified against Kapoor, in house.

One ticket, two stations, and a bill that lands on the right stay.

Organization The Orion Group of Hotels ASAR mid-segment Second brand same product Goa Delhi Mumbai Varanasi Lucknow … Every master and every transaction carries all three identifiers — enforced in the database, not by remembering a filter

One hotel and forty hotels are the same product, at different depths.

One hotel, or forty

Multi-property is native, not an upgrade tier.

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.

  • One login, different roles at different properties. Central guest profile and blacklist across the group.
  • A corporate contract is scoped to the properties it covers — a chain deal and a single-hotel deal are the same object.
  • One hotel's data is unreachable from another's session — enforced below the application, so a bug in a screen cannot leak it.
Choosing between them

Where we are different, and where we are behind.

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 mattersTypical cloud PMSTypical desktop PMSAsar
POS in the same ledger Usually a separate module or productSeparate Same database, posts to the room in one action
The books Export to TallyExport 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 recordOne flat company record Group + branch, each with its own GSTIN and sub-limit; a real receivables ledger behind it
GST slab on declared tariff UsuallyOften manual Computed per night; GSTR-1 and 3B prepared from the documents
Housekeeping A status boardA status board The attendant's phone, inspections, the store, rules, people, forecast
Central reservations & CRM Separate products, separate guest recordsRare One desk over every hotel; a CRM that holds no second copy of a person
OTA connectivity Built in, many channelsUsually third-party Through AxisRoomsLive — Booking.com, MakeMyTrip, Agoda, Expedia and more arriving
Booking engine on your own site Included, matureAdd-on Ours, on your domain, Razorpay and PhonePe, no commission
e-Invoice IRN UsuallyOften add-on BuiltAwaiting sandbox
Works with the internet down Screen stopsYes, but not cloud Cloud + local + LANIn build
Custom report builder Fixed report menuFixed report menu 118 reports todayBuilder on roadmap
Pricing model Per module, per add-onLicence + AMC One price per room, per month
Your data leaves when you want Export on requestIt is your machine Open documented API, webhooks, warehouse CSV, no lock-in
The contract

"Easy to use" is not something you can hold us to. These are.

Every screen is measured against these before it ships. A receptionist should be trainable in half a day.

3 clicks

New reservation, empty screen to confirmed — under 30 seconds.

1 screen

Walk-in check-in including the ID — under 60 seconds.

2 clicks

Check-out with a GST invoice in the guest's hand.

1 click

Night audit — or set a time and it runs itself.

2 levels

The deepest navigation anywhere in the product.

Every list

Search, filter, choose columns, export — always, no exceptions.

Half a day

To train a receptionist, with error messages in plain language.

Undo

Wherever possible, instead of a frightening confirmation box.

Why we built it

Most hotel software is written by people who have never worked a night shift.

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.

An ASAR guest room
Where it goes next

The order we built in, and what is left.

Published because you should be able to plan against it — and hold us to it.

  1. Operational core — done, August

    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.

  2. The group — done, September

    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.

  3. Housekeeping in nine stages — done, September

    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.

  4. The books — done, 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.

  5. The group moves in — done, late September

    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.

  6. Now — the rest of the group, and the certifications

    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.

  7. Next — WhatsApp sending, and the offline client

    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.

  8. Later — guest portal, door locks, aggregators

    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.

Proof, not testimonials

We have one customer, and it is us — thirteen hotels of it. So here are measurements instead of quotes.

Every number below was taken from the live system or a drill somebody ran, and each says when.

11 in one eveningHotels moved from eZee, 26 September

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.

371OTA bookings through AxisRooms, 8 Sep – 1 Oct

Booking.com, MakeMyTrip, Goibibo, Agoda, Expedia and Cleartrip, each on the chart in the same request that delivered it.

Every day since 2 SepThe night audit has rolled the live hotels' days by itself

At the hour each hotel chose, in its own timezone, with nobody watching, refusing rather than guessing where a person should decide.

6,930Corporate accounts loaded for one customer

From their spreadsheet, in an afternoon, on 13 September — each a group over branches with its own GSTIN.

4 sEncrypted backup restored and verified

Decrypt, restore into a scratch database, compare eight tables and the function count against live. Drilled, not assumed.

270Test suites that roll back

Run against a restored copy of production before anything reaches it. On the first honest evening they stopped four defects at the door.

4,000 / 0References issued across two devices, collisions

Per-device number blocks are what make an offline-issued invoice number safe by construction.

2,411Database functions carrying the rules

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.

24Screenshots on this site that are the product

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.

267Help topics, versioned with the code

Every topic is a migration, reviewed like everything else, and published to the web from the same rows the product reads.

9 of 9Housekeeping stages live, 15 September

Written against a 970-line requirement list in one day, each stage trialled on a restored copy before it went on.

Before you ask

Straight answers.

Can I run my hotel on this today?

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.

Does it connect to MakeMyTrip, Booking.com and Agoda?

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.

Does it do my accounts, or do I still need Tally?

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.

Is the offline mode available?

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.

How is a restaurant priced if it has no rooms?

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.

What happens to my data if we leave?

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.

Who is actually behind this?

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 are on eZee. How hard is it to move?

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.

How long does it take to 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.

See it on real data, in thirty minutes.

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