HotelDsk Property Ops
Works with whatever you already run

Keep whatever books your rooms. Add the half that runs the property.

HotelDsk does not replace your booking system, connect to it, or ask it for anything. It runs beside it. Whether you are on a full PMS, a channel manager, a spreadsheet, a WhatsApp group or a paper diary, nothing about how your rooms get sold changes on the day you start.

The short answer

Every property runs on two layers, and almost every property only has software for one of them. The first sells the room: rates, availability, the reservation, the bill. That is what a PMS is, and if you have one it is probably doing that job well enough.

The second layer is everything that happens because the room was sold — it has to be cleaned, checked and released, somebody has to be on shift to do it, the kitchen has to know how many for dinner, the store runs out of something, the chef spends money at the market. That layer is usually run on a WhatsApp group, a printed list and somebody’s memory. HotelDsk is software for the second layer, and only for the second layer.

Which is why there is nothing to choose between. You already have the first one.

The split

Who does what, from tonight

Nothing moves from the left column to the right. This is the arrangement on day one and it is the arrangement in year three.

Whatever books your rooms

A PMS, a channel manager, a spreadsheet, a notebook, the OTA extranets, or the phone.

  • Rates and availability, and keeping them the same everywhere.
  • Reservations arriving, changing and cancelling.
  • The guest’s bill, the deposit, the card, the refund and the invoice.
  • A booking engine on your own website, and the commission you pay when it is somebody else’s.
  • The tax-shaped paperwork your accountant asks for.

HotelDsk runs the property

The half that starts the moment a booking exists and ends after the guest has gone.

  • Which rooms are ready, which are stripped, which failed inspection and need doing again.
  • Who is on shift, who clocked in, who asked for Thursday off and who is covering.
  • The cleaning checklist, the sign-off, the fault found in room 4 and the job it created.
  • What the kitchen is cooking tonight and for how many.
  • What is left in the store, what ran out, and what the chef paid for at the market this morning.
  • Who came through the gate, and which delivery belonged to which order.

So how does HotelDsk know who is arriving?

Today, a stay is typed into HotelDsk by whoever is at the desk — the name, the room, the dates. It takes seconds and it is the only place the two systems overlap at all. It is worth knowing why so little depends on it: the room board does not wait for a booking to appear. A housekeeper marking a room clean is what moves it, so the board is correct for a walk-in, a phone booking and an OTA booking alike, and it is still correct on the morning somebody forgets to type one in.

Where we stop

Four things HotelDsk will never do

Not "not yet". These are the jobs your booking system already does, and this is the whole reason the two fit together instead of competing.

No channel manager, and no OTA rate sync

Whatever pushes your rates and availability today keeps doing it. Distribution is a solved, crowded, expensive job, and doing it badly next to somebody who does it well helps nobody.

No guest folio, and no card payments

We never touch the money a guest owes you. HotelDsk records what a guest used — the dinner, the mini-bar, the late checkout — so whoever bills them has the numbers, and the bill stays where it is.

No booking engine, and no commission

Your website, your direct bookings and your commission arrangements are unchanged. We do not sit between you and a guest.

No migration, and nothing to import

There is nothing here to move your history into. HotelDsk starts empty on the day you start using it, and fills up from the work your staff do.

Running both

What it actually costs you to try this

An afternoon, and no risk to the thing that takes your money. That is not a slogan — it falls straight out of the fact that the two systems never touch.

Nothing to disconnect

You are not migrating anything. Your booking system keeps taking bookings and issuing bills exactly as it does today; HotelDsk starts empty and fills up as your staff use it.

No integration to wait for

The two do not talk to each other, and do not need to. Our room board changes when a housekeeper marks a job done — a person, not a feed. That is also why it works for a walk-in guest and a phone booking, not just an OTA one.

The half a PMS was never built for

Stock counts by store, market purchases, petty cash, meal planning, the visitor gate log, a nightly closing that someone has to actually file. These are not missing features in your PMS; they are a different job.

A price that does not need a meeting

Free to five rooms, then published. If it turns out you did not need it, you have spent an afternoon rather than a procurement cycle.

Whatever you run today

Find yours, and see exactly what changes

Every page is dated, and every claim about another company comes from their own published material or a named review source. Where they publish nothing — and eight of these ten publish no price at all — it says so instead of guessing.

with Mews

Enterprise-grade cloud PMS, with Flexkeeping for housekeeping

Keep it. That page says exactly what changes, and what does not. What it adds →

with Cloudbeds

All-in-one PMS, channel manager and booking engine

