How to scope a B2B travel agent portal
Before choosing suppliers or drawing screens, define agent accounts, pricing, credit, booking states and the work your operations team must handle.
Trillune Engineering6 min read
A B2B travel portal lets agents sell travel products through your inventory and commercial terms. It can look like a familiar search-and-book website, but its hardest requirements sit behind the results page: who can book, whose price they see, how they pay, and what happens when a supplier cannot complete an order.
A useful scope starts with the decisions below. They determine the data model, integrations and operational tools long before they determine the visual design.
1. Define the agent account hierarchy
Decide whether you sell to individual agents, agencies, or agencies with sub-agents. Record who can invite users, place bookings, approve credit, view other users' orders, issue documents and request refunds. An agency owner and a booking clerk should not inherit the same permissions just because they share an account.
- What information is required to approve an agency?
- Can one user belong to more than one agency?
- Who owns a booking when the person who created it leaves?
- Which actions require a second approval or an audit trail?
2. Write down the commercial rules
For each product, define the supplier cost, taxes, platform markup, agency-specific markup or commission, currency conversion and any promotion. Decide which numbers the agent sees before and after confirmation. Keep a snapshot of the accepted quote: a later rule change must not rewrite the price on an existing booking.
An example: two agencies search the same flight. One pays from a wallet and receives a negotiated markup; the other books against a credit line with a different margin. The supplier offer may be identical, but the final price, approval checks and settlement records are not. If this distinction is missing from the first-release scope, it will be expensive to bolt on later.
3. Decide how money and credit move
Choose whether agents prepay, use a wallet, receive a credit limit, pay by card, or use a combination. Specify when balance is reserved, debited, released or refunded. Credit limits need a single reliable balance even when two users at the same agency book at once. Finance also needs a way to reconcile supplier charges, agent statements and payment records.
4. Separate an offer from a confirmed booking
Supplier availability and fares can change between search and checkout. Define when the portal rechecks price and availability, when the agent accepts a changed offer, and which system is allowed to say a booking is confirmed. Do not treat a successful payment as proof that a ticket or hotel voucher exists.
- Search result returned
- Offer repriced and accepted
- Payment or credit reserved
- Supplier booking requested
- Ticket or voucher issued
- Change, cancellation or refund requested
Each transition needs a visible state and a recovery path. Retrying a read is different from retrying a charge or ticketing request. When the supplier response is uncertain, an operations queue is safer than silently sending the write again.
5. Scope integrations by contract and failure behaviour
List the flight, hotel and ancillary suppliers available under your actual contracts. For each one, record authentication, search coverage, rate limits, pricing rules, booking steps, cancellations, support contacts and sandbox constraints. A logo list is not an integration plan. Normalize supplier responses into a consistent internal offer model, while retaining source references and raw replies for investigation.
6. Design the back office with the agent portal
Operations staff need to approve agencies, adjust commercial rules, review exceptions, find a booking by agent or supplier reference, and see an event timeline. Finance needs statements, credit exposure and reconciliation. Support needs to know whether a booking is pending, failed, ticketed or awaiting a human decision. These are first-release workflows, not optional administration screens.
What belongs in the first release?
Choose one agent hierarchy, one payment or credit model, and a small set of contracted suppliers. Prove a complete path from agency approval through booking and after-sales support. Then expand products and commercial rules. This reduces the risk of launching a wide search interface whose bookings cannot be settled or supported.
Before commissioning development, prepare a short decision record covering agent roles, product and supplier scope, pricing ownership, payment and credit rules, booking states, exceptions and reporting. That document gives engineering, operations and finance a shared definition of the portal you actually need.