Hospitality Operating System
Front desk, housekeeping, kitchen, bar, store, maintenance, payroll and the public website — one record of the property, on every phone. Money is counted and signed for at every hand-off, and the owner sees all of it from anywhere.
Module & feature overview — prepared for hotel owners and operators
Why it exists
They lose it in small, quiet, deniable amounts — a drawer that is never counted, stock that walks out between deliveries, a room let for cash that no system ever saw. Every part of this was built to close one of those gaps.
Whoever takes cash opens a drawer and counts it at the end of their shift — before the system tells them what it expected. Any shortfall is worked out automatically, has to be verified by somebody else, and reaches the owner's phone the moment it happens.
Every completed order draws its ingredients down by itself. Nobody types a stock figure to match the shelf, so the gap between what was sold and what is missing is visible instead of being absorbed.
Bar, kitchen, store and laundry count their own stock at handover, against what the system expected. The incoming shift accepts it or disputes it. A shortage that appears at 6am belongs to a named shift and a known minute — not to a stock take three weeks later with nobody left to ask.
A housekeeper clocks into the room and cannot close the job without confirming the door is locked, the windows shut and the key returned. A job still running at double its allowance raises the alarm, because that usually means the room is open and nobody is in it.
Staff clock themselves in from their own phone. Breaks are requested and signed out by a supervisor. Visitors are booked in and out. At any moment the owner can see who is on site, who is working, and who has been idle for half an hour.
Every create, edit and delete is recorded against a named account, with the before and after values, and the device it came from. Append-only — nobody can tidy the log, including the owner.
Concrete floors, one mast, a bad afternoon. Staff keep working offline and the work sends itself when signal returns — with no duplicated orders, because every submission carries a key the server only accepts once.
For the owner
The point of automating a hotel is not the software — it is not having to send a manager round the property to find out what is happening. The control room answers the questions you would have walked the floor to ask.
Every open drawer, who has it, which station, since when, and how much should be in it right now. Not at close of business — this minute.
Sold, free, dirty or broken, with arrivals and departures against it. A room out of service shows why, who reported it, and what the repair has cost so far.
A deliberately short list: drawers that don't balance, orders nobody has picked up in half an hour, urgent faults, counts still unsigned. When it is empty, nothing needs you — and that is the useful part.
Alerts arrive on a locked phone with the app closed. Anything critical also goes out by email and SMS. You do not have to be looking at the system for it to tell you something is wrong.
What makes it different
Offline-first
Pages already opened keep loading. Orders, check-ins and tasks save on the device and send themselves later. A badge shows exactly how many items are still waiting, so nobody hands over a shift with figures stuck on a phone.
Retries can never double-post — enforced at the database, not in the app.
Stock control
Link a dish or a drink to what it consumes, and completing the order draws the stock down. Cancel it and the stock returns. No parallel spreadsheet, no month-end guesswork about where the beer went.
Reversible and idempotent — a sale can only deplete once.
Room keys
Keycards are refused while a balance is outstanding or the checkout date is open, and reception cannot override it. Housekeeper cards expire with the shift. Every door opening is logged, granted or refused.
Vendor-neutral: any controller that can call a URL works.
Accountability
Field-level before and after values, the device and browser used, and the person responsible. It answers "who changed this rate?" in a minute, and it clears the innocent just as fast.
Append-only at the model — a stray delete throws rather than rewriting history.
Adoption
A staff handbook of 37 guides, filtered to each person's role — a housekeeper sees six, an accountant thirteen. It covers the setup order, the daily flows, and how each module feeds the next.
Written per module, including the mistakes that cause most support calls.
Ownership
Analytics, pixels, payment gateways, SMS and push credentials are all set from an admin screen. Secrets are encrypted, never shown again, and changing one takes effect immediately.
No developer, no redeploy, no waiting on an agency.
Loss prevention
Profit & loss, receivables, payables, a VAT summary for FIRS and a full QuickBooks sync cover what an accountant does daily — and a scan runs every 30 minutes flagging what a spreadsheet never catches: a bill reduced after it was paid, stock adjusted with no reason given, a drawer that doesn't balance, an approval sitting untouched for weeks.
Visible to the owner even when the accountant would rather it wasn't — that's the point of it.
The directory
Each person sees only their department's screens. Nothing here is an add-on or a separate licence.
Access
Not about secrecy — a short menu is faster to work and harder to make mistakes in. A bartender never meets the payroll screen.
The guest-facing half
The public site is part of the same system. Change a rate and the website changes. There is no second thing to update.
Guests book and pay online through Paystack or Flutterwave. Bookings land straight on the front desk board — no commission, no third-party inbox.
Structured data for the property, each room tier with its nightly rate, and articles — the markup that earns a rich result instead of a plain link. Sitemap generates itself.
A QR code at each table, lounger or room. Guests order from their phone; the ticket reaches the kitchen or bar tagged with where it came from.
Only guests who actually stayed can review, invited after checkout. Approved ratings feed the stars shown in search results.
Tiers, points and a wallet that works across every property on the network. Returning guests are recognised at the desk, not just in a database.
Images served in modern formats at the size actually displayed; the hero video is skipped entirely on slow connections. The homepage weighs under a quarter of a megabyte on mobile.
Proven in production
Case study
Seven room tiers, twenty-four rooms, a restaurant, two bars and an outdoor pool — all running on this system: the front desk, the kitchen tickets, the store counts, payroll and the public website that takes the bookings.
Getting a property live
The order matters — later records attach to earlier ones. This sequence is the one the built-in handbook walks a new property through.
Property details, currency, tax, check-in times. Then a login for each member of staff, on the right role.
Room tiers with rates and photographs, the floor plan, opening stock counts and reorder levels, suppliers.
Dishes and drinks linked to the stock they consume — the step that makes selling move the shelf. Then departments, employees and salaries.
Photography, promotions, the public site. Then one fake guest all the way through: book, pay, check in, issue a key, order food, check out.
For the group
Each hotel keeps its own data, staff, branding and subscription. Guests and loyalty points move between them.
| What a property gets | Included | Notes |
|---|---|---|
| Its own data and staff | Yes | Fully separated per property |
| Its own branding and domain | Yes | Name, colours, photography, contact details |
| Public website | Yes | Rooms, dining, gallery, blog, booking |
| All 90 modules | Yes | No tiered feature licensing |
| Staff handbook | 37 | Role-aware, editable per property |
| Cross-property loyalty | Shared | Points earned anywhere, spent anywhere |
| Marketplace listing | Optional | Partner hotels and local vendors |
| Runs on shared hosting | Yes | No dedicated server or cloud account required |
Commercials
No per-seat charges and no feature tiers — a twelve-room guest house gets the same software as a group flagship. What changes is the size of the property and the level of support.
Next step
Tell us about the hotel and we will walk the whole system with you — front desk to payroll — on the live installation, not slides.
Ready to run
Every module in this document is finished and in production today. Nothing here is a roadmap item, and nothing waits on a future release.