Download the launch test pack

Download the printable launch test pack (PDF)

The pack contains 18 suggested checks and a repeatable evidence record. They are Travelgenix’s practical recommendations, not a claim that one checklist covers every business. Add cases for your suppliers, products and operating arrangements.

Set up a safe, useful test

Name the tester, the setup being tested and the person who can accept the result. Use agreed sample data and a provider-approved test environment. Stripe’s testing guide explains its simulated payment methods and outcomes; a payment test environment does not automatically make the travel booking itself a test.

Write the expected result before each check. Then record what happened, the evidence and any follow-up owner. This avoids marking a screen as passed just because it loaded.

Check the complete customer journey

Search and results

Use one common booking and one case with more detail, such as children of different ages or a specific fare requirement. Check dates, occupancy, destination and product details as they move through the journey. Include an empty-results case so the customer has a useful next step.

Travelgenix’s published widget guide describes the sequence from search to results, availability and extras, then basket and payment. Follow the actual pages in your own setup and check that back links return to the intended place.

Quotes and enquiries

Open a quote or enquiry route exactly as a customer would. Check the trip, inclusions, total and next action. If a quote can be booked, follow that supported route. If it is an enquiry, confirm the acknowledgement and the record received by the team. We recommend checking both ends because a reassuring message on screen does not prove that staff received the enquiry.

Extras, checkout and payment

Add and remove an optional extra, correct a traveller detail and review the basket. Check the currency, amount due now, balance and terms against the agreed setup. Use the payment provider’s test methods to exercise successful, declined and interrupted payments where supported.

Booking records and documents

Compare the final customer message with the supplier reference, booking status and payment status. Open the actual confirmation or document, rather than only its preview. Check that the dates, travellers, inclusions and contact route match the accepted booking.

This is a recommended consistency check. Agree the specific document requirements for the products and legal role of your business with the responsible person.

Test what happens when the normal route stops

Include a changed price, unavailable product and unclear booking response. Expedia Rapid’s Price Check documents changed and unavailable rates, while its booking recovery guidance addresses uncertain responses. Use these as examples when asking each provider how to test its own integration.

Record the customer message and the recovery owner. Before repeating an uncertain booking, use the supported process to establish whether it already exists. We recommend making this part of the launch review because a retry without that check can create a second problem.

Check mobile use and basic accessibility

Repeat the key journey on a phone-sized screen and on a real phone where available. Check that labels, totals and actions remain readable and usable. Use a keyboard to reach controls and inspect visible focus, form labels and error messages. Increase text size and check that essential content remains available.

These checks draw on W3C WAI’s Easy Checks. W3C makes clear that passing preliminary checks does not establish full accessibility. Record any barriers for a fuller review.

Check the pages you want people to find

Open your important public pages directly and inspect their titles, links and content. Ask the person responsible for search visibility to check the rendered page and indexing settings. Google documents how it crawls, renders and indexes JavaScript pages; a working page or successful test does not guarantee inclusion in search.

Keep private customer and booking records out of the public discovery checklist. The purpose is to check useful public content, not expose account pages.

Make a clear launch decision

Give each failed or incomplete check an owner. Retest after a fix and keep the new evidence. Mark an inapplicable check with a reason instead of treating it as a pass.

Our recommendation is to hold launch for unresolved issues that affect the accepted price, booking outcome, payment, essential customer information or access to private records. Agree the treatment of other issues with the responsible owner and record the decision.

After launch, repeat the relevant checks when a supplier, payment method or booking step changes. Keep the supplier onboarding worksheet alongside the results so the commercial and technical decisions remain easy to find.