Outmatic
Why Outmatic
The engineering partner for the AI era.
Real context first, then the right technology, not the other way around.
Read our storyOutmatic
From raw data to live booking: intelligent integration across Alpitour, Eden, Ideal, and Nicolaus keeps a travel platform selling in real time. Update times cut from hours to minutes, +40% faster searches.
Outmatic
Engineering Team
Clictravel sells holiday packages online, which means the business only works when the catalog reflects what's actually available, at the right price, in the right moment. To make that possible, the platform needed a reliable way to pull package data from the major Italian tour operators (Alpitour, Eden, Ideal, Nicolaus) and turn it into something the booking site could use.
The goal was twofold. Automate the daily flow of package information, availability, and prices coming from each provider. And build a real-time booking engine that could query those providers the moment a user searches, so the customer always sees accurate availability and pricing.
Without that foundation, the platform simply couldn't operate.
The real complexity wasn't technical in isolation. It was the fact that every tour operator exposes data in its own way, with its own format, its own access logic, and its own quirks. Turning that into a single, coherent catalog is where the work lives.
On this project, that meant handling large daily volumes from different sources, normalizing the information into a structure the booking site could actually use, keeping performance and data consistency aligned across systems, and designing for scalability so that adding a new tour operator later wouldn't require rebuilding anything.
We worked side by side with the Clictravel technical team, starting from a careful analysis of the data flows and the day-to-day operational needs. The approach was modular and incremental, split into two distinct but tightly connected workstreams.
Provider data integration. We built a .NET Windows application that downloads holiday packages from each provider on a daily cycle. The raw data lands in MongoDB, gets processed and normalized through RabbitMQ events, and ends up in the SQL Server database that powers the booking site. An automated test suite runs alongside the pipeline to keep stability and data quality in check. Team: two developers, four months.
Real-time booking engine. We developed a .NET Web API that, at search time, queries the providers live to return up-to-date availability and prices. Each provider is handled by its own dedicated gRPC service, which keeps the connectors independent and makes it easier to specialize the logic for each channel. Team: two developers, two months.
The whole project ran on Agile iterations, with short cycles and progressive releases that avoided any impact on the production systems.
The architecture was shaped around three priorities: performance, reliability, and the ability to grow without friction.
The main components:
The result is a pipeline that runs on its own, consistently, and a booking engine that stays in sync with the providers in real time.
More broadly, the platform moved from a semi-manual workflow to a fully automated booking engine. That shift is what actually enables Clictravel's digital business model to run at the pace it needs.
Integrating a complex ecosystem like this is a question of architecture before it's a question of code. Going event-driven with RabbitMQ and isolating each provider behind its own gRPC service kept performance high and made every connector independent, which in turn made maintenance and future evolution much more manageable.
The other lesson was about pacing. Releasing value incrementally, in short cycles shared with the Clictravel team, meant the system kept getting better without ever putting production at risk.
