What to ask a PMS vendor before you sign (from a hostel owner)

I sat through four demos before we built our own software. Every one opened the same way: a polished calendar, a grid of rooms, a salesperson saying “and here is where you see your availability at a glance.” I asked the same question every time. Where are the beds?

Two of the four could not answer it. One said we could “model each bed as a room.” The other said it was on the roadmap. Both demos ended early.

That was the first lesson: a demo is built to show you what the vendor is proud of. Your job on that call is to ask about the things they are not. Here is the list I wish I had taken into those calls, from someone who runs three hostels and has lived with the answers.

Show me a dorm bed, not a room

Hotel software thinks in rooms. A hostel sells beds. If the calendar cannot show you bed 3 in the six-bed mixed dorm, booked by one person for two nights, with bed 4 free on the second night only, then everything downstream becomes a workaround. Housekeeping will not know which bunk to strip. Overbooking checks will count the wrong thing. Group bookings turn into a pile of duplicated rooms.

Ask them to open a dorm in the demo and book a single bed. Then ask them to drag that guest to another bed. If the answer involves creating a “room” for every bed, you are looking at hotel software with a hostel coat of paint. I wrote about why that breaks in why hotel software fails at hostels.

What happens when the channel connection dies at 2am?

Every channel manager works in the demo. The real question is what it does when an OTA's API hangs, or your rate push fails silently for six hours. Ask three things. Does the system notice on its own, or do I notice when a double booking walks through the door? Does it re-sync by itself when the connection comes back? And who gets told?

Then ask to see the sync log. A vendor who cannot show you a record of what was pushed, when, and whether it succeeded is asking you to trust them blind. You will not have that luxury on a sold-out weekend. For the plain-language version of what is happening under the hood, see what a channel manager actually does.

How do I leave?

Nobody asks this because it feels rude in a sales call. Ask it anyway. Can I export every reservation, guest, rate and payment as a plain file, at any time, without calling support? Is there a notice period? A cancellation fee? When does my data get deleted?

A vendor confident in their product answers this easily. A vendor who hesitates is telling you their retention strategy is friction. The same logic applies to getting in: ask who does the migration. “We give you a CSV template” means you will spend your evenings for weeks typing rates into a spreadsheet while running a hostel. We do the move for free and verify the prices on a call, because we have done it the hard way ourselves and never want to again.

Who answers when I message you?

Ask for the actual support path. Not “we have 24/7 support”, but: when I write at 11pm because a guest cannot pay and the card terminal is down, what happens? Is it a bot? A ticket queue? A person who has used the software? A person who has worked a reception desk?

Ask how long a typical reply takes, phrased so they have to give you a number. Ask whether you can reach a human on WhatsApp, because that is where you will be when things go wrong, not at a desktop filling in a form. And ask who built the thing. If the people who wrote the software have never checked in a guest at midnight with a dead printer, it shows in a hundred small ways.

What does it actually cost?

The monthly subscription is the easy number. The hard numbers are hidden. Is there a commission on direct bookings through their booking engine? Some vendors take a cut of every booking you worked hard to win away from the OTAs. That is an OTA with extra steps. Is there a per-booking fee on channel bookings? What does payment processing cost on top of the processor's own rate? Are reports, housekeeping, POS and invoicing separate modules? Is there a setup fee? Is the price per property, per bed or per user, and what happens when I add a second property?

Write every number down and add them up for a realistic busy month and a realistic dead one. Then ask about the minimum term. Long contracts are common, and they mostly exist because switching is painful. If you want something to measure against, I keep an honest side-by-side with the usual names.

How fast is it on a bad connection?

Demos run on the vendor's laptop on the vendor's wifi. Your reception runs on whatever the local provider gives you, with a guest's phone tethered as backup. Ask to log into the demo account yourself, on your own phone, on mobile data, and open the calendar. Count. If a screen takes four seconds, that is four seconds with a tired guest staring at you, sixty times a day.

Speed is not a luxury feature. It is the difference between staff using the system and staff keeping a paper notebook next to it “just for quick stuff.” The paper notebook is where double bookings are born. Our own bar is half a second for every screen, and I would ask any vendor to name theirs.

The checklist

• Open a dorm in the demo. Book one bed. Drag it to another bed.
• Show me the channel sync log. What happens in an outage, and who gets told?
• Can I export all my data myself, today? Notice period? Cancellation fee?
• Who migrates my data in, and what does that cost?
• Support: human or bot, on which channel, how fast, and have they worked a desk?
• Commission on direct bookings? Per-booking fees? Which modules cost extra?
• Price per property, bed or user, and what changes with a second property?
• Minimum contract term.
• Let me log in on my own phone on mobile data and time the calendar.
• Can a volunteer have a login that only sees what they need?
• Does the booking engine take payment itself, with which processors in my country?
• Can I try it with my own real data before paying anything?