← Glossary

Go-live

Go-live is the point at which a new booking platform starts taking real bookings from customers, and go-live time is the elapsed time from a signed contract to that first live booking flow.

How a project reaches go-live

A travel platform project usually runs through discovery, configuration, integration and testing before go-live. Configuration covers branding, products, mark-ups and users. Integration connects suppliers, payment gateways, the airline PSS or GDS, and the loyalty system if there is one.

Testing includes end-to-end bookings in a sandbox, payment and refund flows, and certification with any suppliers that require it. Many projects then run a soft launch, with limited traffic or staff-only bookings, before the full launch.

Why go-live time matters

Every month before go-live is a month of cost with no revenue, and long projects lose sponsors and momentum. Go-live time depends mostly on how much is configured rather than built, how many custom integrations are needed, and how fast the client's own teams supply content, contracts and approvals. Buyers should ask vendors exactly what a quoted timeline includes and which tasks sit on the buyer's side.

Example

An airline signs for a holidays programme. The first weeks cover branding and hotel content, the middle weeks PSS and payment integration, and the final weeks testing and a staff-only soft launch, followed by a public go-live. The vendor's configuration was ready early; the airline's own hotel contracts and sign-offs set the real pace.

Related terms

Where this fits in altovo

altovo publishes one figure per offer: full airline holiday programmes go live in under 8 weeks, stopover programmes in 4 to 6 weeks, and self-serve travel agent accounts in under 10 days. Our process sets out the steps, and altovo for airlines and altovo for agents describe each offer.

Talk to sales