Page History

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt

Status
subtletrue
colourGreen
titleNEW 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
Info
titleSet-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.

Image Removed

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.

Image Removed

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:

Image Removed

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

...

Some fields were already available in the ticket template editor to provide some information on the purchase contact or cultural contact. These fields have been extended so that the contact's complete address may be displayed on the ticket.

Solution

Following fields have been added to the ticket template

  • For purchase contact

Image Added

  • For cultural contact

Image Added

The same naming convention has been used as for organisation or institution addresses. This means that the street1 field matches the first address line, street2 the second and street3 the last address line.

All these fields are also available in the definition of variable sets. As a reminder, variable sets may be used to print test tickets.

These additional fields are only available in the following basic templates:

  • fgl-secutix2 (the basic template for thermal tickets)
  • pdf-secutix2 (the basic template for print@home tickets)
  • pdf-a4-secutix2 (the basic template for A4 tickets used in some special cases)

Getting started

You don't have anything to do to use these additional fields in the template editor. Of course, your existing ticket templates haven't been modified and you will have to adapt them if you want to display the complete address of the cultural contact or purchase contact on your tickets.