A-ROSA Hotels
Brand relaunch
10 hotels in the luxury segment
A-ROSA hotels stand for a sophisticated ambience in a dreamlike setting. For guests, the anticipation of the A-ROSA vacation regions is just as enjoyable as the prospect of wellness, sauna and the variety of delights in the restaurants.
About A-ROSA
A-ROSA has been part of the DSR Hotel Holding since 2004 and operates 10 upscale hotels in Germany, Austria, and Italy. With over 500 rooms, the brand stands for luxurious spa experiences, culinary variety, and rejuvenation in some of Europe’s most beautiful holiday regions.
From breathtaking nature to indulgent wellness, guests look forward to the A-ROSA experience — long before check-in.
Permanent conversion optimization...
... through iterative further development
In addition to integrating further projects into the shared Neos system, we have built and developed many other features together with the customer over the years.
For example, users can book current offers for the next 30 days on the last-minute pages. A special feature here is the display of the current location weather for the next few days, so that users can immediately see where the sun is shining or where they can be pampered in the spa area with a clear conscience when booking at short notice. The display of weather and departure prices optimizes the occupancy rate of DSR hotels, especially in the low season.
Another central feature is the control of DSR's online marketing campaigns via Neos. For this purpose, the information from Neos is provided as an XML feed which is then picked up and displayed by Adform.
By connecting the OptiRez and OnePageBooking booking interfaces, current prices are automatically displayed on the website without any editorial effort. Editors can select parameters such as the hotel location, the number of nights and the desired season in the dynamic offer elements. The element automatically displays the cheapest offer with the corresponding information. Prices and availability are updated on an ongoing basis.
In December 2022, a large part of the A-ROSA booking route for all locations was also revised and moved to the existing Neos system.
Both the new design with a focus on an improved user experience and the technical implementation of sitegeist were successfully implemented.
The IBE (Internet Booking Engine) also uses the OptiRez booking interface and dynamically displays the current daily prices in the calendar overview.
Services
- Consulting
- Conception
- UX/UI design
- Programming
- Conversion optimization
Highlights
- Multibrand platform
- Extensive expansion of the Neos core functionalities
- Connection to various booking systems OptiRez, OnePageBooking
- Last-minute offer page
- API for automated generation of advertising banners
- Integration of the translation tool DeepL for efficient implementation of multilingualism
- Dynamic offer elements with live prices
- Continuous performance optimization
- Continuous Seo optimization
- Expansion of the Pixx.ioPackages
- Integration of the 3Q Video platform
- Revision of the booking route
Higher conversion
To enable maximum flexibility in the design of the booking journey, we retained the existing IBE as a stable technical foundation. On top of that, we implemented a fully customized booking interface in the Neos CMS, entirely optimized for conversion.
By separating technical logic from UX/UI logic, we gained complete freedom in terms of design, messaging, and user flow—without being constrained by the IBE itself. The result: a measurable and significant uplift in conversions.
Upselling through flat rates & packages
Conversion boost through complete individuality
In the Neos frontend, real-time availability and “starting-from” prices are displayed for each day. This helps prevent booking drop-offs—for instance, when users happen to search during a high-demand weekend, such as a festival, and abandon the process due to unusually high prices.
Additionally, users can enter their federal state to view a personalized calendar with all relevant school holidays—providing real value for vacation planning.
All of these features are implemented independently of the underlying IBE. We now use the IBE solely as a data hub, while the CMS layer in Neos allows us to build virtually any functionality without limitations in layout, UX, or UI.
