Setup

Get a property ready for Channex, create its Channex property with Go Live, and read the sync status cards before connecting any OTA.

Before an OTA can be connected, Innvera needs a mirror of your property inside Channex: the property itself, every room type and every rate plan. This happens automatically once the property is Active, but the first push is something you trigger. This page walks through what must exist first, how to run that first push, and how to read the status cards on Settings → Channel Manager.

Where it lives

Open Settings in the sidebar and choose Channel Manager. The screen has two tabs:

Overview — the OTA Channel Connections card (one card per connected channel) and the OTA Channel Activity table (bookings and revenue per channel for the current month).
Logs — the Sync Status card, the Outbox Backlog card and the paginated Sync Logs table.

The Actions menu in the header holds Resync entities and Channex Go Live.

Key terms

Channex property — the copy of your hotel inside Channex. Innvera creates and updates it; you never create it by hand.

Channel — one OTA connection in Channex (for example, your Booking.com account). A channel holds the mappings between OTA rooms/rates and your Innvera room types/rate plans.

Outbox — the queue of pushes Innvera has scheduled for Channex. Every change is a message with a status: PENDING, RETRYING, SENT or FAILED.

Prerequisites

The property must be Active

Pushes to Channex are gated on the property status. A property that is still Pending verification (or Suspended) queues nothing — the badge next to Property Settings shows the current status. Activation happens after an owner document has been verified.

Check each of these before the first push:

Requirement	Why
A full Address on Settings → Property → Address	The property push fails with `Hotel address is required for Channex sync` without one.
The property Currency on Settings → Property → General	Channex ties every rate plan's currency to the property. Rate plans always use the property currency; the API rejects any other value.
At least one room type with rooms	Room types become Channex room types. Availability is pushed per room type.
At least one rate plan per room type you intend to sell	Rate plans become Channex rate plans and carry prices and restrictions.
OTA Policy filled in on Settings → Property → OTA Policy	Max guests, adults-only, internet, parking, pets and smoking policies are pushed to the Channex property.

Sell mode

Live rate and restriction pushes currently support rate plans with the Per room sell mode. Per-person (occupancy-based) rate pushes are a known limitation — see Troubleshooting.

Create the Channex property

Activating the property resets its sync state but does not push anything. The first push is Channex Go Live, which sends everything in dependency order: property → room types → rate plans → availability → restrictions.

On Settings → Channel Manager, click Actions and choose Channex Go Live ("One-time full baseline push").

Confirm the push

The dialog Push full baseline to Channex? explains that 500 days of availability and rates/restrictions will be sent for every room and rate plan. Click Go Live. The request returns immediately; Channex processes it in the background.

Watch the Logs tab

Switch to Logs. In Sync Status, the Hotels, Room Types and Rate Plans boxes move from pending to synced. A toast summarises what was queued (for example, "availability 12 enqueued/0 skipped"). If the toast says Nothing was enqueued, the property, room types or rate plans are not yet synced — check the failed entries below and fix the cause.

Go Live is safe to re-run after an outage or after large inventory or rate changes, but it is rate-limited to two runs per minute per property.

Status indicators

Sync Status card (Logs tab)

Each of Hotels, Room Types and Rate Plans shows counts by state:

Label	Meaning
`synced`	The entity exists in Channex and matches Innvera.
`pending`	Queued, not yet pushed.
`retrying`	A push failed with a temporary error and will be retried automatically.
`failed`	Retries are exhausted. Read the error in Outbox Backlog and fix the cause.
`review`	Needs a person to look — for example, an acknowledgement Channex reported as missing.

Below them, Outbox Backlog shows how many messages are pending, retrying and failed, plus the age of the oldest pending message.

Connection cards (Overview tab)

Each channel card shows an Active or Inactive badge, the number of mappings, and the last connection test: Passed, Failed (hover for the error) or Never tested.

Sync Logs table

Columns are Topic, Type, Status, Retries, Error and Created. Topics are the outbox message names, such as availability.batch_sync_to_channex.requested or restrictions.bulk_sync_to_channex.requested. The status badge uses the same four states as the outbox.

After the first push

Room types and rate plans you add later are queued automatically, as are edits to existing ones (name, occupancy, description, images, policies). You only need Resync entities or Go Live when something shows as failed or pending for longer than a few minutes — see Availability and rate sync.

Common mistakes

Running Go Live on a Pending property. Nothing is pushed until the property is Active; the toast reports nothing enqueued.
Changing the property currency after rate plans exist. Every rate plan is bound to the property currency; change the property currency first, then review rate plans.
Deleting a room type that is mapped to a channel. Deactivate and edit the mappings on the channel first, otherwise OTA bookings for that room arrive as booking_unmapped_room.