A hotelier evaluating Stayhos for the first time often asks the same question early on: does this require connecting to our PMS? The honest answer is no — Stayhos works without a PMS, and the Guest Hub, service requests, and Staff Dashboard all run independently of any reservation system. But there's a related, more specific feature that gets less attention: the optional CSV guest-stay import, which lets a hotel check QR code access against an actual list of arriving or in-house guests. This post is a plain walkthrough of what that import does, what it doesn't do, and where the honest boundary sits.
Why stay validation exists at all
Room QR Cards open the Guest Hub the moment anyone scans them, because the room context comes from the QR code itself rather than a login. For most hotels, that's exactly the point — no account creation, no app download, no friction between arriving in a room and being able to ask for towels or find a local restaurant recommendation.
Some hotels want an additional layer of confidence: a way to know that scans are coming from guests who are actually booked into that room during that stay, not from an old QR card left in a room after checkout, or a code that ended up somewhere it shouldn't. That's the specific problem CSV guest-stay import solves. It is not a requirement for the Guest Hub to work — it is an optional check some hotels choose to turn on.
What the CSV import actually does
The mechanic is straightforward. A hotel exports a list of guest stays from its own PMS — typically arriving or currently in-house guests, with the fields the hotel's PMS makes available for export — and uploads that list into Stayhos as a CSV file. Once imported, QR code access from the Guest Hub can be checked against that list.
That's the entire scope of the feature. It is a validation step layered on top of the existing QR access flow, not a new guest-facing feature and not a change to how requests are submitted, routed, or tracked once a guest is in the Guest Hub. Everything downstream — structured service requests, staff dashboard routing, Discover Near Us recommendations — behaves exactly the same whether or not a hotel has ever imported a CSV.
What it validates — and what it deliberately doesn't
It's worth being precise here, because vague language is how "CSV import" quietly turns into an implied "PMS integration" claim, which would be inaccurate. The import validates one thing: whether a QR scan corresponds to a stay that appears in the most recently imported list. It does not pull live reservation data, does not update automatically as bookings change in the PMS, and does not send anything back to the PMS. There is no bidirectional sync, no webhook, no polling connection of any kind.
Practically, that means the check is only as current as the last import. A guest who checks in five minutes after the most recent CSV upload won't appear in the imported list yet — which is a normal, expected gap for a manual, periodic process, not a malfunction. Hotels that rely on this feature typically build the re-import into an existing routine, like a daily front-desk task, rather than treating it as a one-time setup step.
Why not a full, live PMS connection
The straightforward question is why Stayhos doesn't just connect directly to hotel PMS platforms and skip the manual export step. The honest answer is that full PMS API sync — automatic, live data flow from providers like Mews, Cloudbeds, or Opera — is a materially different (and materially more complex) undertaking than a CSV import, and it's on the roadmap rather than built today. This isn't a minor distinction to gloss over: a live API sync implies real-time accuracy claims that a periodic CSV import simply can't make, and industry reporting on PMS integrations backs up why that gap exists in practice. Independent hotels frequently cite juggling multiple disconnected systems as a persistent operational headache, and PMS integrations that do exist often run on polling intervals of several minutes rather than instant updates — which introduces its own edge cases during high-occupancy periods.
There's also a cost dimension worth naming plainly: per-connection integration fees for smaller hotels connecting several systems can run into hundreds of dollars a month on top of a base PMS subscription, on top of setup fees some legacy providers charge just to open the connection. A CSV import avoids all of that entirely, at the cost of being periodic rather than live. That's a deliberate tradeoff, not a workaround dressed up as a feature — and it's why the wording on this stays consistent: optional CSV import today, full PMS API sync on the roadmap, not live.
Setting it up in practice
There's no special configuration required to start using the Guest Hub, service requests, or the Staff Dashboard — those work from day one, independent of any PMS or CSV activity. CSV import is a separate, optional step for hotels that specifically want the added stay-validation check.
In practice, that means: export a guest-stay list from the PMS in the format the hotel already has available, upload it, and repeat on whatever schedule fits the property's operation — daily is common, though some hotels do it a few times a week depending on turnover. Hotels running a pilot often start without CSV import at all, get comfortable with how requests move through the Staff Dashboard, and add the stay-validation step later once the core workflow is familiar. Nothing about adding it later changes how existing requests or staff assignments behave.
Where this fits with the rest of the platform
CSV guest-stay import sits alongside the parts of Stayhos most hotels use every day: the Guest Hub guests reach by scanning their Room QR Card, the structured requests that land in the Staff Dashboard, and the local recommendations guests find through Discover Near Us. None of those require CSV import to function, and none of them change behavior because of it. It's a narrow, optional layer — one honest answer to one specific question hoteliers ask, not a broader integration claim.
Hotels that have already decided they're comfortable running guest requests without a PMS connection at all can simply skip CSV import entirely. It exists for the subset of hotels that specifically want QR access checked against a real stay list, nothing more.
A practical next step
If you want to see how the Guest Hub, Room QR Cards, and Staff Dashboard work together before deciding whether CSV stay validation makes sense for your property, the Guest Hub demo walks through the guest and staff experience end to end.
To talk through whether CSV guest-stay import fits your specific PMS export format and front-desk routine, contact Stayhos directly.