User Tools

Site Tools

start-woodoo

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

start-woodoo [2014/10/28 13:50]
white
start-woodoo [2014/10/28 13:52] (current)
white
Line 1: Line 1:
-====== ​Start the channel manager ======+====== ​To start the channel manager ======
 \\ \\
 To start using the [[usage-woodoo|channel manager WooDoo]] you need to, first of all, check these few things: ​ To start using the [[usage-woodoo|channel manager WooDoo]] you need to, first of all, check these few things: ​
Line 14: Line 14:
   - **Configuration of the channel**: once the channel is ready to be configured you will be able to map rooms and rates. The channel manager will download the list of rooms created on the OTA extranet and the task is simple: just map (associate) to each room type of the OTA, the related room type of WuBook. Again, for each rate created on the OTA you will have to associate a [[rate-plans-wubook|WuBook Rate Plan]] and a [[restriction-plans-wubook|WuBook Restriction Plan]].   - **Configuration of the channel**: once the channel is ready to be configured you will be able to map rooms and rates. The channel manager will download the list of rooms created on the OTA extranet and the task is simple: just map (associate) to each room type of the OTA, the related room type of WuBook. Again, for each rate created on the OTA you will have to associate a [[rate-plans-wubook|WuBook Rate Plan]] and a [[restriction-plans-wubook|WuBook Restriction Plan]].
  
-{{:mapeo-habitaciones.png?300 |}}//During the configuration process you have to map WuBook rooms to OTAs room types. Finally, to start the connectivity ​ __all downloaded rooms of the OTA have to be connected to at least one different room of WuBook extranet__. If an OTA room type is not associated to any WuBook room, the connectivity will not start to update. On the contrary, it is not necessary to associate all WuBook rooms to an OTA room and keep it only for the direct sale through the Online Reception.//​+{{:ota-mapping.png?300 |}}//During the configuration process you have to map WuBook rooms to OTAs room types. Finally, to start the connectivity ​ __all downloaded rooms of the OTA have to be connected to at least one different room of WuBook extranet__. If an OTA room type is not associated to any WuBook room, the connectivity will not start to update. On the contrary, it is not necessary to associate all WuBook rooms to an OTA room and keep it only for the direct sale through the Online Reception.//​
  
-{{ :mapeo-tarifas.png?​300|}}//​It will be also necessary to connect at least one OTA rate to a Rate Plan and a Restriction Plan on WuBook to start the connectivity. Anyway, you do not have to connect all of them. Not connected and associated rates will not be updated by the channel manager through XML. The same rate plan could be mapped to more than one rate of the portal. Same thing for the restriction plan. With **WuBook parity** we mean the default rate plan of WuBook; that rate plan created with default values used for the direct sale (Online Reception). Also, **standard restrictions** or WuBook Restrictions are the standard and default restrictions used by the Online Booking Engine for direct sale.//+{{ :restrictions-plans.png?​300|}}//​It will be also necessary to connect at least one OTA rate to a Rate Plan and a Restriction Plan on WuBook to start the connectivity. Anyway, you do not have to connect all of them. Not connected and associated rates will not be updated by the channel manager through XML. The same rate plan could be mapped to more than one rate of the portal. Same thing for the restriction plan. With **WuBook parity** we mean the default rate plan of WuBook; that rate plan created with default values used for the direct sale (Online Reception). Also, **standard restrictions** or WuBook Restrictions are the standard and default restrictions used by the Online Booking Engine for direct sale.//
start-woodoo.txt ยท Last modified: 2014/10/28 13:52 by white

These docs are no longer maintained and information within is not up to date :(

...but don't worry :), we have a new docs here: