Right now, one can fetch all products that have been created/set up under a Bookable or an Additional Service in Mews.

All information are returned, except for the Accounting Category that has been assigned to the product.

This creates additional manual work where the property will have to set up the accounting category mapping twice (once in Mews and again in the 3rd party platform - e.g. an Upselling solution), and keep that manually updated in both, or the user has to omit the accounting category setting in the Product in Mews and use the 3rd party platform as the source of truth. The latter would not be ideal if the property also upsells some product manually (i.e. has two distribution channels for upselling products - one manual/in person, and the other via an upselling platform).

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.