I have a rule I learned the hard way: never buy hotel software because the demo was pretty. Buy it because it talks to everything else you already own. The number of times I have watched an independent hotelier sign a contract for a shiny new booking engine, upsell tool, or guest messaging platform, only to discover three weeks later that it does not actually sync with their property management system, is genuinely depressing.
So this is the post I wish someone had handed me years ago. It is the exact set of questions I run every vendor through before a single dollar changes hands. Not the marketing questions. The annoying, in-the-weeds, “let me talk to your engineering team” questions that save you from a six-month integration nightmare.
This is not about which booking engine or website platform to pick. It is about a deeper layer: will this thing connect to your stack at all, and who is on the hook when it breaks?
Why integration-readiness is the whole ballgame
Here is the thing about running an independent or boutique hotel. You do not have an IT department. You have you, maybe a GM, and a front desk team who already have nine jobs each. Every tool you add is a promise that it will reduce work, not create a new manual data-entry chore.
When two systems do not integrate, that gap gets filled by a human copying numbers between screens. Rates typed twice. Availability updated in two places. Guest data living in a silo nobody syncs. That is where overbookings come from. That is where the wrong rate goes live on a Friday night.
And here is the part that ties directly to what I do for a living. Your direct-booking strategy, your whole effort to reduce OTA dependence and win back more direct reservations, lives or dies on clean, connected data. If your booking engine cannot push real-time availability, you cannot compete with the OTAs on your own website. The OTAs already have flawless integration with everything. Independents lose ground when their own stack is held together with copy-paste.
The OTAs do not beat independents because they have better hotels. They beat them because their tech stack is perfectly integrated and ours usually is not. Every disconnected tool is a small gift to Booking and Expedia. Closing those gaps is one of the cheapest ways to win back direct revenue.
The questions, in the order I ask them
I do not save these for the contract stage. I ask them on the very first call, before I have any emotional attachment to the product. If a sales rep cannot answer them, I ask to speak with someone who can. A vendor who is proud of their integrations will connect you with their solutions team in a heartbeat. A vendor who dodges is telling you something.
1. Do you have a certified, pre-built integration with my exact PMS and channel manager?
Not “we can integrate with most systems.” Not “we have an open API.” I want a specific yes or no for my specific stack, named by name and version.
There is a massive difference between these three answers:
- “Yes, we have a certified two-way integration with [your PMS], here is the documentation.” This is the gold standard. The work is done, tested, and supported by both companies.
- “We have an open API you can build against.” Translation: the connection is possible, but you are paying a developer to build and babysit it forever.
- “We are planning to support that soon.” Translation: no, and do not believe the timeline.
Certified matters because it usually means the PMS vendor has reviewed and blessed the connection. When something breaks at 11pm, there is a clear owner and a support path, not two companies pointing fingers at each other while your rates are wrong.
2. Is the integration one-way or two-way?
This trips people up constantly. A one-way integration might push data out but not pull it back, or vice versa. For something like rates and availability, you almost always need true two-way sync, your PMS and the new tool both reading and writing.
Ask explicitly: which fields sync, in which direction, and how often? A guest messaging tool that reads reservations but cannot write a note back to the PMS profile is creating a new silo you will eventually have to reconcile by hand.
3. What exactly does “open API” include, and who maintains the connection?
When a vendor leads with “we have an open API,” I slow down and get specific. An open API is a feature, not a finished integration. So I ask:
- Is the API documented publicly, and can I see the docs right now?
- Is it REST, and does it return modern formats, or is it some legacy XML thing from 2009?
- Does it cover the endpoints I actually need (reservations, rates, availability, guest profiles), or just a sliver?
- If I want a custom connection built, who builds it, who maintains it, and what does that cost over a year?
The maintenance question is the one people forget. APIs change. Both systems push updates. A connection that works today can silently break after a version bump, and if nobody owns it, you find out from an angry guest.
4. What are your rate limits, and will they keep up with my volume?
This is the most technical question on the list and the one vendors least expect from a hotelier, which is exactly why I love asking it.
Rate limits cap how many requests two systems can exchange in a given window, say, 60 calls per minute. For a small property this rarely bites. But if you run frequent rate changes, dynamic pricing, or you are mid-size with real volume, aggressive throttling means your availability and pricing can lag behind reality. Lagging availability is how you end up overselling a room you do not have.
Ask for the published limits in writing. Ask what happens when you hit them, do requests queue, fail, or get dropped? A confident vendor has a clear answer. A vendor who has never thought about it is a vendor whose integration was an afterthought.
5. How does authentication and data security work?
You are handing this tool guest data, names, emails, sometimes payment context. So I ask how the connection authenticates (modern token-based auth like OAuth is what you want, not a password emailed in plain text) and how data is encrypted in transit and at rest. If they cannot speak to this clearly, that is a red flag for both security and engineering maturity.
6. What is your connector ecosystem, and do you support the middleware I might use?
Some tools connect directly. Others connect through middleware or an integration platform that acts as a universal translator between hotel systems. Ask whether the vendor plugs into the connector platforms common in hospitality, because that can turn a “no native integration” into a “yes, through this hub.” It also future-proofs you, if you swap your PMS next year, a tool wired through a hub is far easier to re-point than one hardwired to a single system.
A simple scorecard I use
When I am comparing two or three vendors, I stop trusting my gut and score them. Here is the rough framework, adapt the weights to your situation.
| Integration factor | What a strong answer looks like | Why it matters |
|---|---|---|
| Certified PMS connection | Named, documented, two-way | Owner exists when it breaks |
| Sync direction | True two-way on the fields you need | Prevents silos and manual entry |
| API maturity | Public REST docs, modern auth | You can verify, not just trust |
| Rate limits | Published, generous, clear failure behavior | No stale rates or overbookings |
| Connector support | Works with hub or middleware | Future-proof if you swap systems |
| Support ownership | One clear escalation path | No finger-pointing at 11pm |
If a vendor scores poorly on certified connection and support ownership, I usually walk, no matter how good the product looks in isolation. A great tool that does not integrate is a worse outcome than a decent tool that does.
The best demo of my career was a vendor who, when I asked about rate limits, pulled up their actual API docs on the call and walked me through the failure behavior line by line. I signed within a week. Confidence about the boring stuff is the strongest sales signal there is.
How this connects to your direct-booking and visibility goals
I care about integration because I care about results that show up in your bottom line. Every tool in your stack either supports the goal of healthier OTA mix and more direct bookings, or it quietly works against it.
A booking engine that syncs availability in real time lets your own website compete for the reservation instead of handing it to an OTA. Clean guest data flowing into your CRM powers the follow-up that turns a one-time guest into a repeat direct booker. And accurate, structured information about your property, your rooms, rates, amenities, is also what feeds the systems that decide whether you show up in search and in AI answers. If you want to understand the revenue stakes, the book-direct math on OTA commissions lays out why each percentage point of direct share matters, and our work on book-direct conversion depends entirely on a stack that actually talks to itself.
It also matters for visibility. When I help a hotel with AI visibility across AEO and GEO, the accuracy of your structured data is a huge input. Disconnected systems produce inconsistent information, and inconsistent information is exactly what gets you overlooked or misquoted. If you are curious whether your property is even legible to AI tools, start with is your hotel invisible to ChatGPT. And the same disconnection problem shows up in how OTAs out-rank you in search, they win partly because their data is everywhere and consistent.
One more honest note. No tool, and no agency, can promise you a specific ranking or a guaranteed flood of direct bookings. What integration-readiness buys you is the foundation that makes everything else possible: accurate data, less manual work, and a stack that can actually execute the strategy. Skip the vetting and you are building on sand.
Run the checklist before you fall in love
The pattern I see over and over with independents is buying on emotion, the demo, the rep you liked, the feature that solves one annoying problem, and discovering the integration gaps only after the contract is signed. Flip the order. Confirm integration-readiness first, then let yourself enjoy the demo.
Save the six questions above. Better yet, send them to the vendor in an email before your next call and watch how they respond. The good ones will be relieved you asked. The ones who get cagey just saved you a very expensive mistake.
If you want a second set of eyes on your stack, whether a tool you are about to buy will actually support your direct-booking and visibility goals, or how to wire what you already own into something that works, that is exactly the kind of thing I dig into. Take a look at how we approach book-direct conversion and then book a call. I would rather help you ask the right questions now than untangle a bad integration later.