The Vendor Red Flags Every Hospitality Buyer Should Spot Before Signing

A regional hotel group brought in a robot vendor for a lobby delivery demonstration. The robot navigated smoothly from the service entrance to three mock guest-room doors, handled the simulated elevator call without issue, and returned to base on schedule. The GM was impressed. The contract was signed.

Three weeks into deployment, the robot stalled repeatedly in the east wing — a section of the corridor that hadn't been part of the demo route. Wifi coverage there dropped below the robot's threshold for reliable navigation. The vendor acknowledged it was a known limitation of that corridor type. They had known this before the demo. They had not said anything because the demo route was designed to avoid it.

This is composite — not a specific property. But the pattern is real and it repeats constantly across hospitality technology procurement. The vendor demo is a controlled performance, not an operational preview.

Here are the five categories of vendor red flags, and the questions to ask before you sign anything.

Red Flag Category 1: Demo Theater

What it looks like:

The demo takes place in an optimal environment: the vendor's own facility, a flagship reference property with a dedicated IT setup, or a temporary installation at a trade show floor. Routes are pre-mapped. Obstacles are predictable or removed. Wifi has been tuned for the demonstration. The elevator has been pre-configured and tested six times before you arrived.

None of this is dishonest. The robot did perform those tasks. But it performed them under conditions that your property may not replicate.

What to watch for:

• Demo routes that are significantly shorter or simpler than your actual service corridors
• A vendor who is reluctant to let the robot navigate to a specific area you point to (rather than following the pre-set route)
• Demo floors with unusually wide corridors and no staff foot traffic
• An elevator integration that works in the demo but "will be set up at your property by our integration team during installation"

Counter-move:

Ask the vendor for a 90-day continuous operational reference — not a satisfied customer reference. A property that has been running the robot for at least 90 days without the vendor's on-site team present. Ask to speak directly with the operations manager (not the GM, who may be invested in the tech story). Specific questions to ask that reference:

• "What happened in the first two weeks that the vendor hadn't warned you about?"
• "What's the most common reason the robot is unavailable?"
• "What does the vendor's support response look like when something goes wrong on a Friday night?"

Get at least one reference at a property class similar to yours — similar number of rooms or covers, similar floor plan type, similar labor market.

Red Flag Category 2: SLA Vagueness

What it looks like:

The contract includes language like "best effort" repair windows, uptime targets that are undefined or measured over a 30-day rolling average, and software update schedules that leave all timing decisions at the vendor's discretion.

"Best effort" repair means nothing. It is not an SLA — it is an absence of accountability.

Specific clauses to watch for:

• Uptime defined as "percentage of scheduled operating hours" without specifying how scheduled hours are counted (does a robot that is scheduled for 8 hours but fails after 2 count as 25% uptime or 100% uptime?)
• Software updates that can be pushed at any time without advance notice — and that may change routing behavior, sensor thresholds, or speed settings in ways that affect your operations
• On-site response times that are "24–72 business hours" for a device that runs during every dinner service
• Replacement unit provisions: if the robot is down for more than X days, are you entitled to a loaner unit or a service credit?

What a reasonable SLA looks like:

• Uptime target of 92%+ for scheduled operating periods, defined clearly
• On-site response for critical failures within 24 hours
• 5 business days advance notice before any software update that changes operational behavior
• Replacement unit or service credit if the robot is down for more than 72 consecutive hours

If the vendor's standard contract does not include these terms, ask for them explicitly. Refusal to commit to specific SLA terms is itself a signal.

Red Flag Category 3: Integration Lock-In

What it looks like:

The vendor's fleet management software only runs on their proprietary cloud. Elevator integration is done exclusively by the vendor's own technicians. Replacement parts are only available through the vendor's service channel. The terms of service include language reserving the right to disable ("brick") the unit if service payments lapse.

These are not inherently dealbreakers — some level of vendor dependency is normal in complex hardware. The question is whether the dependency is disclosed upfront and proportionate to the value provided.

Specific terms to review:

