Channex is a connectivity platform to help companies connect to OTA, Meta Search and other systems.
This guide is targeted mainly towards PMS but also any system that is connecting Channex to push their properties prices and availability to OTA or Meta.
IBE (Using Channex as a Channel Manager or Meta Search)
OTA (Using Channex to access Meta Channels)
CM (Use Channex to expand their distribution)
RM (To send and receive prices)
Typically a PMS would have one account with Channex which you would add multiple properties. This is the simplest approach since you only manage one account and credentials.
Because all properties are under one account be careful how you give access in your mapping screen so users cannot connect to other properties.
We suggest to have the credentials page to be admin only and include the property selector here.
At Channex we expect connecting systems to setup accounts via API.
This approach brings many benefits to you as it reduces any manual processes and simplifies mapping.
Properties API Collection https://docs.channex.io/api-v.1-documentation/hotels-collection API methods to receive list of connected Properties and manage it
Room Type API Collection https://docs.channex.io/api-v.1-documentation/room-types-collection API methods to receive list of Room Types and manage it
Rate Plans API Collection https://docs.channex.io/api-v.1-documentation/rate-plans-collection API methods to receive list of Rate Plans and manage it
You can create properties in the Channex interface and then map on your side. However it is much faster if you build to our create property methods so onboarding new properties is faster for your team.
Creating a Room Type is best practice, we would require some information regarding the name and occupancy
Creating Rate plans via API saves a lot of time since by creating you would auto map it to your internal room and rate combination.
We have a content module active in Channex, If you want to provide property images or room type images when you create it is recommended
Tax API is still not yet available, please let us now if you require this. Tax setup is required for Google and the Booking Engine.
For Channex you have 2 ways you can map from your system
Traditional screens lets you map to an account that already exists or allows you to create. This is the most flexible as it allows you to map existing properties, rooms and rates or if it is an empty account to create everything.
Once the property is chosen or created, they you must map the room types and rate plans.
As you notice the mapping screen allows you to map to existing room/rate or to create new. This allows you to be flexible to map something created in Channex.
The Reload Inventory button allows you to pull room and rate information from Channex to show what is already created. This is useful if they user wants to create in Channex then map manually.
For some PMS or systems it might be simpler to auto create and map and to keep the mapping interface to the administrator.
This method would be handy if you want to provide easy self service to your users.
Auto create property, rooms and rate plans on new accounts
Auto sync new rate plans that are created
Delete any removed rate plans (Make sure you check its deleted from Channex before deleting in PMS as it could be mapped to channel)
Provide an iframe of channels from Channex to users to self map to OTA. (Coming Soon)
At Channex we like to receive updates for Availability and Rate & Restrictions separately.
Example: To update Channex for 10 days you would send 10 days of Availability information in one message and prices and restrictions in another.
Push ARI Best Practices
Please send all changes immediately to Channex
If lots of changes try to collect into as few messages as possible for faster processing. We would say its good to batch messages per property each 30-60 seconds.
Reuse the authentication token for future messages
Authentication Token lasts 24 hours, please have way to re-auth on fail and each 24 hours
Advisable to send a daily full update each night per property
Message size should be less than 10mb
Receiving bookings will be the last stage of the connection process. You can create test bookings and see if they are received successfully.
We support credit cards in PCI secure manner and also extras in the bookings.
Use the Booking Revision Feed to get all unacknowledged bookings: https://docs.channex.io/api-v.1-documentation/bookings-collection#booking-revisions-feed
Once you successfully receive a booking you should ack the booking so it wont be provided to you again.
At Channex you may notice we have some advanced tools or methods for controlling availability or mapping to OTA. It would be better to do a basic connection first and then look to add any advanced features required later.