Smily (BookingSync): When and how are imported prices applied to bookings?

• 1) Operating with only default prices
• a) Price type priorities
• b) Mid-term booking example
• 2) Operating with default and short-term prices
• a) Price type priorities
• b) Short-term booking example

When you import rental prices from Smily (formerly BookingSync) into Flatio, these prices will be automatically used for your Flatio bookings. However, if you manually set up any optional prices on Flatio, these prices take priority over the imported ones.

There are slight differences in how this works, depending on whether you have the short-term prices (applicable for bookings up to 29 days) activated or not. Let's look at some examples to understand this better!

1) Operating with only default prices

In this scenario, you have the short-term prices deactivated, and we therefore operate only with the default prices.

a) Price type priorities

To calculate rental payments for a booking, we’ve settled the priorities of each price type. The one with a higher priority always beats the one with a lower priority.

Their order, from the highest priority ("1.") to the lowest one ("5."), is the following:

b) Mid-term booking example

Suppose you receive a booking for the whole month of July (1.7.-31.7.).

• To calculate the price for the booking, first we’ll check if there are advanced prices set directly on Flatio within the default price settings - custom prices (i.e., specific prices set only for a given period) have the highest priority and seasonal prices (i.e., prices for specific months) follow.
• If the prices for all 30 nights are not fully covered, we’ll move to the imported prices. Since this is a mid-term booking, we will first see if there was a basic nightly price for mid-term bookings imported. If there isn’t, we’ll use the imported basic nightly price for short-term bookings.
• And to cover all cases, if there were no prices imported and there are still some dates without a price, for those we’ll use the mandatory default Flatio basic price per month.
  • Please note that even though this basic price is set for a whole month, we’ll divide it appropriately by the number of nights within the given month (in case of July it would be 30) and operate with nightly prices for the missing dates.

2) Operating with default and short-term prices

In this scenario, you have the short-term prices activated, and we therefore operate with both the default and the short-term prices.

a) Price type priorities

To calculate rental payments for a booking, we’ve settled the priorities of each price type. The one with a higher priority always beats the one with a lower priority.

Their order when short-term prices are activated, from the highest priority ("1.") to the lowest one ("5."), is the following:

b) Short-term booking example

Suppose you receive a booking for 2 weeks of August (1.8.-14.8.).

• To calculate the price for the booking, first we’ll check if there are advanced prices set directly on Flatio within the short-term price settings - custom prices (i.e., specific prices set only for a given period) have the highest priority and seasonal prices (i.e., prices for specific months) follow.
• Then we’ll move to the imported prices. Since this is a short-term booking, we will see if there was a basic nightly price for short-term bookings imported.
• If there wasn’t and the prices for all 14 days are not fully covered, for the remaining days we’ll use the mandatory Flatio basic nightly price for short-term rentals.