Back to dictionary

Technical / API

Aggregator vs. Booking Engine — The Layer Model

The architectural distinction between a system that pulls together supply from systems that don't know each other (aggregator) and the system that actually sells to the end customer (booking engine).

In simple terms

Picture three layers stacked: suppliers at the bottom (who don't talk to each other), an aggregator/connectivity layer in the middle that bridges them all into one feed, and a booking engine on top that the customer actually sees and books through.

Real-world example

A booking engine on a tour operator's website might pull hotel inventory through an aggregator layer that's quietly combining feeds from five separate bedbanks the traveler never sees or knows about.

Why it matters

Understanding this layering is essential to diagnosing where a problem actually lives — a 'wrong price' bug could be a supplier issue, an aggregation/mapping issue, or a booking engine display issue, and each needs a completely different fix.

Common mistake

Assuming the aggregator and the booking engine are the same system — they solve different problems and are frequently built or licensed from entirely different vendors.

Interview question

If a customer sees the wrong price on a booking engine, how would you determine whether the bug is in the booking engine, the aggregator layer, or the original supplier feed?

Related terms
Connectivity HubBooking EngineMappingAPI