Keep it. That page says exactly what changes, and what does not. What it adds →

with Oracle OPERA Cloud

The enterprise standard, for large hotels and chains

Keep it. That page says exactly what changes, and what does not. What it adds →

with Little Hotelier

SiteMinder’s system for 1–30 room properties

Keep it. That page says exactly what changes, and what does not. What it adds →

with Guesty

Built for short-term rentals and listing portfolios

Keep it. That page says exactly what changes, and what does not. What it adds →

with eZee Absolute

A long-established favourite among Indian independents

Keep it. That page says exactly what changes, and what does not. What it adds →

with Hotelogix

Cloud PMS from Singapore, used across 100+ countries

Keep it. That page says exactly what changes, and what does not. What it adds →

with RoomRaccoon

All-in-one for small and independent hotels

Keep it. That page says exactly what changes, and what does not. What it adds →

with Stayflexi

Flexible check-in and hourly bookings, popular with budget hotels

Keep it. That page says exactly what changes, and what does not. What it adds →

vs hotelkit real head-to-head

The one genuine head-to-head on this list

The one page here that is a genuine choice — including where they beat us. Read the comparison →

Something else — or nothing at all

A spreadsheet, the OTA extranets, a booking system nobody has heard of, or a diary on the desk. It makes no difference here: HotelDsk never asked your booking system for anything, so there is nothing for it to be incompatible with. Plenty of properties this size start with no booking software and add one later; that day changes nothing on this side.

All ten side by side, feature by feature →

The usual objection

Is a cleaning board any use if it is not wired to your bookings?

This is the question we get most, and it deserves a straight answer: yes, and the reason is that room status has nothing to do with where the booking came from. Whether a guest walked in, phoned you, or arrived through an OTA, the same physical room still has to be stripped, cleaned, checked and released.

What a connected PMS adds is that a checkout flips the room to dirty by itself. That is a real convenience and we do not have it. What it does not do is any of the work afterwards — and the work afterwards is where small properties actually lose the morning.

No more front-desk blindness

Whoever is on the desk can see which rooms are ready without phoning the cleaning crew. In HotelDsk the status changes when the housekeeper marks the job done, which is a person rather than a feed — and a person is what you have.

The clipboard stops going stale

A printed room list is out of date the moment a guest asks for a late checkout. A shared board is not, and your housekeeper updates it from the phone already in her hand.

Faults and mini-bar caught in the room

A broken light or a used mini-bar gets logged where it is noticed, before the guest has left. That is revenue and maintenance you were previously losing to memory.

Nothing to lose by trying

Five rooms are free and there is no card field in the product. If it does not fit your house, you have spent an afternoon.

Before you ask

The questions this raises

Does “works with” mean it integrates with my PMS?
No, and we would rather say so plainly than let you find out. There is no connector, no API key, no sync and nothing to configure. It means the two run side by side without either needing the other — which is why there is no integration to wait for, no list of supported systems to check yourself against, and nothing that breaks when your PMS ships an update.
My PMS already has a housekeeping module. Why would I run two?
If it is being used and it is working, do not. That is a genuine answer and it is on every comparison page here. The reason people run both anyway is that a PMS housekeeping module covers room status and stops there — it does not do the checklist and the inspection sign-off, the shift and the leave request, the meal plan, the stock count, the market money or the gate log. If room status is the only part you are short of, keep what you have.
Will you build a channel manager later?
No. We looked seriously at it and stopped, and the reasoning is the same one that makes this page work: everyone in this market already sells rooms well, nobody runs the property, and a second-rate distribution feature bolted onto an operations product would be worse than what you are using now and would take the attention off the thing only we do. If your distribution is the problem, buy a channel manager — and this still sits underneath whichever one you buy.
What happens to my data if I stop?
You take it and go, without asking us, and your bookings were never in here to begin with — they are still wherever they always were. Stopping HotelDsk costs you the operations history, not your business records. That asymmetry is deliberate: it is what makes trying this a small decision.
Do I have to type every booking in twice?
You type in the stays that need a room made ready — the name, the room, the dates — and that is the only overlap between the two systems. Most of what HotelDsk does never involves a booking at all: the cleaning round, the shift, the kitchen, the store cupboard and the cash tin are the same work whether the house is full or empty.

Add it to whatever you already run

Nothing to connect, nothing to migrate, and your booking system never knows it happened. Free up to five rooms, no card, about a minute to start.

Free up to 5 rooms No card required Nothing to install

Already set up? Log in →

Start now → Log in