Muéstranos tu stack, tu roadmap, tu escenario de replatforming, y te mostraremos cómo encaja Laioutr, cuánto cuesta y qué tan rápido puedes estar en producción.
"Después de 30 minutos supimos que Laioutr hace viable nuestro replatforming." - Daniel B., CEO, hygibox.de
Karls: one storefront for shop, tickets and hotel bookings across eleven experience villages
How Karls brought Shopware, ticketing and hotel booking into one visitor experience instead of three separate systems.
- Just 1Frontend, but 5 Backends
- 1 Experiencefor all visitors
- Campaigningfor seasonal adjustments
The Challenge
A visit to Karls is not one transaction. A family books a room near one of the experience villages, buys admission tickets for the day, and orders something from the shop before or after the trip. Behind those three actions sat three different worlds: Shopware for the shop, a ticketing platform for admission, and separate systems for hotel and event booking. Each of them worked. None of them knew about the others.
For the visitor that showed up as seams. Different interfaces, different logic, different places to identify yourself, for what is from the outside one brand and one trip. With eleven locations, a merchandise range, an admission business, hotels and a growing world of Karls characters and content, the gap kept widening between how the company thinks about its visitors and how its systems presented it. What was needed was one frontend able to hold all of it, without replacing any of the systems that already run the business.
The Solution
Laioutr was chosen for exactly that integration job. It sits as the frontend layer above the existing stack and connects to each system through its own integration: Shopware for the shop, the ticketing system for admission, and the hotel and event booking systems for stays and dates. None of them was migrated or replaced.
Above those connections, one storefront presents a single Karls world. Shop, tickets and hotel are parts of the same experience rather than three destinations, and the content around them, the locations, the attractions, the characters, lives in the same system as the transactional pages instead of in a separate CMS.
Because pages are compositions of components rather than per-system templates, a new location, a seasonal campaign or a new format can be built once and reach the shop, ticket and stay contexts at the same time.
"We kept Shopware, the ticketing platform and the booking systems. That was the condition. Laioutr sits on top as a frontend layer, connected to each of those systems individually, so visitors move between the range, admission and a hotel stay without noticing where one system ends and the next begins."
Head of IT
Why it worked
The systems stayed, the seams went. Karls kept Shopware, its ticketing platform and its booking systems, and gained a single frontend in which a visitor moves between merchandise, admission and a hotel stay without noticing where one system ends and the next begins.
That is also what made the integration affordable. Unifying the experience from the back end would have meant replacing working systems across three different businesses. Doing it in the frontend layer leaves each system where it performs best and puts the unification where the visitor actually is.
For the team, the storefront is now one place to work rather than three. Campaign pages, location pages and the content around the Karls world are built and maintained in Laioutr Studio.