Radisson

The vendor opportunity at Radisson

Radisson presents a compact but open technology landscape for software vendors. In the 2026 FDD, the brand reports 46 total US units—40 franchised and 6 company-owned—all operated by 65 individual operators. None of those operators control more than a single location. This fragmented ownership structure, combined with a 13.04% year-over-year unit decline and an absence of any mandatory technology stack, means every door is a standalone sales opportunity. The top states are Texas (8), Florida (7), Illinois (4), California (4), and Michigan (4). As part of Choice Hotels, Radisson sits within a larger holding vehicle that also includes Choice Hotels International, Radisson Collection, MainStay, Park Inn, Clarion Hotels, and Suburban, but no shared procurement mandate for software is evident in this filing.

Who controls software purchasing

The FDD’s Item 1 does not list any HQ executives by name or title, so a specific buyer—CIO, VP of IT, or otherwise—cannot be identified from this document. The operator footprint is entirely single-unit: 65 operators across roughly 65 located units, with zero operators in the 2–9, 10–24, or 25+ bands. This suggests that individual franchisees have substantial autonomy over their technology choices, absent any evidence of a corporate mandate or preferred vendor program. If your sales motion targets a central procurement lead, you will need to identify that contact outside the FDD, because the filing offers no signal.

Tech named in the FDD, and what is actually required

The 2026 FDD names several technology systems, but none of them are mandated. Oracle and Oracle OPERA appear with a tag indicating they are ‘in place, not required—a fee or usage clause.’ Medallia and Meta carry identical tags. Amadeus, Galileo, and SABRE are ‘named only, not required—the FDD mentions them.’ A central reservation system (CRS) is also noted but remains unclassified. Practically, this means the franchisor has disclosed that these tools can or do incur fees or are mentioned in the filing, but no franchisee is required to adopt them. When you pitch a Radisson operator, you are selling into an environment where Oracle OPERA and Medallia may already be known quantities, but switching or adding adjacent tools is not blocked by a franchisor mandate.

Procurement, renewals, and timing

Item 8 contains no extract that would clarify whether Radisson uses a designated supplier model, an approved supplier list, or an open procurement approach. Without that signal, assume an open market at the unit level. Item 17’s renewal terms are also absent, so there is no brand-level contract cycle to exploit. The initial term length is not disclosed. Given the year-over-year unit contraction and the lack of multi-unit owner groups, the most effective timing strategy is to engage individual operators as they evaluate occupancy-driving or operational-efficiency tools—there is no synchronized renewal window to target.

How to read the Radisson FDD

The full FDD is embedded below. When you open the PDF, focus on Item 8 for any future update on procurement controls, Item 11 for franchisor assistance that might include technology support, and Item 19 to understand financial performance representations that could inform an operator’s willingness to invest in your software. Because no technology is mandated, the value of reading the FDD lies in confirming what is absent, not what is required. For a ranked target list of Radisson operators sized by estimated AUM, royalty burden, and unit location, FranCloud compiles that from the FDD operator data—reach out and we will put it together.