Skip to main content

How Pricepoint Reads Availability from Your PMS

How Pricepoint reads availability from your PMS, using Online Availability or Availability Based on Bookings, and why MinLOS restrictions can make a room appear closed in Pricepoint even with units left.

Pricepoint can read availability in two ways:

Online Availability (default)

Pricepoint reads availability the same way your booking engine does, factoring in restrictions like minimum stay and blocks. If a guest could book the room via your booking engine, Pricepoint shows it as available; if not, Pricepoint reads availability as zero. This is the default method for most properties, set up during onboarding.

Availability Based on Bookings

In rare cases, Pricepoint instead calculates availability by counting booked nights for a given day and subtracting that from total units. This can be set up as an alternative to Online Availability if needed. This method is reliable, but it can produce a different availability number than what's shown online, for example, on days when beds are blocked in the hotel but not reflected as a booking.

Why does a room sometimes show as closed in Pricepoint even though I have units left?

This is usually due to a minimum length of stay (MinLOS) restriction or a block on that unit. For example, if there's a 1-night gap in your calendar but your MinLOS is set to 2 nights, a guest can't actually book that gap through your booking engine, so Pricepoint correctly reads it the same way, not bookable, shown as closed. The same applies if a unit is blocked, if a guest can't book it, Pricepoint won't show it as available either. This isn't a sync issue, it reflects real booking engine behavior.

Did this answer your question?