GUIDE
5-minute read
Last checked
19 October 2026
IN SHORT
Test the agent and administrator views of the same booking.
Include access checks, changed offers and interrupted responses.
Record demonstrated behaviour and unresolved gaps before deciding.
A B2B travel portal has to work for the agent making a sale and the team supporting that agent. Put both people in the demonstration. Follow the same booking through their screens, because a convincing search result tells you little about who can change the price, retrieve documents or resolve a problem afterwards.
Prepare your agency model before looking at software. An operator distributing its own product has different requirements from a homeworking network giving members access to suppliers. Use fictional customer records in an approved test environment and agree the scenarios with the provider. The checks below are buying recommendations, not a claim that every portal includes every function.
Give each test account a specific job
Ask the provider to create the roles your business needs. An agency owner might manage colleagues while a consultant makes bookings and an accounts user checks balances. Write down the permitted actions for each role before signing in. Include who can approve a new agency, change its terms and remove access when someone leaves.
With the provider’s agreement, test whether one agency can open another agency’s fictional booking through the normal interface. Check document downloads and reports as well as the booking screen. Then remove a test user’s access and follow the provider’s process for ending their access to the service. A role name on a settings screen is only the beginning of the evidence.
Trace the price through each view
Bring a rate arrangement that reflects how you sell. Ask to see the supplier amount, the partner’s buying price and any customer-facing selling price, where those apply. Have the presenter explain the currency and where markups or commissions enter the calculation. Keep a record of which amounts each role can see.
Our B2B travel portal page describes member dashboards, net or gross pricing and membership levels managed in Travelify. Those are starting points for a demonstration. Ask us to apply your intended pricing arrangement to two fictional partner accounts and show the resulting offers. Confirm how an authorised price override is recorded and what happens when an agent’s terms change.
For hotels, check that the offers concern the same property before comparing prices. GIATA MultiCodes links supplier property codes to a common hotel identifier. Room type, meal basis and cancellation conditions still need separate attention. Our hotel mapping explanation gives you the terminology to use when a supplier’s hotel name differs from another’s.
Refresh the offer before committing
Run a successful booking through the stages the proposed supplier connection uses. In Travelgate’s documented hotel flow, Quote checks the selected rate before Book and returns current pricing and cancellation conditions. That is a named technical example, not a promise that every connection uses those labels. Ask your provider to identify its equivalent checks.
Next, request a test where the selected price changes or the offer becomes unavailable. Record what the agent sees and whether a fresh decision is needed before continuing. Once a booking succeeds, find both the portal reference and the supplier reference. Someone supporting the sale needs to connect those records without reconstructing the whole conversation.
Follow an uncertain response into support
An interrupted response deserves its own demonstration. Ask how the team establishes whether the supplier created a booking before anyone tries again. The agent needs a clear status and a named route for help. Your operating procedure should explain who investigates and which action is safe next.
Stripe’s idempotency documentation provides an example of recognising repeated requests so an operation is not accidentally performed twice. Ask whether the actual travel connection supports that behaviour and under which conditions. Separately, Expedia Group’s Rapid Notifications API documents messages about booking events and changes. Where your portal receives such messages, test who sees an update requiring action and how they record its resolution.
Take documents and finance through an amendment
Use a fictional booking that has already produced customer documents, then change an agreed detail in the test environment. Ask the consultant to find the current document and the administrator to identify what changed. Check whether an old download remains accessible and how staff distinguish it from the replacement. Agree who contacts the customer when a change needs explaining.
Bring finance into this part of the demonstration. Depending on your model, they may need to inspect commission, agent credit or supplier settlement records. Record any export or separate system involved and give the handover an owner. If credit is part of your arrangement, ask what happens when an agency reaches its agreed limit and which staff can authorise an exception.
Agree the limits before opening access
Ask the provider to document operating limits and the recovery procedure for each relevant connection. Stripe’s rate-limit guidance distinguishes overall account limits from endpoint limits and simultaneous requests. Use that distinction to ask precise questions about your portal, rather than borrowing Stripe’s numbers. Any demand testing should be planned with the provider.
Keep an evidence sheet for each essential requirement: the scenario, expected result, demonstrated result and unresolved work. Give every gap an owner and distinguish available functions from proposed configuration or development. When discussing Travelgenix for B2B travel companies, bring that sheet to the meeting. The next decision should be based on the work your agents can complete.
Five checks for your next demonstration
Create a fictional agency with distinct consultant, manager and accounts roles. Record the actions each is allowed to perform.
Follow one price through supplier, partner and customer views. Check the relevant currency, markup and conditions.
Run a successful booking and an uncertain response. Require a clear process for checking status before a retry.
Amend a test booking after documents exist. Follow the consequences into the agent’s screen and finance’s records.
Send the provider your evidence sheet after the demonstration. Ask for an owner and resolution date for each essential gap.
Check your own position
This guide provides practical editorial recommendations. Check the supplier terms and official guidance relevant to your business before acting.
Sources
The official pages this guide draws on. Rules and fees change, so check the latest version.
QUESTIONS
Common questions
Should we test only the agent screen?
Our recommendation is to follow the same booking through the agent, administrator and relevant financial workflow so handover gaps are visible.
Can we assume all suppliers behave alike?
Use each provider’s documented booking, notification and retry rules. The examples in this guide are scoped to the sources named.
What should go in the acceptance sheet?
Record the requirement, test scenario, expected and actual results, evidence, owner and next action. Mark essential unresolved gaps clearly.
HOW TRAVELGENIX HELPS
Bring your own booking scenarios and requirements to a Travelgenix demonstration. Use the checks in this guide to record what you see and any questions to resolve.