Case study · Hospitality & Travel · Product Engineering

Four booking platforms, one backend that has to hold.

Gaveia runs four online booking platforms for Croatian and Slovenian holiday properties. Moberg builds and maintains the backend systems and admin portals that power all of them.

The client & the project

One operator, four storefronts, three markets of travellers.

Gaveia operates four online booking platforms — Adria Camps, My Mobile Home, Villas Guide and Avtokamp — covering camping, mobile-home and villa properties across Croatia and Slovenia, used heavily by Polish, German and Italian travellers. Four brands, four audiences, one inventory of real properties underneath.

Moberg develops the backend systems and admin portals that power all four platforms: the property hub where inventory lives, the sales tools, and the customer-support tools. The engagement is ongoing — maintenance plus new feature development, which in a booking business is a permanent state rather than a phase.

The solution

Shared machinery behind different storefronts.

The core design decision is that the four platforms are storefronts, not separate systems. Behind them sits a shared backend built and maintained by Moberg: a property hub as the single source of truth for listings, availability and content, with sales tools and customer-support tools operating on the same data. A property updated once shows up correctly everywhere it is sold.

The stack is pragmatic for the job: PHP and TypeScript for the backend systems and portals, WordPress where content management earns its keep, and ElasticSearch for the thing travellers actually do most — search. Fast, tolerant search across thousands of properties in multiple languages is the front line of a booking site's conversion, and it gets dedicated infrastructure accordingly.

Because the engagement is continuous, the work alternates between keeping the season running and building what the next season needs — new features land on a platform that is simultaneously serving live bookings, which shapes how carefully changes to the shared core are rolled out.

The challenges

The honest part.

Architecture

Four platforms, one core

A shared backend cuts duplication but concentrates risk: a change to the property hub touches all four brands at once. Backwards compatibility is not optional.

Data

One truth about each property

Listings, availability and pricing must agree across every storefront that sells them. Divergence is not a cosmetic bug — it is a double booking.

Operations

Changing the engine mid-season

Maintenance and new development run in parallel on systems taking live bookings from Polish, German and Italian travellers. There is no quiet moment to deploy into — only quieter ones.

The value

What it bought Gaveia.

Gaveia runs four consumer brands on one engineering investment. New features — and fixes — are built once in the shared backend and benefit every platform, instead of being re-implemented four times. The admin portals mean the property, sales and support teams work against the same data the storefronts sell from, which keeps the operational side of a multi-brand business manageable with a lean team.

The ongoing arrangement means the platforms compound rather than decay: Moberg carries both the maintenance duty and the roadmap, so the people extending the system are the same people who answer for it when it misbehaves. Incentives, aligned.

KPIs & numbers

The shape of this one.

4
booking platforms on one backend
2
countries of properties — Croatia & Slovenia
3
core admin portals — property hub, sales, support
Under the hood

The stack on this one.

Backend

PHP

The backend systems powering all four booking platforms.

Application

TypeScript

Typed application code across the portals and services.

Content

WordPress

Content management where an editor, not an engineer, should own the page.

Search

ElasticSearch

Property search across markets and languages — the front line of conversion.

← All stories

Get in Touch