-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update LOS pricing #341
Comments
LOS records are computed based on the other entities that contribute to the price calculation, so in that sense they are read-only. If you want to apply discounts per day then, depending on the complexity of the logic behind the discounts, you could use nightly rate maps or rates rules. |
@Azdaroth how can you apply rates for each day with different length of stay? Say for May 10 I want to set the following rats for different length of stays I believe the nightly rate maps doesn't allow it, can you point me to the link that will help us achieve what we are trying to do? May 10 |
@syedsanahassan In such case, you would need to use rates rules, |
@Azdaroth can you give me the link to this particular API exactly with a link? I am not able to see where you have "stay_at_least" anywhere in the https://developers.bookingsync.com/reference/endpoints/rates_rules/ |
@syedsanahassan It's a rates rule kind, all available kinds are listed here: https://developers.bookingsync.com/reference/enums/#rates-rules-types |
Is their an API point to update rates for different length of stays for each day? I see today you have https://developers.bookingsync.com/reference/endpoints/los_records/ that only searches but is there an end point that we can use to update LOS stays with discount percentages?
Say for each day with different stay length we have % of discounts/premiums then we will just like to push these discount/premiums to you so you can calculate the matrix (point 7 https://developers.bookingsync.com/guides/understanding-los-records/)
Is this possible?
The text was updated successfully, but these errors were encountered: