Skip to main content
OnArrival

Run the whole booking flow on one platform.

Keep the GDS deals and direct contracts you spent a decade earning. Replace the adapters and ticket queues holding them together.

What changes

Replace supplier adapters. Keep your contracts.

01
Keep your supply edge
Your GDS, NDC and direct content enters one offer schema.
02
Turn queues into flows
Rebooks, schedule changes and refunds run as code.
03
Keep your funnel data
Every search, offer and booking event streams to your warehouse.
Capabilities

The operating surface, end to end.

Shop
  • Multi-source flight search
  • Hotel dedupe and best-rate
  • Calendar shop
  • Branded fares
  • Loyalty-aware pricing
Book
  • Atomic multi-supplier book
  • PNR sync across operators
  • Group and corporate flows
  • Ancillary attach
  • Insurance attach
Serve
  • Disruption rebook engine
  • Refund and exchange API
  • Voucher and credit ledger
  • Customer support handoff
  • Schedule-change webhooks
Operate
  • Margin rules per product
  • Per-market FX lock
  • Auto-tax and invoicing
  • Per-supplier statements
  • Audit trail per booking
Post-booking

The mid-office, as code.

A cancelled leg can trigger a compliant rebook, a refund-or-exchange decision and a webhook in one replayable flow.

Disruption auto-rebook

A cancelled SQ leg triggers a compliant rebook on the same fare class before an agent ever opens a ticket.

Refund and exchange as API

The refund-vs-exchange decision and the money movement are one idempotent call, replayable end to end.

Schedule-change webhooks

Every status change fires a webhook into your stack, so downstream systems and the traveller stay in sync.
Keep what works

New stack. Same suppliers.

Migrate search, booking, ticketing and refunds while keeping the GDS, NDC and direct deals already in place.

Bring your own content

Plug in your existing GDS PCCs and direct deals alongside ours.

Run in parallel

Cut over market by market: no big-bang migration, no frozen roadmap.

Own the funnel

Every search, offer and booking event streams into your warehouse.
The migration

Migrate route by route.

Most sellers run the new platform beside the old one, then retire the legacy mid-office a route at a time.

  1. Connect

    Map your supply

    Point your GDS PCCs and direct deals at us; we fold them into the offer schema alongside ours.

  2. Shadow

    Run side by side

    Mirror live traffic to compare price, content and conversion before you cut over.

  3. Cut over

    Switch by market

    Move one route or region at a time. Roll back instantly if anything looks off.

  4. Retire

    Decommission legacy

    Power down the old mid-office once the new pipeline carries the volume.

After the switch

What the new stack gives you.

A phased cutover replaces per-supplier connectors and transforms with a shared offer schema and event model.

Get started
Plan a phased migration.
Related

Pairs well with

Most of our customers use two or three of these together.

Related reading

All field notes →