Every module, and what is actually in it.

The screen the hotel lives on: a stay view that loads instantly, a dashboard that answers the manager's first four questions before anyone asks, and one search box.

• Tape chart / stay view — rooms down, nights across. Drag a booking to another room, pull its edge to extend the stay, right-click for the actions that apply in that state.
• Colour by status — in house, due out, arrived, held, out of order. The colours are the room rack the hotel already uses.
• Dashboard — arrivals, departures, in house, occupancy, ADR, RevPAR, revenue so far today, housekeeping wheel, payment dues.
• Keyboard navigation — F-key shortcuts in the desktop tradition, because a receptionist with a queue does not reach for the mouse.
• Global search roadmap — one box resolving guest, phone, booking reference or company from anywhere.

The most repeated action in the building. Three clicks and thirty seconds for an individual; one form for a nine-room wedding party.

• New reservation — availability, rate and tax resolved as you type, not on save.
• Held bookings with a payment link — hold a room for a stated duration, send the guest a link showing the stay, take the deposit. The hold converts or releases itself; nothing sits blocked because someone forgot.
• Group reservation — one form creates the group and every room in it, each with its own guest, folio and bill. It refuses to oversell to fill a group, and names the night that fails rather than booking part of it silently.
• Book that again — clone any past or present stay, with the rate difference stated before it is confirmed.
• Amendment — dates, room type, rate, occupancy, with the price recalculated and the difference shown.
• Cancellation — policy-driven, with the retention charge calculated and posted rather than typed in.
• No-show processing — automatic at night audit, with the retention charge and the room released.
• Deposits and advances — numbered receipt, held against the booking until check-in.
• Room block / allotment — for travel agents and series groups, with a cut-off that releases what is unused.
• Confirmation dispatch in build — email and WhatsApp, carrying the payment link.
• Waitlist, overbooking allowance, reservation traces roadmap — availability is hard-capped today, so walking a guest is deliberate rather than possible.

Arrival to departure. One screen for a walk-in including the ID, one click for a guest who already has a reservation, and a check-out that ends in a GST invoice.

• Walk-in check-in — guest, ID, room, rate and advance on a single screen, targeted at under sixty seconds.
• Check-in from reservation — pre-filled; the only decisions left are the room and the ID.
• Room assignment — free rooms shown with the reason an unavailable one cannot take the guest, rather than the room quietly missing.
• Room move — drag on the stay view or use the dialog. Every room is listed with a verdict; a manager can override with a reason, and the override is logged.
• Forced upgrades — when the booked type physically cannot house the booking (oversold, nothing free, room out of order), the guest moves up at the rate they paid. An upgrade merely because a suite is empty is a revenue decision, so it waits for a person. It never downgrades.
• Stay extension and early departure — with the added or removed nights repriced.
• Check-out with settlement — balance, tender, invoice, in two clicks.
• Form C for foreign guests — generated in the FRRO format from what was captured at check-in.
• Police / arrival–departure register — in the format the local station asks for.
• Blacklist alert — raised at check-in against the chain-wide profile, not just this property's.
• Guest messages and wake-up calls — logged against the stay so the next shift sees them.
• GRC print, self check-in queue with e-sign, express group check-in, day-use and house-use rooms, scanty baggage, key cards roadmap

Every charge, every payment, every adjustment, on a bill that can be split, routed, transferred and reopened — and never quietly rewritten.

• Post a charge — manually, or automatically at night audit for room and tax. Charges carry a category, so routing and reporting work without tagging them later.
• Post a payment or refund — cash, card, UPI, bank transfer, wallet, cheque, OTA-collected or city ledger, each labelled and each landing in the cashier's report.
• Split tender — one bill settled as part cash and part card in a single all-or-nothing action. A rejected third tender leaves no trace of the first two, and the error is about the whole payment rather than the tender that happened to be last.
• Folio split — by charge type, by percentage or by nights.
• Folio transfer — room to room, room to a group master, room to the city ledger.
• Charge routing — the company pays room and tax, the guest pays extras; set once on the booking and applied to every posting after.
• Void and adjustment — with a reason and, above a role's limit, an approval. The original posting stays on the bill.
• Discounts — enforced against the role's ceiling, not the operator's judgement.
• Advance deposit ledger — deposits held separately from revenue until applied.
• Paid-out voucher — money out of the till on the guest's behalf, against a reason.
• Cashier shift open and close — denomination count, cash drop and handover, with the variance stated rather than absorbed.
• GST invoice — B2C, or B2B carrying the buyer's GSTIN; proforma folio at any moment of the stay.
• Reopen a closed folio — a permission, with the reason and the person recorded.
• Currency exchange, credit and debit notes roadmap

