Hello,

I have seen Patryk's comment [1], but tier pricing, as they are implemented, do not cut it.

To remove ambiguities, let me define two terms:
- booking: when the customer interacts with GrandNode to make a reservation
- stay: when the customer actually enjoys what he booked, the period that the customer selected at booking time

The problem with tier pricing is that the specified date range seems to be checked against the booking date, instead of the stay period.
It matters, because if a customer makes a booking in February for a stay in July, they should pay the July price, not the February price.

Patryk's comment might be dated (2018), so maybe it is implemented in another way now?
Otherwise, it seems to me that this feature is a must for most of the hospitality industry, and should be implemented.
What do you think?

Paul

[1] https://grandnode.com/boards/topic/5ad49030ecbda172d4695ecd/type-of-reservations-1-night-in-a-cottage-house-example-problem-that-might-come-up