Book flights, hotels and activities as one trip.

The order tracks which components confirmed and which need recovery. A hold can be released where supported; a confirmed component may need cancellation or refund under its supplier terms. A timeout must be checked before retrying because the supplier may already have created the booking.

Yes. Per-component cancellation with the penalty schedule of that component, and the bundle re-prices if a package discount depended on the cancelled part. The customer sees the net effect before confirming.

A disruption on any component triggers a cascade evaluation: we propose one coherent change set (new flight, re-timed transfer, re-dated activity) that the traveller accepts or declines as a whole.

Often. Opaque-pricing rules let wholesale hotel rates ride inside a package below public rate parity, legally. Your margin rules decide how much of that you keep versus pass through.

One OA reference for the trip, mapped internally to every supplier confirmation. Your support tooling, the customer’s itinerary and our APIs all speak the OA reference; supplier references remain available when needed.