Hi Mews team,

We are using Mews Distributor for our Pay on Arrival dates with activated 1% Pre-authorization on credit/debit cards.

However, the Distributor states that customer will "pay" the 1%.
For example, if the whole booking costs £350.00, the customer will be pre-authorized for £3.50.
Mews Distributor currently states that the customer will "pay £3.50".

This is incorrect, as full payment, not a remainder, will be taken on arrival.

Can we please have the wording changed from "pay" to "pre-authorized" or similar.

Thanks!

DISTRIBUTOR landing page should be able to recognize language of operating system of guest trying to make a reservation

In the call reservations/getall, 'Cancellation Reason' is not included in the response. This would provide integration partners with more granular data of why a reservation was cancelled and improve 3rd party reporting and revenue management. Available information for cancellation reasons from the system would include:
- COVID-19
- Other
- Confirmation missed
- Booked elsewhere
- Force majeure
- Guest complaint
- No show
- Price is too high
- Service not available
- Input error
- Invalid payment
- Travel agency
- Requested by guest

I guess this is a bug in the API.
The call never returns any CompanionIds within a reservation. The companions have been added both, by API Call and via the MEWS frontend

Would it be possible to pre tick the bow "I'd like to receive marketing updates"?

Could the Connector API documentation please give the maximum possible lengths of all string values? It's hard to store responses from the API in a database without knowing how big to make the fields!

In the Connector API documentation it states that Reservation Origin can be one of “Distributor”, “ChannelManager”, “Commander”, “Import”, “Connector” or “Navigator”. But in fact it can have at least one other value "CommanderInPerson". Could the documentation please be updated to list all possible values?

'Create rate plan via Connector API - Rateplan/Add. This to enable contract management from one platform (e.g. a CRM)

There's currently no way to change a reservation's status to "Optional" using the API. There are individual endpoints for confirming and canceling a reservation, but no endpoint for making one optional. A specific endpoint, or an extension to the [PlatformAddress]/api/connector/v1/reservations/update that allows for modifying the reservation state would be great!

Why? We allow our users to create "Enquired" reservations but they now have no way to make those reservations "Optional" (from our system)

Thanks!

Add the possibility to define the consumption date for stay products

Be able to modifiy the product rate depending on the date booked. For example, if you have "Dinner" as a product and its price is changing depending on the day of the week (weekdays or weekends) or the period of the year (Christmas, August...) it is going to be awesome to be able to change its price for every single day you need to.

Now you always need to enter a period when you are looking for a bill (bills/getall). And the period cannot exceed 3 months. If we do not know when an invoice was issued, we just have the number, it is not easy to find.

The booking engine always defaults to tomorrows date

· Given that we are a seasonal property please can we default to our winter opening date... as irritating for people to search for rates over the period that we are closed

There is a possibility to click "Create keys" in the Mews Admin to create keys by the Salto key cutter system. However we want to automize this through the API, so that keys can be automatically generated for guests, e.g. an hour before check-in.

Have the option to restrict product to specific dates.
For example: if we have New Years Eve Gala Dinner created as a product, would be very helpful to be able to restrict this product to only guests staying during the night of the 31st of December, and not to any booking date.

Via the API, being able to update the number of rooms available to be sold to allow for controlled overbookings.

Price shown on Booking engine is always in Euro first.
This is not convenient for guests who book outside euro countries.
If guests select their language then rates change in their selected currency automatically.
It is so much easier for them to understand the price.

Products is not always appropriate as an extra that is offered when booking. I would like to be able to modify Products to Experiences in my case but others may find another term more suitable.