Built by owners, for owners.

Getting Started

Core Concepts

Overview

Bookings & Quotes

Properties

Bookings

Quotes

Guests

Rates

Rules

Reviews

My Account

Messaging

Security Deposits

Insurance and Damage Protection

Taxes

Renter Agreements

Payment Processing

Dynamic Pricing Integrations

Widgets

Listing Site Integration

Property Management

Technical Stuff

Hosted Websites

WordPress Plugin

Door Locks

OwnerRez API

Other Integrations

Reporting

Email Template Library

Data Management

QuickBooks Integration

Privacy & Security

Channel Management

Payment Processing

Testing

Change Log

API Integrations - Property Field Quirks

Our Channel Management feature is extremely powerful and can greatly simplify your channel advertising. Learn how it works by reading our Channel Management Overview article.  The most powerful part of our Channel Management is the API Integrations we have with certain channel partners.

However, each API Integrated channel has different sets of fields they support with lots of overlap between them. Even if they support the same field, there are differences in what the field means or how you are limited in using it.

To make matters worse, some of the fields have hidden interactions with various channels.  For instance, if you select both option A and a different option B, you may get some third option C appearing in the channel that doesn't appear in OwnerRez at all.

This document is an attempt to record and explain these complexities.  As the channels are constantly adding new amenities and features, it will likely not be fully up-to-date - if you find a new such interaction, please let us know!

Health & Safety and Vrbo

The health and safety amenities are populated automatically based on your property rules.

1) The "Is Your property implementing"  section expands to show the safety procedures you've selected, and will automatically load those from OwnerRez:

2) The "self checkin" option populates based on whether you've selected that sort of checkin (screenshot 2)

3) The time between bookings populates based on your required gaps rule (screenshot 3)