Corporate business in India is rarely one company at one address. Asar models a group with branches — because the branch is what has its own GSTIN, and the GSTIN is what decides the invoice.

• Two-level company master — a group (legal name, PAN, group credit limit, master contract, relationship owner) over branches (city, own GSTIN, own billing address, own contact). Both bookable and billable.
• Contracted rates that inherit — the contract attaches at group level and applies to every branch, with a per-branch override where one negotiated its own.
• Contract scope across the chain — applies to a chosen set of organizations, brands or properties. A chain deal and a single-hotel deal are the same object with a different scope.
• Validity and versioning — from and to dates, expiry warning, renewal reminder, and historic bookings keep the rate they were booked on.
• Credit limit as a pool with sub-limits — the block evaluates branch sub-limit and group pool together, and says which one tripped.
• Billing instruction per branch — consolidated to HQ or separate per branch. This drives which GSTIN prints.
• Bill-to-company routing — room only, room and tax, or all extras, held on the branch.
• Authorised booker list — who at that branch may raise a company-billed booking.
• Statements — per branch and rolled up per group, with branch-wise subtotals.
• Payment knock-off — one receipt allocated across several invoices, oldest-first or manual, with unallocated advance held at group level.
• Ageing follow-up — per branch and consolidated, so a group view shows which branch is dragging the overdue.
• Travel agent commission — calculated and carried into a payout register.
• Rate confidentiality roadmap — hide the contracted rate from the front desk display.

The department that decides whether the room the desk just sold can actually be handed over.

• Room status — dirty, clean, inspected, with the history of who set what and when.
• Task assignment board — auto-assign by floor or attendant, with the workload visible before the shift starts.
• Minibar posting — recorded by the attendant, straight onto the guest's folio.
• Discrepancy report — housekeeping's physical status against the front desk's, which is how a guest still in the room is caught before it is resold.
• Out of order and out of service — with an expected release date, so the room returns to sale by itself.
• Mobile app in build — the schema and endpoints exist; the device client that runs on the attendant's phone over the property LAN is being built.
• Linen and laundry, lost and found, inspection checklist with photos roadmap

Built in, not bolted on. The restaurant, the bar, room service and the spa run on the same database as the rooms.

• Orders and KOT — dine-in by table, room service, takeaway and delivery, with the ticket routed to the right station: kitchen, bar or bakery.
• KOT modify and cancel — with a reason and a kitchen reprint, because the kitchen has already started.
• Menu with per-channel pricing — a dish priced differently for dine-in, room service and delivery, schedulable by day-part.
• Variations and add-ons — size, preparation, toppings, each with its own price effect.
• Room posting with verification — the guest name must match the room, so a bill cannot be charged to the wrong stay.
• Settlement — cash, card, UPI, room post, city ledger, staff and non-chargeable, with a reason required for NC.
• Cashier float, cash in and out, variance — the till is opened, counted and closed like the front desk's.
• Outlet day-end — each outlet closes its own business date. It refuses while an order is unsettled or a till is open, and records what the day took.
• Kitchen inventory — raw materials with units and storage, recipe-based automatic deduction, low-stock and reorder alerts, purchase orders, goods receipt, vendor payables.
• Setup wizard in build — outlets, stations, tables, categories, dishes and prices maintained by the restaurant itself. The largest open piece of POS work.
• Merge and split tables, split a bill by item, transfer a KOT, favourites grid, steward-wise sales, thermal printing, aggregator sync roadmap

One click, under two minutes, or set a time and let it run itself. The audit makes the day's numbers final, so it checks before it commits.

• Pre-audit checklist — pending check-outs, unsettled folios, open KOTs and open tills, each linked to the screen that clears it.
• Automatic room and tax posting — every in-house room charged at its resolved rate, with the correct GST slab.
• No-show processing — automatic, with the retention charge from the policy on the booking.
• Date roll with locked-day accounting — after the roll the day is closed; changing it is a permission and it is logged.
• Idempotent — running the audit twice cannot post the night twice. Tested, not assumed.
• Manager flash on close, and the signed audit pack roadmap

A room can be taken out of order with a reason and a release date today, and that is genuinely useful. The department around it is specified and not yet built.

• Out-of-order blocking with an expected release date live
• Work orders — raised from the housekeeping app, the desk or a guest request, with assignment, status, parts used and cost.
• Preventive maintenance scheduler — AC service, deep clean cycles, AMC dates, meter readings.
• Maintenance categories and SOP checklists — the hotel's own lists.

Deliberately deferred, and deliberately not faked. Banquets has its own calendar, its own document and its own billing rules, and it is scheduled after the rooms and F&B core rather than alongside it.

