Please add surcharge categories for "Gate passes" and "Credit Card Processing".
Furhermore, the community we property manage for has a fee for a gate pass to allow cars into the community. Right now we don't have a great way to categorize these. Please add a multiplier option for this similar to pet fee. If people need more than 1 guest pass (which they frequently do) it would be great if they could request that with the multiplier so we can have the surcharge updated accurately.
Thanks for taking the time to share this request, Ryan!
Here is a video response I made showing how you can categorize these surcharges using our current categories and how to create surcharges that will allow you to automatically charge for multiple gate passes.
Understanding Surcharge Categories and Feature Requests at OwnerRez - Watch Video
Regarding the surcharge categories for things like Gate Passes and Credit Card Processing, those categories are driven largely by what the major channel APIs (like Airbnb and Vrbo) support. Because of that, it’s unlikely we’ll be adding new predefined categories in the near term. The good news is that you can still label your surcharge however you’d like, while assigning it to one of the existing types (for example, using Community Fee for gate passes or Reservation Fee for credit card processing). You can name them anything you want. That approach will still show correctly in reports and allow consistent categorization across bookings.
As for the quantity or multiplier idea for optional surcharges, that’s a great suggestion. However, the current multiplier logic depends on data points provided by channels (such as guest count or pets), so it isn’t easily expandable to new fields, like “number of cars.” To support this properly, we’d need to introduce a separate quantity field specifically for optional surcharges, which would take some development work.
As with all feature requests, we have a lot on the roadmap and prioritize based on user demand, so votes on this post will help us gauge broader interest.
Thanks again for sharing your use case. It’s a helpful example that gives our team context for how these features could be improved.
