Heated Pool at a Short-Term Rental: Pricing It So the Math Works

A heated pool is one of the strongest filters in vacation rental search. Guests who want one will pay more per night to have it, they book further in advance, and they're less price-sensitive on length of stay. That part most operators already know.

What catches people off guard is the cost side. Pool heating is one of the largest variable expenses on a rental property, and unlike most operating costs, it scales with occupancy. More guests means more pool time, which means more run time on the heater. In a warm market, that's manageable. In a property that runs through shoulder season in a cooler climate, it's worth a close look before you set your fee.

What running a heater actually costs

Gas and propane heaters are the most common in vacation rental markets. A standard pool heater running in cool weather costs roughly $30 to $80 per day to maintain temperature, depending on pool size, outside temperature, wind, whether you're using a pool cover overnight, and how long the system has to run to recover from a cold start.

Heat pumps are more efficient in moderate climates and cost $5 to $20 per day in electricity under similar conditions. The tradeoff is that they heat slowly. A heat pump takes 24 to 48 hours to bring a 15,000-gallon pool from 65°F to 85°F. That's fine if you're heating continuously between stays. It creates problems when a guest books a two-night stay and expects to swim the afternoon they arrive.

Solar is inexpensive to run but weather-dependent and rarely sufficient on its own in the shoulder season when guests actually want heating. Most operators with solar use it to reduce gas or heat pump run time, not replace it.

The numbers matter because most operators set their pool heating fee once, when they first add it as an option, and never revisit it. A fee that made sense in year one can silently run at a loss by year three if your energy costs have moved or you've started accepting more short stays in cooler months.

Flat fee vs. nightly fee vs. baked in

Most operators charge a flat fee per stay. Something in the $150 to $300 range for a week-long booking is common. Guests understand it, it's easy to collect at booking, and it signals that heating is optional rather than assumed.

The problem with a flat fee is that it doesn't account for stay length. A two-night stay in April costs roughly the same to heat as a seven-night stay in July for the first day of heating. After that, the seven-night stay consumes four to five times more energy. Charging both guests $200 means you're collecting a reasonable margin on the week and a comfortable margin on the two-night stay, which might feel fine until occupancy shifts and your average stay length drops.

A per-night fee fixes this but adds friction. Guests have to understand what they'll pay before they commit, and the total isn't clear until they choose their dates. Some booking platforms handle this cleanly. Others make variable add-on fees awkward to display at checkout. For most operators, the complexity isn't worth it until their portfolio is large enough that the revenue difference at scale becomes material.

Baking heating into the nightly rate works well in warm-climate markets where the pool rarely needs active heating. A Scottsdale property where the pool sits at a natural 75°F from May through September doesn't need a heating fee for summer bookings. The calculation changes when that same property books in January and guests expect 82°F.

The temperature expectation problem

Most guests who search for a "heated pool" are expecting something in the 80 to 84°F range. They're not thinking about what it takes to get there, how long it holds, or what happens if the heater has a bad day.

Setting a specific temperature in your listing, and a timeline, prevents the most common complaint. "Pool heated to 82°F. If you'd like it warm on arrival, complete pool heating payment at least 24 hours before check-in" is a complete statement. The guest knows what they're getting and when. You have a record of whether they paid. If they didn't pay and ask why the pool is cold, you have a clear answer.

The "pool isn't warm" text at 9 PM is nearly always a communication failure rather than an equipment failure. Guests who paid and received confirmation that heating would start at a specific time almost never send that text. Guests who assumed heating was included, or who thought it would happen automatically, often do.

When occupancy is back-to-back

High summer occupancy creates a specific heating problem. If checkout is at 10 AM and check-in is at 3 PM, and both guests have paid for heating, the pool doesn't cool in five hours. You're essentially running the heater continuously through the season.

That's actually favorable for your energy cost per reservation, because maintaining temperature is cheaper than recovering from cold. A pool that drops from 82°F to 82°F between guests costs almost nothing to keep at temperature. The expensive cycle is cold start: a pool that drops to 65°F in a week of no bookings and needs to come back up before the next guest arrives.

If your property has significant gaps in occupancy, decide whether to heat between bookings. Letting it cool to ambient temperature and then recovering costs more energy per stay than maintaining continuously. For a property with two to three gap days per week on average, the math often favors running at a lower maintenance temperature during gaps rather than letting it fully cool.

The maintenance piece

Heated pools require more chemical management than unheated ones. Warmer water consumes chlorine faster and creates conditions for algae and bacteria to grow. If you're manually managing chemistry or relying on a once-a-week visit from a pool service, a heated pool with high occupancy will occasionally arrive at the service visit in bad shape.

Heaters also fail, usually at the beginning of the season or during the first cold stretch of shoulder season. A heater that worked fine in September may not fire reliably in November. Testing equipment before the cold stretch matters. A guest arriving to a cold pool because the heater failed on day one of a week-long stay is a guest asking for a partial refund.

The maintenance overhead is part of what makes the heating fee legitimate from a business standpoint. You're not charging for the energy alone. You're pricing in the chemical cost, the service calls, and the operational attention that keeping a heated pool running properly requires.

Keeping it out of the statement surprises

The less visible issue is that pool heating fees often end up in the wrong place in an owner statement. If a guest pays for pool heating and you collect it through a payment link or a separate transfer, and you don't attach that payment to the specific reservation in your system, it shows up somewhere in the owner's monthly totals without context.

Connecting each pool heating payment to its reservation at the time of collection ties the revenue to the right property, the right stay, and the right reporting period. It also gives you a defensible record when a guest disputes a charge or claims they never paid.

For the broader picture of how add-on revenue rolls up across a portfolio, the post on per-booking revenue lifts covers the full range of what operators typically offer. If you're thinking about how heating fits into seasonal pricing adjustments, the dynamic pricing post gets into how operators factor amenity access into their rate structures. And Pomello's features include reservation-level tracking for pool heating payments so nothing falls through between the guest's Stripe confirmation and the owner's monthly statement.