Availability and Rate Sync
How availability, prices and restrictions reach your OTAs, what triggers a push, the Resync and Go Live actions, and what to do when a channel drifts.
Innvera pushes changes to Channex as they happen, not on a timer. Every edit that affects what an OTA can sell — a booking, a cancellation, a price, a stop-sell — writes a message to the outbox, and a worker delivers it to Channex within seconds. Channex then fans it out to every active channel. This page explains what triggers a push, how to read the outbox, and the manual actions for when something is out of step.
Key terms
Availability — units free per room type per date. Pushed per room type; every mapped channel receives it.
Restrictions — per rate plan per date: Stop Sell, Closed to Arrival, Closed to Departure, Min Stay Arrival, Min Stay Through, Max Stay. Daily prices travel in the same push, which is why a rate-only change appears in the logs as a restrictions topic.
Outbox — the queue between Innvera and Channex. Messages are PENDING, then SENT; a temporary failure becomes RETRYING, a permanent one FAILED.
What triggers a push
| You do this | Innvera pushes |
|---|---|
| Change Availability on the Inventory page (single cell or bulk edit) | Availability for the affected room type and dates |
| Change a Rate, Stop Sell, Min Stay Arrival / Through, Max Stay, Closed to Arrival / Departure on Inventory | Restrictions and prices for the affected rate plan and dates |
| Create, cancel, move or mark a reservation as no-show | Availability for the room type and stay dates (units return or are taken) |
| Block a room (out of order) or change a room's condition, add or delete a room | Availability for that room type |
| Create or edit a room type or rate plan | The room type / rate plan record (name, occupancy, description, images) |
| Edit OTA Policy, property details or property images | The Channex property |
| Receive an OTA booking or cancellation | Availability, so other OTAs stop selling the same unit |
Only Active properties push. A property that is Pending verification or Suspended queues nothing.
Batching and rate limits
Changes made together are sent together — a bulk edit across dates and rate plans goes out as one Channex call. Innvera also throttles its own calls to stay under Channex's limits, so a very large bulk edit may take a minute or two to fully deliver. Watch the Outbox Backlog on the Logs tab.
Stop-sell
To close a rate plan to new OTA bookings on given dates, open Inventory, find the rate plan's Stop Sell row and set the dates to on, then Save. The restriction is pushed for the mapping marked Primary on each channel. To close a whole room type, set availability to 0 for those dates instead — availability applies to every rate plan under the room type.
Retries and failures
Each push is classified after it fails:
| Failure | Behaviour |
|---|---|
| Network error, timeout, Channex rate limit or server error | RETRYING with increasing delay until it succeeds |
| A dependency is not synced yet (for example a rate plan whose room type is still pending) | RETRYING; picks up automatically once the parent is synced |
| Validation error, unauthorised, or the Channex record no longer exists | FAILED — needs a fix, then a resync |
Failed and retrying messages are listed under Logs → Outbox Backlog with the job name, entity, retry count, last error and age. Filter with the Failed and Retrying pills.
Manual actions
Open Settings → Channel Manager → Actions.
Resync entities
The Resync Actions dialog queues anything that has not been pushed yet; entities with an active job are skipped. Each button reports N enqueued, M skipped in a toast.
| Button | Queues |
|---|---|
| Hotels | The Channex property, for properties without one |
| Room Types | Room types not yet in Channex |
| Rate Plans | Rate plans not yet in Channex |
| Inventory | Availability for properties not yet synced |
| Restrictions | Restrictions and prices for the next 90 days on rate plans that have date overrides |
| Restrictions (Full Sync) → Full Sync | A 500-day baseline for every synced rate plan, including plans that only use default weekly pricing. Intended for go-live, not routine use. |
Channex Go Live
Channex Go Live pushes a complete 500-day baseline of availability and rates/restrictions for the property in two consolidated calls, after first repairing any missing property, room type or rate plan. Use it:
- once, when the property first goes live;
- after an outage, when you suspect the OTAs no longer match Innvera;
- after large structural changes (new room types, rate plan overhaul).
It is limited to two runs per minute per property and runs in the background; Channex may take a while to apply it.
Automatic drift correction
Two background jobs run every hour:
- Restrictions drift correction looks for properties with a
FAILEDrestrictions push and re-pushes the next 90 days for those properties only. If nothing has failed, it does nothing. - Channel reconcile lists every channel in Channex and updates the local connection cards: it imports channels connected in the Channex panel, applies mapping or activation changes made on the Channex side, and removes cards for channels Channex has deleted. The cloud download button on the connections card runs the same reconcile on demand.
Channex also reports OTA-side rejections back to Innvera as sync_error, rate_error and sync_warning events, which appear as the notifications Sync error, Rate sync error and Sync warning and as entries in Settings → Logs.
When a channel is out of sync
Check the Logs tab
Open Logs. Look at Sync Status for failed or review counts and at Outbox Backlog → Failed for the error text. Fix the cause first — a missing address, an unsynced room type, a rate plan in the wrong currency.
Resync the failed entity
Use Actions → Resync entities and click the button for the entity that failed. Confirm the toast shows at least one item enqueued.
Re-push the baseline if needed
If prices or availability on the OTA still disagree with Innvera, run Actions → Channex Go Live to resend the full 500-day baseline.
Verify on the OTA
Check a few dates on the OTA extranet. Remember that Channex applies pushes asynchronously; allow a few minutes.
Common mistakes
- Expecting a rate change to show as an "availability" push. Prices and restrictions share a topic; look for
restrictions.bulk_sync_to_channex.requestedin the logs. - Running Go Live repeatedly. It is capped at two per minute, and routine drift is corrected automatically; use it deliberately.
- Changing dates or room type on an OTA booking in the PMS. Channex does not push those changes back to the OTA, so the PMS blocks them before check-in. Amend the booking on the channel instead.
Related
Mapping Rooms and Rates
Pair each OTA room and rate with an Innvera room type and rate plan in the mapping tree, choose the primary occupancy, and change mappings later.
Receiving Bookings
How OTA bookings arrive as reservations, what the front desk sees (source, status, guest, payment and card details), and how modifications and cancellations are applied.