Adrasis™

DistributionReceive supplier data

Channel managers

A channel manager sends a hotel's prices and available room counts to connected sales channels. Adrasis can receive supply information from the hotel through this connection.

Connection scope

  • Supply information: Hotel prices and room details are received from the channel manager.
  • Updates: Price and sales-condition changes sent by the hotel are transmitted through the relevant connection.
  • Bookings: Bookings received through the connection are linked to the relevant records using property, room and rate-plan mappings.

You can review the information in the Console. Corrections to prices sent by the supplier must be made in the source system.

Which channel managers are supported

Adrasis connects to the most well-known channel managers in the market, both global players and partners that lead in their regional markets. New partners are added through the same operator workflow.

Open Connectivity, then Supply sources and Channel managers to see the channel managers available to your organization.

What you do as an operator

For each channel manager you bring online:

  1. Activate the connector for your organization.
  2. Bind a property through the property's Channels tab. Enter the channel manager's identifier for the property.
  3. Map rooms, rate plans, meal plans, and attributes between your catalog and the partner's vocabulary. The mapping page shows gaps and helps you close them.
  4. Watch the connector status for the property, last successful message, error rates, anything in retry.

Adrasis manages connection authentication, retries and data-format conversion. It prevents a repeated message from applying the same change twice.

One channel per property

A property carries one connected channel at a time, the single source for its rates and availability. This keeps source information unambiguous: two live channels writing the same rate and inventory cells would race, and you could not tell which one is authoritative.

To move a property to a different channel, disconnect the current one first, then connect the new one. The Console blocks a second connection while one is already live and prompts you to disconnect first.

Channel-managed connectors

Some connectors run in channel-managed mode: the partner addresses your rooms and rate plans by their Adrasis identifiers, so the room and rate-plan mapping step does not apply. For those, you manage the connection and data flow from the Connectivity page rather than the mapping screen.

A channel manager prices and restricts a room and a rate together, so these connectors work with shared rate plans. Each rate code identifies a separate plan within the property connection. Two breakfast-inclusive rates with different codes stay separate, even if their meal and cancellation terms match. The same plan can be linked to every room the channel sells it in.

A stop-sale, minimum stay, child price or extra-adult amount sent for one room and one rate becomes a room exception; other rooms keep their own terms. Change the rooms of a channel-managed rate plan on Connectivity. Correct its prices in the source channel manager. Prices are stored as sent, for each adult count the channel manager names; a single room price is stored for every adult count the room takes, and the plan's ratios are not applied.

Some channel managers read the number in a rate code as the adult count. For them, each plan is offered as one code per adult count, up to the room's adult limit, and one code for a child's price where a child fits the room. Some channel managers also do not accept a hyphen in a rate code: Console refuses such a code before anything is written and asks for an underscore or digits instead.

Prices are kept per night. Some channel managers price a whole stay by its arrival date and length, for example 360 for three nights from 10 May. From such a message the one night price is stored as the nightly price; a price for a longer stay is not stored, and that stay sells at the sum of its nightly prices. A pattern of allowed stay lengths sent for an arrival date is applied: if it allows only two night stays from 10 May, a one or three night stay from that date is not sold.

Incoming price currency

Agree one currency for the property with the supplier and set the property to that currency. If Hotel Sunrise sends TRY prices, its property currency is TRY and every incoming rate plan uses TRY. A received currency mismatch is rejected; it neither changes the property currency nor creates a foreign-currency plan. For independently authored EUR and TRY prices without an incoming channel-manager connection, use static contract plans.

What this means for your product record

Every inbound change from a channel-manager partner lands in the product record, tagged with the source. As an operator you can:

  • Trace a rate or inventory cell back to the partner that wrote it.
  • See, on the cell history, when the partner last touched it and what it was before.
  • Inspect channel-supplied prices in read-only calendars. Correct a price at the supplying channel manager; manual Console and Adrasis AI Operator price edits are blocked while the source connection exists, including when transport is paused.
  • Read inventory, stop sales and stay rules the same way. The Rates and Restrictions pages show Connected to with the channel manager's name and View connection, and they offer no manual change. Change these values in the channel manager too.

Source information identifies which supplier provided each value.

Adding a new channel manager

When a new channel manager partnership is available, you activate it for your organization, save the credentials, bind your properties and review the mapping, the same workflow as any other channel.

Where to next