Keys (using keycutter) are automatically made based on check-out and check-in times. It would be useful to make a key that works until 10h15 if the check-out is for example at 10am. Now, if guests forgot something or want to pick up luggage they left in the room at 10h01 front office needs to make a new key.

Lightspeed POS offers a Self Order Menu. It would be revolutionary if Mews can integrate Mews Navigator with this. As this would allow Lightspeed to identify the guest(Room Number/Guest Name) and then based on their purchases, post the necessary charges to the correct room. The self order menu would contain the menu/prices directly from Lightspeed and hence would not be needed in Mews.
See below link for Lightspeed Self Order Menu information - https://www.lightspeedhq.com/pos/restaurant/self-order-menu/

Use case: allow guests to eventually check out on Operator tablet by using their key card as an identifier of the reservation/guest that is checking-out.

Other use cases can include making use of "check-out" features available in key cutter programs such as Salto for increased security

Besides dividing the Marketplace into integrations' categories, I think it would be smart to divide it into integrations' country of reference. This would allow the user who is picking the integrations to first check the ones provided by the country where his business is located, as they probably are a better fit to his business type and are able to solve certain issues related to that specific country.

We have an action for "create order", which adds a service product. However, the orders/add endpoint in Connector API does not allow for adding of stay products.

Add a Zapier action to allow for adding a reservation product.

Salto can receive a check out command from PMS. Currently, MEWS does not send these commands via the key cutter integration to Salto (early check out fe.).

Would be a great benefit (and improvement in terms of security) since currently we cannot create a new key via our integrating party for Kiosk.

Mews currently supports Kaba key cutters via FIAS, however this does not include mobile key functionality.

It would be great to have mobile keys as an integral part of providing a contactless and smooth arrival experience for guests.

Develop following triggers for potential usage of Zapier with CRM:

-Get prices
-Get availability
-Add reservation event
-Cancel reservation event

By doing more actions Mews to Mews on Zapier we would be able to have an infinite possibility of automations in various fields such as :
- payments : charge 50% remaining of a flexible rate, 30 days before arrival
-preauthorisations : on day of arrival, charge automatically the preauthorisations. If failed send email to team and guest...
- out of order : if maintenance issue task, turn property to OOO
-...
If doable the possibilities would be endless and allow advance users through automation to personalize/automate their PMS

(EN) When the customer returns their card, I place the card on the SSalto Reader. Click the card to check-out button. The card is read and the corresponding room is displayed at check-out.

(DE) Wenn der Kunde seine karte zurückgibt, lege ich die Karte auf den SSalto Reder. Klicke den Button Karte zum Check-Out.
Die Karte wird gelesen und das entsprechende Zimmer wird zu Check-Out angezeigt.

Assaabloy provides now door locks solution with possibility to the guest to press a button to set status do not disturb or make my room.

Does the DND/make my room status communication between Commander and Assa Abloy could be developped ?

Then communication between commander and roomchecking ?

Possibility to bill as a package the bills through the Fiscal printer as seen Mews.

If the GuestID can be written on the RFID in Sector2 of the Onity KeyCard System, Guests can authenticate at the POS for placing F&B orders on the room bill.

In this case there's no more need to write down the guest's name, only the key card is needed. The key card is read by an RFID reader coupled to the POS. The guestID is used to authenticate the guest and post the bill to Mews calling the API's. Supplementary the guest's last name can be checked to engage two-factor-authentication.

We now have the ability to connect task to reservations in Mews and this functionality has been added to the Mews API. However it would be really useful to have this added to the Zapier functionality as we have a number of zaps that create tasks in Mews, currently just putting the reservation number into the description field.

For the packages that include breakfast or other meals, the integration with the POS should post into the POS the meals that have been sold in the PMS. That way people at the restaurant have to know ahead and keep their inventory system.