• Venue and hall master — capacities, layouts, minimum spend.
• Availability calendar — blocked by held enquiries as well as confirmed events.
• Enquiry pipeline — prospect to confirmed, with follow-up dates.
• Banquet Event Order — the function sheet the operation runs off, printed and versioned.
• Advance schedule and payment tracking — staged payments against the event.
• Post-event billing — guaranteed pax against actual, charged by the rule agreed up front.

We connect to a channel manager rather than becoming one. Building OTA connectivity means maintaining a dozen fragile integrations that break on somebody else's release schedule, and it is not where a hotel gets value from us. AxisRooms already does that job well, so the rooms go out through them and come back into a PMS that actually owns the stay. The booking engine on your own site is ours, because a direct booking should not route through anybody.

• AxisRooms integration — rates, inventory, restrictions and bookings flow both ways between Asar and AxisRooms, and AxisRooms handles MakeMyTrip, Booking.com, Agoda, Expedia, Goibibo and the rest.
• Channel mapping — room type and rate plan against the AxisRooms equivalents, held as a master so adding a channel is their mapping, not our project.
• Booking engine — ours. Mobile-first, two-step checkout, UPI and cards, promo codes, add-on upsell, WhatsApp confirmation. Commission-free, straight into the same ledger the front desk uses.
• Google free booking links and Hotel Ads — metasearch pointing at your own engine rather than at an OTA.
• Payment gateway — Razorpay, PayU or Stripe, per property.

If you already run AxisRooms, that stays exactly as it is and we plug into it. If you run something else, tell us at the demo — the integration is built against one channel manager first and we would rather say so than imply it is built against all of them.

The guest's whole relationship with the hotel on the app they already have open, and a hotel-side record of every touch.

• Guest payment page live — a held booking sends a link showing the stay and the amount, takes the deposit and confirms the hold. A dead link says "that link is not live" rather than showing a login screen.
• WhatsApp journey in build — confirmation, pre-arrival check-in link, digital registration card with e-signature, in-stay requests, folio at checkout, payment link, feedback.
• ID scan with OCR roadmap — Aadhaar via DigiLocker and passport OCR, auto-filled into the registration card.
• Guest portal roadmap — live folio, service requests, express checkout.
• Review management roadmap — Google and OTA reviews aggregated, replies drafted, sentiment tagged.
• Chain-wide preference engine roadmap — preferences recorded in Goa surface at the Delhi desk.

Around thirty ship today, every one computed against the same figures the folio uses, so a report and an invoice cannot disagree.

• Front office — manager flash, arrival and departure list, in-house list, police report, Form C register, night audit report, room discrepancy, no-show and cancellation, expected occupancy.
• Revenue — daily revenue, monthly production, segment / source / rate plan / room type wise, ADR and RevPAR trend, OTA production and commission, corporate production branch-wise with group rollup and contracted-versus-actual variance.
• Finance — sales register (GST-ready), tax summary with GSTR-1 export, receipt register, city ledger ageing at branch and group level, agent commission, paid-out register, void and discount audit, cashier summary.
• POS — item sales, category sales, KOT versus bill audit, NC report, outlet daily summary, shift variance.
• Housekeeping — attendant productivity, room status history, work order status.
• Chain — consolidated flash, property comparison, brand rollup.
• Custom report builder roadmap — pick columns, filter, save it, schedule it by email. The one that removes the parallel spreadsheet.

Nothing here is blocked on engineering. Each needs an account, an approval or a contract, so they are started early and ship as the counterparty allows.

• Accounting — Tally native voucher push, Zoho Books, plain export for everyone else.
• Payments — Razorpay, PayU, Stripe, HDFC/ICICI terminals, UPI dynamic QR with automatic reconciliation, PineLabs and Paytm EDC.
• Door locks — Vingcard, Onity, be-tech and the Indian brands, with key card issue and verified duplicates.
• Compliance — e-invoice IRP, DigiLocker Aadhaar verification, passport OCR, DLT-registered SMS.
• Food aggregators — Zomato and Swiggy order intake and menu sync into the POS.
• Telephony — call accounting and EPABX posting to the folio.
• Open REST API and webhooks — documented and open, so your own developer can build on it. This one is ours alone and is not waiting on anybody.

The things nobody looks at until the day they matter enormously.

• Audit trail viewer live — every event, filterable by user, record, device and date.
• Supervised support access live — granted by you, time-boxed, fully logged.
• Data export in build — guests and transactions, on request, in an open format. No lock-in.
• Automatic cloud backup and a downloadable property backup roadmap
• Device management roadmap — which devices hold unsynced offline data, and remote wipe for a lost machine.
• Public uptime status page roadmap