Skip to content
Holidario Documentation

Pricing and availability

Review prices and availability before activating channels

Check rates, minimum stays, reservations, and blocks before opening a live connection.

For
  • I manage my own rentals
  • I own or administer an agency
  • I manage operations
Available on
  • Owner
  • Agency

The goal is to prove that Holidario will send the availability and conditions you genuinely intend to sell. Perform this review before activating Booking.com or Airbnb and after any major migration.

Prepare prices#

  1. Open the Price calendar for the correct operation.
  2. Confirm that at least one usable rate plan exists.
  3. Review minimum prices, seasons, and future monthly rules.
  4. Check minimum stays for normal and special periods.
  5. Verify that assignments cover the entire period you intend to sell, not only the current month.

Bulk views, gap search, and the compact calendar retrieve active operations only. A disabled operation remains outside these reviews until it is deliberately re-enabled.

Choose which rentals you see#

The matrix carries the same Characteristics filter and the same team quick filters on both of its layers, and switching layers keeps them. Filtering only changes what is listed: it changes no price, saves no group and grants no extra access. The steps, the available criteria and the quick-filter configuration are in Assign rate plans.

You can include a location and exclude another within it. Exclusions cover its neighbourhoods and areas and take precedence over inclusions. The filter uses the property's recorded location.

The incomplete minimum-price toggle combines with those criteria: if every rental in an area has complete minimum prices, the list is empty. Turn that toggle off to include those rentals without removing the location filter.

Changing the criteria returns to page one and drops the selection: mark the rows or cells again before applying any bulk change.

Minimum price source#

Each operation can use its own minimum prices or a shared preset. In the grid's Minimum prices layer, every row states its source: Model / operation values or Preset · name. The amount alone does not identify where it is stored, so trust that label rather than the numbers: two operations can show the same amount and read it from different places.

A preset is a live reference to all twelve months, not a copy. Changing a preset's prices immediately affects every operation that uses it. Assigning one does not touch the prices the operation has saved: they stay where they are and apply again if you later return it to model values.

To change the source of several operations at once:

  1. Tick the operation checkboxes in the name column.
  2. Choose the source under Minimum price source. The list shows your team's presets; those that do not cover all twelve months appear as incomplete and cannot be applied.
  3. Review the preview. Choosing a preset shows its twelve monthly amounts before you apply them. Returning to Model / operation values shows, operation by operation, how many months have a saved value.
  4. Press Apply source.

Months that were never saved stay empty when you return to model values: nothing is copied from the preset and nothing is filled in automatically. Complete them before selling that period.

Listing and assigning presets requires permission to read minimum price presets; returning to model values does not. If an assigned preset has been deleted or is no longer available, the row says so: an unavailable preset applies no minimum price at all and does not fall back to the operation's saved values. Return those operations to their model values.

Edit minimum prices in bulk#

Bulk amount editing only accepts operations using their own values. Rows that read from a preset are shown in the grid but cannot be selected for editing, and a range dragged across them skips them. If a request still includes one, the whole request is rejected and nothing partial is saved: reload the selection and exclude those operations, or switch them to model values first.

The Saved values toggle adds the operation's own amounts beneath the preset's on preset-backed rows, so you can compare them without changing anything.

Review availability#

In the central calendar, check a representative future period:

  • imported or confirmed reservations;
  • owner stays or blocks;
  • maintenance blocks;
  • dates that must remain closed;
  • dates that can genuinely be sold;
  • visible price and minimum stay.

Pay particular attention to boundaries between months, seasons, and years, as well as high-demand dates.

Compare with the OTAs#

Before activation, compare several dates with the correct Booking.com or Airbnb listing. Include at least one occupied date, one blocked date, and one available date.

Do not correct a difference by editing both systems simultaneously. First determine which system currently controls the calendar and retain evidence of the comparison.

Expected result#

You can explain why every checked date is open or closed and which price and minimum stay will be sent. The review task is complete only after that verification.

Stop and request help if#

  • a future reservation is missing;
  • an occupied date appears available;
  • the price or minimum stay has no clear source;
  • two systems appear to control the same listing;
  • the previous connection can still write availability.

Do not activate the channel until the difference is resolved and checked again.

Browse all documentation Press ⌘K or Ctrl+K from any page.

Preparing search…