Sync problems with a channel (Airbnb, VRBO, Booking.com — often called an OTA) almost always fall into one of three symptoms. Find the one that matches what you are seeing, then follow the checks in that section. Each section ends by telling you when the issue is something you can fix yourself and when to contact support.
A booking on the OTA never appeared in Lodgix. See Symptom A.
Rates or availability you changed in Lodgix are not showing on the channel. See Symptom B.
A listing shows as closed or not bookable on the channel even though the dates are open in Lodgix. See Symptom C.
Before any of the checks below, open Settings > Integrations (under the Channel Management heading). This page shows, per property and per channel, whether the channel is enabled, the remote listing id, and the channel status. Most of the diagnosis starts here.
This article covers bookings, rates, and availability. If your problem is with listing content — photos, amenities, or property descriptions not updating on the channel — see the setup article for that channel (Airbnb Integration, VRBO Integration, Booking.com Integration) for how listing content is managed and synced.
iCalendar feeds are not the same thing. If your problem is with an imported iCal calendar (for example an external calendar not blocking your dates, or an iCal feed not importing), that is a separate sync path with its own troubleshooting. iCalendar is a separate item under Channel Management, not part of the channel integrations covered here. See Sync Calendars Using iCal and Importing Multiple iCal Feeds into Lodgix for setup, and Why an Imported iCal Feed Stopped Syncing if a feed that used to work has stopped. Do not use the channel checks below for iCal problems.
First, confirm the channel is actually connected
This single check resolves a large share of reported sync problems. On the Integrations page, look at the channel for the affected property:
If it shows disabled with no remote id, the integration was never set up for that property. This is a setup task, not a sync failure. Follow the setup steps in the relevant channel article (Airbnb Integration, VRBO Integration, Booking.com Integration or NextPax Integration).
If it shows enabled with a remote id, the channel is connected and you should continue with the symptom-specific checks below.
Symptom A: a booking on the OTA did not import into Lodgix
Confirm the channel is connected for that property (see the section above). If it reads disabled or has no remote id, the booking cannot import because the integration was never completed.
Confirm imports are turned on at the account level. If your account for that channel is suspended or has importing turned off, new bookings will not pull in.
Allow for normal timing. Each channel delivers bookings on its own schedule. Airbnb and VRBO deliver bookings to Lodgix automatically; Booking.com bookings arrive through our integration partner and are processed as they are received.
Check for a calendar conflict. If the same dates were already booked or blocked in Lodgix, the incoming reservation can be rejected as a conflict rather than created.
When to contact support: the booking exists on the OTA, the channel shows enabled with a remote id, imports are on, and the reservation still never appeared in Lodgix (or you are seeing a double booking caused by a sync failure). Include the property name and the OTA-side reservation id. If the channel was never connected, the setup article above will resolve it — no support ticket needed.
Symptom B: rates or availability are not pushing out to the channel
Confirm the values are correct in Lodgix first. Check your rates and booking rules for the affected property and dates before assuming the channel is wrong. See Adding and Editing Rates and Visual Rate Tape (VRT). The most common cause is that the value being sent is not the value you expected.
Check whether dynamic pricing is in control. If you have connected PriceLabs Integration or Beyond Pricing Integration, those tools set your nightly rates and override Lodgix rates. In that case, edit the rate in your dynamic pricing tool, not in Lodgix.
Confirm the listing is actually serving. A property can be enabled on a channel yet silently fail to push because it is not ready to serve. A listing will not serve when it is missing an address or map coordinates, is missing photos, has a zero or invalid default nightly (or weekly or monthly) rate, or has no number of bathrooms set. For VRBO there are additional readiness conditions, such as the property being inactive, a "Pending VRBO. Please check back in 24 hours." status on a freshly enabled listing, per-person rate configurations that are too complex, or too many discount values (the limit is 15). Fix the flagged item and the listing resumes pushing.
Look for a sync error on the channel status. On the Integrations page, a channel with a sync error will indicate it. For Airbnb, the error message is shown so you can act on it; many are listing-side issues such as an address mismatch (see Airbnb Address Sync Error and Airbnb Troubleshooting).
Allow for VRBO's update window. VRBO picks up changes on its own schedule, and an update can take up to 72 hours to appear on the VRBO site. A rate or availability change that is less than three days old is usually normal timing, not a sync failure.
NextPax channels work differently. NextPax (and the OTAs reached through it, such as Expedia and Agoda) pulls listing content, availability, and rates from Lodgix on its own schedule rather than receiving an instant push. If a rate change has not appeared on a NextPax channel yet, it is usually a matter of the next pull cycle, not a failed push.
When to contact support: your Lodgix configuration is correct, the listing is serving, dynamic pricing is not overriding it, and the channel still shows the wrong rates or availability, or a channel that was previously enabled has stopped syncing. Include the property name, and for VRBO include the remote id shown on the Integrations page.
Symptom C: the listing shows closed or not bookable on the channel
The words "closed" and "not bookable" are Booking.com terminology. Booking.com marks dates it considers unavailable as closed (stop-sell). If you are seeing this on Airbnb, follow Symptom B instead; for VRBO, see step 4 below.
Check what Lodgix actually has for those exact dates. Lodgix sends what your calendar contains, so the first step is always to confirm the dates really are open in Lodgix. Open your Calendar Tape (under the Calendar menu) for the disputed dates and look for a block, a manual close, or a zero availability count, and check Visual Rates Tape (the VRT) for a minimum-stay or change-over (arrival or departure) restriction. Any of these will correctly push to Booking.com as closed or restricted.
Confirm the channel feed is enabled. A disabled feed marks every date as unavailable, which reads as closed on the channel.
Confirm the listing is serving. A missing address, missing photos, or an invalid default rate will keep a listing from being bookable (see the readiness conditions in Symptom B).
For VRBO, the equivalent of closed is an inactive property or a "Pending VRBO. Please check back in 24 hours." status on a newly enabled listing.
When to contact support: the dates are genuinely open in Lodgix, the feed is enabled, the listing is serving, and there is no block or restriction that explains the close, yet the channel still shows the dates as closed. Include the property name, the date range, and the channel.
A note on Booking.com through NextPax
Booking.com can be connected either directly or through the older NextPax route. If your Booking.com listing runs through NextPax, the direct Booking.com integration is the current recommended path. See Booking.com Integration for the direct setup.
A note on Expedia
There is no standalone direct Expedia connection in Lodgix. Expedia is reached either through your VRBO connection (VRBO and Expedia are part of the same Expedia Group network) or as one of the channels behind NextPax — see Expedia Integration for the details. To troubleshoot Expedia, follow the VRBO or NextPax guidance above depending on how your listing is connected.
What to have ready when you contact support
The property name as it appears in Lodgix.
The channel (Airbnb, VRBO, Booking.com, or the NextPax channel).
The remote listing id from the Integrations page, and for an import problem the OTA-side reservation id.
The specific dates involved for an availability or "closed" problem.
A note of what you already checked from this article, so support does not repeat it.