In the current Visonline integration with Mews, Mews only sends one room number/lock id to be encoded in Visionline. This presents an operational challenge for properties that have the following room structure:

6228 - main suite (parent space)
230 - private room for 2 persons (child space)
228 - dorm room with 4 beds (child space with 4 additional child spaces nested)
228-1,2,3,4 - four separate dorm beds

230 and 228 can be sold separately, as is any of the four beds. A party of 6 can also book the entire suite 6228.

In the latter case, a key card encoded for all 6 guests with a reservation occupying 6228 should include access to both 230 and 228.

In Visionline, it is currently not possible to manage mapping 6228 with clients 228 and 230 (i.e. key card encoded for 6228 automatically comes with access to the two child spaces).

It is recommended that Mews extends key creation message to include "Second room to be opened by the card."

You have an API endpoint https://mews-systems.gitbook.io/connector-api/operations/finance#get-all-accounting-items

Returned Accounting Item data has OrderId field:

Unique identifier of the order (or Reservation which is a special type of order) the item belongs to.

Can you add ReservationId field into Accounting Item?

The problem is that we can't know if an accounting item belongs to any specific reservation or not.

I tried to collect unique OrderId values from the list of accounting items and next fetch reservations with ReservationIds filter (to see if we have a reservation with Id same as OrderId), but if I pass non-reservation ID - I see the error "Invalid ReservationIds". So, this will not work.

It's the problem for our app because we need to understand if an accounting item belongs to a specific reservation or not.

Adding ReservationId field into Accounting item will solve this issue: if ReservationId is empty - the item belongs to order.

Otherwise, ReservationId has Id of reservation ( ReservationId equals to Orderid).

Adding functionatlity to create/edit vouchers and their codes would be useful for a number of use cases.

Firstly in my opinion the Mews process for creating this is a little clunky, especially if you want to track the usage of each VC as it needs to be it's own Voucher, there's no way to track the codes within that voucher.

Therefore lets say you have a staff friends & family rate, and you want the voucher code to be the employee name so you can track usage and abuse of the incentive.

Creating additional codes for an already created voucher is one thing but as I said above you can't track individual codes. For this reason you need to create a new voucher. Now imagine you want this code to work across all your properties and you have a large portfolio, you have to create the voucher/code within each property. Lets say you have 100 employees across 10 properties (arbitrary numbers) this means the creation of a total of 1,000 vouchers in total, in order to be able to track them. Now amplify that to 1000 employees across 50 businesses... For each new employee, for their unique code to work you'd need to create 50 vouchers, one for each property.

Doing this via an integration would be so much quicker.

Other use cases are marketing campaigns where you want a unique voucher per campaign to track the ROI of each.