Where to manage what with ZenHost?
Choose the right tool for prices, listings, bookings, messages, payments and access, with synchronization limits.
At a glance: where to make changes
Where to start for a property connected to ZenHost. Each column shows where to act; synchronization details are explained below.
On mobile, scroll the table horizontally to see all four tools.
| Change | ZenHost | Airbnb | Booking.com | PriceLabs |
|---|---|---|---|---|
| Nightly price, without PriceLabs | ✓ Yes | — | — | — |
| Nightly price, with PriceLabs | ◐ Override | — | — | ✓ Yes |
| Airbnb promotion | — | ✓ Yes | — | — |
| Booking.com promotion | — | — | ✓ Yes | — |
| Cleaning fees | ◐ Direct | ◐ Airbnb | ◐ Booking | — |
| Tourist tax | ◐ Direct | ◐ Airbnb | ◐ Booking | — |
| Change / cancel a booking | ◐ Direct | ◐ Airbnb | ◐ Booking | — |
| Property photos | ◐ Website / portal | ◐ Listing | ◐ Listing | — |
| Listing description | ◐ Website / portal | ◐ Listing | ◐ Listing | — |
| Default property check-in/out times | ◐ Website / portal | ◐ Listing | ◐ Listing | — |
| Check-in/out times for a stay | ✓ Yes | — | — | — |
| Guest messages | ✓ Yes | ◐ Airbnb | ◐ Booking | — |
| Open / close the calendar | ✓ Yes | — | — | — |
| Minimum stay | ◐ No PL / override | — | — | ◐ With PriceLabs |
✓ Yes: act here · ◐ Conditional: follow the scope shown · —: use the tool indicated in another column. This summary describes the recommended ZenHost workflow, not every feature each platform offers.
Remember: changing photos, descriptions, fees or taxes in one tool does not guarantee an update elsewhere. For messages, choose one inbox to avoid sending twice. With PriceLabs, a manual ZenHost override protects the edited fields on the selected dates; check the details below.
Connection and import guides
- Connect Airbnb to ZenHost
- Connect Booking.com to ZenHost
- Import historical bookings from CSV
- Import prices and calendars from CSV
Understanding synchronization
This guide explains where to make a change, where it takes effect and what to check. It applies to all customers; results depend on your connections, permissions and the property involved.
Each action in the tables links to its detailed guide. Saving in ZenHost, sending to the channel and seeing the result on the platform are separate steps. After a significant change, check both the channel and ZenHost; there is no universal guaranteed delay.
If PriceLabs manages a property, start with its settings for dynamic pricing and understand the scope of ZenHost manual overrides. For an Airbnb or Booking.com booking, handle dates, occupants and cancellation on the source platform first.
Pricing and calendar
| Action and guide | Where to act, propagation and limits |
|---|---|
| Nightly price, without PriceLabs | ZenHost → Calendar. Rates sent to linked channels and used for direct bookings. Check the result on each channel. |
| PriceLabs-managed price | PriceLabs. PriceLabs → ZenHost → linked channels. Enable sync and check the linked property. |
| Manual PriceLabs override | ZenHost → Calendar. Edited fields are protected for selected dates. Removing the override triggers sync, without guaranteeing an instant reset. |
| Existing rate plan | ZenHost → Property → Rates. Edit displayed plans. No creation/deletion on this screen or choice of all plans on the direct website. |
| Channel adjustment | ZenHost → Rates. Percentage applied to the selected channel. A shared connection can affect several properties; check confirmation. Direct is separate. |
| Airbnb promotion | Airbnb. Applies to Airbnb; may combine with the sent price. Does not create a ZenHost promo code. |
| Booking.com promotion | Booking.com → Extranet. Applies to Booking.com, subject to eligibility. Check the final platform price. |
| Direct-site promo code | ZenHost → Websites. Discount for that site only; does not change platform promotions. |
| Direct cleaning fees and taxes | ZenHost → Property → Rates. ZenHost calculations follow the rule and inclusion setting. Check totals; OTA fee updates are not guaranteed. |
| OTA listing fees and taxes | Airbnb or Booking.com. Edit on the relevant platform and check its total. Separately check ZenHost rules to avoid double counting. |
| Open, close, minimum stay | ZenHost → Calendar. Availability and restrictions sent to linked channels. Booked nights and calculated blocks can limit reopening. |
| Edit multiple properties | ZenHost → Calendar. One-off selection, summary, then per-property results. Partial failures are possible; no currency conversion. |
Bookings
| Action and guide | Where to act, propagation and limits |
|---|---|
| Create a manual direct booking | ZenHost → Bookings. Creates the stay and adjusts linked-channel availability; does not create an Airbnb/Booking.com booking. |
| Receive a site booking | Guest → Direct website. The booking arrives in ZenHost. Do not enter it again; check its status and payments. |
| Direct dates and occupants | ZenHost → Booking. Save the card. Check prices, availability, messages and access afterwards. |
| OTA dates and occupants | Airbnb or Booking.com, according to booking source. Change on the source channel, then check receipt in ZenHost. Those fields are read-only there. |
| Operational stay times | ZenHost → Booking. Editable for OTA stays too. Separate from guest estimates; do not change channel booking dates. |
| Cancel a direct booking | ZenHost → Booking. Local calendar, message and access effects. Paid extras or collected money require separate financial handling. |
| Cancel an OTA booking | Airbnb or Booking.com. Cancel on the source channel, then check ZenHost. Local cancellation does not cancel on the channel or automatically refund. |
| Import and check sync | ZenHost → Integrations / Imports. Check mappings, identifiers, conflicts and report. Saving or sending is not proof the channel applied it. |
Listings and communication
| Action and guide | Where to act, propagation and limits |
|---|---|
| ZenHost photos and descriptions | ZenHost → Property. Feed ZenHost surfaces, including site and portal. Save; automatic OTA republication is not guaranteed. |
| OTA photos and descriptions | Airbnb or Booking.com editor. Edit each listing on its platform. Importing into ZenHost is not reverse content synchronization. |
| Property amenities and times | ZenHost for its surfaces; platform for the OTA listing. Check both displays. A booking-specific operational time can override the standard in ZenHost. |
| Guest message and photos | ZenHost → Messages. Compatible platform, email or SMS according to context. Photos are platform-only; WhatsApp opens an external tool. |
| Automate a message | ZenHost → Automations. Several channels may produce several deliveries. Check scope and scheduled messages. |
| Read and reply to a review | ZenHost → Reviews, when available. Reviews received from platforms; public reply sent to source. Publication, deadline, permissions and no previous reply govern eligibility. |
| Review an Airbnb guest | ZenHost → Reviews, if eligible. Airbnb only, after checkout and within its allowed window. Separate from replying to a received review. |
Payments and property access
| Action and guide | Where to act, propagation and limits |
|---|---|
| Collect stay payment | Linked Stripe account for direct; stated collector for an OTA. Airbnb/Booking.com and the host do not necessarily collect the same items. Check each payment and status. |
| Record a manual payment | ZenHost → Booking → Payments. Records an item and its status; does not initiate a transfer or charge. |
| Create a payment link | ZenHost → Booking → Payment links. Select existing payments and the Stripe account. The guest must pay; the link alone confirms nothing. |
| Refund | Collector’s tool: Stripe, Airbnb, Booking.com or bank. Identify the actual collection and confirm the result. Cancelling a stay or extra alone does not refund it. |
| Sell and attach an extra | ZenHost → Upsells / Property. Catalogue, then property and portal availability. The upsell Stripe account may differ from the stay account. |
| Request a deposit | ZenHost → Booking → Deposit. Create and share the request. The guest then authorizes through Stripe; check status and expiry. |
| Capture or release a deposit | Stripe → Payment on linked account. No capture/release button on the ZenHost card. Check account, booking and bank status before acting. |
| Guest invoice | ZenHost → Invoices. Check the stay seller and upsell seller. Separate from commission invoices to the owner. |
| Connected Nuki code | ZenHost → Property → Locks. Creation and revocation depend on provider responses. Check the lock and status after cancellation. |
| Connected or offline TTLock code | ZenHost → Property → Locks. Type depends on the lock. An old offline code may remain valid despite cancellation or changed dates. |
| Static code or key box | Physical device, then ZenHost record. Changing the stored value does not reprogram the lock. Physically check the old access. |
| Share the portal | ZenHost → Booking → Portal. Access to available stay information and actions. Expiry relates to departure; not a guaranteed 24 hours after checkout. |
If results differ, check the correct listing, linked account, dates, operation report or status, and channel total. Contact support with those details if the result remains inconsistent.