Skip to content
Zyelra

What Zyelra controls vs Channex

Clear split of responsibilities: Zyelra PMS owns inventory and stays; Channex synchronizes to OTAs; OTAs remain guest-facing marketplaces.

Responsibility split

  1. Zyelra — properties, units, pricing/rate plans, stays, guests, operations, finance books of record
  2. Channex — channel management and synchronization layer to supported OTAs
  3. OTAs (Airbnb, Booking.com, Expedia, Vrbo when enabled) — guest marketplace listing and booking surfaces

When something fails

  • Wrong unit on a booking → remapping in Zyelra (Mappings / quarantine)
  • Wrong rate on OTA → fix pricing/rate plan in Zyelra, confirm mapping, then ARI sync
  • Messaging/reviews missing → check channel capability (often unsupported for some OTAs)
  • Expedia/Vrbo live paths → deferred / NEEDS VERIFICATION for many environments

Next step

Connect OTAs through Channex — mapping, sync, and troubleshooting.

More Channels guides →

Related guides

  • How channel management works

    Zyelra is the PMS source of truth. Channex is the channel sync layer to supported OTAs — not parallel direct Airbnb/Booking.com/Vrbo/Expedia connectors.

  • Map properties and rooms

    Map Zyelra properties and units to Channex / OTA listings so rates, availability, and reservations attach to the right inventory.

  • ARI and availability sync

    How rates and availability move from Zyelra through Channex to OTAs — and what is out of scope for vacation-rental ARI.

  • Channel capabilities

    Messaging, reviews, content, and booking depth differ by OTA. Use capability-aware expectations — not universal feature claims.

  • Channel and Channex troubleshooting

    Fix mapping gaps, quarantine bookings, sync confusion, and partner-gated or deferred OTA availability.

  • Pricing and rate plans

    How short-term pricing and rate plans work in Zyelra, where to edit them on property/unit hubs, and how they relate to Channex mapping — without hotel multi-plan ARI claims.