The booking window controls how far into the future guests can see availability and book on your website. HomeRunner ships with a 365 day window by default, and it can be extended up to 720 days (about 24 months).
Availability flows from your PMS, through your HomeRunner connection, and into your website. Each layer has its own idea of how far out the calendar goes, and guests always see the shortest one. Extending the window means updating all three, in order.
How the booking window flows #
- Your PMS decides how far out availability and rates exist for each property.
- Your HomeRunner PMS connection pulls that data and builds a calendar for every property.
- Your website displays the calendar, capped by two plugin settings.
If dates stop being selectable at some point in the future, one of these layers is the reason.
Step 1: Update the booking window on your PMS connection #
The booking window on your PMS connection tells HomeRunner how many days of availability and pricing to pull for each property.
- Some PMSs, Hostfully for example, store a booking window per property inside the PMS. HomeRunner reads it automatically during sync, so make the change in your PMS first.
- For most other PMSs, the window lives on your HomeRunner connection. Update it from your HomeRunner dashboard, or ask the HomeRunner team and we will change it for you.
Per-property windows from your PMS are always respected. If one property should stop selling sooner than the rest, set its window in the PMS and leave the connection default alone.
Step 2: Sync your availability #
Once the window is updated, run a fresh sync so the longer calendar and pricing reach HomeRunner. You can trigger one yourself by following Sync a connection, or ask us to run it for you. Large portfolios can take a little while to finish.
Step 3: Update your website plugin settings #
In WordPress, open HomeRunner Settings, choose the Property Settings tab, and expand the General section. Two settings control the window on the site:
- Maximum calendar days is the site-wide ceiling. It sets how far ahead visitors can browse any calendar on your site, and it also determines how many days of nightly pricing the site stores.
- Default booking window is a fallback for properties that arrive from your PMS without a booking window of their own. Properties that bring one keep it; this value fills the gap for the rest.
The short version: Maximum calendar days is the ceiling for the whole site, and Default booking window fills in for properties that never specify their own. Unless you have a reason to split them, set both fields to the same number.
After saving, run a property sync from the Sync Settings page so the site pulls availability and pricing for the added days, then clear your site cache if you use a caching plugin.
Quick reference #
| Setting | Where to change it | What it controls |
|---|---|---|
| Booking window | Your PMS or your HomeRunner PMS connection | How many days of availability and pricing HomeRunner pulls |
| Maximum calendar days | HomeRunner Settings, Property Settings tab, General section | Site-wide cap on how far ahead guests can browse and book |
| Default booking window | Same screen | Window used for properties that have none set in the PMS |
If dates still aren’t bookable #
- Confirm the new window saved in your PMS or on your connection.
- Run a fresh sync and let it finish.
- Re-check both plugin settings, then run a property sync from the Sync Settings page.
- Clear your site cache.
If dates past the old window still won’t open after these checks, email helpdesk@homerunner.io and we will extend it for you.
Looking to limit how soon guests can book instead? That end of the calendar is covered in Toolkit: Advance Notice Messaging.