Software Release - 2025R2 - v3.25.02

Modified on Mon, 1 Sep at 2:07 PM

Overview

This release guide documents the changes made to the iPro CRM Software during the second release of 2025

Reminder: All clients have the ability to view all software changes on their staging site (IPROSTAGE), prior to deployment on the live site.

i.e. clientdomain(com).iprostage.com

(com) is the extension of domain .co.uk, .net, .info, etc...

Deployment Process

Deployment of the updated software is by client request raising a ticket with the support desk or via an email to support@ipro-software.com.

Deployment will be scheduled within an agreed time window. If you wish to change the time which has been agreed, please contact the support desk to arrange a suitable alternative. ,

Enhancements


Block Booking Rule [7096]

The block booking rule, which blocks guests from making bookings too close to the check in date, has been updated to behave the same way as the OTA's that use it.  Instead of blocking bookings for a set number of days before check in, the rule will now block a set number of hours before 23:59 on the day of check in.

For example,

  • If the rule is set to 6 hours, bookings will be allowed up until 17:59 on the day of check in
  • If the rule is set to 24 hours, bookings would be allowed up until 23:59 the day before check in
  • If the rule is set to 36 hours, bookings would be allowed up until 11:59 the day before check in

  • If the rule is set to 48 hours, bookings would be allowed up until 23:59 two days before check in

You may want to review this rule, which can be found by going to Company Settings under the Settings menu, editing a company and clicking on the Booking Rules tab.  Any existing value will have been converted to hours, but may need to be amended to behave the way that you want given the updated behaviour.

The rule can be set separately for different brands and each property (both in iPRO and in OTA's via the channel manager) will use the rule for the brand the property is associated with.


Channel Manager

  • If you are communicating with the guest via the OTA then only the latest message in a discussion thread will be shown in the inbox or communications section of a booking.  Clicking on that message will bring up the entire discussion showing all previous messages [7125]
  • If we receive a booking request from an OTA this will be created as a provisional booking and an email will be sent to you.  When you open the booking you can review the details and choose to either accept or reject the request.  This will then be forwarded to the OTA though the channel manager and the booking request will either be cancelled or updated to a full booking.  Booking requests do no block the availability on a property [7086]
  • If the channel provides a breakdown of the number of adults, children and infants then these will be populated in the booking in iPRO.  If they don't then the total number of guests will be set as adults [7158]
  • Vrbo Bookings can now be cancelled via iPRO and this will update the booking on that Sales channel within 24 hours.


Statements

  • Bookings on the owner statements are now sorted by check in date [7091]
  • The feature to show future bookings on a statement, which can be controlled with the "Show future bookings" switch on the statement tab of company Settings, now works when using statements in the Inline Layout [7150]
  • The order of the entries on the statement summary has been updated to make it easier to check the calculations before processing statements [7144]
  • Ad additional check has been added to the statement summary to highlight statements that may have an error on them so that they can be checked before processing [7144]
  • The Future Bookings section now works when using the Inline statement format.  This can be enabled or disabled in Company Settings [7150]


User Permissions [7128]

If you have given suppliers (such as housekeepers) access to the iPRO back office they will now get a restricted view when accessing he task list or calendar.  

  • On the calendar they will only be able to see when bookings have been made.  All guest bookings are shown in green, with owner bookings in blue and blockouts in grey.  They will not be able to see any of the guest details or the payment status of a booking.
  • The task list will only show the basic details of a task and will not include any financial or owner information.  You may want to set the permission to restrict the users from seeing tasks for other users or properties where they are not an assigned contact.

Other 

  • The Financial reports now have the option to show a breakdown of individual extras rather than combining them all into a single value.  You can split individual extras out into their own column by turning on the new "Show On Financials Reports" switch when comnfiguring an extra [7161]


Bugs Fixed

  • Unable to create a review for a language property [6883]
  • Abandoned Opayo back office payment updates balance incorrectly [7075]
  • XCover pricing not working on language web site [70777]
  • Alerts failing for balance payments that also pay the SD or have an error [7078]
  • Last Minute discounts sent to channel manager incorrectly [7083]
  • Channel manager rates sync fails if discount ends on the first day of a season [7095]
  • Length of stay discounts may not be applied correctly via the channel manager when bookings cross seasons [7098]
  • Discounts applied to a booking are displayed incorrectly if there are discounts in iPRO as well as an OTA discount [7120]
  • Property Search API ignores the block booking rule when performing a flexible search [7146]
  • Cost of extras shown in the owners area is incorrect [7147]


Follow us via social media to gain an insight into things as and when they are happening.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article