NEW V3.15 After the price refactoring and breakdown implemented in the previous releases for different product families, it's now time to extend this feature to the services. The goal of the refactoring is to store all kinds of prices (no matter the product family, inside an advantage or not, etc.) to a price grid in a standard way so that all product families can benefit from the new features like the price breakdown.
Solution
The Bishorn V3 release will provide price breakdown for services. This doesn't include vouchers and donations because their price isn't always defined in the catalog (the price may be defined during the sales process in some cases). Here are the main characteristics of this feature:
- The breakdown will be available for services:
- Bought alone
- Bought by means of an advantage.
- External price components (which amount comes in addition to the catalog price) are also available
Set-up (see details in next section)
The set-up of the catalog price itself undergoes only minor changes, As in the current solution, the prices of a service cannot be reused for another service. This approach allows to keep a very simple way of setting-up prices. Indeed, prices can directly be set-up when creating the service without having to assign explicitly a price grid to it.
Getting started
Setting up the prices of a service
The prices are set-up exactly in the same way as before.
The price grid displays one column for each service item.
Setting up the price breakdown
The price breakdown uses the price components defined in the season. Please refer to Define flexible price breakdowns for the definition of the price components.
You can enter a price breakdown for each service price. The definition of the price breakdown is optional.
The set-up process is exactly the same as for the other product families. You can find more detailed information on Define flexible price breakdowns.
Reporting
The sold amounts of the price components defined above (that may need to be shared among the different stakeholders) are provided by the reporting domain "Summary of fees". An example is given below:
Documents
You can display the price components on order related documents as well as on the file summary. You will find more details here.
Data migration
You can immediately start working with this new feature and create price breakdowns for services. Indeed, all pricing data have been migrated to the new pricing model. The reports will only take into account the defined price breakdowns for the reservations and sales created after the definition of the price breakdown (no retroactive effect).
