Under Settings > Discounts, when you create or edit a discount rule, you'll see a new option to set a promo code as the trigger for a discount:
You can build up rules with several conditions, for example you might require a certain duration, and a promo code, to earn the discount:
To display a promo code field in your widget, go to Settings > Online Bookings > Customise size and basic appearance, and check the "Promotion code" box:
Click 'Generate widget code' to get the custom code for a widget with promo code field (or, if you prefer, just manually add "promo_code=yes" as a parameter to the widget URL). Your widget will then display a promo code field:
Guests will automatically see the discounted rate if they enter the promo code that you have configured in your discount rule.
A note on multiple rules and multiple conditions: You can set up several different rules. And each rule can have more than one condition. For a discount to be triggered, ALL conditions on a particular rule must be met. If multiple rules are satisfied, then the guest will earn multiple discounts. So, for example, you might offer 15% discount for bookings of over a week in duration. And, with a different rule, offer 5% off for promo code "promo5". If a guest books for a week, and uses the promo code, they'll get both discounts (which will be combined). So a $100 rate would be discounted to $80.75 (15% off is $85, then 5% off that is $80.75).
And promo codes now also appear in a separate column in your .csv export file (Reports > Export Data > Download bookings and guests), so you can analyse bookings by promo code in a spreadsheet)
We've also changed any existing (duration-based) discount rules to display as "between x and y" nights, rather than "more than x" nights. Previously, if you had one rule that said "more than 6" nights, and another that said "more than 14" nights, the system took your first rule to mean "more than 6 but less than 15". We have just chosen to make that date range explicit, to make more complex rules easier to construct.





0 comments:
Post a Comment