Latest Activity...
That sounds exactly like what I was looking for!
I'm not sure how that managed to never show up in any of my searching and asking Rezzy, though . . .
Quality Center with Airbnb data included released this week!
Currently, Booking-type custom fields shown to guests during checkout only support Plain Text, Rich Text, and File formats. While useful, this means guests must manually type responses to questions that would be better served by a structured selection such as Yes/No/Maybe, a dropdown list, or radio buttons.
My use case: I want to ask guests during checkout whether they plan to bring an EV, so I can ensure charging access and remember check to see if they actually used the charger so that I can charge them properly after checkout. (The code could be BXEVREADY). A plain text field works, but asking guests to type "Yes," "No," or "Maybe" feels unprofessional and invites inconsistent responses that are harder to track and report on.
Requested feature: Add one or more of the following field format options for guest-facing Booking custom fields:
HI Jory,
You are right. By definition, a bank deposit goes to a bank account, not a 'channel'. There is definitely a value to the idea of mapping properties to different bank accounts, or the equivalent would be to sync deposits from each individual payment account (if you have say, 2 Stripe accounts) to a different bank account. Right now, per this example, all of your Stripe accounts would have deposits sent to the same bank account. The best workaround that I have found for that is to regularly click into each 'bank deposit' before I 'balance my checkbook' in QuickBooks where I can easily switch which account it applies to. No, that is not ideal, but the time saved by the deposit sync is still far better than having to manually create every single one in QuickBooks, like I had to for many years before. I have made the need known internally. If you don't see a feature request that you think expresses your views on the subject, either add to one that you think is similar or create a new one.
Actually you could have the emails shared with those particular guests automatically.
1) Create a custom field for the email addresses of those guests who should receive the particular emails you want shared.
2) Add the field to your booking form.
3) Instruct guests when completing the form to put the extra emails in the field, separated by a comma and space.
4) Add the custom field code to the ‘to’ field of the email templates you want to be shared, like arrival information, with a comma and space between them, like this: {guest email}, {custom field code}
That’s it. The emails you want shared will automatically go out to the guest AND the addresses the guest entered on the form. You don’t have to do anything manually ever. Just set up the system once and it will work every time, as long as the guest enters multiple addresses properly.
if you find that guests don’t put multiple addresses in properly, then setup three different custom field codes, and put this in the ‘to’ field of the template and it will still work just fine:
{guest email}, {custom field code}, {custom field code}, {custom field code}
Just be sure to add all three custom fields to your booking form with appropriate instructions.
[This topic has been merged with another topic (Request to Prevent Stacking Using Standard Discounts on VRBO and Direct Bookings). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (VRBO Channel Specific Last Minute & Early Bird Discount to avoid stacking)]
What if instead you use the cancellation policy grace period, allowing you to grant the guests a grace period time to cancel before you charge the card.
OwnerRez supports a Grace Period option on cancellation policies, which allows guests to cancel within a set timeframe without incurring non-refundable card processing fees.
How It Works
Cancellation Policies > Grace Period
How to Configure a Grace Period
Maximum grace period: 72 hours after booking Maximum "arrival date is at least X hours away": 800 hours (33 days)
Guest Experience
During the booking process on Hosted Websites, guests will see the Grace Period displayed alongside your Cancellation Policy. In OwnerRez, grace period payments appear as normal payments with scheduled capture dates, shown as "Pending" in the payments grid until automatically captured at the end of the grace period.
Cancellation Policies > Grace Period
Important Notes for Vrbo Users
Vrbo's built-in cancellation policies (e.g., Firm, Moderate, Strict) do NOT include grace periods. Grace periods only apply when using custom cancellation policies.
If you want a grace period on Vrbo, you must:
Email Blast July 1, 2025 - Cancellation Policy Grace Period Behavior Update > Cancellation Policy Grace Period Behavior Update
Vrbo Setup & Connecting > Cancellation Policy and House Rules
Note on Channel Display
Grace periods are not prominently displayed on listing channels such as Airbnb, Vrbo, or Booking.com — they are visible to guests booking directly through your Hosted Website.
Great suggestion—thanks for submitting! Know anyone else who'd benefit from this? Send them the link so they can add their vote and show there's interest in making this happen.
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
Hi Kimberly,
Although there isn't an option to delay an immediate (event-based) trigger by minutes or hours, you could create a scheduled trigger to send the renter agreement on the day of booking creation at a specific time. This way, it still goes out on the day their booking is created, but not as soon as the booking is created. You could set it to a time later in the afternoon or the evening, to account for any guests who book later in the day:
However, if it's a same-day booking, you'd want to create a separate trigger to send the renter agreement as soon as the booking is created so that they receive it right away.
Hi Nicole,
Although it wouldn't add the other guests and their contact information to the booking, you could create custom field codes asking for the information for the additional guests, such as their names and email addresses. This should show up on the POC form, and once it's been filled out, it should show up under the Custom Fields tab of the booking. More on how to set this up here: https://www.ownerrez.com/support/articles/capture-additional-fields-on-checkout-quote-acceptance
Once you have the email addresses for the additional guests, you could manually send emails to those guests about check-in instructions, property details, etc.
Hello,
The issue has been raised that it is common that different properties will need to map deposits to separate bank accounts. I see no reason why anyone would need to map deposits to different channels. Has there been a feature request for this? Do I need to set up separate OwnerRez accounts to achieve this currently? Or is there another workaround?
Thank you.
Jory
Hey Jimmy,
I see what you’re getting at from a security standpoint.
Right now, our API doesn’t support scoped permissions like read-only vs. write. OAuth applications and personal access tokens are granted full access, and it’s up to the application itself to determine what actions it performs. So if your app is only making GET calls, it will effectively behave as read-only.
Since OAuth is already handling authentication securely, and the application controls which endpoints it calls, this isn’t something we currently have plans to change. Adding permission scoping at the token level would be a fairly large architectural shift.
That said, I appreciate you sharing the use case. It’s helpful context as we continue to evaluate API improvements over time.
-Steve
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
Hello OwnerRez Team,
I am requesting a new feature that would allow users to limit an OAuth application's access to be strictly read-only.
Current Problem
I am developing an application to pull daily updates on my vacation rentals. Per confirmation from Partner Help, currently, both personal access tokens and OAuth applications are granted full write access to the API.
For security and best practice, applications that only need to retrieve data, like my daily snapshot bot, should not be granted full write permissions. This unnecessarily expands the risk profile for the user's data should the application ever be compromised.
Requested Feature
Please add an option to scope a new OAuth application or Personal Access Token to "read-only" access. This would ensure that API calls using that specific token or app cannot perform any create, update, or delete actions, providing a more secure way to use the API for informational and reporting purposes.
This feature would significantly improve the security and utility of your API for developers building read-only integrations.
Thank you,
Jimmy
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
Exciting! Thank you for this update, Bri!
Owner Bookings made it through development and is moving to QA / Testing at this time! Do keep in mind that our testers may need to kick it back to our devs for some fine tuning, so there's not a great ETA I can provide yet. The ball is rolling though, and I've seen the work myself. It's coming along very nicely.
We'll keep everyone posted with updates as they become available.
I currently have about 55 properties listed with Homes and villas by Marriott through Hostaway and I would love to bring them over to Ownerrez and get rid of Hostawy. please advise me asap as to when I can do that
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
[This topic has been merged with another topic (Feature Request: Export and Import Listing Descriptions for AI Optimization). All unique votes have also been merged.]
[Another topic was closed as a duplicate of this topic (Archive or export entire Property Description)]
I'm aware of that but that's rather "old school", really want a dashboard info thing instead, way more useful.
Hello!
Along with setting up tag automation, you can create a template and trigger to send yourself an email for any guests who haven't signed the RA yet. We have this support article that goes over how you can set it up: https://www.ownerrez.com/support/articles/trigger-example-reminder-yourself-renter-agreement-has-not-been-signed
We've received your feature request—thank you! If you think others would love this too, spread the word and invite them to upvote. Community feedback really helps us prioritize what to build next.
We appreciate you taking the time to submit this feature request! If you know other users who would benefit from this, we'd encourage you to share it with them so they can add their support by way of an upvote at the top of the page.
Throwing mine in for beta testing too!
But does this require having 10 properties?
