...
If needed, you can handle exceptions by modifying some amounts in the detailed price breakdown above.
More to come
Price refactoring
- Get rid of the rate type and define the prices of your exhibitions only one. The pricing of the timeslot and visit passes won't 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 exhibition 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 breakdown
- Use the price breakdown for almost every kinds of prices (all product families for which a price is defined in the catalog, products within advantages or packages)
- Use price components to define external charges that come in addition to the catalog price. Whymper V2 will provide price components that are included in the catalog price and which amount isn't displayed to the end customer. Later releases will provide components which amount 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.