This article will help you understand the reason for the errors you may encounter during or after connecting Priceline/Agoda to Cloudbeds PMS and how to solve them.
If you can't find the problem you're facing in this list, reach out to our support. You can also reach out to your Priceline/Agoda Account Manager if you have questions about the Priceline/Agoda extranet.
Errors while connecting and updating the channel
Property can't create a listing with Priceline/Agoda
Problem
While trying to create a listing with Priceline/Agoda, you get the following error message on Priceline/Agoda's extranet or in Cloudbeds PMS:
"An error occurred while creating this listing which may result in the failure to create one or more rate plans in Priceline/Agoda. Reach out to support@cloudbeds.com for assistance"
This is an error upcoming from the channel side, due to Priceline/Agoda limitations for Priceline/Agoda Homes supply (single unit properties) in some countries.
Solution:
Hotel-type properties (multi-unit) should be eligible. In case you can't connect this property type, reach out directly to Priceline/Agoda support team.
Login Error: Cloudbeds is not activated for this property
Problem
When a user enters their Agoda Hotel ID, they see a red login error screen.
Error message shown:
"There could be two reasons why the connection was not successful: The Hotel ID might not be valid. Cloudbeds is not currently set as the channel manager on Agoda / Priceline."
Cause
This means the property has not yet selected Cloudbeds / Myallocator as its channel manager in the Agoda extranet.
Solution
Log in to Agoda YCS and go to Property Settings Optional Settings. From there, you must enable the Channel Manager Mode and select Myallocator (Cloudbeds). Process detailed in Step 2 of this connection guide.
Once done, you can return to Cloudbeds and retry the login.
Login Error: Hotel ID is already used by another Cloudbeds property
Problem
After entering the Agoda Hotel ID, the customer receives a login error.
Error message shown:
"We've detected that another Cloudbeds property is already using this Agoda / Priceline Hotel ID. Please verify that you've entered the correct Hotel ID."
Cause
This ID is already linked to a different Cloudbeds property. For security reasons, self-onboarding is blocked in these cases.
Solution
The connection won't work, but an automatic email will be sent to our Customer Support team, who will reach out to you to help you with this login issue.
Rates could not be updated: Some or all rates are above the maximum room rate set by the channel
Background
After an update attempt, the following error may appear for Priceline/Agoda:
Failed: 1114 Rates could not be updated: Some or all rates are above the maximum room rate set by the channel. As an example, please check [?roomname?] with rate [?ratename?], which should be below [?rate?]. To raise the maximum rate login into your Priceline/Agoda backoffice, go to Settings, Room Settings and raise the rates. (#FAULT.OTA.RATE.TOOHIGH.AGO)
Reasons and Solutions
Reason 1: Limitation due to Minimum Rate on Priceline/Agoda
Problem
There is a setting on Priceline/Agoda called Minimum Rate. It is set in order to prevent too low of prices being added by mistake or a third party.
If you have set a price on Cloudbeds PMS that is lower than the Minimum Rate set in Priceline/Agoda, the channel will respond with an error during the Full Refresh.
Solution
Go to your Priceline/Agoda's extranet and check the Minimum Rate for each room type.
You need to:
- Either make sure there are no base rates of all room types on Cloudbeds PMS that are lower than the Minimum Rate on Priceline/Agoda – and if you do, raise the room rates on Cloudbeds PMS. Follow the instructions here: How to Add / Edit Base Rates.
- Or lower the Minimum Rate of your room types in Priceline/Agoda.
Reason 2: Rate is too low on Cloudbeds PMS
Reason
One of the rates on Cloudbeds PMS is too low.
Solution
Check your Availability Matrix on Cloudbeds PMS and make sure there are no rates that are too low (for example, you have set the room rate to 1 USD by mistake).
Follow instructions on how to update your base rates on the Availability Matrix: Availability Matrix Overview.
Reason 3: Mismatch in currency between Cloudbeds PMS and Priceline/Agoda
Problem
In very rare cases, the error is caused by a mismatch in the currency between Cloudbeds PMS and Priceline/Agoda.
Solution
Make sure the currency on Cloudbeds PMS and inside Priceline/Agoda's extranet is the same.
Follow the instructions to set up the currency for your channels on Cloudbeds PMS: How to set up currency for channels.
Please select a different rate plan for updates, as the currently selected rate plan is not enabled for updates
Background
The following error appears when performing a full refresh:
"Please select a different rate plan for updates, as the currently selected rate plan is not enabled for updates."
Solution
According to this error code, the Rate plan that failed is a child rate plan, which is not allowed to set rate. Most likely, this rate plan is linked to another master Rate plan, so the system does not allow setting the rate of the child rate plan.
In case you would like to set the rate for each rate plan separately, you need to unlink the rate plan on YCS before sending the ARI update.
We understand it can be frustrating when your inventory appears open in Cloudbeds, but guests are unable to book on Agoda. This issue often stems from a few common synchronization points between Cloudbeds (via Myallocator) and Agoda's system (YCS).
Please use the checklist below to troubleshoot. If the issue persists, the final step involves escalating the XML data to Agoda Support for deeper investigation.
Common Troubleshooting Checklist
Before contacting support, please verify the following four areas in both Cloudbeds and Agoda's YCS platform:
1. Channel Manager Status
Action: Ensure the "Channel Manager" setting in your Agoda YCS account is correctly configured to Cloudbeds Channel Manager (Myallocator).
Location: Check under Rates & Availability -> Connectivity settings in YCS.
Why it matters: If this setting is deactivated, Agoda will hide your rates and availability, regardless of what Cloudbeds sends.
2. Room and Rate Plan Availability/Restrictions
Action: Verify that the specific room type and rate plan intended for the booking period are fully open.
-
Check:
Do you have a positive allotment (inventory count)?
Are there no restrictions applied (e.g., Stop-Sell, Min-Stay, or Cut-Off dates)?
Location: Review your calendar or Open/close Rooms section in YCS.
3. Price/Rate Threshold Limits
Action: Confirm that the rates sent from Cloudbeds fall within any minimum or maximum rate limits you have set in YCS.
Why it matters: If your rate is too low or too high according to your YCS settings, Agoda may block the sale of that rate plan.
4. Mapping and Rate Plan Selection
Action: Ensure that the rate plan you have mapped and synchronized in Cloudbeds exactly matches the public-facing rate plan open for sale on Agoda.
Important: If you have made recent changes to your mapping, you must perform a Full Refresh of distribution from Cloudbeds to push the updated mapping information to Agoda.
If the Issue Persists (Escalation to Agoda Support)
If you have completed the checklist above and confirmed everything is correct, but bookings are still blocked, the issue requires detailed analysis by Agoda's connectivity team.
Next Step:
Trigger a Full Refresh from your Cloudbeds system.
-
Extract the following data:
The Update-ID log from the Full Refresh.
The corresponding Full-Refresh XML file generated by Cloudbeds/Myallocator.
Contact Agoda Support: Forward the Full-Refresh XML file and the Update-ID log to Agoda Support via the YCS Connectivity channel.
Why the XML is needed: Agoda's team can analyze the precise data within the XML to pinpoint subtle issues like hidden promotions, internal holds, or discrepancies in room definitions that are blocking the booking flow.
Comments
Please sign in to leave a comment.