On 26 October 2026 Cloudbeds announced Cloudbeds POS, a native mobile point of sale for hotel restaurants, bars, spas and shops. For most hoteliers it is a product update. For everyone who sells a standalone POS, an upsell tool or a payments product into hotels, it is a positioning event, because the platform their customers already run now offers a version of their category.

Point-solution sales teams tend to react with panic or a shrug. Both lead to bad sales decisions. Here is a clearer position, tested against the strongest objections.

What Cloudbeds actually announced

According to the Cloudbeds announcement on Hotel Online, Cloudbeds POS covers the outlet workflow from setup and menus to orders, kitchen tickets, payments, folio posting and reporting. Staff take orders and payments on a phone or tablet, guests can pay by cash, Tap to Pay, Pay by Link or room charge, room charges post directly to guest folios, orders can still be recorded offline, and outlet sales appear in the same reports as accommodation. CEO Adam Harris framed it as closing the gap between experiences beyond the room and "systems that can't talk to the rest of the property".

Two details matter for anyone selling against or alongside it. First, the problem Cloudbeds names is re-entering purchases, checking room charges and piecing together revenue reports. That is an integration problem, not a restaurant-operations problem. Second, Cloudbeds POS is currently available as a pilot to select customers. It is a real product with a clear direction, and it is early.

The thesis: platform POS kills the vague middle, not the specialist

When an all-in-one platform enters your category, it does not take the customers who need your depth. It takes the customers who only bought you to connect two systems.

Put plainly: a native platform POS competes hardest with the part of a point vendor's pitch that says "we integrate with your PMS". If folio posting, unified reporting and one bill at checkout are the main reasons a hotel bought your product, the platform now does that job by default. If your reason to exist is depth in a specific operation, such as a high-volume restaurant, a spa schedule or a complex retail floor, the launch changes your sales conversation but not your market.

Argument one: the platform is solving the seam, not the kitchen

Almost every feature is about the join between the outlet and the property: room charges to folios, house accounts, outlet revenue in hotel reports. That matches what hotels say hurts. In the Hotel Yearbook annual tech survey (2025), which gathered 264 responses, integration, fragmentation and lack of industry standards were the most commonly cited frustrations of both hotel operators and tech vendors. A platform that removes one seam is answering that complaint directly.

This is why I have argued that integrations sell hotel software more than features do. The corollary is uncomfortable: if your integration was the feature, a native module makes it redundant for the buyer who only wanted the seam closed.

Argument two: the POS market is growing, so this is not a zero-sum fight

Demand for modern POS is rising across hospitality. In its fiscal 2027 second-quarter results (October 2026), Agilysys reported record revenue of $93.4 million, up 17.7%, and said one-time product revenue was higher than expected "as the hospitality industry continues to increase its investments in modern point-of-sale (POS) technology solutions". Point vendors who are clear about who they serve can benefit from the same buying cycle.

Argument three: coexistence is already the norm

Mews shows what the market looks like once a platform has its own POS. Mews sells Mews POS, purpose-built for hotels and integrated with its PMS and payments. Yet the Mews Marketplace advertises 1,000+ integrations with no connection fees, and Toast's support documentation for its Mews integration explains how Toast POS posts room-charge checks to the guest folio in Mews and passes all sales data on to hotel accounting tools. A native POS and a marketplace full of third-party POS options sit side by side.

The native POS becomes the default where outlet needs are light; properties with serious F&B keep choosing specialists. Your job is to be the obvious specialist, not the generic alternative.

The counter-arguments, taken seriously

"Bundles always win in the end"

Sometimes, especially with small independents who want one vendor and one contract. But every module in a bundle has to be good enough for every segment. I have written about why all-in-one hotel platforms struggle to win some independents, and the same tension applies to a POS. A bundle is weaker where the outlet is a business in its own right.

"It is only a pilot, so ignore it"

A pilot shows the direction of the roadmap. The right response is not alarm: update your discovery questions and battlecards now, before your prospects have seen a demo.

"Point vendors should simply partner with every platform"

A connection gets you listed; it does not get you chosen. Before you invest, work through the build or partner decision for each platform: how many of your target properties use it, how deep the integration must be, and whether the platform treats marketplace partners fairly when its own module is in the deal.

How point-solution vendors should respond

1. Audit your win reasons. Tag why each of your last twenty wins bought. Where "connects to our PMS" was the main reason, that revenue is exposed.

2. Pick a segment the platform will not prioritise. High-volume restaurants, spas and multi-PMS groups are examples.

3. Make the integration boring. Folio posting, sales category mapping and reporting should work on day one.

4. Arm sales for the side-by-side. Prospects on Cloudbeds will now ask why they should not use the native option. Give reps a fair, specific answer.

5. Be a good marketplace citizen. Be the partner a platform is happy to recommend for the deals its own module does not suit.

What it means for the platforms' own GTM

For Cloudbeds and every platform watching it, a native POS is a retention and expansion play. Each module a hotel adopts deepens the relationship and lifts revenue per property. The GTM risks are specific, though.

• Segment the pitch. Lead with the native POS where outlets are simple, and lead with the marketplace where they are complex.

• Protect partner trust. Marketplace partners will watch how their listings and referrals are treated now that the platform competes with them.

• Price as expansion, not replacement. Customers with a working third-party POS need a reason to switch beyond "it is ours".

• Show the pilot results. Once pilot customers have outcomes, such as fewer missed charges or faster month-end reconciliation, publish them.

Platforms that move into adjacent categories are also making a category claim: that a unified system is the right way to run the whole property. That is a bet worth understanding, and I covered how vendors make it in the case for category creation in hotel tech.

The takeaway

Cloudbeds POS is a sensible move for a platform whose customers wanted fewer seams. It does not end the specialist POS market. It does end the easy sale for any point vendor whose main value was the connection. Point vendors should narrow their segment, make integration invisible and sell depth. Platforms should sell the module where it fits and keep the marketplace honest where it does not. Both are positioning decisions inside a wider hotel tech go-to-market strategy.

If you sell POS, upsells or payments into hotels and are not sure how much of your pipeline depends on the integration alone, a free revenue leak audit will show where platform bundles are most likely to cost you deals.

Frequently Asked Questions