Expedia Errors during and after connection

Follow

This article will help you understand the reason for the errors you may encounter during or after connecting Expedia to myfrontdesk and how to solve them.

If you can't find the problem you're facing in this list, please contact our Support Team at support@cloudbeds.com. You can also reach out to your Expedia Market Manager if you have questions about the Expedia extranet.

If you are not connected to Expedia yet, please find the connection guide here: How to Connect Expedia with myfrontdesk

How to View Errors affecting your channels

Step 1 - Navigate to the Channel Distribution Settings

1. Click on Manage > Channels under Channel Distribution Section.

2. You will see a red  'Action Needed' message box. Click on "Click here to view details".

Step 2 - Identifying the Errors

A new window will appear to the right of your screen, detailing the errors affecting your channels.

In the example below you will see that this property has errors with Expedia and Airbnb.

The Expedia error : "At least one rate is not within the rate verification threshold, set by Expedia. Please contact your Expedia account manager to lower the threshold."

It also presents information on how to fix it. The error is detailing the Room and Date that need adjustments. In this example you should check the settings for for the Room 'Quarto Porto' on 2020-07-26.

Please continue reading this guide to learn how to fix the most common Expedia Errors.

Errors during the connection process

The login details you provided are incorrect. Please update your channel details

This error occurs due to one of two reasons that we will cover below.

Reason 1: The Channel Manager myallocator is no longer connected to your Expedia Extranet

PROBLEM:

If myallocator (channel manager by Cloudbeds/myfrontdesk) is no longer connected as your channel manager in the Expedia Extranet, this error will be displayed.  

SOLUTION:

Reauthorize myallocator as your channel manager in the Expedia Extranet. Check out this article for further information

Once finished, myallocator will authorize the connection and email you when it's ready to use again.

Reason 2: The Channel Manager Myallocator is connected to Expedia, but your Expedia API password has expired

PROBLEM:

In certain cases, Expedia will expire your special API password for connecting with myallocator.  When this happens, the error above will also occur.  The API password is typically expired due to inactivity.  If you connect myallocator to Expedia, but don't finish the connection, your API password will expire and must be reset.

SOLUTION:

Contact Expedia and ask for the API password to be reset. To solve this problem, please follow the steps below

  1. Email rollout@expedia.com
  2. Copy support@myallocator.com
  3. Ask Expedia the following:

Hello Expedia,

This is [name] with [Property].  My Expedia Property ID is [expediapropertyid].  The API password provided to myallocator is no longer working.  Can you please reset the API password and reply all with the new API password.

Thank you,

[Property Name]

Once Expedia replies with the new API password, we will update our system and the connection will work again.

Why isn't Venere (Expedia Easy Manage) supported in myallocator?

Expedia informed us in 2012 that they would migrate everyone to their full Expedia interface.  For that reason, we do not support the Venere (Expedia Easy Manage) contracts or interface.  

Please contact your Expedia account manager with any further questions.

Errors after the connection process

Why don't prices change in Expedia if the Availability is 0?

For Expedia, they ignore the rate that we send if the availability is 0. 

This is because the room is not available for booking, so Expedia simply ignores the rate. If the room ever becomes available again (Availability >=1), the updated rate will be reflected on Expedia.

Currency setting doesn't match the channel's currency setting

The currency set on our system must match the currency that you have configured on Expedia's extranet. Please confirm that both currencies are matching.

Errors during Full Refresh

Failed: 2003: At least one rate is not within the rate verification threshold, set by Expedia

PROBLEM:

Many channels implement rules (thresholds) for values that are set in their extranet.  This is so that they can ensure the information presented to potential guests is accurate.

In most cases, the limitation is on the low side of the price, meaning it believes you have set a rate that is too low - The error will appear when you submit a Full Refresh.

Some examples of threshold data are:

  • Minimum Length of Stay settings
    • Example: MinLos of 30 nights will typically be rejected
  • Rates
    • Example: Extremely low or high rates may be rejected

These limits are set directly in your channel account (it's set by your channel account manager).  These are NOT limitations coming from myallocator (channel manager by Cloudbeds)

SOLUTION:

When this occurs, there are two solutions:

  1. Raise the rates, or contact your Expedia account manager to remove the pricing limitation. 
  2. Contact your account manager to have them adjust these thresholds.    
  • Until this is done, Cloudbeds team cannot adjust your inventory on Expedia, which may cause overbookings, incorrect pricing and availability, etc.
  • This threshold can be removed only by your Expedia account manager
Does not currently auto-adjust because of this error: At least two rooms have the same rate plan assigned with conflicting rates. Please redo the channel setup.

PROBLEM:

This error can happen when a rate plan was changed for a room, and the room was mapped to another channel room without choosing the correct rate plan.  

SOLUTION:

For each rate plan shown select the one below the [Room not updated] selection.

Failed: 1003 Channel is not responding. Please try again later. (#FAULT.OTA.OFFLINE)

PROBLEM:

When performing a Full Refresh to Expedia, you receive the following error:

Reason 1: Pricing Model is set incorrectly

PROBLEM:

Expedia operates with two different Pricing Models:  Per Day Pricing, and Occupancy Based Pricing. When telling myallocator which Pricing Model you use, the setting must match what is in your Expedia Extranet.

If you choose the wrong option on this page, myallocator will complete the channel setup, but when you perform a Full Refresh, the error will be displayed.

Currently, only Per Day Pricing is accepted - Check further information here: Expedia Pricing Models - Everything you need to know

SOLUTION:

When the wrong setting is chosen, myfrontdesk will detect this when the Full Refresh is sent.  When myfrontdesk detects the wrong selection, we will automatically correct the setting to match your Expedia Extranet.  When you send a Full Refresh again (the 2nd time) the setting will have been corrected, and the connection will function normally.

Reason 2: Expedia outage

If Reason 1 does not solve this error, it means that Expedia is experiencing an outage on their side. In this case, please contact your Expedia support team for further assistance.

Failed: We encountered an unknown channel error. Please contact support or try again later
Expedia errors - Google Docs - Google Chrome

PROBLEM:

Although you can see Occupancy Based Pricing Model under the drop-down menu on the Expedia mapping page, we currently do not support different prices for different numbers of guests.
Expedia can only be enabled if you choose Per Day Pricing option on the mapping page. 

SOLUTION:

The problem can be fixed by selecting the'Per-Day Pricing' Model on the Channel-specific Options Screen on the mapping page to Expedia. 

Please check the following article to learn more about Expedia Pricing Models: Expedia Pricing Models - Everything you need to know

Failed: Please select a different rate plan for updates, as the currently selected rate plan is not enabled for updates
Expedia errors - Google Docs - Google Chrome

PROBLEM: 

Myallocator (channel manager by Cloudbeds/myfrontdesk) can only update one Rate Plan for the channel. That way, myallocator sends the regular rate for the Standard Rate, and the other plans/packages can be derived from the Standard Rate Plan directly on the extranet.

SOLUTION:

You should always select the "SellRate S" rate plan or "Default"/"Standard" Rate Plan when mapping Expedia. The Default Rate is always the first (top) rate presented.

Failed: You were trying to allocate more availability than is configured on the channel
Expedia errors - Google Docs - Google Chrome

PROBLEM

Currently, only 'Per Day Pricing' is accepted for the connection to Expedia.

SOLUTION:

You should choose 'Per-Day Pricing' Model on the Channel-specific Options Screen on the mapping page to Expedia.

Please check the following article to learn more about Expedia Pricing Models: Expedia Pricing Models - Everything you need to know

Have more questions? Contact Support

Comments

Powered by Zendesk