Bring your supply portfolio together in Adrasis Console. Decide which products each sub-agency, API partner and sales channel can sell, set their prices and manage the resulting bookings.
B2B (business-to-business) distribution lets your agency sell travel products through other agencies and booking platforms. Adrasis connects your supply, sub-agency access, pricing and bookings in one Console.
Your agency can work with directly contracted properties, receive supply from bedbanks and channel managers, and make that portfolio available to sales partners. You decide what each sub-agency and API partner can sell and the commercial terms that apply. Supply can carry a net rate to which you add a markup, or a selling rate on which the supplier pays commission.
Sub-agencies search and book from their own Console accounts, and API partners connect their own systems. For the commercial model and terminology, see What is B2B in travel?
Manage the supply you receive and the products you publish to sales channels from the same Console. Each connection has a defined role in your distribution.
| Connection | What you manage | Sources or recipients |
|---|---|---|
| Supply | Property content, rates, inventory and restrictions | Your property contracts, channel managers and bedbanks |
| Sales | Published products, sub-agency access, selling prices and bookings | Sub-agencies, OTAs (Online Travel Agencies), metasearch engines (hotel comparison sites) and booking platforms |
See where a rate or inventory update came from and when it changed. Your team can distinguish its own entries from supplier updates and follow the price history.
Channel status shows recent updates, connection errors and missing room or rate plan matches. Your team can identify the affected connection and review the issue in the Console.
Manage your own property contracts alongside supply from bedbanks and channel managers. Keep the source of each offer clear as you build your sales portfolio.
A connected bedbank lets you sell hotels beyond the properties you manage. Adrasis asks it for current prices and rooms on each search and sends the selected stay to it for confirmation. Your markup applies to eligible prepaid offers, while pay-at-property offers keep the supplier's price. Book from New booking and follow the supplier's answer in the booking detail; cancellation follows the selected offer's terms.
The guide What is a bedbank? explains the buying and resale model.
Connect to a property's channel manager to receive rate and availability updates. Each property has one connected supply source for these updates. Channel-supplied prices are read-only in the Console; corrections are made at the supplying channel manager. This supply rule does not limit the number of channels you can sell through.
Supplier systems use different formats to exchange rates, availability and bookings. Adrasis connectors handle those formats so your team can manage the connection from the Console. See integrations for connection options, including XML (Extensible Markup Language).
Prepare a sub-agency request in Sales Network. An independent organization accepts it before you activate the relationship and open access. The sub-agency searches and books from its own Console account without building an integration.
Choose the sub-agency's currency and source market: source markets describe sale countries, destinations describe product locations. Open access to single properties, a group by destination or the whole catalog. Access granted to one sub-agency leaves the others unchanged, and sale-country restrictions are set on the rate plans.
Pricing rules by source market, sub-agency or product determine the amount the sub-agency pays. An optional floor price brings a calculated selling price up to the agreed minimum.
The sub-agency sees its payable price and its own products and bookings. Other sub-agencies' commercial terms remain private, as does the retail markup the sub-agency adds for its customers. Bookings are recorded under your organization with the sub-agency attached for reporting.
Open an account for a sub-agency with its currency, credit limit and due days. Each booking is charged to the account and each payment you receive is recorded on it, with a statement both sides can export. A booking above the available amount is refused before any room is held.
A sub-agency working with several organizations can search their available products together, with each result priced under its relationship with that organization. See the travel agencies solution for the wider agency workflow.
Manage technical partner connections in API Partners. Each partner account holds its credentials, booking references and the profiles that determine which properties it can discover.
Sales Network manages sub-agency relationships under Distribution. Use API partners to manage technical accounts for connected systems under Connectivity, on the Sales channels page. A partner profile defines a catalog audience; source markets, destinations and commercial pricing are managed separately.
Each account starts with a Default profile. Its Open properties lists your own properties open to that profile, starting as a snapshot of the accommodation properties published at that moment. Properties published later stay closed until you add them. Products you sell as a sub-agency of other Adrasis organizations are sold through the Console only; they are not listed in your online shop and cannot be published through the Partner API.
Add profiles when the same partner needs different catalogs. New profiles start empty. You can open a property to more than one profile or close it in one profile while keeping it available in others.
The API partner's payment terms decide how it pays you. Partners with on-account terms can book eligible prepaid rates, and a confirmation does not mean the partner has paid. The account's statements group these bookings by period and currency, record the payments you receive and export as CSV or Excel.
Credentials belong to the partner account and can be disabled when needed. The partner picks one of the profiles open to it, and the Default profile applies otherwise. See the API Partners documentation for account and access management.
The Distribution Partner API (application programming interface) lets partners use their own systems to access your catalog and manage bookings. Hotels, villas and apartments share one content and booking flow.
Partners can retrieve descriptions, photos, rooms, locations and policies, then keep their catalog current as content changes. Accommodation booking follows four steps.
Compare available properties and review the offers for a selected stay.
Recheck the selected offer's availability, price and cancellation policy before booking.
Submit the guest details and create the booking from the checked offer.
Review the cancellation quote and its charges before confirming a cancellation.
Partners can retrieve booking status, receive notifications when it changes and find bookings by their own references. This keeps their records aligned with bookings in Adrasis.
The API also supports transfers, tours, charter flights and packages. A package combines two or more travel services in one booking with one inclusive price. A trip groups independent bookings in one itinerary, with each booking keeping its own price, policy and status.
A demonstration catalog provides test rates and availability. Test bookings use demonstration inventory and create no charges. Your partner completes integration testing before access moves to live supply. The connection address and booking flow stay the same.
Share the developer guide with your integration team for authentication, testing and the move to live supply. For AI tools using Model Context Protocol (MCP), see the MCP server integration.
Publish availability, rates and inventory to connected metasearch engines and B2B platforms. Each connector handles the format and delivery requirements agreed with that partner.
Choose the properties to publish and review how rooms, rate plans and meal plans match the channel's catalog. The Console lists the connectors available to your organization and shows connection status.
Choose which rate plans each channel can display. For example, keep a members-only rate off public comparison sites while publishing a non-refundable rate for the same property.
Metasearch engines display your rates and direct travelers to a booking site. A booking reaches Adrasis through your direct booking flow or the separate booking integration agreed with the partner. Publishing rates to a comparison site does not itself establish that booking connection.
Agree the request limits for each partner connection before traffic grows. The terms specify the covered operations, account scope and time window.
Several operations can share one account allowance. Additional credentials or profiles do not increase that allowance. Review expected traffic with your Adrasis contact when adding a partner or planning more volume.
Insights shows observed requests, channel errors and traffic trends to support that review. Capacity changes follow the agreed connection terms.
The platform subscription is priced per organization. Included capacity, any purchased capacity and the applicable booking service fee follow your agreement. See pricing for Adrasis subscription options.
Provider fees. Suppliers, channel managers, metasearch engines and other distribution channels set their own fees and request limits. Provider fees are separate from Adrasis pricing, and an Adrasis capacity change does not change a provider's limits.
Apply for Console access, or review your supply portfolio, sales partners and integration needs with our team. You can start on Adrasis Usage Credits without paying for a plan upfront.
