A property connection identifies the external system that exchanges information with your property. For example, you can receive prices and available room counts from a hotel's channel manager. Mappings identify which property, room and rate plan that information belongs to.
Connections and mappings
| Concept | Question it answers |
|---|---|
| Connection | Which system exchanges information with this property? |
| Mapping | Which of our records matches a code from that system? |
Open the property's Connectivity tab to review its connections. Required details vary by connection: access credentials, the property's source code, and room or rate-plan mappings.
Connections have different requirements. Some require individual room and rate-plan mappings; others do not. Follow the fields and notices for the selected connection.
Review connection codes
In the connection details, check Hotel code, Room code and Plan code against the codes used by the connected system. For example, if the channel manager sends room code DBL, use that code for the matching double room. Changing a code does not change the room's name or capacity.
For connections that support it, How the price spreads over the guests states how a room price from the source applies to different guest counts. Use the setting agreed with the source, and review any notice about the linked rate plans. The Console stores the source's prices as sent, for each adult count, and applies no ratio to them. This setting does not turn a source price into a manually editable Console price.
A supported connection can be set up for a property without a shared catalog link. Review its own rooms and connection codes. Creating the connection does not add the property to the shared catalog or establish that a channel has accepted it.
Information received and sent
- Price received from a supplier: The supplier's room and rate-plan codes are matched to the relevant records.
- Price sent to a sales channel: The codes expected by that channel are used.
- Incoming booking: The property, room and rate-plan codes in the booking are matched to their records.
Prices and bookings can travel in opposite directions. When checking a connection, identify the information you are following rather than just calling it incoming or outgoing.
What should you check when something is wrong?
| Problem | Check |
|---|---|
| The system cannot connect | Whether access credentials are valid and what the connection error says. |
| A room or rate plan cannot be found | Whether the source code matches the correct record. |
| An expected price is missing | Whether the supplier sent it, the connection status and sales conditions. |
Supplier prices are corrected at their source. You can view prices received from a channel manager in the Console. Changes must be made in the system that sends those prices.