Highlights

SecuTix has started a major project in Whymper V2. This project will last during several releases and will continue in 2019. The purpose is to bring major improvements in the definition of the prices and price breakdowns. In particular:

• Easier Prices configuration .
• More flexible price breakdown and availability for all kinds of product family.
• Future pricing features will be available for all kinds of product family (as long as it makes sense from a business point of view), thanks to a uniform way of storing prices within SecuTix.

Whymper V2 features

Developments in Whymper V2 concern the pricing of events and related product families, i.e., competitions and visits (not visit passes), as well as events defined inside an advantage, a calculated price season ticket or a package.

Pricing

Get rid of the rate type when defining the prices of an event. A rate table is now directly assigned to a performance, and not indirectly through the rate type as it was the case in the past. Of course, several performances may share the same rate table, no matter if they belong to the same event or not. It's still possible to define exception prices for a given performance. The concept of rate type isn't used anymore for the price definition but may still be used for other needs, for example to define the performances on sale within a package.

When the operator creates new performances, he may select a rate table to be assigned to the new performances. He can assign (or reassign) a rate table later on from the performances menu.

Gain flexibility while defining the price of a (set of) performances within an advantage or a package. This price is now defined by a fully separated grid. In other words, the rate table defining the price of a product within an advantage or a package is not a sub-grid anymore of the rate table defining the price of the same product sold alone. This change provides you major benefits:

• You can easily define the same prices for several events while defining different prices for advantages or packages using these events.
• You can easily define different prices for several events while defining the same price for advantages or packages using these events.

Concretely, when the operator defines the prices of performances within an advantage or package, he has the choice between:

• Define new prices for these performances within the advantage or package. These prices will be stored in a rate table that may be reused later as any other rate table.
• Reuse an existing rate table.

Price breakdown

Take profit of numerous improvements

The price breakdown will receive major improvements in the next releases:

• For each rate table, define freely if you want to create price breakdowns or not.
• Minimize the amount of work needed to set up a price breakdown while keeping maximum flexibility:
  • Define a default amount computation rule for each price component.
  • While working on a specific price breakdown, reuse the default computation rules defined before or override them.
  • Let SecuTix compute all the amounts for you according to previous computation rules.
  • Modify single amounts in the price breakdown, if needed.
• Use the price breakdown for almost every kind of prices (all product families for which a price is defined in the catalog, products within advantages or packages)
• Generate reports to get the revenue by price components

Price breakdown in practice

Whymper V2 will provide the new price breakdown for events as well as for events defined inside an advantage, a calculated price season ticket or a package.

You can define as many price components as you want:

A rate table may have zero, one or more price breakdowns. The first price breakdown created is the default one. Additional price breakdowns, valid for specific sales channels may be created:

Select the price components you want to use in your breakdown and, if necessary, override the default computation rule:

Click on the CALCULATE PRICE button:

If needed, you can handle exceptions by modifying some amounts in the detailed price breakdown above.

Information on data migration

Your catalog (pricing) data have been migrated to the new pricing model. Therefore, you can directly start working with this new feature. The old pricing model isn't available anymore (for the events). Depending on your pricing strategy, the number of rates table may increase for the following reasons:

• The price sub-grids are now handled as independent price grids. They will appear as such in the list of rates tables. The name of the rates table matches exactly the name of the price sub-grid.
• A new price grid is created for each performance with modified prices (storing all prices in a uniform way (the price grid) allows SecuTix to provide uniform features, like price breakdown, for all kinds of prices). The name of the price grid is defined as the concatenation of:
  • The name of the rates table containing the non modified prices
  • The code of the event
  • The date and time of the performance
• By this way, it is possible to find the performance (with modified price) for which this dedicated rates table is used, simply from its name.

Remarks:

• The list of rates table screen allows to filter out these dedicated rates table in order to display only "regular" rates table.
• If you have modified the price of multiple performances in the same way (example: reduce price for child tariff each Wednesday, without defining a separate rate type), a rate table will be created for each performance. You can (but don't have to) link all concerned performances to the same rate table and ignore the other ones.

More to come (next SecuTix releases)

Price refactoring

• Get rid of the rate type and define the prices of your exhibitions only once. The pricing of the timeslot and visit passes will not need rate types anymore. As for the events, the rate type may still be used in order to select a subset of timeslots, for example the list of timeslots on sale for a given pass within a package.. The pricing of the timeslot and visit passes will be based on reusable price grids. For example, if several exhibitions have the same price, you need to define the prices only once.
• Define simply the price of your advantage or package with a discount. Instead of setting up a complete price grid, define simply that the advantage (or the purchase within a given package) provides a rebate of 15%.

Price breakdeown

• Use the price breakdown for almost every kind of prices (all product families for which a price is defined in the catalog, products within advantages or packages)
• Apply price breakdown for some tariffs only. Add a "Tariff" filter to the screen displaying the detailed price breakdown. Define for which tariffs the breakdown applies or doesn't apply.
• Define minimum and maximum amount for each price component defined with a rate.
• Use price components to define external charges that come in addition to the catalogue price. Whymper V2 will provide price components that are included in the catalog price and their corresponding amounts are not displayed to the end customer. Later releases will provide components that are not included in the price and their corresponding amounts comes in addition to the catalog price. The operator may decide which components are showed to the end customer. These components, called outside price components, will replace the simple charges. Unlike the simple charges, it will be possible to define several outside price components for the same product. It will also be possible to define charges for some tariffs only.

See the replays of our webinars on this topic:

Replay - The new price management (English)

Replay - La nouvelle gestion des prix (Français)