What is a hospitality orchestration layer?
Last reviewed: 2026-11-02
A hospitality orchestration layer is middleware that sits between a property's operational systems (PMS, POS, golf management, spa and access control) and the channels guests use, such as a branded app or web portal. It connects to those systems through APIs, unifies guest profiles, availability, bookings and payments, and presents them as one experience. The systems of record stay in place.
Why do properties use one?
A property uses an orchestration layer because guests experience one property while the property runs many systems. Booking happens in one place, dining in another, tee times somewhere else and loyalty in a fourth app. Every hand-off can lose the guest and the revenue with them.
An orchestration layer closes those gaps without ripping anything out. Staff keep the tools they know. Guests get a single branded experience across stay, golf, dining, loyalty and payments.
How does an orchestration layer work?
An orchestration layer has three parts. Your existing systems stay where they are: the PMS, POS, tee sheet, dining, payments, CRM and access control you have already invested in. The orchestration layer is secure API middleware and an identity layer that unifies guest profiles, real-time availability, bookings and payments across those systems. On top sits your branded experience, a white-label app and web portal under your name, colors and voice.
In practice, a guest can check in from the app while the PMS confirms the room is ready, book a tee time that updates live in the golf system, and unlock the door with a mobile key. The whole stay sits on a single secure folio. The connections are bidirectional, so data moves in both directions between the layer and each system. See the platform for the full architecture.
Which systems can it connect to?
An orchestration layer connects to the categories of system a property already runs. Zenda ships pre-built API adapters for these:
- Property management: Oracle Opera, Mews, Stayntouch and Cloudbeds.
- POS and dining: Lightspeed, Toast, Micros, SevenRooms and OpenTable.
- Golf management: Lightspeed Golf, Jonas and GolfNow.
- Access control: Salto and ASSA ABLOY.
- Loyalty and messaging: Airship and Klaviyo.
- Payments and content: Stripe and Kontent.ai.
A custom API integration path covers systems that are not on the list. Integration work is field mapping and testing against your instance rather than building connectors from scratch. The integrations page has the full list.
How does it compare with the alternatives?
The two common alternatives are point-to-point integrations and a custom build. The table below describes general characteristics of each approach, not a measurement of any specific product.
| Criterion | Orchestration layer | Point-to-point integrations | Custom build |
|---|---|---|---|
| Existing systems | Stay in place and connect through shared adapters | Stay in place, each pair connected separately | Stay in place, each connector written in-house |
| Guest experience | One branded app across all connected systems | Often one app or login per system | One app, designed from scratch |
| Maintenance | Adapters are maintained by the layer's provider | Each link needs attention when either system changes | Owned by the property's team, for every integration |
| Time to launch | Typically weeks for Zenda, scoped in discovery | Depends on the number of connections | Typically many months |
For Zenda, Shockoe builds the layer and maintains its integration adapters as the connected platforms change.
When is an orchestration layer the wrong tool?
An orchestration layer is not a replacement for a PMS, POS or golf management system. It connects to them. If the need is a new system of record, or a consumer booking site for guests who are not yet tied to a property, a different product fits better.
What is Zenda?
Zenda is a hospitality orchestration platform by Shockoe that connects a property's PMS, POS, golf, access control and loyalty systems into one branded guest app for web, iOS and Android. It serves hotel resorts, golf clubs, destination resorts, casinos and multi-property groups. Read more about Zenda, or request a demo to see it mapped to your property.
Frequently asked questions
Does an orchestration layer replace our PMS or POS?
No. An orchestration layer connects to the systems a property already runs and adds a guest-facing layer on top. The PMS, POS and golf management system stay the systems of record.
How long does it take to deploy an orchestration layer?
It depends on which systems are connected. For Zenda, a branded launch is typically measured in weeks rather than the many months a custom in-house build usually takes, and scope and timeline are confirmed during discovery.
Is the guest experience a native app or a web app?
Both. Zenda delivers branded native iOS and Android apps and a matching web experience from the same orchestration layer, so guest identity and itinerary stay consistent across channels.