INDEX


Introduction

Price lists are useful to configure various options for the sale of multipacks (memberships, subscriptions, passes, etc.). It is recommended to read the manual about multipack planning in order to better understand the planning of price lists.


Example of price list:

  • 5 passes valid for two weeks = 100 €
  • 10 passes valid for a month = 170 €
  • 20 passes valid for two months = 320 € 


When should a price list be planned then?


  • Multipacks sold without a price list: it will be necessary to create a multipack for each option. This option is recommended in case of few multipacks
  • Multipacks linked with a price list: this option doesn't require the creation of many multipacks, since the different pricing and validity is specified by the price list. Therefore price lists are useful to plan less multipacks and speed up sales, since there will be a shorter list of multipacks to choose from. Once the desired mutlipack has been selected, the system will require to choose price and duration from the price list.


Please note that multipacks that require the deduction of credit for each booking or access cannot be linked with the same price list of those multipacks that guarantee unlimited bookings/access within their validity. It will be necessary to create two different price lists and link them with each type of multipack.



Planning

Basic Planning

To create a multipack price list you will need to click on Planning -> Multipacks -> Multipack Price List -> Add

and specify:

  • code (name of the price list). Example: gym passes, fitness-class passes, personal-trainer passes, all-inclusive membership...
  • price-list optional rows: please note that if you require optional rows it is good practice to complete the planning of the standard rows first and then carry on with the planning of optional rows that are to be linked with a specific price list. Plese refer to the manual about optional rows to know how to configure them.


After specifying the name of the price list, click on OK. 

A button labelled "rows" will appear next to the name of the price list. 

After clicking on it, a table will appear at the bottom of the page with a yellow button to add rows to the price list.


 

Info required for the creation of price-list rows:

  • code: name of the row. It can correspond to the price, the duration or the number of passes. It is important in order to differentiate each row during sales
  • value: if the multipack allows unlimited access and/or bookings for the whole duration of its validity, leave 0, otherwise specifiy the credit, which corresponds to the number of bookings and/or access passes the customer is entitled to (limited by the validity of the multipack)
  • duration: validity of the multipack: choose between Days, Weeks, Months, Years, Sub-Season, Season. Please note that sub-season and season must be created beforehand. Click here to see how. If a multipack's validity corresponds with a season or sub-season the last day of validity will be the same as the last day of the season/sub-season. This means that if a multipack is sold one day before the season/sub-season ends, the customer will be only able to enjoy their memership for one day
  • price: if the current row is selected during the sale of the multipack, the customer will be charged the price specified in this field.

FAQs


QUESTION

ANSWER

AFTER THE PRICE LIST HAS BEEN CONFIGURED, IS IT POSSIBLE TO START SELLING?NO, IT WILL BE NECESSARY TO CREATE THE CORRESPONDING MULTIPACK, WHICH IS THE ITEM THAT WILL BE SOLD. ITS PRICE AND DURATION WILL DEPEND ON THE SELECTED PRICE-LIST ROW.
HOW CAN I SPECIFY THE AMOUNT OF CREDIT DEDUCTED FOR EACH BOOKING/ACCESS? AND THE TAX?IT WILL BE POSSIBLE TO SPECIFY THEM DURING THE PLANNING OF THE MULTIPACK.

Advanced Optional Planning

  • Optional Rows: select the optional rows exclusively linked with the specific standard row (more info can be found in the manual about optional rows)
  • order of appearance of the row in the list (where 1 = first row of the price list). If no value is specified, rows will follow the default order of appearance
  • booking limit: number of maximum classes/services that can be booked within the specified period. If the advanced booking limit is:
    • enabled: the limit will take into consideration the whole multipack. Example: if the multipack includes 5 bookable activities and the limit is 1 booking per week, clients will be allowed to book just one activity a week among all those included in the multipack. This means that each week they are only allowed to take part into one activity
    • disabled: the limit will consider the individual activity. Example: if the multipack includes 5 bookable activities and the limit is set to 1 booking per week, clients will be allowed to book each activity only once a week, which means that in a week they could potentially book no more than 5 different activities, since the system will prevent them from booking the same activity more than once.

Warningplease remember to enable the following settings in the multipack corresponding  to the price list, otherwise the booking limit won't work: 

  1. click on Planning -> Multipacks -> Detail -> click on Courses or Services, depending on where the booking limit is needed -> tick the box shown in the picture below:
  2. then click on Edit next to the Services/Courses the booking limit must be applied to and tick the box in the Limit column. Then click on OK to save.


  • available on the E-Commerce: if the sale is enabled, this specific price-list row will be available for sale on the E-Commerce. If deactivated, it won't be visible on the E-Commerce. To activate this option for all the rows of the price list, it will be necessary to tick this option for each single row
  • store: the standard row can be stored so that it won't be an available option during the sale of the corresponding multipack, but it will still be kept for record purposes. This option will be automatically activated by the system if an operator clicks on the Delete button next to the name of the row in the table after the row has been already used for the sale of a multipack. A stored row is marked with a padlock
  • daily price: do not use
  • statistic details: fields useful for advanced data analysis and integrations with an external accounting software. More details can be found here
  • automatic creation of instalments: please read the manual about automatic instalments to know more about this option.