Expedia Monitoring Page messages

Below are a list of common errors and their solutions/information on what to do next; 

Invalid credit card / unable to send card details

• Click on view and check payment type – e.g. Amex. Site do not accept AMEX but this is set as a valid Credit Card with the channel so all reservations with that guarantee will come in as warnings. Hotel need to contact their account manager and remove AMEX from accepted card list. 

Rate plan: null not converted. ROOMLYNXBB applied: null Room type: Standard Double not converted. DOUBLE applied.: Standard Double

• Warning indicates that the conversions are not correct. Check conversions against channel details that they are correct.​

Card code: MasterCard not converted. VISA applied.: MasterCard

• Warning indicates that the conversions are not correct. Check conversions details and ensure that they are correct.​

Unable to cancel reservation - There is nothing to be cancelled​

• This is because the original reservation for the cancellation could not be found. This will either be because the original reservation has already been cancelled manually by the hotel or because it was made prior to the interface being switched on and the reservation not having its CRS reference completed. Advise site to check and if the reservation is still active and cancel manually.

Error Code: 10 org.jboss.ws.core.WSTimeoutException: Timeout Exceeded  ​Serevity High

• These errors usually occur when the channel has been ‘temporarily unavailable’ or when they have had an outage. These errors therefore can be cleared. To establish whether the channel is still down check the last timestamp of the processed (successful) and it the timestamp is newer than the error then there is no longer an outage. Resync to be sent only for dates specified in update error.

<Warning code="7014">Inventory date 2013-11-09; Room Type ID 354210; Rate Plan ID 2077893; Close out on last active standalone or corporate rate plan outside of Y with remaining base availability  Ref=[02812012-47bb-11e3-81ad-d3de3c803013] </Warning>

• This would be expected these errors should be cleared down.