There are a lot of issues arising from the fact that we do not have the dates an accounting item or bill is created and updated.

We would like to maintain a snapshot of the accounting items and bills dataset for a 4 year period (2 years past, 2 years future). We would like this to be as "synced" as possible. We are doing this by making an API call for all accounting items every hour. The reason we have to be pulling the entire dataset is because a deletion of an accounting item is possible. d

However, because:
1) We have a lot more data than your average customer, ie we currently have 35 properties in a single integration
2) The API call limit is 2000 per integration per 15 minutes, no matter how many properties a client has in MEWS
3) The maximum time period of each accounting items call is 3 months

It subsequently means that for a single data sync of accounting items, we need to make:

16 calls per property (a period of 4 years) x 35 properties = 560 calls

Please note that accounting items is not the only dataset we would like to have a synced database table for. And therefore, we regularly receive empty responses due to exceeded API call limits.

Could we please suggest
1) Either tailoring your API call limits to the size of datasets of your clients instead of a global API call limit for all
2) Addition of CreatedUtc and UpdatedUtc fields for the AccountingItems and Bills so they can be utilized as filters in an API call (ie grab the AccountingItems/Bills updated the last hour) and drop the number of API calls needed every hour from 16 per property to 1 per property. A similar process is already available in Reservations using the CreatedUtc/UpdatedUtc filters.

The current rates/getall API call does not bring up the Rate Description and Rate Segment.

Regarding the Segment: Arguably, someone could link the rates response to the reservations response and grab the Segment of the rate from the reservations it's linked to. The issue however is that once a rate is applied to a reservation, the user can go to the reservation and change the segment field, which leads to different segments on the reservation level and the corresponding rate level.

Regarding the Descriptions: It would be useful if we can have the Rate Descriptions in the rates/getall API response for reporting.

This task would be to expose a new flag in the

https://mews-systems.gitbook.io/connector-api/operations/finance#get-all-bills

API Endpoint that would determine whether a particular bill item originated from POS.

You may need to have this flag set to true when items are pushed into Mews.

What's our Use Case?

We want to be able to retrieve bill items that have originated in POS to Mews and we'll use Mews' interface to receive this information.

However, we only want POS specific items, other items not originating from POS we don't want.

Alternatively, there may be an option to get a list of interfaces that the Mews account is currently connected to. And perhaps have an origin ID or something that could associate back to the list of interfaces.

This could assist us greatly in managing revenue between both systems.

Mews now send and API call to Hotek Key cutter for only one key at a time, if you want to create multiple keys at a time it send it separately and not in one command. We check with Hotek and they confirmed to us that Mews send multiple keys creating in different commands and not in one command. This cause a lot of irritation with people at the reception, because it's not clear when the first key is created and when they need to put the second key on the card reader. Allowing duplicate keys is not and option as lost card or stolen card are not deleted from the system and still has access to the room creating a security issue.

Connector API does not have an endpoint for updating an availability block. There are only endpoints for creating (availabilityBlocks/add), deleting (availabilityBlocks/delete) and updating its service availability (services/updateAvailability).

Some reasonable use cases for updating an availability block would be:

1) Block created for 5 days. After some time the sales person needs to extend the block with, let's say, one day pre and two days post, so the block becomes 8 days long.

2) Update the release date of the block.

3) Update the booking notes with some special instructions which has been assigned later.

4) Update the block's name (in case of typo or whatever reason).

These are some of the scenarios where the block itself needs to be modified. The scenarios are very common in all property management systems which manage group blocks.

A workaround like deleting the block and re-creating it with the new data wouldn't work for several reasons:

• Already linked blocks may be sent again and mess up the hotel's general availability.
• If the block has active reservations, it can't be deleted. So, to do, let's say, a simple modification of the release date, the vendor must cancel all reservations, then the block, then to create them back as fresh block and reservations in order to simply change the cutoff date.
• Potential reporting mismatches.

External systems that have group room blocks typically allow groups to go through a series of statuses that determine whether the blocked rooms should be taken from inventory. This is important as once a hotel promises a number of rooms to a group, it has to make good on that promise.

With the way availability is updated in Mews currently, space categories can be overblocked and cause our users to fail to have all promised rooms available for their guests.

Example:

1. Hotel has space category "King Villa" with 10 rooms available for every day in July

2. External system creates an availability block "A" for July 1st to July 5th, blocking 10 "King Villa" rooms for each day

3. Group "A" in the external system has its status marked as "Definite", which in this example means the contract has been signed and those rooms are promised to the group.

4. External system creates an availability block "B" for July 4th to July 8th, blocking 5 "King Villa" rooms for each day. Despite July 4th and 5th having all their rooms blocked by a definite group, this availability will be successfully blocked in Mews.

5. Reservations for the "B" block get created in Mews before reservations for "A" get created

6. When a user tries to create reservations for the July 1st to July 5th for the "A" block, not all of the inventory will be available.

In Mews there needs to be some type of overbooking prevention or statuses on availability blocks to determine whether their availability adjustments should take priority over other block's availability adjustments.