OPSENO

Operator overview

Audience: Owner / general manager
Objective: Understand what Opseno covers and how a day flows so you can assign modules and roles confidently.

What Opseno is

One workspace for:

PillarWhat you get
SellPOS, GST invoices, inventory, purchases, customer/supplier ledgers, retail reports
HostReservations, check-in/out, folios, rates, night audit, housekeeping, C-Form export
ServeTable service, KOT/KDS, charge-to-room, split settlement, multi-outlet
RelateCustomer 360, pipelines, quotes, Opseno Rewards, accounts, segments
EmployHR org, attendance, leave, documents, rosters, India-oriented payroll
AssistTorQ Concierge (ask, propose actions, Feeder setup, Pulse)

You enable modules in Settings. Navigation follows roles - housekeeping staff land on /hk; cashiers keep self-service payroll without admin payroll screens.

How a typical hotel day feels

  1. Morning - Front desk reviews arrivals and clean rooms on /front-desk. Walk-ins check in; deposits hit the folio.
  2. Day - Shop sales and restaurant checks can post to the same guest folio. Housekeeping moves rooms on the kanban (English or Hindi UI).
  3. Evening - Departures check out with GST invoice (SAC 9963 for lodging). Dirty rooms become HK tasks.
  4. Close - Manager runs night audit. Dashboard shows occupancy, ADR, RevPAR.
  5. Month-end - Attendance feeds payroll; approve & lock; print English payslips.

Design principles that affect documentation

  • One guest, one bill - Folio is the stay ledger; retail and F&B can contribute.
  • Property isolation - Multi-property workspaces keep inventory and audits separate.
  • English guest paperwork - Receipts and invoices stay English; Hindi is for HK staff UI.
  • Maker-checker for AI writes - TorQ proposes; humans approve.
  • Honest limits - Print-agent hardware and live payment keys are operator-configured.

Where to go next