Wrong rental’s calendar? Verify the property mapping

A working iCal link can still belong to another rental. Trace the source listing, protect genuine bookings and check each destination before correcting the import.

GGribadan3 min read
Wrong rental’s calendar? Verify the property mapping

A confirmed stay appears under the wrong rental in your combined calendar. The import has no error, so the connection looks healthy. Yet a successful download only shows that a calendar could be read; it does not prove that you connected the right property.

Use a property-mapping check when the dates look plausible but belong elsewhere. This is different from a slow refresh or a duplicate bar. First establish where the booking actually belongs, then repair the connection while keeping genuine occupied nights protected.

Trace one stay back to its source listing

Open the reservation in the account where it was made. Check the actual listing, booked dates and current status. Compare the listing details with your internal property record, rather than relying on similar names or a guest name in an imported title.

Illustrative example: a confirmed booking belongs to Rental A from 10 to 13 December, three nights. Its dates appear under Rental B in your combined view. That does not transfer the booking to Rental B. It gives you a specific source stay to trace through the connection.

Check whether you are seeing a second representation of the same source before diagnosing two real reservations. The duplicate-entry workflow handles that separate question. Do not cancel, rename or move a genuine booking just to make the calendar look consistent.

Match the export to the receiving property

In the source account, select the intended listing before opening its calendar export settings. In RentTools, check the property and platform attached to the import. Record the direction privately as “source listing → receiving property”, without copying the full calendar link into a shared note.

Airbnb’s calendar connection guide distinguishes import and export after selecting the listing calendar. Check each direction separately: a correct inbound link does not validate the outbound one.

Vrbo’s calendar-sync instructions likewise tell hosts with multiple properties to select the listing before importing. Use the connection controls actually available in the account you manage. Do not guess the property from the appearance of an iCal URL or assume a readable link validates its destination.

Also identify every calendar subscribed to the affected RentTools export. A wrong import can affect more than the combined view if that availability is then passed to selling channels.

Check that Rental A’s genuine booked nights cannot be sold again on the platforms where A is listed. If protection is missing, use each platform’s supported availability controls and verify the result. Keep any temporary hold identifiable by property, dates, reason and a review owner.

At Rental B, investigate any apparent restriction before removing it. B may also have a genuine booking, preparation time or an owner block on the same dates. A suspected wrong import is not a reason to open the entire date range indiscriminately.

In RentTools, calendar connections belong to a property and platform and their import URL can be updated. Removing a connection also removes that platform’s cached imported events for the property. It is therefore not a harmless way to tidy the display while you are still investigating. Keep the actual booking record at its source as the reference.

Once you have identified the correct export for the intended property, use the feed-replacement checklist for the connection update. Saving the correct URL is followed by a fresh import and a comparison of dates; it does not relocate a platform reservation or prove every subscriber has refreshed.

Check both properties and close the follow-up

After a successful import, inspect both A and B. In the example, verify A’s nights of 10, 11 and 12 December, and inspect why those dates are open or closed at B. Do not expect a cancellation, a different guest assignment or a new reservation to result from fixing the link.

Check the affected selling calendars in their own accounts as well. If an old imported block remains, trace its current source and refresh state instead of deleting a genuine stay. Remove only your identified temporary holds after confirmed nights remain protected, and preserve unrelated restrictions.

Give the team the corrected property context for any arrival or cleaning instruction affected by the mismatch. Keep an owner for any unresolved destination. Use the broader double-booking checks if the discrepancy has exposed a real conflict.

For your next connection review, open RentTools and trace one confirmed stay from source listing to receiving property and onward to the selling calendars. A useful completion test is that the right rental is protected for the right nights, not merely that the link saves.

Comments

Sign in to comment.

  • No comments yet.