For consolidators, host agencies, and travel groups, the biggest operational challenge is rarely the inventory. It is the distribution. Getting Amadeus GDS content in front of hundreds or thousands of sub-agents, each with their own pricing agreements, credit limits, and booking workflows, requires a level of technical infrastructure that a standard B2B portal cannot provide. That is where the Amadeus agent network portal model comes in. Also known as a B2B2B platform, it is a multi-tier distribution system where a primary organisation at the top of the network supplies inventory and booking capability to a layer of sub-agents beneath them, each of whom operates their own separate booking environment within the same platform. At Flight Terminus, we build Amadeus agent network portals for consolidators, franchise travel groups, host agencies, and travel technology companies that need to manage agent networks at scale. This blog covers what a B2B2B platform is, how it differs from a standard B2B portal, what it needs to contain, and how to build one that actually holds up in production.
An Amadeus agent network portal is a multi-tier travel booking platform where one primary organisation, the consolidator or host agency, operates the top tier and supplies booking access to a network of sub-agents beneath them. Each sub-agent has their own login environment, their own pricing, and often their own branded interface, but all bookings flow through the same centralised Amadeus GDS connection managed by the primary organisation.
The B2B2B label describes this structure precisely. The first B is the primary organisation. The second B is the sub-agent. The third B is the sub-agent's client, which may be another agency, a corporate account, or an individual traveller.
This is architecturally more complex than a standard B2B portal. A B2B portal serves one organisation and its own agents. An Amadeus agent network portal serves an entire ecosystem of separate businesses that all operate under the umbrella of a single platform, each with their own commercial relationships, credit arrangements, and booking histories.
Tier | Who They Are | What They Do on the Platform |
Tier 1: Super Admin | Consolidator, host agency, or travel group | Manages the entire network, sets global pricing rules, assigns credit, monitors all bookings, and controls platform configuration |
Tier 2: Sub-Agent Admin | Independent travel agency or franchisee | Manages their own agents, sets sub-agent-level markups, views their own bookings and financial performance |
Tier 3: Booking Agent | Individual agent within a sub-agency | Searches fares, makes bookings, views their own booking history and commission |
Some networks require four or five tiers, for example where a regional manager sits between the super admin and the sub-agent admin. Flight Terminus builds the hierarchy to match the actual structure of the organisation, not a rigid template. For networks that also want a consumer-facing booking layer, see our B2C flight booking portal page for how a public booking front end can sit alongside the agent network.
The Amadeus agent network portal model is built for organisations that sit above individual agents in the travel distribution chain. If your business supplies booking access, inventory, or technology to other travel businesses, you need this model.
A consolidator holds negotiated fares from Amadeus-connected airlines and distributes them to a network of retail sub-agents who could not access those fares on their own. An Amadeus agent network portal gives the consolidator a single platform to manage every sub-agent relationship, including their pricing tier, credit limit, booking volume, and commission entitlement, while each sub-agent sees only their own environment.
Host agencies operate an IATA or ARC accreditation on behalf of affiliated independent travel agents. An agent network portal gives each affiliated agent their own booking environment under the host's Amadeus connection, with financial controls that protect the host from credit exposure.
Franchise travel groups need to supply all franchisee locations with consistent access to Amadeus inventory, while allowing each franchisee to operate as an independent business with their own local branding, markups, and reporting. The agent network portal provides this without requiring each franchisee to maintain their own GDS contract.
Technology companies that have built a travel platform and want to offer it as a licensed product to multiple agency clients. The B2B2B architecture allows the technology company to be the platform operator at Tier 1, with each agency client operating as a Tier 2 admin and their own agents operating at Tier 3. See our travel aggregator portal development page for how technology companies build scalable multi-client platforms.
Large travel groups with multiple regional offices or subsidiary brands often need to consolidate their Amadeus GDS access into a single platform while maintaining separate reporting and pricing for each region or brand. The agent network portal provides centralised control with decentralised operations.
Airlines operating a preferred agent programme sometimes build an Amadeus agent network portal to give their preferred agents priority access to specific fares, seat blocks, or promotional inventory. Tourism boards use a similar model to support inbound travel agencies selling their destination.
Building an Amadeus agent network portal that works in production requires a specific set of features that go well beyond what a standard B2B portal provides. The following breakdown covers the critical components Flight Terminus builds into every B2B2B platform.
The Amadeus GDS connection at the core of an Amadeus agent network portal is shared across the entire agent network. The platform holds one Amadeus API connection at the super admin level, and all sub-agents access inventory through that single connection. This is what makes the model commercially viable for consolidators: one GDS agreement, one set of negotiated fares, distributed to an unlimited number of sub-agents.
For networks that need content beyond the Amadeus GDS, Flight Terminus integrates direct airline APIs and LCC content alongside Amadeus inventory. All content sources appear in a single unified search result under the platform's brand. Visit our AQC flight API integration solution page and our Amadeus integration page for the full scope of content integration options.
When hundreds of sub-agents are searching simultaneously, the platform's API layer must manage Amadeus request volume efficiently. Flight Terminus builds an intelligent caching and rate management layer between the platform and the Amadeus for Developers API that reduces redundant calls, manages quota allocation, and maintains fast search response times even under peak load.
The pricing layer of an Amadeus agent network portal is where the commercial model of the entire distribution network lives. Getting it right from the architecture stage is critical. Retrofitting pricing logic into a platform that was not designed for it is one of the most common and costly mistakes in B2B2B travel platform development.
Markup stacking means that the super admin's margin and the sub-agent's margin are each applied separately at the correct stage of the pricing calculation, without either tier being able to see the other's margin.
Stage | Who Controls It | What Happens |
1. Base Fare | Amadeus GDS | Live fare retrieved from Amadeus at net cost to the consolidator |
2. Consolidator Margin | Super Admin | Super admin markup applied. This becomes the net fare visible to sub-agents |
3. Sub-Agent Margin | Sub-Agent Admin | Sub-agent adds their own markup on top of the consolidator net fare |
4. Customer Price | End Traveller | Customer sees the final price inclusive of both markup layers |
Neither tier can see the other's margin. Sub-agents see only the net fare set by the consolidator, not the original Amadeus base fare. Travellers see only the final customer price, not either markup layer. This protects the commercial confidentiality of every party in the chain.
Super Admin Pricing Controls | Sub-Agent Pricing Controls |
Global network markup applicable to all sub-agents | Their own additional markup on top of the consolidator net fare |
Per-sub-agent pricing overrides for preferred partners | Route-specific markups within their own booking environment |
Route-level and airline-level margin configuration | Promotional pricing tools for their own customer campaigns |
Minimum and maximum markup limits to control sub-agent behaviour | Currency selection for their local market |
Network-wide promotional campaigns and flash sale pricing | Their own loyalty or repeat-customer discount tools |
Financial risk management is one of the most important functions of an Amadeus agent network portal. When sub-agents are booking against your Amadeus GDS account, every booking creates a financial obligation. Without proper credit controls, a sub-agent can generate significant liability before the platform operator is aware of the exposure.
A B2B2B platform is only as valuable as the agent network that uses it. The speed and ease of onboarding new sub-agents directly affects how quickly your network grows and how much friction your team faces in day-to-day operations. Flight Terminus builds sub-agent onboarding workflows that are structured, auditable, and scalable.
Flight Terminus builds onboarding flows that scale from 10 sub-agents to 10,000.
The architecture of an Amadeus agent network portal is more complex than a standard travel portal because it needs to support multiple isolated user environments, a shared inventory layer, and a financial management system, all within a single platform that performs reliably at scale.
For businesses integrating the agent network portal with external tools such as CRMs, accounting systems, or reporting platforms, see our integration services page for the full scope of third-party connectivity Flight Terminus delivers.
Travel businesses evaluating platform options often find the distinctions between B2B, B2B2B, and white label portal models confusing. The table below clarifies the differences so you can identify which model, or which combination of models, fits your business.
Dimension | B2B Portal | B2B2B Agent Network Portal | White Label Portal |
Who uses it | Your own internal agents | Your sub-agents, each running their own agency | Any audience you define, under your brand |
Tiers | Two (admin and agent) | Three or more (you, sub-admin, sub-agent) | One to three depending on model |
Branding | Single brand throughout | Per-sub-agent branding within one platform | Your brand only, no sub-agent customisation unless layered |
Pricing | One markup layer | Stacked markup layers per tier | One markup layer typically, customisable per market |
Credit management | Internal only | Sub-agent credit limits and wallets | Typically single-tier payment |
Primary use case | Internal agency operations | Consolidator or host agency distribution | OTA, bank, loyalty, or corporate portal |
Many organisations combine these models. A consolidator might operate a B2B2B agent network portal at the core of their business and layer a white label front end for their premium sub-agents. Flight Terminus designs architectures that support this kind of layering from the start. See our white label flight booking portal page for how white label sits alongside the agent network model.
One of the core operational benefits of a centralised Amadeus agent network portal is the visibility it gives the platform operator over the entire distribution network. Without a purpose-built reporting layer, super admins are left reconciling data from multiple sub-agent systems, which is time-consuming and error-prone. Flight Terminus builds reporting that makes network management straightforward.
An Amadeus agent network portal built exclusively on Amadeus GDS content will cover most full-service carrier inventory globally, but it will have gaps in LCC and regional airline coverage. Flight Terminus builds agent network portals that aggregate content from multiple sources and present it in a unified interface for all sub-agents.
All content sources are normalised into a single format before reaching the sub-agent booking interface. Sub-agents see one unified search result with consistent fare presentation regardless of the underlying source. See our travel aggregator portal development page for how Flight Terminus builds multi-source aggregation into network portal architectures.
Payment management in an Amadeus agent network portal operates at two distinct levels: the payment flow between sub-agents and the platform operator, and the payment flow between the platform and Amadeus for ticket settlement. Both need to be handled correctly for the platform to function without financial risk.
An Amadeus agent network portal is one of the more complex travel platform builds due to the multi-tier architecture, credit management requirements, and per-sub-agent branding capabilities. Below is a general delivery framework based on Flight Terminus project experience.
Platform Scope | Estimated Timeline | Typical Network Size |
Standard B2B2B Portal (3 tiers, flights) | 12 to 16 weeks | Up to 100 sub-agents |
Multi-Product B2B2B (flights, hotels, cars) | 16 to 20 weeks | Up to 500 sub-agents |
Multi-Brand B2B2B with per-sub-agent white label | 20 to 24 weeks | Up to 1,000 sub-agents |
Enterprise Network Portal with BI and API layer | 24 to 32 weeks | Unlimited sub-agents |
Timelines assume that Amadeus API credentials, brand guidelines, and commercial terms for the sub-agent pricing structure are confirmed within the first two weeks of the project. Delays in these inputs extend the delivery schedule.
Flight Terminus delivers in phases. A core platform with essential booking, markup, and credit management features is delivered first and tested with a pilot group of sub-agents. Additional features such as advanced reporting, white label sub-agent branding, and API extensions are added in subsequent phases. This approach reduces risk and gets the platform generating revenue faster. For a detailed project estimate, contact us via the Flight Terminus contact page.
Frequently Asked Questions
A B2B portal serves your own internal agents and operates within a single organisation. A B2B2B Amadeus agent network portal serves external sub-agents who are separate businesses, each with their own accounts, pricing, credit limits, and branding. The complexity of managing multiple independent businesses within one platform is what distinguishes the two models. See our custom B2B flight booking solution page for a comparison of the two approaches.
Yes. Flight Terminus builds per-sub-agent branding into the Amadeus agent network portal architecture. Each sub-agent can have their own logo, colour scheme, domain or subdomain, and branded email confirmations. This is managed centrally by the super admin and applied dynamically per sub-agent login. See our white label flight booking portal page for more on white label sub-agent environments.
Yes. The platform supports markup stacking, where the super admin's margin is applied first and the sub-agent then applies their own additional margin on top. Neither tier can see the other's margin. The system handles the calculation automatically at the point of fare display.
Flight Terminus builds multi-currency credit management into the platform from the architecture stage. Each sub-agent can hold their credit balance or limit in their local currency, with the platform converting to the GDS settlement currency transparently at the time of booking.
Yes. Access to Amadeus GDS content requires an active Amadeus agreement. For consolidators, this typically means a direct Amadeus accreditation agreement that covers your network. Flight Terminus can advise on the correct structure based on your geography and network size. In some cases, we provide API access under our own Amadeus relationship during the initial platform build.
Flight Terminus builds agent network portals on cloud infrastructure with auto-scaling, so there is no hard cap on the number of sub-agents the platform can support. We have designed network portals for clients with plans to onboard several thousand sub-agents, and the architecture scales to accommodate this without platform rebuilds.
Flight Terminus provides ongoing support covering Amadeus API updates, bug fixes, performance monitoring, and feature additions. We also offer network growth consulting, helping platform operators optimise their sub-agent onboarding, pricing structure, and credit management as the network scales. Contact our team via the Flight Terminus contact page to discuss support options.