Mehta · 2A
Check in a guest, post a charge, take a payment, print a GST invoice, fire a KOT and close the night. Built inside a working hotel group, on the floor, at the desk — not in a product meeting.
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.
Nine modules ship in one product. There is no per-module price list, and no module you discover is extra after signing.
Rooms down, nights across. Drag to move a guest, pull the edge to extend a stay, right-click for what applies. Three clicks to a booking, thirty seconds.
Walk-in on one screen including the ID. Check-in from a reservation in one click. Check-out that ends in a GST invoice, not in a second system.
Charges, payments, splits, routing, voids with a reason, cashier shifts counted by denomination. One bill settled as part cash and part card, in one action.
Company group over branches, because the branch is what has its own GSTIN — and the GSTIN is what decides the invoice. Credit limits pool and sub-limit together.
KOT routed to the right station, per-channel menu pricing, kitchen inventory with recipe deduction, and each outlet closing its own business date.
Status, attendant boards, minibar straight onto the folio, and the discrepancy report that catches a guest still in a room the desk thinks is empty.
One click, under two minutes, or set a time and it runs itself. Checks before it commits, and running it twice cannot post the night twice.
Around thirty, from the manager flash to GSTR-1, every one computed from the same ledger the folio uses. Front office, revenue, finance, POS and housekeeping.
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 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.
Templates, outbox, rendering and delivery log are built. The API sender 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.
The sales register in filing format, and the FRRO Form C generated from what was captured at check-in.
Generated inside the check-out flow, queued when the line is down and fired on reconnect. Needs your IRP credentials.
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 two rows where they win today.
| What matters | Typical cloud PMS | Typical desktop PMS | Asar |
|---|---|---|---|
| Works with the internet down | Screen stops | Yes, but not cloud | Cloud + local + LANIn build |
| POS in the same ledger | Usually a separate module or product | Separate | Same database, posts to the room in one action |
| Corporate: group over branches | One flat company record | One flat company record | Group + branch, each with its own GSTIN and sub-limit |
| GST slab on declared tariff | Usually | Often manual | Computed per night, changes mid-stay correctly |
| Custom report builder | Fixed report menu | Fixed report menu | ~30 reports todayBuilder on roadmap |
| Pricing model | Per module, per add-on | Licence + AMC | One price per room, per month |
| OTA connectivity | Built in, many channels | Usually third-party | Through AxisRoomsIntegration on roadmap |
| Booking engine on your own site | Included, mature | Add-on | Not built yet — this one is theirs too |
| Your data leaves when you want | Export on request | It is your machine | Open documented API, full export, no lock-in |
If distribution is what you need most this quarter, say so at the demo — we will tell you plainly to keep your channel manager and revisit us when the AxisRooms link ships.
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, forced upgrades, housekeeping, restaurant POS with per-outlet day-end, night audit, ~30 reports.
Restaurant setup and pricing screens, then the remaining masters: seasons, packages, promo codes, reason codes, charge master. Today a price change is a job for us; it should be a job for you.
Connect the sender to the outbox that already exists. Then the edge application that makes the offline engine visible to a receptionist, and LAN mode.
A two-way integration with AxisRooms, who already do OTA connectivity properly, and our own booking engine for your website. We connect to a channel manager rather than becoming one; a direct booking is the part that should not route through anybody.
Real modules, deliberately deferred. None is needed to run rooms and F&B, and each is better started after the core is finished than alongside it.
Yes, for rooms and F&B. Reservations, front desk, folio and cashiering, corporate billing, GST invoicing, housekeeping, restaurant POS and the night audit are live and running in our own hotels. What you would not get today is OTA connectivity, a booking engine on your own website, banquets, or the offline client. If any of those is the reason you are switching, we will say so at the demo rather than after.
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.
Through AxisRooms, and not yet. We are building 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.
Until it ships, hotels running Asar keep their existing channel manager and inventory lives in two places. That is a real daily burden and we would rather you hear it now than discover it in week two.
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, and our hotels are still the first to get every release.
The target is one day: the setup wizard takes your room list, rates and mappings from Excel, and the migration importer reads exports from the common Indian systems. It is a target we would rather be measured against than described by, so ask us 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