New Features and Updates: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
'''<span style="color: #7aab0a;" >{{#fas:plus-square}} </span>New Feature: Optimize for Airbnb</span> ''' | |||
We've added a new channel management feature called Optimize for Airbnb — designed for properties that already perform well on Airbnb and want to increase their share of bookings on peak dates, without manually blocking calendars or reducing visibility on other channels. Please note that eligibility criteria apply and not all listings will receive opportunities. | |||
When activated, selected dates remain open on Airbnb while other connected channels are temporarily restricted during the booking window. Once the window ends, availability is automatically restored to all channels. | |||
*Fully optional — adjust or disable at any time | |||
*Unsold dates reopen automatically after the booking window ends | |||
For eligibility details and setup instructions, visit our wiki page: [https://wiki.beds24.com/index.php/Optimise_for_Airbnb Optimise for Airbnb:] | |||
June 2nd 2026 | |||
---- | |||
'''<span style="color:#019cde;“ >{{#fas:external-link-square-alt}} </span>System (PHP) Upgrade – 27 May 2026''' | '''<span style="color:#019cde;“ >{{#fas:external-link-square-alt}} </span>System (PHP) Upgrade – 27 May 2026''' | ||
We will be performing a planned system upgrade on 27 May 2026 during the following window: | We will be performing a planned system upgrade on '''27 May 2026''' during the following window: | ||
Upgrade window: 07:45–08:15 CEST | |||
'''Upgrade window:''' 07:45–08:15 CEST | |||
'''Expected downtime:''' Approximately 60 seconds | |||
Based on our tests, the actual interruption should be very short (around 60 seconds or less). We will aim to time the brief downtime as close to 08:00 as possible. While we do not expect delays, there is always a small chance the process may take longer. | Based on our tests, the actual interruption should be very short '''(around 60 seconds or less)'''. We will aim to time the brief downtime as close to 08:00 as possible. While we do not expect delays, there is always a small chance the process may take longer. | ||
Services temporarily unavailable during the downtime | '''Services temporarily unavailable during the downtime''' | ||
Beds24 Frontend website | *Beds24 Frontend website | ||
Control panel | *Control panel | ||
API V1 and V2 | *API V1 and V2 | ||
Reseller sites | *Reseller sites | ||
Support tools | *Support tools | ||
Booking Engine | *Booking Engine | ||
Services that will continue to run normally | '''Services that will continue to run normally''' | ||
Auto actions | *Auto actions | ||
Routines | *Routines | ||
Webhooks | *Webhooks | ||
Incoming bookings | *Incoming bookings | ||
Channel connections | *Channel connections | ||
Wiki, forum, and blogs | *Wiki, forum, and blogs | ||
What users will experience | '''What users will experience''' | ||
If accessing the website or control panel during the downtime: | If accessing the website or control panel during the downtime: | ||
*They may see a browser message such as “Unable to connect” or “Site unavailable”. | |||
For integrations using our API: | '''For integrations using our API:''' | ||
*Requests made during the downtime will return an error such as “Connection refused”. | |||
After the system is back online: | '''After the system is back online:''' | ||
*Everything will operate as usual. Users will not need to log in again and should not notice any changes. | |||
May 26th 2026 | May 26th 2026 | ||