Currently most accounting items (aside from those created as part of the initial reservation order) are attached only to the customer, not the reservation. A common part of many revenue management system designs is attaching all charges to the reservations they are associated with, to allow for showing breakdowns of all revenue by things like room types, rate plans, and origin. The Mews dashboard should allow users to associate a charge with a reservation when they create it, so that when all accounting items are queried from the Connector API they can all be easily connected to their corresponding reservation.

integration with PayByLink

it would be great to have a feature within the task section to create a task which can be set for certain time period, like 2-5 days not jus

being able to store a pin code received from the door lock and send it to guest

Voucher code only shows one rate in the Distributor! That is a problem if you want to add several rates to the same voucher.
For example, I tried to add a choice for travel agents to choose accommodation, accommodation with half board or accommodation with full board.
Instead, now I have to send three separate vouchers and more importantly travel agents need to log in with three separate vouchers to compare the options...not ideal for a smooth workflow.

OTAs are now pushing special rates for phone apps. We should be able to do the same to maintain parity with the main OTAs.

Distribution via facebook messenger (which will be merged into instagram messenger soon). Give guests the option to check availability and book a room via Facebook messenger.

https://www.facebook.com/business/news/f8-2019-making-it-easier-for-businesses-to-connect-with-customers-on-messenger

In the API make all external payment types available for adding a payment, not only cash or credit card. Also add a possibility to add an external id through the API that will end up in the payment report.

Within Mews, there is a messaging hub where users can have two way conversations with guests.

By adding messaging to the Connector API, integrators would be able to push in messages and receive messages. For example, a chatbot.

With the reservation response from the Connector API, the total price of a cancelled reservation is not returned. With this extension, it would be possible.

Currently, RMSs can call 1 rateID for any interval. It would be helpful to call all rateIDs for an interval instead.

Currently via the Connector API, you're not able to retrieve information about employees in the enterprise. With this endpoint, information such as creator and created date would be visible.

Adding these extensions would allow for retrieval of data on which employee from which property added the company profile and when it was last added or updated via the API.

In Mews, you're able to attach a segment to a reservation, via the Connector API it is currently not possible for an integrator to update a reservation to have a segment. With this development it could be possible.

Adding this extension would allow an RMS integration to make calls that pull a longer period of time but for only 1 space category.

With this endpoint, an integrator would be able to remove a stay product from a reservation through the Connector API.

Some integrators build self service kiosks, with this extension to the configuration/get endpoint the terms and conditions the property has loaded in to Mews will be returned.

This would allow for integrators to retrieve not only the product category id but the name of the category as well when calling Get all products.

Integrators are currently not able to update a reservation already existing in Mews with notes. Creating an update reservation endpoint would allow an integrator to do so.