Channel manager
The channel manager setting tells Wink which external system owns the rates and availability of a property. To open it, click Channels > Channel manager from the main nav bar. The page has two sections: Property code and Select your channel manager.
You need the integrations write permission on the property to save a change. If you do not have it, the save is refused.
Choose your channel manager
Section titled “Choose your channel manager”- Open the Channel manager dropdown and pick your provider.
- Click
Updateand confirm the dialog (Confirm this is your channel manager).
Update stays disabled until your choice differs from the saved one. The field is required, so you cannot clear it. A page with no entries shows No channel managers are available to choose from yet.
Two entries are not providers:
- None lets Wink manage your rates directly. This is the value a property has until you choose another one.
- Other is how you tell Wink about a channel manager it should integrate with. See If your provider is not listed.
Property code
Section titled “Property code”Your provider usually asks for a code to start connecting the property. Click the copy icon next to Hotel ID to copy it. The value follows the provider you have selected in the dropdown, even before you save:
- For Yanolja (formerly Ezee), the code is the property’s hotel code. It is empty if the property has no hotel code.
- For every other provider, the code is the property’s Wink ID.
Enter this code in your provider’s system as the property or hotel identifier. Wink looks the property up by this value whenever the provider sends rates or availability.
Selected, configured and connected
Section titled “Selected, configured and connected”These are three different states, and the portal only sets the first one.
| State | What it means | Who sets it |
|---|---|---|
| Selected | The provider is saved on the property. | You, on this page. |
| Configured | The provider’s side has your property code and credentials, and its inventory is mapped to your rooms and rate plans. | You and the provider, outside Wink. |
| Connection verified | The provider has successfully called Wink for this property. | Nothing in this page. |
Saving only stores your choice. It does not contact the provider, test credentials, check mapping or show a connection status, and nothing on this page tells you that a connection works. Check your provider’s own dashboard to confirm that it reaches Wink.
What selecting a provider does change:
- Rates and availability the provider sends for this property are recorded with that provider as their source.
- Several integrations (for example SiteMinder, Yanolja, TravelClick, D-Edge and Omnibees) check which provider is selected before they accept or return data for a property, so a property pointing at a different provider is turned away.
- New bookings are routed to the provider that supplied the rate, not to whichever provider is selected at that moment. Changing providers mid-stream does not move bookings already tied to the old one.
Some integrations, Channex among them, answer a provider’s connection test with only whether the property exists in Wink. A passing test from the provider therefore proves the property code is right, not that this page is set to that provider.
Supported providers
Section titled “Supported providers”The dropdown is built from two sources: a fixed list of built-in providers, and any active channel manager, property management system (PMS) or central reservation system (CRS) registered on Wink. The second group changes over time, so this page does not list it. Appearing in the dropdown does not by itself mean an integration exists.
Integrations that exist in the platform code:
| Dropdown entry | Notes |
|---|---|
| SiteMinder | Direct integration. |
| RateGain | Direct integration. Synxis properties are handled by the same integration. |
| Synxis | Handled by the RateGain integration. |
| CloudBeds / MyAllocator | Direct integration. |
| Travelclick | Direct integration. |
| d-edge | Direct integration. |
| Rate Tiger | Direct integration. |
| Omnibees | Direct integration. |
| Yanolja (formerly Ezee) | Direct integration. Uses the hotel code. |
| Channex | Direct integration. |
| Exely | Direct integration. |
Built-in entries with no integration in the platform code: YieldPlanet, Booking Jini and Comanche. Selecting one saves the choice, but nothing in Wink sends or receives data for it.
Providers registered on Wink as a channel manager, PMS or CRS can use Wink’s own channel manager API to read your property and rooms, update rates and read bookings, and can receive a notification for each new booking at an endpoint they register. They only see properties where they are the selected provider.
Direct and proxied providers
Section titled “Direct and proxied providers”A direct provider has its own integration with Wink. The table above lists them.
A proxied provider is a PMS that reaches Wink through another platform, such as Channex. Wink has a direct integration with Channex, so a PMS that connects through it sends its rates and availability to Wink via Channex. Which PMS vendors work that way is not defined in the platform code. Ask your PMS vendor, or the Wink team, whether your system connects through Channex and which entry to select.
If your provider is not listed
Section titled “If your provider is not listed”- Choose Other and save, so Wink knows you use a channel manager it does not support yet. Choose None instead if you want to keep managing rates in Wink.
- Send feedback with the button in the bottom right corner of the portal and name your provider.
Wink can only add an integration for a system that can call Wink’s APIs and receive bookings. Developers building one can start from Add your channel manager.
