# Setting Up a New Capital Vacations (SPI) Property

> 💡 Best Practice: Configure SPI First, Then activate the channel in ChannelRUSH

When onboarding a new property to the Capital Vacations SPI integration, the most important step is to ensure your property is fully configured on the SPI side before activating the channel in ChannelRUSH.

*Specifically, SPI must have rate weeks (date ranges with day-of-week pricing) created for the property's room types and rate plans.*

ChannelRUSH pushes rate updates by editing existing SPI rate weeks — if no rate weeks exist on SPI, there's nothing to update, and rate pushes from ChannelRUSH will be rejected with a "No Date Ranges were found in SPI to update" message.

Recommended order:

1. Have the property setup in SPI, with rate weeks created for the date range you intend to manage.
2. Verify mappings (room types and rate plans) match between ChannelRUSH and SPI.
3. Then activate the channel and begin pushing inventory and rates.

Following this order avoids the situation described below.

## **What Happens If You Activate Before SPI Is Ready**

ChannelRUSH caches the list of editable rate weeks per property to avoid hammering the SPI API on every inventory update. The cache is populated the first time we query SPI for that property.

If you activate the channel before SPI has rate weeks configured, the first query returns an empty list, and ChannelRUSH treats the property as "not yet ready." Rate updates won't go through until ChannelRUSH refreshes the cache and finds rate weeks present.

To recover quickly without overloading the SPI API server, ChannelRUSH uses a graduated retry schedule when the rate list comes back empty.

Each consecutive empty response stretches the wait before the next refresh:

- 1st attempt: wait 5 minutes before retrying
- 2nd attempt: wait 15 minutes
- 3rd attempt: wait 30 minutes
- 4th attempt: wait 1 hour
- 5th attempt: wait 2 hours
- 6th attempt and beyond: wait 4 hours (capped)

As soon as SPI returns rate weeks, the cache is populated, the retry counter resets, and ChannelRUSH switches to its normal refresh cadence (once per day, just after midnight).

Worst-case timeline: a property activated before SPI is ready, with SPI taking many hours to populate, will retry roughly at +5 min, +20 min, +50 min, +1h 50m, +3h 50m, then every 4 hours thereafter — a maximum of about 5 attempts in the first hour.

## Bypassing the Wait — Just Save the Channel Settings

If you've confirmed with SPI that rate weeks now exist but ChannelRUSH is still in its retry window, you don't need to wait.

Simply open the channel's settings page in ChannelRUSH and click Save. That's it.

ChannelRUSH automatically detects when channel settings are edited and treats it as a signal that something has changed on your side, warranting a re-check. The next inventory or rate request for that property will:

1. See that the settings row's edit timestamp moved forward.

2. Reset the retry counter for that property.

3. Immediately query SPI again instead of waiting out the current backoff timer.

You don't have to change anything on the settings page — just opening it and saving is enough to update the timestamp and trigger a fresh attempt.

> 💡 💡 Tip: This works even if you've never modified the settings page since activation. The save action itself is what nudges the system; it's the equivalent of saying "I've done something on my end, please look again."

This check is intentionally lightweight: it only runs while a property is actively in a backoff window. Healthy, working properties incur no extra overhead.

## Symptoms of an Activate-Too-Early Scenario

You may see one or more of the following while ChannelRUSH waits on its next retry:

- Rate updates failing with "No Date Ranges were found in SPI to update."
- Inventory reports showing no rate data for the property.
- Updates that suddenly "start working" minutes or hours after the property was added, with no apparent intervention (this is the retry timer firing on its own).

These are not bugs — they're the cache holding the empty result until the next scheduled retry or a settings save. Activating only after SPI is fully configured avoids this entirely.

## Quick Reference

- Setting up a new property → Confirm SPI has rate weeks before activating the channel.
- Property is stuck waiting on retry → Open the channel settings page and click Save.
- Updates working normally → No action needed; cache refreshes daily.