Elevator integration: If the vendor requires using their proprietary integration middleware (rather than connecting through an open API like KONE's developer program), ask what happens when you change elevator controllers or add a new elevator bank. Will you need to re-pay integration costs?

Fleet management software: Ask whether you can export your operational data in a standard format (CSV, JSON). If your data is locked inside the vendor's platform with no export path, you have no leverage at contract renewal.

Parts sourcing: Ask specifically whether parts are available from third-party suppliers or whether they are vendor-exclusive. Vendor-exclusive parts means you pay whatever the vendor charges at renewal, with no market comparison.

Software kill switch: Check the ToS for language about the vendor's ability to disable the robot remotely. This language exists in some contracts. If the robot stops working the moment a service contract lapses — including during a payment dispute — that is a material operational risk.

Data ownership: Who owns the operational data generated by the robot — the routes, the delivery logs, the usage analytics? If the vendor owns it and takes it with them when you don't renew, you lose your own operational history.

Red Flag Category 4: Pricing Opacity

What it looks like:

The vendor's opening number is a "special promotional price" available only for a limited time. The RaaS fee "scales with volume" without a published schedule. The contract includes riders for software updates, additional route maps, expanded elevator coverage, or extra robots that weren't discussed in the sales conversation.

Pudu's BellaBot Pro is one of the few hospitality robots with publicly listed pricing — you can find it at RobotLAB. Most competitors require custom quotes, which is not inherently problematic, but it makes price comparison harder and puts the buyer at an information disadvantage.

What to ask:

• "What is your published list price?" If there is no list price, ask why and what factors determine the quote you're receiving.
• "What would the price be if I signed a 12-month contract instead of 36 months?" A vendor who can't give you a clear answer to a direct question about pricing is not a vendor you want to be locked into for three years.
• "What line items are not included in this quote?" Get the exhaustive list of everything that costs extra: installation travel, route remapping after a floor renovation, additional user licenses for fleet software, annual software upgrade fees.
• "What does the contract look like in year 4? Is the renewal rate fixed or variable?"

Red Flag Category 5: Reference Checks That Don't Actually Work

What it looks like:

The vendor offers three reference contacts. All three are glowing. Two are the same account manager in different companies. None of them has been using the robot for more than 6 months. None of them operated in a property type similar to yours.

Vendor-curated reference lists will always show you the top three customers. You need customers who did not renew.

How to find better references:

Ask the vendor directly: "Can you give me one contact from a property that did not renew their contract with you?" This question will make a vendor uncomfortable. That discomfort is informative.

If they refuse, try other channels: hospitality technology forums (Hospitality Net, Hotel Tech Report reviews), LinkedIn groups for hotel GMs, or simply calling properties in the vendor's reference list and asking your contact there if they know of any deployments that didn't work out.

For the non-renew reference, ask:

• "What would you do differently if you were starting the pilot over?"
• "What was the main reason you didn't renew?"
• "What did the vendor do well and what did they do badly during the failure/wind-down?"

Even if you don't find a non-renew reference, push the vendor's best references harder: "What's the thing about working with this vendor that most surprised you — negatively?" Most references will give you something useful if you ask a specific negative question.

The 12-Question RFP Checklist

Use these in writing, in the RFP or in a pre-contract conversation, and require written answers. A fluffy answer to a specific question is visible — and informative.

1. What is your standard uptime guarantee, and how is uptime measured and reported?

2. What is the contractual on-site response time for a critical failure that takes the robot out of service?

3. What advance notice do you provide before pushing a software update that changes robot behavior?

4. If the robot is down for more than 72 consecutive hours, what is the remedy — replacement unit, service credit, or "best effort"?

5. Are replacement parts available from any third-party supplier, or exclusively through you?

6. Does the contract include language allowing you to remotely disable the robot? Under what conditions would you exercise that right?

7. What is the contract price for a 12-month term vs a 36-month term? What is the year-4 renewal rate?

8. What line items are not included in the quote I received? List every potential additional cost.

9. What elevator brands and models have you successfully integrated in the last 12 months? Can you provide a technical contact at one of those properties?

10. What is your integration path if the building changes elevator controllers in the next 3 years?

11. Can I export all operational data — delivery logs, uptime records, usage analytics — from your platform in a standard format at any time?

12. Provide at least one reference from a comparable property that has been operational for 90+ days without your on-site team. Provide at least one reference from a property that chose not to renew their contract.

If a vendor's answers to questions 1, 4, 5, 6, or 12 are vague or deflected, those are the most material terms. Don't let them move to contract until you have clear written answers.

The Las Vegas Model as a Change Management Template

The Culinary Workers Union Local 226 in Las Vegas negotiated automation protections into their 2023–2024 contracts with Strip casino properties after making technology a strike-threat issue. The contract terms: six months advance notice before any technology impacting union jobs; mandatory free retraining for affected employees; six months of health and pension benefits as severance if workers are laid off due to automation.

Importantly, the contract does not ban robots — it regulates the effect on workers.

Even if your property has no union, this template is worth adopting as an internal standard. Not because you are legally required to — you're not, absent a union — but because it is good change management practice.

Six months advance notice gives you time to retrain affected staff before the robot arrives, rather than presenting them with a fait accompli. Severance and retraining commitments demonstrate that the organization is acting in good faith. Both reduce the passive resistance and subtle sabotage that the WSU robot-phobia research identified as a real operational risk.

If you're bringing in a robot that will reduce hours for a specific role, tell those employees directly, early, and with a specific plan. The cost of that conversation is minor. The cost of a disengaged team silently routing around your $16,000 robot for six months is not.

What Separates a Vendor from a Partner

The vendors worth working with respond to specific questions with specific answers. They can explain exactly what happens when the robot fails, how long it takes to fix, and what the remedy is. They can give you a non-renew reference without a long silence first. Their pricing has a logic to it that they can explain.

The vendors to avoid are the ones who present every difficult question as a "unique situation we'll handle together" or who keep redirecting to the demo video.

You are not evaluating a demo. You are evaluating an operational relationship that will last 2–3 years, involve regular staff interaction, and affect your guests' experience every day. Treat it like a hire, not a purchase.