Planyo Help :: Pricing manager

[--- Reservation form ---, Reservation form item, Number of persons, Additional persons present, Additional adults present, Additional children present, Custom property (User), Custom property (Resource), Custom property (Unit), Quantity of resources, Unit, Voucher, Resource sharing, ZIP/Postal code, --- Date ---, Season of the start date, Season of the end date, Season, Date, Start date, End date, Date including year, Start date including year, End date including year, Number of days from beginning of rental, Weekday, Start weekday, End weekday, Number of calendar days, Number of days in season, --- Hour ---, Hour, Start hour, End hour, --- Duration & Reservation time ---, Duration, Rental duration chosen, Number of months reserved, Additional days, Additional hours, Time remaining until rental, Time remaining until event ends, Time between reservation and rental, Reservation time (hour), Reservation time (date), Reservation time (weekday), Same-time arrivals/departures, Total number of existing rentals in given period (any customer), --- Returning customer ---, Number of hours reserved recently, Number of times reserved recently, Total hours in existing rentals in given period, Total number of existing rentals in given period, --- Shopping cart ---, Total resource quantity in cart, Position in shopping cart, Resource present in shopping cart, Total price of shopping cart, Additional hours in shopping cart, Total hours in shopping cart, Repeated reservation number, --- Other ---, Coupon holder, Label of the last usable coupon purchased, Base resource present in flexible package, Quantity still available, Price calculated so far, Daily pricing, CSV file, Always true, Agent reservation, User role, Using frontend mobile app, User is logged-in, Price used in search, Simplified daily pricing for external channel]
Specify what the pricing for this rule will be based on, e.g.: day of the week, date range, duration etc.

[>24h , >25h , >26h , >27h , >28h , >29h , >30h , >31h , >32h , >33h , >34h , >35h , >36h , >37h , >38h , >39h , >40h , >41h , >42h , >43h , >44h , >45h , >46h , >47h , >2 days]

[<2h , <3h , <4h , <5h , <6h , <7h , <8h , <9h , <10h , <11h , <12h , <13h , <14h , <15h , <16h , <17h , <18h , <19h , <20h , <21h , <22h , <23h , <24h , <25h , <26h , <27h , <28h , <29h , <30h , <31h , <32h , <33h , <34h , <35h , <36h , <37h , <38h , <39h , <40h , <41h , <42h , <43h , <44h , <45h , <46h , <47h , <2 days]

Single value or comma-separated zip/postal codes. Use the * suffix at the beginning or end of a zip code to search for a range of codes, e.g. AB1* will find all postal codes starting with AB1

[any resource, same resource, Test resource]

[any duration, same duration]

[Yes (Mobile app), No (Website)]

[Yes, No]

[Yes, No]

[No agent, Any agent]

[Customer, Administrator or moderator]

[No, Yes]

[day (same resource), week (same resource), month (same resource), year (same resource), start time (same resource), rental duration (same resource), - any time in the future (same resource), day (any resource), week (any resource), month (any resource), year (any resource), start time (any resource), rental duration (any resource), - any time in the future (any resource)]

[Email address, Country]

[Custom value]

Specify the value(s) of the custom property for this rule. In case of checkbox properties (yes/no), enter Yes or No, in other cases enter the full value. You may enter multiple values by separating them with comma. If this property has numerical values, you may also leave this empty and in the price fields use x to multiply the entered price by the actual value of this property, e.g. if you have the custom property adults and want to increase the final price by USD 10 per adult, enter +10x in the price field. Also, in case of numerical values, you can enter greater-than and less-than signs, e.g. >10 or <10. If you want to match a prefix or suffix, add a star, e.g. ABC* or *ABC. The value can be also specified in form of universal, resource and calendar tags. The special values $(empty) and $(notempty) will check for an empty/not-empty field.

This option only makes a difference if you have multiple seasons which cover the same period. In such case, you can decide whether to use only the active (first matching) season for given period or any season with matching dates

See Q240 in the FAQ for the description of the file format. Enter full URL in this field including http://. This location can be overridden if a resource uses a private CSV file (specified in a pricing cell). If all your resources have private CSV pricing files, leave this setting empty.

[EUR per hour, EUR per person, EUR per hour&person, EUR per week&person, EUR, day, EUR per day&person]
If you don't specify a price unit (e.g. EUR per person or USD per day) in the CSV, then this unit will be applied. This setting is overridden if a resource uses a private CSV file (specified in a pricing cell). In such case the unit chosen for given resource will be the default one.

If you leave this empty, the rule will be applied if no voucher was specified. Use the value * to apply the rule for all valid voucher codes. Use a specific value (e.g. ABC) or a value followed by * (e.g. ABC*) if you want the rule to be applied for a specific voucher code or codes with given prefix.

[Any type, Prepaid amount, Number of hours, Number of entries, Valid for given number of days, Discount valid for given number of days]
This rule will only check if the customer possesses a coupon of specified type and not if the coupon will actually be used.

Use a specific value (e.g. ABC) or a value followed by * (e.g. ABC*) if you want the rule to be applied for coupon labels with given prefix.

This rule will only work with flexible packages, it will be applied if the flexible package being reserved includes one of the listed base resources. You should list one or more resource IDs (comma-separated)

If you leave this empty, the rule will be applied if no unit was chosen. Use the value * to apply the rule for all unit names (except if none was chosen). Use a specific value (e.g. A101) or a value followed by * (e.g. A*) if you want the rule to be applied for a specific unit name or unit names with given prefix.

This rule is useful if you selected one of the recurring/repeating reservations in active features in site settings (recurring reservations/return trip/multiple dates). In such case you can enter the number of the reservation, e.g. 1 for the first of a series, 2 for the second etc. If you leave this empty or use the value of 0, the rule will be applied when the reservation should not be repeated. You can also type >2 or <3. Please note you can specify multiple values separated by comma.

[No channel (Planyo reservation), Any external channel, API call, Booking.com]

[if all of the following rules, if any of the following rules, if none of the following rules, for the times for which the following rules]