Reservation Custom Fields or Tags
Having the ability to add custom fields to the operator system would be extremely helpful for specific use cases outside of the general hotelier playbook. Tags would also achieve the same result.
Example: ability to tag or flag reservations with "vehicle information" or "Missing ID" etc would allow for fine tuning reports. Currently, we have to add product rules with no value to flag reservations. It's a workaround, but would love to see the addition of tags and custom reservation fields.
Hello all,
This status update is part of our ongoing work to simplify and streamline how our UserVoice feedback forum operates. We are reducing the number of statuses to two (Idea to Upvote + Released) to help manage expectations about where each idea stands and to minimize the number of status updates required from our product teams. Our product team reviews everything you share, and we might reach out for more info if we need it.
Thanks for your patience as we work to bring your ideas to life! You can learn more about the changes coming to UserVoice from this post in the Mews Community.
-
Sebastien Long
commented
I really don't understand how custom fields and tags are not already part of different objects in 2026, including reservations and contacts. This is standard across many PMS, across different real estate verticals (hotels, STR, multifamily, etc...). It allows clients to start building custom things without putting pressure on the PMS to build the features themselves. What's the alternative? Having to store this data elsewhere and sync it up to reservations.